Hello,
I previously updated 2 databases that are part of a Dataguard configuration (no broker), from 11.2.0.1 to 11.2.0.2 on Linux x86_64.
They work ok with tested shipping and switchover operations.
Then I updated my recovery catalog, again from 11.2.0.1 to 11.2.0.2, and again on Linux x86_64.
It seems I have now some problems with backup on standby (JDE9DR) that are caused by db_unique_name case....
On primary
SQL> select name,db_unique_name from v$database;
NAME DB_UNIQUE_NAME
--------- ------------------------------
JDE9 jde9
On standby:
SQL> select name,db_unique_name from v$database;
NAME DB_UNIQUE_NAME
--------- ------------------------------
JDE9 jde9dr
After Oracle upgrade on catalog server, I upgraded the catalog itself, after issuing 2 times:
upgrade catalog;
and after patching the recover.bsq file due to a bug in 11.2.0.2.
The diff with the original recover.bsq in admin directory is:
[oracle@lb-orajde admin]$ diff recover.bsq recover.bsq.orig
65550,65551c65550,65551
< tf_key in (select tf_key from tf, dbinc
< where dbinc.dbinc_key = tf.dbinc_key
---
tf_key in (select tf_key from df, dbinc
where dbinc.dbinc_key = df.dbinc_key
RMAN> upgrade catalog;
recovery catalog upgraded to version 11.02.00.02
DBMS_RCVMAN package upgraded to version 11.02.00.02
DBMS_RCVCAT package upgraded to version 11.02.00.02
resync catalog commands from primary and standby are ok.
so far so good.
But now I get this trying to do a full resync for all db_unique_db (I admit probably I didn't run this when in 11.2.0.1, perhaps...)
it is the same from which db I run it (after a switch over), so it is specular...
Example. jde9dr is primary now and jde9 is standby
rman against jde9dr
RMAN> RESYNC CATALOG FROM DB_UNIQUE_NAME all;
starting full resync of recovery catalog
full resync complete
resyncing from database with DB_UNIQUE_NAME JDE9
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of resync from db_unique_name command at 11/24/2010 14:49:01
ORA-17629: Cannot connect to the remote database server
ORA-17628: Oracle error 17629 returned by remote Oracle server
In alert.log of remote (so jde9 DB) I get:
Wed Nov 24 14:49:36 2010
Errors in file /app/oracle/diag/rdbms/jde9/jde9/trace/jde9_ora_25738.trc:
ORA-17627:
ORA-17629: Cannot connect to the remote database server
Errors in file /app/oracle/diag/rdbms/jde9/jde9/trace/jde9_ora_25738.trc:
ORA-17629: Cannot connect to the remote database server
ORA-17627:
ORA-17629: Cannot connect to the remote database server
In trace file there is:
krbmsrvgrcf:Expected db_unique_name: JDE9
krbmsrvgrcf:mydbuname = :jde9:
krbmsrvgrcf:Instance with connect id JDE9DR requested controlfile.
krbmsrvgrcf:Filespec: /app/oracle/product/11.2.0/dbhome_2/dbs/snapcf_jde9dr.f
So it seems that rman asks for JDE9 instead of jde9....
I also tried to reset the configuration of connection but without luck....
Any tip?
Could this be an effect of upgrade and something changed in caseness between 11.2.01. and 11.2.0.2?
Gianluca