When a datafile has been configured such that it will autoextend onto a 4GB boundary, any attempt to autoextend the file causes the file the database to crash (when in noarchive log mode). If the database was in archive log mode,will be marked offline recover and access to the database continues.
This bug is fixed in 9203. Upgrading the database to the latest relase followed by a recovery will solve this problem.
Here are the steps:
1.Do a clean shutdown of the database
2. Upgrade the database to the latest version ( greater than 9.2.0.3) as this bug is fixed in 9203.
If the database version is below 9i Rel 2(9.2.0.1) then first upgrade to 9iRel2 and then apply the
latest available patchset.
Kindly check metalink for the latest patchset available
3.Mount the database
4.Do a COMPLTE recovery of the dataabse
5.Then start the database in migrate mode and upgrade the database.
Refer Note 159657.1: Complete Upgrade Checklist for Manual Upgrades from 8.X / 9.0.1 to Oracle9i
我的操作:
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/5359/viewspace-620506/ ,如需转载,请注明出处,否则将追究法律责任。