Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

registering a 10g database to an 11g catalog database hangs at resync

993419Feb 26 2013 — edited Feb 26 2013
I have a problem in which I try to migrate a 10g database to use a new recovery catalog database, 11g. I connect to target and catalog but after issuing register database it hangs as follows:


server123:oracle 1> rman target / catalog catuser/catpw@CATALOG456

Recovery Manager: Release 10.2.0.2.0 - Production on Tue Feb 26 13:23:11 2013

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: TRGT (DBID=823102274)
connected to recovery catalog database

RMAN> register database;

database registered in recovery catalog
starting full resync of recovery catalog

[[--hangs here (have let it try to do the resync for +3 hours)--]]


When I look from the recovery catalog I see it can connect to it:

SQL> r
1 SELECT s.inst_id,
2 s.sid,
3 s.serial#,
4 p.spid,
5 s.username,
6 s.program
7 FROM gv$session s
8 JOIN gv$process p ON p.addr = s.paddr AND p.inst_id = s.inst_id
9* WHERE s.type != 'BACKGROUND'

INST_ID SID SERIAL# SPID USERNAME PROGRAM
---------- ---------- ---------- ---------- ---------- ---------------------------------------------
1 126 19297 6229 catuser rman@server123 (TNS V1-V3)



However, from v$session_wait I can see it is idling:

SQL> select sid,wait_class,seconds_in_wait,wait_time,state,event from v$session_wait where SID = '126';

SID WAIT_CLASS SECONDS_IN_WAIT
---------- ---------------------------------------------------------------- ---------------
WAIT_TIME STATE EVENT
---------- ------------------- ----------------------------------------------------------------
126 Idle 507
0 WAITING SQL*Net message from client





Theres plenty of space left in datafiles in the recovery catalog database. The target is 10g

SQL> select * from v$version;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bi
PL/SQL Release 10.2.0.2.0 - Production
CORE 10.2.0.2.0 Production
TNS for HPUX: Version 10.2.0.2.0 - Production
NLSRTL Version 10.2.0.2.0 - Production

and the recovery catalog is 11g

SQL> select * from v$version;

BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production



There are many other databases registered to that recovery catalog database, 10g's and 11g's. I can connect from the recovery catalog database server to the target database server, even using sqlplus. I have done crosschecks and delete expired archivelogs/backups/copies while connected only to target.

I didn't find anything relating to this except this but its about 10g/10g setup and in 11g the indexes are in place: http://pythianpang.wordpress.com/2010/07/29/rman-resync-catalog-hang-10g-workaround/

Any thoughts?
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 26 2013
Added on Feb 26 2013
2 comments
2,369 views