Dear group,

We are moving our Oracle database on redhat 4 10.2.0.4 to redhat 5 and
upgrade it to 10.2.0.5

so, on server A(redhat 4), i took a hot backup using RMAN, 10.2.0.4

on server B, (redhat 5), i installed 10.2.0.5, i can restore and
recover the database without problem. But i cannot start the
database. I tried

alter database open resetlogs;
alter database open upgrade resetlogs;
alter database open upgrade;

None of them seems working. Could somebody help me out?

Thanks very much for your help

On Feb 3, 5:48*pm, charles <dshprope... (AT) gmail (DOT) com> wrote:
Why don't you give us exactly the sequence of actions you performed
with all the complete details ...

Typically you do a recover database until cancel using backup
controlfile then eventually cancel the recovery ... then alter
database open resetlogs ... I find it is much less buggy doing stuff
like this in sqlplus than in rman personally.

What happens on the open resetlogs? Sometimes it takes a very long
time to complete that and you have to wait it out ...

On Feb 3, 5:48*pm, charles <dshprope... (AT) gmail (DOT) com> wrote:
When asking a "what's wrong" question, it is customary to include
error messages with EXACT commands issued. Without the error codes
and state of your db, the answer to your problem is purple.

The restore and recover finished fine, but i just cannot open it to
apply the script

RMAN> alter database open resetlogs upgrade;

RMAN-00571:
================================================== =========
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
================================================== =========
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "upgrade": expecting one of: ";"
RMAN-01007: at line 1 column 31 file: standard input

RMAN-00571:
================================================== =========
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
================================================== =========
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate,
alter, backup, beginline, blockrecover, catalog, change, connect,
copy, convert, create, crosscheck, configure, duplicate, debug,
delete, drop, exit, endinline, flashback, host, {, library, list,
mount, open, print, quit, recover, register, release, replace, report,
renormalize, reset, restore, resync, rman, run, rpctest, set,
setlimit, sql, switch, spool, startup, shutdown, send, show, test,
transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 38 file: standard input

RMAN> alter database open upgrade resetlogs;

RMAN-00571:
================================================== =========
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
================================================== =========
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "upgrade": expecting one of:
"resetlogs, ;"
RMAN-01007: at line 1 column 21 file: standard input

RMAN> alter database open upgrade;

RMAN-00571:
================================================== =========
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
================================================== =========
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "upgrade": expecting one of:
"resetlogs, ;"
RMAN-01007: at line 1 column 21 file: standard input

RMAN-00571:
================================================== =========
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
================================================== =========
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate,
alter, backup, beginline, blockrecover, catalog, change, connect,
copy, convert, create, crosscheck, configure, duplicate, debug,
delete, drop, exit, endinline, flashback, host, {, library, list,
mount, open, print, quit, recover, register, release, replace, report,
renormalize, reset, restore, resync, rman, run, rpctest, set,
setlimit, sql, switch, spool, startup, shutdown, send, show, test,
transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 28 file: standard input

RMAN> alter database open resetlogs;

RMAN-00571:
================================================== =========
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
================================================== =========
RMAN-03002: failure of alter db command at 02/03/2011 20:08:58
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
RMAN-00571:
================================================== =========
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
================================================== =========
ORA-03114: not connected to ORACLE
RMAN-00571:
================================================== =========
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
================================================== =========
RMAN-03002: failure of alter db command at 02/03/2011 20:08:58
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option

On Feb 4, 1:09*am, charles <dshprope... (AT) gmail (DOT) com> wrote:

What documentation are you following?

-g

On Thu, 03 Feb 2011 17:09:29 -0800, charles wrote:

I don't think you can specify upgrade in RMAN. Also, I am not sure that
you can specify it at the same time as "resetlogs".



--
http://mgogala.byethost5.com

On Feb 3, 5:48*pm, charles <dshprope... (AT) gmail (DOT) com> wrote:
separate your steps.
If you performed a cold backup using rman whereby the online redo logs
would be moved over as well, no recovery would be required.
Why not just perform a manual cold backup and move that backup set?
Using a cold backup set (with a clean shutdown) no recovery is
required and you can go straight into upgrading the catalog, e.g.

( from a 10.2.0.5 home on the new server)

cd $ORACLE_HOME/rdbms/admin
sqlplus / as sysdba
startup upgrade
@catupgrd.sql;
shutdown immediate
startup
@utlrp.sql;
alter system set compatible='10.2.0.5.0' scope=spfile -- or make the
change in the pfile and create a new spfile if you wish.
shutdown immediate
startup

check your invalids and apply whatever patch set update you feel is
appropriate (or not).


By using a backup method that requires recovery to be made consistent,
you can't change the catalog in that same step.
open database set restored - needs to be recovered on that version.
After its brought to be consistent - and opened resetlogs, it can be
cleanly shutdown and opened upgrade in order to upgrade the catalog to
the new patchset.

but you could have found out all of this info from the upgrade guides.

-bdbafh