From: Jeffrey_Hummel@albemarle.com
Date: Mon Apr 29 2002 - 14:03:49 EDT
Original Question:
Has anybody ever resolved an Oracle Migration Assistant error ORA-01219?
Answer:
If you are in the process of upgrading to Oracle 8.1.7.x, make sure to
rename the bin and lib directories for the previous version before starting
the migration assistant or 8.1.7 for the first time.
In my case a well-intentioned operator (in another room) kicked off a
backup job that started the database (v8.0.6 - the program logs what is
backed up and the status) after the database had already been started by
the migration assistant. This left two instances of Oracle executables
accessing the same datafiles and controlfiles simultaneously. This lead
first to an Ora-600 by the 8.0.6 archive process and later updates to the
header structures of the datafiles by 8.0.6 forced 8.1.7 to report errors
ora-904 and ora-604. The only solution is to restore from backup and try
again.
Two precautions:
1. empty the cron schedule for all accounts that call Oracle. Do not rely
upon Cron's allow and deny security. During one test we found that
although the security was correctly configured, the cron jobs continued to
be spawned.
2. rename the lib and bin directories or the Oracle home directory to
prevent well-intentioned accidents or old forgotten scripts from resulting
in two different versions of Oracle executables being loaded.
Many thanks go to the guidance I received from Raul Sossa, Andy Cohen, and
Martin Vasas.
Jeff
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:39 EDT