4 Replies Latest reply: Oct 11, 2012 5:10 AM by 11567 RSS

    failover

    11567
      Dear All,

      Post failover getting below error message in alert log file.

      Thu Oct 11 14:34:20 2012
      krsk_srl_archive_int: Enabling archival of deferred physical standby SRLs
      Errors in file /oracle/EHP/saptrace/diag/rdbms/ehp_matoda/EHP/trace/EHP_arc2_17591.trc:
      ORA-19816: WARNING: Files may exist in db_recovery_file_dest that are not known to database.
      ORA-27038: created file already exists
      Additional information: 1
      *************************************************************
      WARNING: A file of type ARCHIVED LOG may exist in
      db_recovery_file_dest that is not known to the database.
      Use the RMAN command CATALOG RECOVERY AREA to re-catalog
      any such files. If files cannot be cataloged, then manually
      delete them using OS command. This is most likely the
      result of a crash during file creation.
      *************************************************************

      tried renaming archive log file show in /oracle/EHP/saptrace/diag/rdbms/ehp_matoda/EHP/trace/EHP_arc2_17591.trc file.

      But after that again shows message as below and getting same logs with the same sequence numbers are coming back.

      Thu Oct 11 14:42:57 2012
      krsk_srl_archive_int: Enabling archival of deferred physical standby SRLs
      Archived Log entry 516 added for thread 1 sequence 1231 ID 0xf3ed9e21 dest 3:
      krsk_srl_archive_int: Enabling archival of deferred physical standby SRLs
      Unable to create archive log file '/oracle/EHP/oraarch/EHParch1_1231_790785542.dbf'
      Errors in file /oracle/EHP/saptrace/diag/rdbms/ehp_matoda/EHP/trace/EHP_arc2_17591.trc:
      ORA-19816: WARNING: Files may exist in db_recovery_file_dest that are not known to database.
      ORA-27038: created file already exists
      Additional information: 1
      *************************************************************
      WARNING: A file of type ARCHIVED LOG may exist in
      db_recovery_file_dest that is not known to the database.
      Use the RMAN command CATALOG RECOVERY AREA to re-catalog
      any such files. If files cannot be cataloged, then manually
      delete them using OS command. This is most likely the
      result of a crash during file creation.
      *************************************************************

      Regards,
      Nikunj Thaker
        • 1. Re: failover
          mseberg
          Hello;

          Had a similar question a few months ago. Check this thread :

          Errors after successful automatic failover in 11.2.0.2.

          Best Regards

          mseberg
          • 2. Re: failover
            11567
            Thanks.

            Already gone through with that message prior to posting but did not get clarity hence posted.

            Post failover to physical standby database found parameter log_archive_dest_3 added with below values
            location="USE_DB_RECOVERY_FILE_DEST", valid_for=(STANDBY_LOGFILE,STANDBY_ROLE)

            Why added and whats the reason ?

            Regards,
            Nikunj Thaker
            • 3. Re: failover
              mseberg
              Generally you would see this error with DG BROKER as it does not account for the parameter db_file_name_convert.

              If standby_file_management was set to manual and a data file had been added to the standby you might throw this error.

              Not sure its much of an issue.

              Best Regards

              mseberg
              • 4. Re: failover
                11567
                In my case standby_file_management set to AUTO.

                SQL> show parameter standby_file_management

                NAME TYPE VALUE
                ------------------------------------ ----------- ------------------------------
                standby_file_management string AUTO
                SQL>


                Surprise after multiple time executed shutdown immediate; and startup; command not getting message in alert log file.

                I think i have to test the scenario again to find out facing the same problem or not.

                Thanks,
                Nikunj Thaker