Toad World® Forums

Earliest Toad version to support Oracle 11g

Hi!

We will be soon migrating databases from Oracle 10g to 11g. There are different versions of Toad being used in the team in function of the acquisitions we made. My question is therefore:

What is the minimum version of Toad REQUIRED to connect to Oracle 11g and be able to do usual developers operations: select, … compile packages, …?

In some places (http://old.nabble.com/Oracle-11g-td14686864.html), I find that version 9.5 is the minimum and in the following, I understand that any version will do as far as your SQL*net client is on par with the DB version: http://asktoad.com/DWiki/doku.php/faq/answers/database_versions#what_version_oracle_database_servers_does_toad_support

Thank you in advance for clarifying this to me!

Patrick

To me the main issue is passwords: Oracle 11g has default that passwords are now
case sensitive. Older versions of Toad (pre-11) all basically raised all
passwords before sending to database – so you will get error saying cannot
connect. That to me is reason enough to require toad >= 11 for oracle >=
11g

So, IIUC, we could just pay attention to capitalize all our passwords when migrating to Oracle 11g, communicate it through the team, and this should be a non issue.

On 15/02/12 16:56, Patrick wrote:

So, IIUC, we could just pay attention to capitalize all our passwords
when migrating to Oracle 11g, communicate it through the team, and this
should be a non issue.

You could set the initialisation parameter SEC_CASE_SENSITIVE_LOGON =
false to get around the problem. However, that would reduce the security
of the database a tad.

Other things to watch for in a default 11g database are:

  • The default profile limits password life time to 180 days then you
    have to change it.

  • the initialisation parameter (in Enterprise Edition)
    CONTROL_MANAGEMENT_PACK_ACCESS defaults to allowing use of the tuning
    and/or performance packs even if they are not licensed. Set this to NONE
    if you don’t have those licenses.

The first is a PITA the second could allow Oracle to sue you. Nice defaults!


Cheers,
Norm. [TeamT]

Hi!

Thank you for those useful tips!

But… My original question remains. Can anybody confirm my assumptions?

TIA!

Patrick

I have reread the emails and the best answer was given by Bert Scalzo: Toad 11.
If you are only interested in queries and compilations, I think a lot of toad
versions qualify, but you can get into some problems as described. I would say,
use at least version 9? But forget about the DBA options and other interesting
stuff that Toad delivers.

If you are only interested in querying and compilation, you could switch to the
free product of Oracle itself. SQL Developer. There is a nice discussion going
on just now on this forum about the differences betweed Toad and SQLdeveloper.
Groetjes,
Wim

2012/3/1 Patrick

Message from: patriiiiiiiiiick

Hi!

Thank you for those useful tips!

But... My original question remains. Can anybody confirm my assumptions?

TIA!

Patrick

Historical Messages

Author: Patrick
Date: Thu Mar 01 01:38:14 PST 2012
Hi!

Thank you for those useful tips!

But... My original question remains. Can anybody confirm my assumptions?

TIA!

Patrick

__

Author: Norman Dunbar
Date: Wed Feb 15 08:56:16 PST 2012
On 15/02/12 16:56, Patrick wrote: > So, IIUC, we could just pay attention
to capitalize all our passwords > when migrating to Oracle 11g,
communicate it through the team, and this > should be a non issue. You
could set the initialisation parameter SEC_CASE_SENSITIVE_LOGON = false to
get around the problem. However, that would reduce the security of the
database a tad. Other things to watch for in a default 11g database are: *
The default profile limits password life time to 180 days then you have to
change it. * the initialisation parameter (in Enterprise Edition)
CONTROL_MANAGEMENT_PACK_ACCESS defaults to allowing use of the tuning and/or
performance packs even if they are not licensed. Set this to NONE if you
don't have those licenses. The first is a PITA the second could allow
Oracle to sue you. Nice defaults! -- Cheers, Norm. [TeamT]
__

Author: Patrick
Date: Wed Feb 15 08:56:16 PST 2012
So, IIUC, we could just pay attention to capitalize all our passwords when
migrating to Oracle 11g, communicate it through the team, and this should be
a non issue.

__

Author: Bert Scalzo
Date: Wed Feb 15 08:17:51 PST 2012
To me the main issue is passwords: Oracle 11g has default that passwords are
now case sensitive. Older versions of Toad (pre-11) all basically raised all
passwords before sending to database – so you will get error saying cannot
connect. That to me is reason enough to require toad >= 11 for oracle >= 11g

__

Author: Patrick
Date: Wed Feb 15 08:06:09 PST 2012
Hi!

We will be soon migrating databases from Oracle 10g to 11g. There are
different versions of Toad being used in the team in function of the
acquisitions we made. My question is therefore:

What is the minimum version of Toad REQUIRED to connect to Oracle 11g and be
able to do usual developers operations: select, ... compile packages, ...?

In some places ( http://old.nabble.com/Oracle-11g-td14686864.html ), I find
that version 9.5 is the minimum and in the following, I understand that any
version will do as far as your SQL*net client is on par with the DB version:
http://asktoad.com/DWiki/doku.php/faq/answers/database_versions#what_version_
oracle_database_servers_does_toad_support

Thank you in advance for clarifying this to me!

Patrick

__
_______________________________________

Toad 10.1 (Q4-09) officially states support for Oracle 11g R2 (Q3-09). But there
were changes in 11g R2 that evolved on the Oracle side after initial release so
I would advise strongly Toad >= 10.5.

Yes – I double checked and could see going one major release earlier (i.e.
10.5). But then you lose multi-byte/Unicode support – and since the
default for databases is now Unicode, I still think 11.0 is the real and best
answer. But this user seems far more interested in how far back can I go than
issues like what’s recommended – just what can I get away with. So
10.5 in that case ……

Wim … the speed issue will probably not make today’s Beta, I will
have it in for Monday

lle