Thanks heaps, Mark. I'm aware of the differences you mentioned, we have some dbs in 11r1 and those were ironed out a while ago. I'm more interested in the so-called "gotchas". Like the resource manager being left on by default in r2 and other such. As well as any known bugs that may have affected other's upgrades. Been reading the patch bug fixes and those are always very helpful. But nothing replaces talking to the "coal face" folks. We don't use RAC or ASM so we are more or less shielded from the problems associated with those. But we do use roles and login triggers extensively to control access and environment for multiple applications in same db. And PL/SQL to a great extent. As well as standby, via SAN replication. Ah yes: we're on IBM's AIX, power6.
-- Cheers Nuno Souto in cold Sydney, Australia dbvision@xxxxxxxxxxxx Mark W. Farnham wrote,on my timestamp of 3/07/2010 12:21 PM:
Non-exhaustive list starter: 1) case sensitivity of passwords (which you can switch off, but which is on by default, may wreak havoc if you have passwords laying around encrypted somewhere lowercase for programs to pick up or in root guarded scripts but the real existing passwords are really uppercase unless someone defined them with surrounding quotes. Now it matters what you toss at the login software. 2) changes (many permissions removed) for the connect privilege. They have provided stuff to handle it and recommendations about it, but you need to notice that you probably need to do something. I think the new defaults are improvements to security, but there is work for you to do to make your existing least privileged existing connectors able to do about anything. y'all chime in.
-- //www.freelists.org/webpage/oracle-l
