# TOAD Beta 13.0.0.60 new Bug pop-up error message- Invalid release: ""

**URL:** <https://forums.toadworld.com/t/toad-beta-13-0-0-60-new-bug-pop-up-error-message-invalid-release/40687>\
**Category:** Toad for Oracle - Beta\
**Created:** [March 9, 2018, 8:30am UTC](https://forums.toadworld.com/t/toad-beta-13-0-0-60-new-bug-pop-up-error-message-invalid-release/40687 "2018-03-09T08:30:43Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![mstaszew](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/mstaszew/32/23_2.png) [@mstaszew](https://forums.toadworld.com/u/mstaszew)\
**Post date:** [December 5, 2019, 7:28pm UTC](https://forums.toadworld.com/t/toad-beta-13-0-0-60-new-bug-pop-up-error-message-invalid-release/40687/9 "2019-12-05T19:28:48Z")

</div>

See this thread... [Toad 13.1.1.5 with Oracle 19.0.0.0.0 issue](https://forums.toadworld.com/t/toad-13-1-1-5-with-oracle-19-0-0-0-0-issue/48233)

Is your Oracle compatible parameter set to "12.2.0." ? If so follow the resolution steps in the other thread. There is a regular expression that validates the Oracle release version of both your database and its compatible setting and a release string with a trailing period like that is not handled. I will look at the regex and see how to enable it to be more flexible while remaining useful for its intended purpose.

---

_[View the full topic](https://forums.toadworld.com/t/toad-beta-13-0-0-60-new-bug-pop-up-error-message-invalid-release/40687)._
