DISCLAIMER: The information and links provided on this site are my personal notes, based on my limited experience installing, using, and deinstalling Oracle databases and application servers on a variety of computers using Windows NT/2000/XP operating systems. The installation and deinstallation procedures found here can cause irreversable loss of data and may damage your operating system. However, you are welcome to use them AT YOUR OWN RISK. I am in no way responsible for data you lose or operating systems you damage or destroy.
PROBLEM: After upgrading a 9.0.1.5 database to 9.2.0.6 with the Oracle Database Upgrade Assistant on a Windows 2000 Server operating system, the database failed to mount and start when the Windows Service was started. This was an issue because the database was used as a metadata repository for an OracleAS 10g (9.0.4.2) Infrastructure. In case of a system re-boot, the database had to be manually started using SQL*Plus. This was not only inconvenient, but in the case of our customer it meant the middle-tier application servers would be unavailable until the metadata repository was restarted. The customer does not employ a full-time DBA, so there was great risk of large amounts of down-time.
SOLUTION: I requested assistance on the Oracle Technology Network (OTN) Database forum and I'm happy to say it was solved quickly by two expert DBAs in France. In short, the Database Upgrade Assistant, for whatever reason, failed to update the 'Compatible' system parameter contained in the database's spfile and pfile. The steps required to update this parameter follow:
Now when the Windows service for the Oracle instance starts, the database will mount and open.
The forum thread can be viewed at:
http://forums.oracle.com/forums/message.jspa?messageID=1128824#1128824