| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Patch 8.1.6.1 -> 8.1.6.3 - any problems?
hi ... i upgraded to 8.1.6.3 ... to correct a problem with RMAN ... it fixed
the problem and there appears to be no problems whatsoever ... it's been up
and running for > 1month ...
HTH
thank you ...
nechama glasrot
561-981-0635
nglasrot_at_edata.com
-----Original Message-----
From: jared still [mailto:jkstill_at_teleport.com]
Sent: Thursday, December 28, 2000 11:02 AM
To: ORACLE-L_at_fatcity.com; oracledba_at_quickdoc.co.uk
Subject: Patch 8.1.6.1 -> 8.1.6.3 - any problems?
Hi all,
We have a database here that is at version 8.1.6.1.
Have any of you experienced problems in upgrading from 8.1.6.1 to 8.1.6.3?
The problem we have is that this database is used in production, and for some strange reason, there is no corresponding development or test databases. ( I've only been here a month, gimme a break! :)
We are hesitant to upgrade until we feel some level of confidence in going to 8.1.6.3.
Among the version specific problems it has: ( written up by a fellow DBA )
Histograms (analyze column) on partition tables with any empty partitions causes the optimizer to crash on any query for the affected table. Workaround is to drop statistics and rebuild them without using histograms.
Problem caused by Bug # 962964 which is fixed in 8.1.6.2 (or 8.1.7).
Rebuild partitioned index (happened on more than one index build) in parallel mode crashed about 3/4 of the way through with ORA-12801 and ORA-27062 errors. The analyst handling this strongly suggested upgrading to 8.1.6.3 because of multiple bugs in the Parallel Query Option -- he included a list of about 30 PQO bugs, none of them an exact match with my problem. Pull up the TAR if you want to review this. Workaround was to drop the PARALLEL clause on the index builds.
Weekly structure only exp has been failing with ORA 1000 (too many open cursors). I looked this up on Metalink and got an exact hit in a Forum thread. Apparently, this is caused by Bug # 1244182 and occurs on full exports of databases that use locally managed tablespaces. The problem is supposedly fixed in 8.1.6.3 but may need an additional patch also. Workaround is to increase the open_cursors parameter to a larger value (I suppose I could open a TAR to get something a bit more specific than "larger").
Thanks,
Jared Still
Certified Oracle DBA and Part Time Perl Evangelist ;)
jkstill_at_teleport.com
jared_still_at_enron.net
 |
 |