that only happenes with versions <= 188.8.131.52, you should have 184.108.40.206 anyways
Originally posted by Akila
if u r running 220.127.116.11 then its a bug
the metalink suggest to set the parameter _db_handles_cached=0
It is 18.104.22.168 - the contractor installed only to here from some emergency disks. the plan is to upgrade to 9.2+ asap.
Question about the error messages: I've been told by a consultant that this type of message SHOULD NOT appear in the alert log as its a client side error? Doesn't sit easily with me that one. Any comments.
Did u set the parameter _db_handles_cached=0 ? any results for that.
Doing that today. Will check the effectiveness tomorrow.
I know you've probably called the consultants everything in the book by now but just out of curiosity would it be possible instead of upgrading to do a fresh install of 22.214.171.124 and just import the schemas? Based on the assumption that the database isn't all that big?
I've got a database that was upgraded from 8.1.6 to 126.96.36.199 to 188.8.131.52 and I've had nothing but problems with it. It's 75 gigs and I'm going to take a weekend here sometime and do a fresh install of 184.108.40.206 and import the schemas. I still have dictionary managed tablespaces for christs sake!
shawd up! Davey I don't want to hear it
Oracle it's not just a database it's a lifestyle!
BTW....You need to get a girlfriend who's last name isn't .jpg
I'd feel more comfortable doing that anyway Doc. I have 3 Oracle Homes now and 1 Db at 220.127.116.11 and 1 Db at 18.104.22.168. I believe that the 22.214.171.124 one was a fresh install and an import whilst the 8.1.7 one was an 8.1.5-8.1.7 upgrade.
Click Here to Expand Forum to Full Width