topic Re: HELP - database in limbo in Operating System - HP-UX

HELP - database in limbo

Dave Chamberlin — Thu, 12 Jan 2006 11:33:58 GMT

Hello,
I am doing a migration of Oracle from 8.1.7.4 (64bit) to 9i. When I did startup migrate, one datafile had wrong permission set. Database shutdown. I fixed the permission of that file, but cannot startup the database under the 9i HOME(ORA-1092 instance terminated..)
I cannot open the database under the 8.1.7 HOME because the redo logs are now in 9i format. What can I do?

Re: HELP - database in limbo

Steven E. Protter — Thu, 12 Jan 2006 11:46:45 GMT

Shalom Dave,

I suggest retoring the database files to the original copies and re-doing the migration after correcting the permissions.

You also might be able to do a startup, followed by an abort and then a normal startup.

Can you do a startup attempt and post the sqlplus output? There may be commands you can do to bring this one tablespace up.

SEP

Re: HELP - database in limbo

Dave Chamberlin — Thu, 12 Jan 2006 12:02:45 GMT

Unfortunately I cannot replace original files as my new ultrium tape drive failed last night (as I was going to take a backup). I am attaching the output of the log file (9i alert log).

Re: HELP - database in limbo

Peter Godron — Thu, 12 Jan 2006 12:18:04 GMT

Dave,
given your situation (no backups) I would raise a TAR with Oracle.
One further mistake and the whole DB may be lost.
At least perform a backup now, so if anything goes wrong, you have something to go back to.

Re: HELP - database in limbo

A. Clay Stephenson — Thu, 12 Jan 2006 12:24:09 GMT

Dave,

Let me understand this. You decided to do a database migration after a failed backup? and without a working tape drive? That was truly state of the art stupid and you deserve whatever happens to you. Never underestimate God's sense of humor. If you have good backups, you don't need them; on the other hand, if you don't have good backups ...

You may be out of limbo and are now in purgatory. I hope you are on Oracle support; they may be able to help. Please tell me that you have a backup from two days ago.

Re: HELP - database in limbo

Dave Chamberlin — Thu, 12 Jan 2006 12:57:53 GMT

Thanks Clay. This is not a production database and I intended to have a backup before procedding, but felt pressured to start this upgrade test (since replacing the tape drive will take at least a couple of days. Can the database be restarted as the 8.1.7 database with a reset of the redo logs?

Re: HELP - database in limbo

Patti Johnson — Thu, 12 Jan 2006 16:14:15 GMT

Dave,

Did you see note 267118.1 in Metalink, basically it says the problem is the compatibility parameter at 9.2 while db at 8.1.7, but changing back to 8.1.7 causes another problem. Here is the solution from the note.

Solution
To resolve this problem we need to migrate the database so that the redo logs are in the correct format:

Startup migrate;
Database opened

The migration to 9.2 was completed manually.

Just a thought.

Patti

Re: HELP - database in limbo

Dave Chamberlin — Thu, 12 Jan 2006 17:24:02 GMT

The problem as indicated from Oracle was the same as Patti indicated. The compatible parm was set to 9.2 in the init file. Edited the init file to have "EVENT=10619 trace name context forever, level 1 allowed the instance to open correctly ignoring the compatable flag, and migration proceeded normally. Thanks.

Re: HELP - database in limbo

Yogeeraj_1 — Thu, 12 Jan 2006 23:49:48 GMT

hi,

Can you investigate if you can offiline drop the datafile which you were having problems and create it again and import the data?

It would also be advisable to work with Oracle Support on that!

good luck

kind regards
yogeeraj

Re: HELP - database in limbo

VikramAdmin — Tue, 11 Apr 2006 03:12:04 GMT

Thats a DB question.
Did you check if there is any information in the traces/logs? Is there more error message information that can be used here?

I remember one Oracle DBA telling me that he had to comment out rollback parameters when he did the first restart.

Re: HELP - database in limbo

Dave Chamberlin — Tue, 11 Apr 2006 10:08:10 GMT

problem was solved with compatability setting in init file. thanks.