Wednesday, August 29, 2012
Tuesday, August 28, 2012
Recover the Primary Database's datafile using a copy of a Physical Standby Database's Datafile
Recover the Primary Database's datafile using a copy of a Physical Standby Database's Datafile
Before replacing a datafile with a copy from either production or standby, please confirm that all archivelogs are available for full recovery of this datafile.
Check the following before replacing :
a). dbv must return with zero corrupted pages
$ dbv file=<full path filename> blocksize=<tablespace blocksize> logfile=<output log>
b). rman validate:
RMAN> backup validate check logical datafile n; (n is datafile number)
c). Once RMAN is completed, this view must return zero rows:
SQL> select * from v$database_block_corruption;
Recovering the Primary's Datafile :
1). In the Physical standby database, backup the datafile to a cooked file system:
RMAN> backup datafile 5 format '/tmp/df5_st.bk';
2). Transfer the backuppiece from the standby to the primary host using scp, ftp, nfs etc
3). In the primary database, do the following:
a). Catalog this backuppiece and confirm that it is available for use:
RMAN> catalog backuppiece '/tmp/df5_st.bk';
RMAN> list backuppiece '/tmp/df5_st.bk'
RMAN> list backup of datafile 5;
b). Restore the datafile:
SQL> alter database datafile 5 offline;
RMAN> restore datafile 5;
c). Recover the datafile:
RMAN> recover datafile 5;
d). Place the datafile online:
SQL> alter database datafile 5 online;
e). Check the datafile status:
SQL> select file_name from dba_data_files
Before replacing a datafile with a copy from either production or standby, please confirm that all archivelogs are available for full recovery of this datafile.
Check the following before replacing :
a). dbv must return with zero corrupted pages
$ dbv file=<full path filename> blocksize=<tablespace blocksize> logfile=<output log>
b). rman validate:
RMAN> backup validate check logical datafile n; (n is datafile number)
c). Once RMAN is completed, this view must return zero rows:
SQL> select * from v$database_block_corruption;
Recovering the Primary's Datafile :
1). In the Physical standby database, backup the datafile to a cooked file system:
RMAN> backup datafile 5 format '/tmp/df5_st.bk';
2). Transfer the backuppiece from the standby to the primary host using scp, ftp, nfs etc
3). In the primary database, do the following:
a). Catalog this backuppiece and confirm that it is available for use:
RMAN> catalog backuppiece '/tmp/df5_st.bk';
RMAN> list backuppiece '/tmp/df5_st.bk'
RMAN> list backup of datafile 5;
b). Restore the datafile:
SQL> alter database datafile 5 offline;
RMAN> restore datafile 5;
c). Recover the datafile:
RMAN> recover datafile 5;
d). Place the datafile online:
SQL> alter database datafile 5 online;
e). Check the datafile status:
SQL> select file_name from dba_data_files
11.2.0.3.3 Patch Set Update for Oracle 11g R2 (11.2.0.3.0)
Patch 13923374 - 11.2.0.3.3 Patch Set Update :
To install the PSU 11.2.0.3.3 patch, the Oracle home must have the 11.2.0.3.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 11.2.0.3.0
This patch is Data Guard Standby-First Installable.
If you are installing the PSU to an environment that has a Grid Infrastructure home, note the following:
- Grid Infrastructure PSU 11.2.0.3.3 <<Patch 13919095>> should be applied to the Grid Infrastructure home and Database home using the readme instructions provided with the patch.
PSU 11.2.0.3.3 contains the following new fixes
Buffer Cache Management
13457582 - INSTANCE CRASH AFTER ORA-600 [KCLANTILOCK_8]
13467683 - JOIN OF TEMP AND PERMANENT TABLES IN RAC MIGHT CAUSE CORRUPTION OF PERMANENT TBL
13916709 - FIX FOR BUG 13916709
Generic
9761357 - ORA-600[QKEISEXPRRE...ED1] WHEN QUERYING DUAL WITH PREDICATE INVOLVING ORA_ROWSN12535346 - DML ON TABLE W/ RI AND INTERVAL PARTITIONED PARENT TABLE MAY FAIL WITH SIGSEGV
12617123 - SPLIT SUBPARTITION ON TABLE W/ CHILD REFERENCE-PARTITIONED TABLE FAIL WITH ORA-1
12646784 - ALTER TABLE FAILS WITH ORA-600 [KKPOFFOC]
12658411 - LARGE RESULT CACHE CAUSING INSTANCE TO HANGS
12678920 - CONCURRENT SPLIT/MERGE,DROP PARTITION OPERATIONS ON TABLE MAY FAIL WITH SIGSEGV
12797420 - KGLHDGH CONTENTION ON THE DB INSTANCE HANDLE WHEN CURSOR_SHARING IS SET TO FORCE
12913474 - DISABLED INVALID TABLE TRIGGER CAN STILL BLOCK DML
12976376 - MEMORY LEAK IN SHARED CURSOR LAYER: "KKSFBC:HASH1"
13035360 - TASK FORCE: UNEXPECTED ORA-02303: RAISED FROM PATCH EDITION OF THE INSTANCE
13370330 - ORA-600[QKEISEXPRREFERENCED1] FROM QUERY W/ VIRTUAL COLUMN WITH A CONSTANT VALUE
13419660 - UNSHARED DATAPUMP SESSION STATE THRU DBMS_REDEFINITION CALLS CAUSES MEMORY LEAK
13502183 - VALID PACKAGE BODY IN CHILD EDITION MARKED AS INVALID DURING UTL_RECOMP
13588248 - COREDUMP IN RAC ENV WITH SESSION POOLING, DRCP, FLASH CACHE, SERVER CACHE, AC
13657605 - ORA-600 [KKZGBTCOLS] DURING BUILD DEFERRED REMOTE WITH ROWID MV CREATION
High Availability
10133521 - LOGICAL STANDBY APPLY COULD FAIL WITH ORA-26808/26786 FOR SOME NLS_SORT VALUES12879027 - LMON PROCESS CAN GET STUCK IN DRM QUIESCE STEP TRIGGERING PSEUDO RECONFIGURATION
13366202 - DBNEWID [ NID ] DOESN'T ALLOW TARGET=/
Oracle Network
12880299 - RAC: TCP HANDLERS BLOCK IF LISTENER REGISTRATION IS RESTRICTED TO IPC W/COST
Oracle Security
11840910 - ORA-604 DURING STARTUP WITH SYSOPER13340388 - ORA-600 [KZAXPOPR14...] WHILE READING XML AUDIT FILES WITH XML EXTENDED AUDITING
Oracle Space Management
12401111 - ORA-00600 [KDLIXFMCHECK] ON 11.2.0.213103913 - ORA-600 [25027] [TS#] [1] DURING DML WHILE INDEX IS BEING REBUILT ONLINE
13326736 - ORA-959 RENAMING A TABLESPACE TO ALREADY DROPPED TABLESPACE NAME
13981051 - CORE DUMP IN TBSAFL MAY BE SEEN WHILE CREATING TABLESPACE WITH COMPRESSION
Oracle Transaction Management
13903046 - ORA-600 [4417] WHILE PERFORMING BLOCK CLEANOUTS ON HCC COMPRESSED TABLE BLOCKS
Oracle Utilities
9858539 - DATA PUMP IMPORT FAILS FOR LOGON TRIGGER ORA-04072: INVALID TRIGGER TYPE13001379 - DATAPUMP TRANSPORT_TABLESPACES PRODUCES WRONG METADATA FOR SOME TABLES
Server Manageability
13338048 - ORA-1476 OCCURRED WHILE OUTPUTTING THE AWR REPORT FOR STREAMS-RELATED SECTIONS13527323 - AWR REPORT GENERATION COULD FAIL WITH ORA-6502 WITH MULTIBYTE CHARS IN SQL TEXT
Subscribe to:
Posts (Atom)