I just came across an essential Oracle 11g Interactive Quick Reference guide – which has the key dictionary views, background processes and architecture diagram.
Hope you may find it useful. It can be downloaded from
http://www.oracle.com/webapps/dialogue/ns/dlgwelcome.jsp?p_ext=Y&p_dlg_id=9575302&src=7027600&Act=54
RMAN-06169: could not read file header for datafile nn error reason 4
RMAN-06169: could not read file header for datafile nn error reason 4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 10/20/2011 07:41:54
RMAN-06056: could not access datafile nn
The reason code of 4 meant for DBWR could not find the file. After investigating found that the new data file added on locally for a RAC database. That data file not available on other node cause this backup failure.
To resolve this, the locally create data file moved to ASM.
Method 1: Using RMAN
| Step 1: Start RMAN and connect to the target database. Step 2: Generate a report that shows the names of the datafiles. RMAN> REPORT SCHEMA; RMAN> BACKUP AS COPY DATAFILE '+DG_DEVSYS_mydb1_FLASH_01/mydb1/datafile/data01.290.709985421' FORMAT '+DG_DEVSYS_mydb1_DATA_01'; Step 5: Point the control file to the newly created copy of the datafile Step 6: Recover the renamed datafile Step 7. Bring the datafile online. Step 8. Delete the old datafile |
Reference: http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmasmmi.htm
Method 2: Using ASMCMD CP ( Copy ) Command
| Step 1: Start RMAN and connect to the target database. Step 2: Generate a report that shows the names of the datafiles. RMAN> REPORT SCHEMA; Step 3: Bring the Datafile Offline ASMCMD [+] > cp +DG_DEVSYS_mydb1_FLASH_01/mydb1/datafile/data01.290.709985421 +DG_DEVSYS_mydb1_DATA_01 Step 5: After copied datafile, then rename file in database. With ASM(OMF) this delete old datafile. alter database rename file '+DG_DEVSYS_mydb1_FLASH_01/mydb1/datafile/data01.290.709985421' to '+DG_DEVSYS_mydb1_DATA_01/mydb1/datafile/data01.272.764459767' Step 6: Recover the renamed datafile Step 7. Bring the datafile online. |
Method 3: Using RMAN Copy
| Step 1: Restrict the Session ALTER SYSTEM enable restricted session; Step 2: Bring the Datafile Offline alter database datafile '+DG_DEVSYS_mydb1_FLASH_01/mydb1/datafile/data01.290.709985421' offline Step 3: Start RMAN and connect to the target database. Step 4: RMAN Copy datafile Step 5: After copied datafile, then rename file in database. With ASM(OMF) this delete old datafile. alter database rename file '+DG_DEVSYS_mydb1_FLASH_01/mydb1/datafile/data01.290.709985421' to '+DG_DEVSYS_mydb1_DATA_01/mydb1/datafile/data01.272.764459767' Step 6: Recover the renamed datafile Step 7. Bring the datafile online. Step 8: Verify the file name ALTER SYSTEM disable restricted session; |
After issuing of SHUTDOWN ABORT command, when opening up database following step are performed
1. SPFile / PFile: Server Parameter file ( SP File ) or the initialization parameter (initSID.ora / PFILE ) file is read
2. Memory : SGA is allocated
3. Background Process: Background process are started
4. Control File : Control file is read
5. Redo Log File: Redo Log file is read
6. Data File: Data files are checked for consistency
7. Instance Recovery: Instance Recovery is started
| Verify the file specification information for the current control file(s): SQL> show parameters control_files |
| If your are using pfile, change CONTROL_FILES to point to the remaining control files. Make sure that the full file specification is used. vi $ORACLE_HOME/dbs/init<SID>.ora. CONTROL_FILES = (/oradata/<sid>/data1/control_01.ctl, /oradata/<sid>/data3/control_02.ctl) If you are using spfile, you may modify the CONTROL_FILES parameter using the ALTER SYSTEM SET command. SQL> alter system set control_files = /oradata/<sid>/data1/control_01.ctl, /oradata/<sid>/data3/control_02.ctl scope=spfile; |
| Shutdown and startup the database. |
| Verify the file specification information for the current control file(s): SQL> show parameters control_files If desired, delete the control file from the O/S. |
---- Check if flashback on?
| SELECT flashback_on, log_mode FROM v$database; |
--- Check for Flashback Parameters existing
| set linesize 121 SELECT name, value |
---- Stop the RAC Database , it will stop all the instances of the DB
| srvctl stop database -d sfodb |
--- Start the DB in mount state
| srvctl start instance -d sfodb -i sfo38u1 -o mount |
-- Set the Flashback on
| alter database flashback on; |
--- Open the database
| alter database open; |
--- Start the remaining instances of the RAC
| srvctl start instance -d sfodb -i sfo38u2 -o mount exclusive |
-- Verify the flashback settings
| select INST_ID,Name, FLASHBACK_ON from gv$database; |
After starting the instance, the Oracle software associates the instance with specific database. This is called mounting the database.
Oracle DB Storage Structure
Relationship of Database, Tablespace and Data files
How table data is stored in Oracle Database
Content of Database Data Block
