SQL> select status from dba_registry;
select status from dba_registry
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 12168
Session ID: 1 Serial number: 21
[oracle@test2 dbs]$ rman target sys/oracle@samp auxiliary sys/oracle@samt
Recovery Manager: Release 11.2.0.2.0 - Production on Sat Dec 1 17:51:06 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ORACLE error from target database:
ORA-03113: end-of-file on communication channel
Process ID: 8729
Session ID: 33 Serial number: 61
error executing package DBMS_RCVMAN in TARGET database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
Alert Log Errors:
Exception [type: SIGSEGV, Address not mapped to
object] [ADDR:0x74] [PC:0xFDF42B6, pevm_icd_call_common()+638] [flags:
0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/samp/samp/trace/samp_ora_11729.trc (incident=5797):
ORA-07445:
exception encountered: core dump [pevm_icd_call_common()+638] [SIGSEGV]
[ADDR:0x74] [PC:0xFDF42B6] [Address not mapped to object] []
ORA-04067: not executed, package body "GGS_OWNER.DDLREPLICATION" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "GGS_OWNER.DDLREPLICATION"
ORA-04067: not executed, package body "GGS_OWNER.DDLREPLICATION" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "GGS_OWNER.DDLREPLICATION"
Incident details in: /u01/app/oracle/diag/rdbms/samp/samp/incident/incdir_5797/samp_ora_11729_i5797.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
2012-12-01 18:07:30.908000 +05:30
Dumping diagnostic data in directory=[cdmp_20121201180730], requested by (instance=1, osid=11729), summary=[incident=5797].
Workaround:
1.Startup database in upgrade mode "startup upgrade"
2.Then run catalog & catproc