ORA-17629, ORA-17628 DURING RESYNC CATALOG FROM DB_UNIQUE_NAME ALL;
(Doc ID 1421065.1)
Last updated on MARCH 14, 2023
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Database - Enterprise Edition - Version 11.2.0.2 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Not able to get RESYNC CATALOG FROM DB_UNIQUE_NAME ALL; to work.
The resync fails from either the primary or the standby database
Primary:
$ rman target / catalog <catalog schema>/<password>@<catalog service>
Recovery Manager: Release 11.2.0.2.0 - Production on Mon Jan 9 15:59:32 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: <DB_NAME>(DBID=1587204231)
connected to recovery catalog database
RMAN> resync catalog from db_unique_name all;
starting full resync of recovery catalog
full resync complete
resyncing from database with DB_UNIQUE_NAME <db_unique_name>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of resync from db_unique_name command at 01/09/2012 15:59:56
ORA-17629: Cannot connect to the remote database server
ORA-17628: Oracle error 17629 returned by remote Oracle server
Recovery Manager: Release 11.2.0.2.0 - Production on Mon Jan 9 15:59:32 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: <DB_NAME>(DBID=1587204231)
connected to recovery catalog database
RMAN> resync catalog from db_unique_name all;
starting full resync of recovery catalog
full resync complete
resyncing from database with DB_UNIQUE_NAME <db_unique_name>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of resync from db_unique_name command at 01/09/2012 15:59:56
ORA-17629: Cannot connect to the remote database server
ORA-17628: Oracle error 17629 returned by remote Oracle server
Standby:
$ rman target / catalog <catalog schema>/<password>@<catalog service>
Recovery Manager: Release 11.2.0.2.0 - Production on Mon Jan 9 16:00:13 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: <DB_NAME>(DBID=1587204231)
connected to recovery catalog database
RMAN> resync catalog from db_unique_name all;
resyncing from database with DB_UNIQUE_NAME <db_unique_name>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of resync from db_unique_name command at 01/09/2012 16:00:30
ORA-17629: Cannot connect to the remote database server
ORA-17628: Oracle error 17629 returned by remote Oracle server
Recovery Manager: Release 11.2.0.2.0 - Production on Mon Jan 9 16:00:13 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: <DB_NAME>(DBID=1587204231)
connected to recovery catalog database
RMAN> resync catalog from db_unique_name all;
resyncing from database with DB_UNIQUE_NAME <db_unique_name>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of resync from db_unique_name command at 01/09/2012 16:00:30
ORA-17629: Cannot connect to the remote database server
ORA-17628: Oracle error 17629 returned by remote Oracle server
sqlplus connections work between all three database instances: primary,
standby, recovery catalog
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |