oracle-dba-solution

1-i was asked for incomplete rman restore , after the restore and recovery ,i tried to open the db restore logs, the instance crashed with the following errors:

RMAN> run {alter database open resetlogs; }

using target database control file instead of recovery catalog

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-00601: fatal error in recovery manager

RMAN-03004: fatal error during execution of command

ORA-03114: not connected to ORACLE

RMAN-03002: failure of alter db command at 04/20/2015 15:54:49

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-00704: bootstrap process failure

ORA-39700: database must be opened with UPGRADE option

Process ID: 27721760

Session ID: 1 Serial number: 453

ORACLE error from target database:

ORA-03114: not connected to ORACLE

explanation

=========

the db was upgraded put the backup was before the upgrade

solution

======

upgrade the db to open it

SQL> STARTUP UPGRADE

SQL> @?/rdbms/admin/catupgrd.sql

SQL> STARTUP

SQL> @?/rdbms/admin/utlrp.sql

الاثنين، 20 أبريل 2015

some oracle errors

sources	solution	error
metalink Doc ID 756799.1	as per metalink Doc ID 756799.1 this is due Bug 6767655 and fixed in 10.2.0.5 (Server Patch Set) And the Workaround is Avoid concurrent DML and index rebuild online. Serialize these operations	ORA-07445: exception encountered: core dump [kauxs_do_journal()+4] [SIGSEGV] [Address not mapped to object] [0x000000002] [] []
(Doc ID 293002.1)	cause ~~~~~~~~ The "UPGRADE CATALOG" step list in the patch or patchset readme was not submitted. This could leave the recovery catalog schema in a version lower than 9.2.0.4.0. Fix ~~~~~ Connect to the target and the catalog database then run "UPGRADE CATALOG". Re-enter "UPGRADE CATALOG" a second time when prompted. If "RESYNC CATALOG" then runs without errors the issue should be resolved. resync catalog; RMAN> upgrade catalog; # twice to confir	RMAN-03014 implicit resync of recovery catalog failed
Doc ID 1312448.1		RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on B1 channel at 10/26/2014 12:56:48 ORA-19513: failed to identify sequential file ORA-27206: requested file not found in media management catalog

TNS-12502 Tips

Cause: No CONNECT_DATA was passed to the listener.

Action: Check that the service name resolved from TNSNAMES.ORA has the CONNECT_DATA component of the connect descriptor.

SQL> select * from scott.dept_view;
select * from scott.dept_view
*
ERROR at line 1:
ORA-01578: ORACLE data block corrupted (file # 11, block # 34)
ORA-01110: data file 5: '/home/oracle/oradata/users.dbf'

solution

=====

follow metalink DBMS_REPAIR example (Doc ID 68013.1)

sources

=====

How to identify the corrupt Object reported by ORA-1578 / RMAN / DBVERIFY (Doc ID 819533.1)

RMAN-20033

Error

=======

Rman backup failed with error

Starting Control File and SPFILE Autobackup at Dec 13 13 12:59:20

piece handle=ORA_CFc-6717079-20131213-10 comment=API Version 2.0,MMS Version 4.2.0.0

Finished Control File and SPFILE Autobackup at Dec 13 13 13:00:29

released channel: B1

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03008: error while performing automatic resync of recovery catalog

RMAN-20033: control file sequence# too

explanation

==========

2 rman backups running at the same time ,kill all the rman session and restart the backup again