'Dbua Thinks This Is A Rerun Operation''

[tekpr00]

Hello,

I have four databases on the same server, after patching my $ORACLE_HOME, I was able to upgrade 2 of the databases using the same $ORACLE_HOME.

however, I cannot update the other 2 as it is erorring out with:
"DBUA thinks this is a Rerun operation and is trying to
connect to the database with the oracle home
<full path of $ORACLE_HOME>. If you believe this is
not a Rerun operation, remove the below file and invoke
DBUA again.
<full path to $ORACLE_HOME>/cfgtoollogs/dbua/logs/Welcome_<$ORACLE_SID>.txt"

The problem is there is no file Welcome_<$ORACLE_SID>.txt anywhere.

I have deleted the upgrade folder many times.

I have also started the database in startup upgrade mode. According to Metalink

Please help and thnks

PS: I am using the same oratab file for all the four databases, yet 2 are upgraded while the other 2 are erroring out.

 

[Turkbear]

Hi,
The replies in this forum:

http://forums.oracle.com/forums/thread.jspa?threadID=656705&start=0&tstart=0

mention a preference for manual upgrade rather then using DBUA..Maybe a try with that approach may work..It seems DBUA faiures can leave the database in a odd state..





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[tekpr00]

Here is the manual upgrade steps that I copied from BaBu's blog.

Upgrade the Database

After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home:

1. Start all services

2. Connect sys user

C:\> sqlplus /NOLOG

SQL> CONNECT SYS/pass_word AS SYSDBA

3. Enter the following SQL*Plus commands:

SQL> STARTUP UPGRADE

SQL> SPOOL patch.log

SQL> @$ORACLE_HOME\rdbms\admin\catupgrd.sql

SQL> SPOOL OFF

Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script.

This list provides the version and status of each SERVER component in the database.
If necessary, rerun the catupgrd.sql script after correcting any problems.

4. Restart the database:

SQL> SHUTDOWN
SQL> STARTUP

5. Compile Invalid Objects

Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
SQL> @$ORACLE_HOME\rdbms\admin\utlrp.sql

SQL> select * from v$version;

BANNER