# Toad 13.1.1.5 with Oracle 19.0.0.0.0 issue

**URL:** <https://forums.toadworld.com/t/toad-13-1-1-5-with-oracle-19-0-0-0-0-issue/48233>\
**Category:** Toad for Oracle & DevOps Toolkit\
**Created:** [November 21, 2019, 2:13pm UTC](https://forums.toadworld.com/t/toad-13-1-1-5-with-oracle-19-0-0-0-0-issue/48233 "2019-11-21T14:13:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikael.hedlund](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@mikael.hedlund](https://forums.toadworld.com/u/mikael.hedlund)\
**Post date:** [November 21, 2019, 2:13pm UTC](https://forums.toadworld.com/t/toad-13-1-1-5-with-oracle-19-0-0-0-0-issue/48233/1 "2019-11-21T14:13:43Z")

</div>

I'm trying to work with a brand new 19c server. When logging in from TOAD 13.1.1.5 I get a pop-up "Invalid release 19.3.0". It seems to be working to some point but I have issues with Schemabrowser Users section saing "Table not found" errors.

Is the combination TOAD 13.1.1.5 - ORACLE 19.0.0.0.0 - Client 12.1.0.2 supported?

---

<div class="post-metadata">

**Author:** ![JohnDorlon](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/johndorlon/32/9997_2.png) [@JohnDorlon](https://forums.toadworld.com/u/JohnDorlon)\
**Post date:** [November 21, 2019, 2:23pm UTC](https://forums.toadworld.com/t/toad-13-1-1-5-with-oracle-19-0-0-0-0-issue/48233/2 "2019-11-21T14:23:23Z")

</div>

I've used Toad 13.1 w/Oracle 19c without problems. Can you post a screen shot of the "invalid release" message, and turn on spool SQL to show the query for the "table not found" error?

---

<div class="post-metadata">

**Author:** ![mikael.hedlund](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@mikael.hedlund](https://forums.toadworld.com/u/mikael.hedlund)\
**Post date:** [November 21, 2019, 3:22pm UTC](https://forums.toadworld.com/t/toad-13-1-1-5-with-oracle-19-0-0-0-0-issue/48233/3 "2019-11-21T15:22:26Z")

</div>

Problem solved: Oracle parameter "compatible" needs to be set to "19.3.0.0.0"  
In our case it was "19.3.0." thus the popup
