Thu Apr 26 08:28:57 2012ERROR: ORA-48178 encountered when checking if the process is able toERROR: create the ADR schema in the specified ADR Base directory [/u02/app/oracle]ERROR: The ORA-48178 error is caused by the ORA-48101 error.ORA-48101: error encountered when attempting to read a file [block] [/u02/app/oracle/diag/rdbms/stdby/STDBY/metadata/ADR_INTERNAL.mif] [0]ORA-27072: File I/O errorLinux Error: 22: Invalid argumentAdditional information: 4Additional information: 1Additional information: -1ERROR: Check if the directory is readable and check if the OS version is supported for ADR.ERROR: The process will switch back to the pre-ADR method of tracing and logging.Thu Apr 26 08:36:52 2012ALTER SYSTEM SET _diag_adr_enabled=TRUE SCOPE=MEMORY;Thu Apr 26 08:38:02 2012Shutting down instance: further logons disabledStopping background process MMNLStopping background process MMONShutting down instance (immediate)License high water mark = 1Waiting for dispatcher 'D000' to shutdownAll dispatchers and shared servers shutdownALTER DATABASE CLOSE NORMALORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...ARCH: Archival disabled due to shutdown: 1089Shutting down archive processesArchiving is disabledArchive process shutdown avoided: 0 activeARCH: Archival disabled due to shutdown: 1089Shutting down archive processesArchiving is disabledArchive process shutdown avoided: 0 activeThu Apr 26 08:38:16 2012ERROR: ORA-48178 encountered when checking if the process is able toERROR: create the ADR schema in the specified ADR Base directory [/u02/app/oracle]ERROR: The ORA-48178 error is caused by the ORA-48101 error.ORA-48101: error encountered when attempting to read a file [block] [/u02/app/oracle/diag/rdbms/stdby/STDBY/metadata/ADR_INTERNAL.mif] [0]ORA-27072: File I/O errorLinux Error: 22: Invalid argumentAdditional information: 4Additional information: 1Additional information: -1ERROR: Check if the directory is readable and check if the OS version is supported for ADR.ERROR: The process will switch back to the pre-ADR method of tracing and logging.Thu Apr 26 08:38:32 2012ALTER SYSTEM SET _diag_adr_enabled=TRUE SCOPE=BOTH;Shutting down instance: further logons disabledStopping background process MMNLStopping background process MMONThu Apr 26 08:38:43 2012Shutting down instance (immediate)License high water mark = 1Waiting for dispatcher 'D000' to shutdownAll dispatchers and shared servers shutdownALTER DATABASE CLOSE NORMALORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...ARCH: Archival disabled due to shutdown: 1089Shutting down archive processesArchiving is disabledArchive process shutdown avoided: 0 activeARCH: Archival disabled due to shutdown: 1089Shutting down archive processesArchiving is disabledArchive process shutdown avoided: 0 activeThu Apr 26 08:38:54 2012ERROR: ORA-48178 encountered when checking if the process is able toERROR: create the ADR schema in the specified ADR Base directory [/u02/app/oracle]ERROR: The ORA-48178 error is caused by the ORA-48101 error.ORA-48101: error encountered when attempting to read a file [block] [/u02/app/oracle/diag/rdbms/stdby/STDBY/metadata/ADR_INTERNAL.mif] [0]ORA-27072: File I/O errorLinux Error: 22: Invalid argumentAdditional information: 4Additional information: 1Additional information: -1ERROR: Check if the directory is readable and check if the OS version is supported for ADR.ERROR: The process will switch back to the pre-ADR method of tracing and logging.Thu Apr 26 08:39:08 2012ALTER SYSTEM SET _diag_adr_enabled=TRUE SCOPE=BOTH;Thu Apr 26 08:39:54 2012alter database mount standby databaseSet as converted control file due to db_unique_name mismatchChanging di2dbun from PROD to STDBYSetting recovery target incarnation to 2ARCH: STARTING ARCH PROCESSESThu Apr 26 08:39:58 2012ARC0 started with pid=19, OS id=24546Thu Apr 26 08:39:58 2012ARC1 started with pid=20, OS id=24549Thu Apr 26 08:39:58 2012ARC2 started with pid=21, OS id=24552ARC0: Archival startedARC1: Archival startedThu Apr 26 08:39:58 2012ARC3 started with pid=22, OS id=24555ARC2: Archival startedARC3: Archival startedARCH: STARTING ARCH PROCESSES COMPLETEARC0: Becoming the 'no FAL' ARCHARC0: Becoming the 'no SRL' ARCHARC3: Becoming the heartbeat ARCHARC0: Thread not mountedARC1: Thread not mountedARC2: Thread not mountedARC3: Thread not mountedPhysical Standby Database mounted.Lost write protection disabledCompleted: alter database mount standby databaseThu Apr 26 08:41:15 2012Redo Shipping Client Connected as PUBLIC-- Connected User is ValidRFS[1]: Assigned to RFS process 24586RFS[1]: Identified database type as 'physical standby'Primary database is in MAXIMUM PERFORMANCE modeRFS LogMiner: Client disabled from further notificationPrimary database is in MAXIMUM PERFORMANCE modeRFS[1]: No standby redo logfiles createddb_recovery_file_dest_size of 2048 MB is 2.44% used. This is auser-specified limit on the amount of space that will be used by thisdatabase for recovery-related files, and does not reflect the amount ofspace available in the underlying filesystem or ASM diskgroup.Thu Apr 26 08:41:17 2012Redo Shipping Client Connected as PUBLIC-- Connected User is ValidRFS[2]: Assigned to RFS process 24598RFS[2]: Identified database type as 'physical standby'RFS[2]: No standby redo logfiles createdRFS[2]: Archived Log: '/u02/app/oracle/flash_recovery_area/STDBY/archivelog/2012_04_26/o1_mf_1_35_7sljmf9z_.arc'Thu Apr 26 08:42:12 2012Redo Shipping Client Connected as PUBLIC-- Connected User is ValidRFS[3]: Assigned to RFS process 24643RFS[3]: Identified database type as 'physical standby'Thu Apr 26 08:42:12 2012ALTER DATABASE CONVERT TO SNAPSHOT STANDBYAllocated 3981204 bytes in shared pool for flashback generation bufferStarting background process RVWRThu Apr 26 08:42:13 2012RVWR started with pid=26, OS id=24646Created guaranteed restore point SNAPSHOT_STANDBY_REQUIRED_04/26/2012 08:42:12tkcrrxms: Killing 3 processes (all RFS)RESETLOGS after incomplete recovery UNTIL CHANGE 904565Standby became primary SCN: 904563Converting standby mount to primary mount.ACTIVATE STANDBY: Complete - Database mounted as primary (STDBY)ALTER DATABASE CONVERT TO SNAPSHOT STANDBY: Complete (STDBY)Completed: ALTER DATABASE CONVERT TO SNAPSHOT STANDBYThu Apr 26 08:43:44 2012Shutting down instance: further logons disabledStopping background process MMNLStopping background process MMONShutting down instance (immediate)License high water mark = 4Waiting for dispatcher 'D000' to shutdownAll dispatchers and shared servers shutdownALTER DATABASE CLOSE NORMALORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...ARCH: Archival disabled due to shutdown: 1089Shutting down archive processesArchiving is disabledThu Apr 26 08:43:48 2012ARCH shutting downARC3: Archival stoppedThu Apr 26 08:43:48 2012ARCH shutting downARC1: Archival stoppedThu Apr 26 08:43:48 2012ARCH shutting downARC2: Archival stoppedThu Apr 26 08:43:48 2012ARCH shutting downARC0: Archival stoppedARCH: Archival disabled due to shutdown: 1089Shutting down archive processesArchiving is disabledArchive process shutdown avoided: 0 activeThu Apr 26 08:44:02 2012ERROR: ORA-48178 encountered when checking if the process is able toERROR: create the ADR schema in the specified ADR Base directory [/u02/app/oracle]ERROR: The ORA-48178 error is caused by the ORA-48101 error.ORA-48101: error encountered when attempting to read a file [block] [/u02/app/oracle/diag/rdbms/stdby/STDBY/metadata/ADR_INTERNAL.mif] [0]ORA-27072: File I/O errorLinux Error: 22: Invalid argumentAdditional information: 4Additional information: 1Additional information: -1ERROR: Check if the directory is readable and check if the OS version is supported for ADR.ERROR: The process will switch back to the pre-ADR method of tracing and logging.Thu Apr 26 08:44:11 2012ALTER SYSTEM SET _diag_adr_enabled=TRUE SCOPE=BOTH;Thu Apr 26 08:44:41 2012alter database mountSetting recovery target incarnation to 3Allocated 3981204 bytes in shared pool for flashback generation bufferStarting background process RVWRThu Apr 26 08:44:46 2012RVWR started with pid=19, OS id=24731Database mounted in Exclusive ModeLost write protection disabledCompleted: alter database mountThu Apr 26 08:46:39 2012ALTER DATABASE CONVERT TO PHYSICAL STANDBYALTER DATABASE CONVERT TO PHYSICAL STANDBY (STDBY)Flashback Restore StartFlashback Restore CompleteStopping background process RVWRDeleted Oracle managed file /u02/app/oracle/flash_recovery_area/STDBY/flashback/o1_mf_7sljo4os_.flbGuaranteed restore point droppedThe primary database controlfile was created using the'MAXLOGFILES 16' clause.There is space for up to 13 standby redo logfilesUse the following SQL commands on the standby database to createstandby redo logfiles that match the primary database:ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;Setting recovery target incarnation to 2Completed: ALTER DATABASE CONVERT TO PHYSICAL STANDBYThu Apr 26 08:47:45 2012Shutting down instance: further logons disabledStopping background process MMNLStopping background process MMONShutting down instance (immediate)License high water mark = 1Waiting for dispatcher 'D000' to shutdownAll dispatchers and shared servers shutdownALTER DATABASE CLOSE NORMALORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...ARCH: Archival disabled due to shutdown: 1089Shutting down archive processesArchiving is disabledArchive process shutdown avoided: 0 activeARCH: Archival disabled due to shutdown: 1089Shutting down archive processesArchiving is disabledArchive process shutdown avoided: 0 activeThu Apr 26 08:48:10 2012ERROR: ORA-48178 encountered when checking if the process is able toERROR: create the ADR schema in the specified ADR Base directory [/u02/app/oracle]ERROR: The ORA-48178 error is caused by the ORA-48101 error.ORA-48101: error encountered when attempting to read a file [block] [/u02/app/oracle/diag/rdbms/stdby/STDBY/metadata/ADR_INTERNAL.mif] [0]ORA-27072: File I/O errorLinux Error: 22: Invalid argumentAdditional information: 4Additional information: 1Additional information: -1ERROR: Check if the directory is readable and check if the OS version is supported for ADR.ERROR: The process will switch back to the pre-ADR method of tracing and logging.Thu Apr 26 08:48:19 2012ALTER SYSTEM SET _diag_adr_enabled=TRUE SCOPE=BOTH;Thu Apr 26 08:49:01 2012alter database mount standby databaseSetting recovery target incarnation to 2ARCH: STARTING ARCH PROCESSESThu Apr 26 08:49:05 2012ARC0 started with pid=19, OS id=24814Thu Apr 26 08:49:05 2012ARC1 started with pid=20, OS id=24817Thu Apr 26 08:49:05 2012ARC2 started with pid=21, OS id=24820ARC0: Archival startedARC1: Archival startedARC2: Archival startedARC3: Archival startedARCH: STARTING ARCH PROCESSES COMPLETEARC0: Becoming the 'no FAL' ARCHARC0: Becoming the 'no SRL' ARCHARC0: Thread not mountedThu Apr 26 08:49:05 2012ARC3 started with pid=22, OS id=24823ARC2: Becoming the heartbeat ARCHARC1: Thread not mountedARC3: Thread not mountedARC2: Thread not mountedPhysical Standby Database mounted.Lost write protection disabledCompleted: alter database mount standby databaseThu Apr 26 08:50:01 2012alter database recover managed standby databaseMedia Recovery Start: Managed Standby Recovery (STDBY)Fast Parallel Media Recovery enabledManaged Standby Recovery not using Real Time Apply parallel recovery started with 2 processesMedia Recovery Log /u02/app/oracle/flash_recovery_area/STDBY/archivelog/2012_04_26/o1_mf_1_35_7sljmf9z_.arcMedia Recovery Waiting for thread 1 sequence 36Thu Apr 26 08:50:21 2012Shutting down recovery slaves due to error 1013Recovery interrupted!Media Recovery user canceled with status 1013ORA-16043 signalled during: alter database recover managed standby database...Thu Apr 26 08:50:39 2012alter database recover managed standby database disconnect from sessionAttempt to start background Managed Standby Recovery process (STDBY)Thu Apr 26 08:50:39 2012MRP0 started with pid=23, OS id=24842MRP0: Background Managed Standby Recovery process started (STDBY)Fast Parallel Media Recovery enabledManaged Standby Recovery not using Real Time Apply parallel recovery started with 2 processesWaiting for all non-current ORLs to be archived...Clearing online redo logfile 1 /u02/app/oracle/STDBY/redo01.logClearing online log 1 of thread 1 sequence number 1Completed: alter database recover managed standby database disconnect from sessionClearing online redo logfile 1 completeMedia Recovery Waiting for thread 1 sequence 36Thu Apr 26 08:53:12 2012Redo Shipping Client Connected as PUBLIC-- Connected User is ValidRFS[1]: Assigned to RFS process 24875RFS[1]: Identified database type as 'physical standby'RFS LogMiner: Client disabled from further notificationdb_recovery_file_dest_size of 2048 MB is 1.01% used. This is auser-specified limit on the amount of space that will be used by thisdatabase for recovery-related files, and does not reflect the amount ofspace available in the underlying filesystem or ASM diskgroup.RFS[1]: Archived Log: '/u02/app/oracle/flash_recovery_area/STDBY/archivelog/2012_04_26/o1_mf_1_36_7slk9rrh_.arc'Thu Apr 26 08:53:12 2012Redo Shipping Client Connected as PUBLIC-- Connected User is ValidRFS[2]: Assigned to RFS process 24884RFS[2]: Identified database type as 'physical standby'RFS[2]: Archived Log: '/u02/app/oracle/flash_recovery_area/STDBY/archivelog/2012_04_26/o1_mf_1_37_7slk9rvr_.arc'Thu Apr 26 08:53:17 2012Media Recovery Log /u02/app/oracle/flash_recovery_area/STDBY/archivelog/2012_04_26/o1_mf_1_36_7slk9rrh_.arcMedia Recovery Log /u02/app/oracle/flash_recovery_area/STDBY/archivelog/2012_04_26/o1_mf_1_37_7slk9rvr_.arcMedia Recovery Waiting for thread 1 sequence 38FAL[client]: Error fetching gap sequence, no FAL server specifiedThu Apr 26 08:53:54 2012RFS[2]: No standby redo logfiles createdRFS[2]: Archived Log: '/u02/app/oracle/flash_recovery_area/STDBY/archivelog/2012_04_26/o1_mf_1_38_7slkc2gx_.arc'Thu Apr 26 08:53:54 2012Redo Shipping Client Connected as PUBLIC-- Connected User is ValidRFS[3]: Assigned to RFS process 24906RFS[3]: Identified database type as 'physical standby'Primary database is in MAXIMUM PERFORMANCE modePrimary database is in MAXIMUM PERFORMANCE modeRFS[3]: No standby redo logfiles createdThu Apr 26 08:54:18 2012Media Recovery Log /u02/app/oracle/flash_recovery_area/STDBY/archivelog/2012_04_26/o1_mf_1_38_7slkc2gx_.arcMedia Recovery Waiting for thread 1 sequence 39 (in transit)