BW missing Redo logs

Hi all
There are missing Redo logs in Db12 in BW server. There are gaps in the sequence of redo logs and about 13 are not there. If we try to restore from a backup the database is going to become inconsistent.
Can anyone give us an idea why it is happening.
Thanks

Missing Redo Logs???
I would be very worried...
When was your last full offline backup?
How are you dealing with redo logs?  Copy, save and delete?
What are the parameters in you init<sid>.sap and init<sid>.ora file for dealing with redo logs?

Similar Messages

  • Problem in creating database -Missing Redo log file

    I am try to create a new database using DBCA .While creating a database it shows the error oracle instance terminated.Force Disconnected.
    My alert log file is
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/oracl/redo01.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Wed Nov 06 10:07:27 2013
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/oracl/redo02.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/oracl/redo03.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Wed Nov 06 10:07:38 2013
    Setting recovery target incarnation to 2
    Wed Nov 06 10:07:38 2013
    Assigning activation ID 1876274518 (0x6fd5ad56)
    Thread 1 opened at log sequence 1
      Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/oracl/redo01.log
    Successful open of redo thread 1
    Wed Nov 06 10:07:38 2013
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Wed Nov 06 10:07:38 2013
    SMON: enabling cache recovery
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc  (incident=1345):
    ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
    Incident details in: /u01/app/oracle/diag/rdbms/oracl/oracl/incident/incdir_1345/oracl_ora_5424_i1345.trc
    Wed Nov 06 10:07:46 2013
    Trace dumping is performing id=[cdmp_20131106100746]
    Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
    ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
    Error 600 happened during db open, shutting down database
    USER (ospid: 5424): terminating the instance due to error 600
    Instance terminated by USER, pid = 5424
    ORA-1092 signalled during: alter database "oracl" open resetlogs...
    ORA-1092 : opiodr aborting process unknown ospid (5424_47935551851664)
    Wed Nov 06 10:07:47 2013
    ORA-1092 : opitsk aborting process
                                                                                                                                   251,1         95%

    >I am try to create a new database using DBCA
    >Please help me to resolve this issue.My redo log file was missing
    DROP and recreate the database.  It is a *new* database without any data.
    Check what datafile locations and redo log file locations you specify when creating the new database. Check if you have permissions and enough disk space.
    Hemant K Chitale

  • Oracle standby/redo log file shipping keeps needing logs re-registering

    Hi
    We have Log File Shipping enabled and the prod system ships redo logs over to the LFS server. It's kept 24 hours behind. It usually ships the logs (and I believe automatically registers them) without issue.
    EXCEPT - it keeps complaining about missing redo log files.
    The file is usually there; but just needs registering with:
    alter database register or replace logfile '/oracle/S1P/saparch/S1Parch1_636443_654987192.dbf';
    (we found if we left out the 'or replace' it takes a very long time or even hangs)
    It then plods on and applies the next... can go for another 2 or 3... or 20... but then often gets stuck again, and you need to register the next.
    Can spend whole days on this...!!
    We did try running a script to register the next 1365 redo logs! It failed on 4, so I ran it again... it worked on those 4, but turned up 3 others it had worked with before! HUH?!? So manually did those 3 ... fine... it carried on rolling forward... but got stuck after 10 minutes again when it hit another it reckoned needed registering (we'd already done it twice!!).
    Any ideas?
    Ross

    Hi
    We have Log File Shipping enabled and the prod system ships redo logs over to the LFS server. It's kept 24 hours behind. It usually ships the logs (and I believe automatically registers them) without issue.
    EXCEPT - it keeps complaining about missing redo log files.
    The file is usually there; but just needs registering with:
    alter database register or replace logfile '/oracle/S1P/saparch/S1Parch1_636443_654987192.dbf';
    (we found if we left out the 'or replace' it takes a very long time or even hangs)
    It then plods on and applies the next... can go for another 2 or 3... or 20... but then often gets stuck again, and you need to register the next.
    Can spend whole days on this...!!
    We did try running a script to register the next 1365 redo logs! It failed on 4, so I ran it again... it worked on those 4, but turned up 3 others it had worked with before! HUH?!? So manually did those 3 ... fine... it carried on rolling forward... but got stuck after 10 minutes again when it hit another it reckoned needed registering (we'd already done it twice!!).
    Any ideas?
    Ross

  • Open database if an active online redo log is missing

    Hi,
    Sorry for the rather long post, but I specified all the steps I performed and couldn't make it shorter :-(
    I need an advice on how to open the database if an active online redo log is missing.
    For test purposes I intentionally performed a shutdown abort when the redo log group 1 was in active state and then renamed its only member (REDO01.LOG) so that the database couldn't perform crash recovery using it. Then upon startup I obviously got the message:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.Ok, so I checked the state of the logs:
    {noformat}
    SQL>SELECT a.GROUP#, first_change#, SEQUENCE#, a.status, SUBSTR(b.MEMBER, 1, 40) MEMBER, b.status mem_status, a.archived
      2    FROM v$log a, v$logfile b
      3   WHERE a.GROUP# = b.GROUP#
      4  ORDER BY a.GROUP#, b.MEMBER;
    GROUP# FIRST_CHANGE#  SEQUENCE# STATUS           MEMBER                         MEM_STA ARC
         1        592134         29 ACTIVE           H:\ORADATA\TESTDB\REDO01.LOG           YES
         2        592268         30 CURRENT          C:\ORADATA\TESTDB\REDO02.LOG           NO
         3        592129         28 ACTIVE           C:\ORADATA\TESTDB\REDO03.LOG           YES
    {noformat}Since opening the database to perform a log switch and thus change the status of the redo log group 1 from ACTIVE to INACTIVE to recreate the member isn't possible, I performed database recovery.
    SQL>recover database until cancel;
    ORA-00279: change 592129 generated at 02/04/2009 10:31:15 needed for thread 1
    ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_28_%U_.ARC
    ORA-00280: change 592129 for thread 1 is in sequence #28
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00279: change 592134 generated at 02/04/2009 10:31:28 needed for thread 1
    ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_%U_.ARC
    ORA-00280: change 592134 for thread 1 is in sequence #29
    ORA-00278: log file 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_28_4RLR3JS9_.ARC' no longer needed for this rec
    overy
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_4RLR4MF3_.ARC'
    ORA-00279: change 592268 generated at 02/04/2009 10:32:03 needed for thread 1
    ORA-00289: suggestion : C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_30_%U_.ARC
    ORA-00280: change 592268 for thread 1 is in sequence #30
    ORA-00278: log file 'C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\ARCHIVELOG\2009_02_04\O1_MF_1_29_4RLR4MF3_.ARC' no longer needed for this rec
    overy
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    'C:\ORADATA\TESTDB\REDO02.LOG'
    Log applied.
    Media recovery complete.
    SQL>So for log sequence #28 I accepted the proposed archived redo log in the FRA, for sequence #29 (that's the online redo log that is missing!) I manually specified its archived copy, and for sequence #30 I specified the CURRENT online redo log. And as it seems the media recovery was successful.
    Next I tried to open the database but again got the error:
    SQL>alter database open noresetlogs;
    alter database open noresetlogs
    ERROR at line 1:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    The status of the log groups and its members is exactly as it was in the first query I wrote above, i.e. the redo log group 1 is still ACTIVE, so it's needed for crash recovery (which I had already done manually if I understand correctly how Oracle works!). I also checked if the datafiles are inconsistent (described in metalink doc id 1015544.102):
    SQL>SELECT DISTINCT CHECKPOINT_CHANGE#, FUZZY FROM V$DATAFILE_HEADER;
    CHECKPOINT_CHANGE# FUZ
                592269 NOSo, everything seems ok as far as datafile consistency is concerned.
    My question is: how can I rename/drop/clear/whatever the member of redo log group 1 to open the database?
    I tried to rename the log file member, to add another member to it, to open the database with resetlogs, to clear the logfile group 1, but all without success:
    1)
    SQL>alter database clear logfile group 1;
    alter database clear logfile group 1
    ERROR at line 1:
    ORA-01624: log 1 needed for crash recovery of instance testdb (thread 1)
    ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
    2)
    SQL>alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    3)
    SQL>alter database rename file 'H:\ORADATA\TESTDB\REDO01.LOG' to 'C:\ORADATA\TESTDB\REDO01.LOG';
    alter database rename file 'H:\ORADATA\TESTDB\REDO01.LOG' to 'C:\ORADATA\TESTDB\REDO01.LOG'
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01512: error renaming log file H:\ORADATA\TESTDB\REDO01.LOG - new file C:\ORADATA\TESTDB\REDO01.LOG not found
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    4)
    SQL>alter database add logfile member 'C:\ORADATA\TESTDB\REDO01.LOG' to group 1;
    alter database add logfile member 'C:\ORADATA\TESTDB\REDO01.LOG' to group 1
    ERROR at line 1:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: 'H:\ORADATA\TESTDB\REDO01.LOG'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.Sorry again for the long post and thank you in advance for any suggestion.
    Regards,
    Jure

    You could check if the recovery was complete by (re)creating the controlfile with the resetlogs option.
    <CREATE CONTROLFILE REUSE DATABASE define_db_name RESETLOGS NOARCHIVELOG
    ...>Thanks for the hint. If possible, could you only check if the steps I'm going to perform are ok.
    I did an "alter database backup controlfile to trace;" and then extracted the create controlfile definition part. So in essence I should run the following statements:
    CREATE CONTROLFILE REUSE DATABASE "TESTDB" RESETLOGS  ARCHIVELOG
        MAXLOGFILES 16
        MAXLOGMEMBERS 3
        MAXDATAFILES 100
        MAXINSTANCES 8
        MAXLOGHISTORY 292
    LOGFILE
      GROUP 1 'C:\ORADATA\TESTDB\REDO01.LOG'  SIZE 20M,
      GROUP 2 'C:\ORADATA\TESTDB\REDO02.LOG'  SIZE 20M,
      GROUP 3 'C:\ORADATA\TESTDB\REDO03.LOG'  SIZE 20M
    -- STANDBY LOGFILE
    DATAFILE
      'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF',
      'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\UNDOTBS01.DBF',
      'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSAUX01.DBF',
      'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\USERS01.DBF'
    CHARACTER SET EE8MSWIN1250
    ALTER DATABASE OPEN RESETLOGS;
    ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\TEMP01.DBF' REUSE;Is that correct?
    About the RMAN backups: Wouldn't a 'CATALOG RECOVERY AREA' populate the controlfile with backup information again (I'm not using a recovery catalog in this case)?
    Thanks for the help!
    Regards,
    Jure

  • Recover from missing files(redo log file/control file) and state of the DB

    Hello,
    i hv go through the doc. as well. But have some doubts what will happen in each on these situations.
    Pls help me to clarify these!
    Scenario is like this;
    hv 3 redo log files - multiplxed
    hv 3 control files - multiplxed
    - What will happen if 1 redo log file missing when starting the DB?
    - What will happen if 1 redo log file missing when using(performing operations) the DB?
    (will it recover automatically/db abort/even redo log lost will the DB run as usual... ?)
    -How to recover this lost redo log?
    - What will happen if 1 control file missing when starting the DB?
    - What will happen if 1 control file missing when using(performing operations) the DB?
    (will it recover automatically/db abort/even control file lost will the DB run as usual... ?)
    -How to recover this lost redo log?
    thanks

    - What will happen if 1 redo log file missing when starting the DB?IF you have multiplexed the members you can drop the lost file and will be able to open the DB
    What will happen if 1 redo log file missing when using(performing operations) the DB?Again if multiplexed it will drop a warinign in the alert log and contnue to write on othere members
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/recoscen.htm#sthref1385
    - What will happen if 1 control file missing when starting the DB?Just remove the entry from the init.ora and start the DB
    What will happen if 1 control file missing when using(performing operations) the DB?Will shutdown

  • Missing current redo log files

    hello to all
    i have a question please if you can guide me.
    if i lose all current redo log files (current redo log group files) how i can repair it and open
    database ? (i don't have problem by missing INACTIVE redo group)
    thanks

    Hi,
    >>if i lose all current redo log files (current redo log group files) how i can repair it and
    open database ? (i don't have problem by missing INACTIVE redo group)Well, It depends. The database was active when the current log file was lost ? Are you using RMAN ? The database is operating in ARCHIVELOG mode or NOARCHIVEMOG mode ? Basically, an incomplete recovery is necessary when there is a loss of the current redo log files. It means that you don’t have all the redo log files up to the point of failure, so the only alternative is[b] to recover prior to the point of failure. To perform incomplete recovery after the redo log files have been lost, you do the following (if you are not using RMAN):
    1) Execute a SHUTDOWN command and restore all data files (*.dbf) from most recent backup.
    2) Execute a STARTUP MOUNT command to read the contents of the control file.
    3) Execute a RECOVER DATABASE UNTIL CANCEL command to start the recovery process.
    SQL> startup mount;
    4) Execute a RECOVER DATABASE UNTIL CANCEL command to start the recovery process.
    SQL> recover database until cancel;
    5) Apply the necessary archived logs up to, but not including, the lost or corrupted log.
    6) Open the database and reset the log files.
    SQL> alter database open resetlogs;
    7) Shut down the database.
    SQL> shutdown normal;
    8) Take a full cold backup
    In resume, for more information, take a look at [url http://download-west.oracle.com/docs/cd/B19306_01/backup.102/b14191/recoscen008.htm#sthref1872]Recovering After the Loss of Online Redo Log Files: Scenarios
    Cheers
    Legatti

  • Redo Log Missing + AWR Reports

    Hi Techies,
    1)how to start up the database, if my active group of redo is missing or corrupted. can you please suggest me with steps?
    2)What are the main things we need look in the AWR reports. (How to analyze the AWR reports)
    Thanks,
    Tippu

    Hi,
    1)how to start up the database, if my active group of redo is missing or corrupted. can you please suggest me with steps?If your last shutdown was clean then you can follow these steps...
    1. Start mount
    2. Alter database recover until cancel;-------just a fake recovery...nothing done if your database was shutdown cleanly..
    3. Alter database open resetlogs;......This step will recreate the missing or corrupted redo logs
    4. Backup your database
    2)What are the main things we need look in the AWR reports. (How to analyze the AWR reports)Go through the link http://www.nyoug.org/Presentations/2008/Sep/Ault_AWR.pdf
    Regards

  • Standby database is not applying redo logs due to missing archive log

    We use 9.2.0.7 Oracle Database. My goal is to create a physical standby database.
    I have followed all the steps necessary to fulfill this in Oracle Data Guard Concepts and Administration manual. Archived redo logs are transmitted from primary to standby database regularly. But the logs are not applied due to archive log gap.
    SQL> select process, status from v$managed_standby;
    PROCESS STATUS
    ARCH CONNECTED
    ARCH CONNECTED
    MRP0 WAIT_FOR_GAP
    RFS RECEIVING
    RFS ATTACHED
    SQL> select * from v$archive_gap;
    THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
    1 503 677
    I have tried to find the missing archives on the primary database, but was unable to. They have been deleted (somehow) regularly by the existing backup policy on the primary database. I have looked up the backups, but these archive logs are too old to be in the backup. Backup retention policy is 1 redundant backup of each file. I didn't save older backups as I didn't really need them from up to this point.
    I have cross checked (using rman crosscheck) the archive log copies on the primary database and deleted the "obsolete" copies of archive logs. But, v$archived_log view on the primary database only marked those entries as "deleted". Unfortunately, the standby database is still waiting for those logs to "close the gap" and doesn't apply the redo logs at all. I am reluctant to recreate the control file on the primary database as I'm afraid this occurred through the regular database backup operations, due to current backup retention policy and it probably might happen again.
    The standby creation procedure was done by using the data files from 3 days ago. The archive logs which are "producing the gap" are older than a month, and are probably unneeded for standby recovery.
    What shall I do?
    Kind regards and thanks in advance,
    Milivoj

    On a physical standby database
    To determine if there is an archive gap on your physical standby database, query the V$ARCHIVE_GAP view as shown in the following example:
    SQL> SELECT * FROM V$ARCHIVE_GAP;
    THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
    1 7 10
    The output from the previous example indicates your physical standby database is currently missing log files from sequence 7 to sequence 10 for thread 1.
    After you identify the gap, issue the following SQL statement on the primary database to locate the archived redo log files on your primary
    database (assuming the local archive destination on the primary database is LOG_ARCHIVE_DEST_1):
    SQL> SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND 2> SEQUENCE# BETWEEN 7 AND 10;
    NAME
    /primary/thread1_dest/arcr_1_7.arc /primary/thread1_dest/arcr_1_8.arc /primary/thread1_dest/arcr_1_9.arc
    Copy these log files to your physical standby database and register them using the ALTER DATABASE REGISTER LOGFILE statement on your physical standby database. For example:
    SQL> ALTER DATABASE REGISTER LOGFILE
    '/physical_standby1/thread1_dest/arcr_1_7.arc';
    SQL> ALTER DATABASE REGISTER LOGFILE
    '/physical_standby1/thread1_dest/arcr_1_8.arc';
    After you register these log files on the physical standby database, you can restart Redo Apply.
    Note:
    The V$ARCHIVE_GAP fixed view on a physical standby database only returns the next gap that is currently blocking Redo Apply from continuing. After resolving the gap and starting Redo Apply, query the V$ARCHIVE_GAP fixed view again on the physical standby database to determine the next gap sequence, if there is one. Repeat this process until there are no more gaps.
    Restoring the archived logs from the backup set
    If the archived logs are not available in the archive destination then at that time we need to restore the required archived logs from the backup step. This task is accomplished in the following way.
    To restore range specified archived logs:
    Run {
    Set archivelog destination to '/oracle/arch/arch_restore'
    Restore archivelog from logseq=<xxxxx> until logseq=<xxxxxxx>
    To restore all the archived logs:
    Run {
    Set archivelog destination to '/oracle/arch/arch_restore';
    Restore archivelog all;
    }

  • Data Guard Missing Redo Archive Logs

    Hi All Gurus
    I have setup data guard on windows 2008 server sp2 with oracle 10.2.0.4.0 (Both OS & Oracle DB are 64 bits).
    The Network Admin have shutdown Backup server. Now when I checked the Archive status as follows
    1. select * from v$archive_gap;            It shows a gap in archives       e.g. 891 - 920.
    2. SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;                 e.g. 891-920 Not Applied.
    Now I issue following command
    1. SELECT RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS;                                e.g. MANAGED REAL TIME APPLY
    2.  DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; 
    or  ALTER DATABASE RECOVER  managed standby database disconnect from session ;     
                        e.g.      incompatible Media Recovery in Progress
    3. Alert Log says Adjust CONTROL_FILE_RECORD_KEEP_TIME to sufficient limits.
    I have also adjusted CONTROL_FILE_RECORD_KEEP_TIME to 90 days as follows
    4. show parameter control_file          e.g. CONTROL_FILE_RECORD_KEEP_TIME=90
    5. I have checked firewall and tnsping for both Primary and Standby Server e.g. tnsping CVMIS (Primary), CVMISBK (Standby)
         Both are OK. TNSPING is showing 10-30msec delay.
    6. I have checked the web for gap Removal, Mostly are using RMAN method to Backup and then Restore to Standby DB.
          Is there any other way to fill this gap without using RMAN? I mean DG automatically fill it by using some commands
         are settings?
    Kind Regards
    Thunder2777

    Hi CKPT
    Thanks for the scripts which I executed today on 24 Mon 2013. Here are the Results.
    Standby Database Script Output:
    NAME                           DISPLAY_VALUE
    db_file_name_convert
    db_name                            UMIS
    db_unique_name                 UMISBK
    dg_broker_config_file1         C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR1UMISBK.DAT
    dg_broker_config_file2         C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR2UMISBK.DAT
    dg_broker_start                TRUE
    fal_client                          (DESCRIPTION=(ADDRESS_LIST=(AD
                                           DRESS=(PROTOCOL=tcp)(HOST=WIN-
                                           7VSLKL4CGU2)(PORT=1521)))(CONN
                                           ECT_DATA=(SERVICE_NAME=umisbk_
                                           XPT)(INSTANCE_NAME=umisbk)(SER
                                           VER=dedicated)))
    fal_server                         (DESCRIPTION=(ADDRESS_LIST=(AD
                                           DRESS=(PROTOCOL=tcp)(HOST=CV-A
                                           JKDB)(PORT=1521)))(CONNECT_DAT
                                           A=(SERVICE_NAME=umis_XPT)(SERV
                                           ER=dedicated)))
    local_listener
    log_archive_config               DG_CONFIG=(UMIS,UMISBK)
    log_archive_dest_2             SERVICE=UMIS LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=UMIS
    log_archive_dest_state_2           ENABLE
    log_archive_max_processes      10
    log_file_name_convert                E:\oracle\product\10.2.0\flash_recovery_area\UMIS\, D:\ORACLE\FRA\UMISBK
    remote_login_passwordfile         EXCLUSIVE
    standby_archive_dest                D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
    standby_file_management                         AUTO
    NAME       DB_UNIQUE_NAME                 PROTECTION_MODE DATABASE_R OPEN_MODE
    UMIS       UMISBK      MAXIMUM PERFORMANCE PHYSICAL STANDBY MOUNTED
       THREAD# MAX(SEQUENCE#)
             1            890
    PROCESS   STATUS          THREAD#  SEQUENCE#
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CLOSING                   1       1062
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    MRP0      WAIT_FOR_GAP          1        891
    RFS       IDLE                  1       1063
    RFS       IDLE                  0          0
    NAME                           VALUE      UNIT                           TIME_COMPUTED
    apply finish time                         day(2) to second(1) interval
    apply lag                                   day(2) to second(0) interval
    estimated startup time                22         second
    standby has been open              N
    transport lag                             day(2) to second(0) interval
       THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
             1           891            948
    NAME                                                            Size MB    Used MB
    D:\ORACLE\FRA                                                      2048          0
    STANDBY Alert Log:
    Mon Jun 24 10:19:55 2013
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[2]: Assigned to RFS process 1868
    RFS[2]: Identified database type as 'physical standby'
    RFS[2]: Successfully opened standby log 5: 'D:\ORACLE\ORADATA\UMISBK\SLOG02.LOG'
    Mon Jun 24 10:22:09 2013
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Mon Jun 24 10:22:09 2013
    Starting ORACLE instance (normal)
    Mon Jun 24 10:22:09 2013
    alter database mount standby database
    ORA-1154 signalled during: alter database mount standby database...
    Mon Jun 24 10:22:09 2013
    alter database recover managed standby database using current logfile disconnect from session
    Mon Jun 24 10:22:40 2013
    ORA-1153 signalled during: alter database recover managed standby database using current logfile disconnect from session...
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Mon Jun 24 10:24:40 2013
    Starting ORACLE instance (normal)
    Mon Jun 24 10:24:40 2013
    alter database mount standby database
    ORA-1154 signalled during: alter database mount standby database...
    Mon Jun 24 10:24:40 2013
    alter database recover managed standby database using current logfile disconnect from session
    Mon Jun 24 10:25:11 2013
    ORA-1153 signalled during: alter database recover managed standby database using current logfile disconnect from session...
    Mon Jun 24 10:26:46 2013
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Mon Jun 24 10:26:46 2013
    Starting ORACLE instance (normal)
    Mon Jun 24 10:28:04 2013
    alter database mount standby database
    Mon Jun 24 10:28:04 2013
    ORA-1154 signalled during: alter database mount standby database...
    PRIMARY Database Script Output:
    NAME                           DISPLAY_VALUE
    db_file_name_convert           UMIS, UMISBK
    db_name                             UMIS
    db_unique_name                  UMIS
    dg_broker_config_file1           E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR1UMIS.DAT
    dg_broker_config_file2           E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR2UMIS.DAT
    dg_broker_start                   TRUE
    fal_client                             UMIS
    fal_server                            UMISBK
    local_listener
    log_archive_config               DG_CONFIG=(UMIS,UMISBK)
    log_archive_dest_2             service="(DESCRIPTION=(ADDRESS
                                             _LIST=(ADDRESS=(PROTOCOL=tcp)(
                                             HOST=WIN-7VSLKL4CGU2)(PORT=152
                                             1)))(CONNECT_DATA=(SERVICE_NAM
                                             E=umisbk_XPT)(INSTANCE_NAME=um
                                             isbk)(SERVER=dedicated)))",
                                             LGWR ASYNC NOAFFIRM delay=0 O
                                             PTIONAL max_failure=0 max_conn
                                             ections=1   reopen=300 db_uniq
                                             ue_name="umisbk" register net_
                                             timeout=180  valid_for=(online
                                             _logfile,primary_role)
    log_archive_dest_state_2          ENABLE
    log_archive_max_processes      2
    log_file_name_convert               E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\, D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
    remote_login_passwordfile            EXCLUSIVE
    standby_archive_dest
    standby_file_management             AUTO
    NAME       DB_UNIQUE_NAME                 PROTECTION_MODE      DATABASE_R OPEN_MODE  SWITCHOVER_STATUS
    UMIS       UMIS                   MAXIMUM PERFORMANCE  PRIMARY    READ WRITE SESSIONS ACTIVE
       THREAD# MAX(SEQUENCE#)
             1           1062
        Thread Last Sequence Received Last Sequence Applied Difference
             1                   1062                  1062          0
             1                   1062                  1062          0
    SEVERITY        ERROR_CODE timestamp            MESSAGE
    Error                12514 24-JUN-2013 10:08:02 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
    Error                12514 24-JUN-2013 10:08:04 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
    Error                12514 24-JUN-2013 10:08:07 FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    Error                12514 24-JUN-2013 10:08:31 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
    Error                12514 24-JUN-2013 10:08:59 FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    Error                12514 24-JUN-2013 10:14:57 PING[ARC1]: Heartbeat failed to connect to standby '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'. Error is 12514.
    ID STATUS    DB_MODE         TYPE RECOVERY_MODE        PROTECTION_MODE      SRLs ACTIVE ARCHIVED_SEQ#
      1 VALID     OPEN            ARCH IDLE                 MAXIMUM PERFORMANCE     0      0          1062
      2 VALID     UNKNOWN         LGWR UNKNOWN              MAXIMUM PERFORMANCE     4      3          1054
    NAME                                                            Size MB    Used MB
    E:\oracle\product\10.2.0\flash_recovery_area                       2048          0
    Primary Alert Log:
    System parameters with non-default values:
      processes                      = 150
      __shared_pool_size        = 335544320
      __large_pool_size           = 16777216
      __java_pool_size            = 33554432
      __streams_pool_size      = 0
      sga_target                     = 1258291200
      control_files            = E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL01.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL02.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL03.CTL
      db_file_name_convert     = UMIS, UMISBK
      log_file_name_convert    = E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\, D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
      control_file_record_keep_time= 90
      db_block_size                      = 8192
      __db_cache_size                 = 855638016
      compatible                           = 10.2.0.3.0
      log_archive_config                = DG_CONFIG=(UMIS,UMISBK)
      log_archive_dest_1       = location="E:\oracle\product\10.2.0\flash_recovery_area\UMIS\ARCHIVELOG", valid_for=(ONLINE_LOGFILE,ALL_ROLES)
      log_archive_dest_2       = service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))",    LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180  valid_for=(online_logfile,primary_role)
      log_archive_dest_state_1 = ENABLE
      log_archive_dest_state_2 = ENABLE
      log_archive_max_processes= 2
      log_archive_min_succeed_dest= 1
      standby_archive_dest     =
      log_archive_trace        = 0
      log_archive_format       = ARC_s%S_r%R_t%T.arc
      fal_client               = UMIS
      fal_server               = UMISBK
      archive_lag_target       = 0
      db_file_multiblock_read_count= 16
      db_recovery_file_dest    = E:\oracle\product\10.2.0\flash_recovery_area
      db_recovery_file_dest_size= 2147483648
      standby_file_management  = AUTO
      undo_management          = AUTO
      undo_tablespace          = UNDOTBS1
      remote_login_passwordfile= EXCLUSIVE
      db_domain                =
      dispatchers              = (PROTOCOL=TCP) (SERVICE=UMISXDB)
      job_queue_processes      = 10
      audit_file_dest          = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\ADUMP
      background_dump_dest     = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\BDUMP
      user_dump_dest           = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\UDUMP
      core_dump_dest           = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\CDUMP
      db_name                  = UMIS
      open_cursors             = 300
      pga_aggregate_target     = 417333248
      dg_broker_start          = TRUE
    PSP0 started with pid=3, OS id=2824
    MMAN started with pid=4, OS id=2820
    DBW0 started with pid=5, OS id=2396
    LGWR started with pid=6, OS id=2676
    CKPT started with pid=7, OS id=2692
    SMON started with pid=8, OS id=2096
    RECO started with pid=9, OS id=2924
    CJQ0 started with pid=10, OS id=2832
    MMON started with pid=11, OS id=3052
    Mon Jun 24 10:07:34 2013
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    Mon Jun 24 10:07:34 2013
    starting up 1 shared server(s) ...
    MMNL started with pid=12, OS id=2700
    DMON started with pid=15, OS id=2908
    PMON started with pid=2, OS id=2812
    Mon Jun 24 10:07:35 2013
    alter database mount exclusive
    Mon Jun 24 10:07:40 2013
    Setting recovery target incarnation to 2
    Mon Jun 24 10:07:42 2013
    Successful mount of redo thread 1, with mount id 316954407
    Mon Jun 24 10:07:42 2013
    Database mounted in Exclusive Mode
    Completed: alter database mount exclusive
    Mon Jun 24 10:07:42 2013
    alter database open
    Mon Jun 24 10:07:47 2013
    Starting Data Guard Broker (DMON)
    NSV1 started with pid=16, OS id=3552
    Mon Jun 24 10:07:50 2013
    Beginning crash recovery of 1 threads
    parallel recovery started with 7 processes
    INSV started with pid=24, OS id=3628
    Mon Jun 24 10:07:52 2013
    Started redo scan
    Mon Jun 24 10:07:53 2013
    Completed redo scan
    144 redo blocks read, 60 data blocks need recovery
    Mon Jun 24 10:07:53 2013
    Started redo application at
    Thread 1: logseq 1059, block 8380
    Mon Jun 24 10:07:53 2013
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 1059 Reading mem 0
      Mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
    Mon Jun 24 10:07:53 2013
    Completed redo application
    Mon Jun 24 10:07:53 2013
    Completed crash recovery at
    Thread 1: logseq 1059, block 8524, scn 26461769
    60 data blocks read, 60 data blocks written, 144 redo blocks read
    Mon Jun 24 10:07:57 2013
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=25, OS id=3804
    ARC1 started with pid=26, OS id=3808
    Mon Jun 24 10:07:57 2013
    ARC0: Archival started
    ARC1: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    RSM0 started with pid=27, OS id=3812
    LNS1 started with pid=28, OS id=3824
    Mon Jun 24 10:08:01 2013
    Thread 1 advanced to log sequence 1060 (thread open)
    Thread 1 opened at log sequence 1060
      Current log# 1 seq# 1060 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
    Successful open of redo thread 1
    Mon Jun 24 10:08:02 2013
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Mon Jun 24 10:08:02 2013
    ARC1: STARTING ARCH PROCESSES
    Mon Jun 24 10:08:02 2013
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    Mon Jun 24 10:08:02 2013
    ARC2: Archival started
    Mon Jun 24 10:08:02 2013
    ARC1: STARTING ARCH PROCESSES COMPLETE
    ARC2 started with pid=29, OS id=3544
    ARC1: Becoming the heartbeat ARCH
    Mon Jun 24 10:08:02 2013
    LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2
    Error 12514 received logging on to the standby
    LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    Mon Jun 24 10:08:02 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_3824.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    Mon Jun 24 10:08:02 2013
    SMON: enabling cache recovery
    Mon Jun 24 10:08:03 2013
    ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"','   LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180  valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
    Mon Jun 24 10:08:03 2013
    LNS: Failed to archive log 1 thread 1 sequence 1060 (12514)
    Mon Jun 24 10:08:03 2013
    ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
    Mon Jun 24 10:08:03 2013
    ALTER DATABASE OPEN
    Mon Jun 24 10:08:03 2013
    ORA-1531 signalled during: ALTER DATABASE OPEN...
    Mon Jun 24 10:08:04 2013
    Error 12514 received logging on to the standby
    LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    Mon Jun 24 10:08:04 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_3824.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    LNS: Failed to archive log 1 thread 1 sequence 1060 (12514)
    Mon Jun 24 10:08:04 2013
    Successfully onlined Undo Tablespace 1.
    Mon Jun 24 10:08:04 2013
    SMON: enabling tx recovery
    Mon Jun 24 10:08:05 2013
    Database Characterset is WE8MSWIN1252
    Opening with internal Resource Manager plan
    where NUMA PG = 1, CPUs = 8
    Mon Jun 24 10:08:06 2013
    Error 12514 received logging on to the standby
    Mon Jun 24 10:08:06 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    FAL[server, ARC1]: FAL archive failed, see trace file.
    Mon Jun 24 10:08:07 2013
    replication_dependency_tracking turned off (no async multimaster replication found)
    Mon Jun 24 10:08:07 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
    ORA-16055: FAL request rejected
    Mon Jun 24 10:08:07 2013
    ARCH: FAL archive failed. Archiver continuing
    Mon Jun 24 10:08:08 2013
    Starting background process QMNC
    QMNC started with pid=28, OS id=3984
    Mon Jun 24 10:08:15 2013
    db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Mon Jun 24 10:08:15 2013
    Completed: alter database open
    Mon Jun 24 10:08:19 2013
    ALTER SYSTEM SET standby_archive_dest='' SCOPE=BOTH SID='umis';
    Mon Jun 24 10:08:19 2013
    ALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='umis';
    Mon Jun 24 10:08:19 2013
    ALTER SYSTEM SET log_archive_format='ARC_s%S_r%R_t%T.arc' SCOPE=SPFILE SID='umis';
    Mon Jun 24 10:08:20 2013
    ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';
    Mon Jun 24 10:08:20 2013
    ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';
    Mon Jun 24 10:08:20 2013
    ALTER SYSTEM SET log_archive_max_processes=2 SCOPE=BOTH SID='*';
    Mon Jun 24 10:08:21 2013
    ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';
    Mon Jun 24 10:08:21 2013
    ALTER SYSTEM SET db_file_name_convert='UMIS','UMISBK' SCOPE=SPFILE;
    Mon Jun 24 10:08:21 2013
    ALTER SYSTEM SET log_file_name_convert='E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\','D:\ORACLE\FRA\UMISBK\ARCHIVELOG\' SCOPE=SPFILE;
    Mon Jun 24 10:08:21 2013
    ALTER SYSTEM ARCHIVE LOG
    Mon Jun 24 10:08:21 2013
    Thread 1 cannot allocate new log, sequence 1061
    Private strand flush not complete
      Current log# 1 seq# 1060 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
    Mon Jun 24 10:08:22 2013
    Shutting down archive processes
    Mon Jun 24 10:08:22 2013
    Thread 1 advanced to log sequence 1061 (LGWR switch)
    Mon Jun 24 10:08:22 2013
      Current log# 2 seq# 1061 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO02.LOG
    Mon Jun 24 10:08:27 2013
    ARCH shutting down
    ARC2: Archival stopped
    Mon Jun 24 10:08:27 2013
    ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"','   LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180  valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
    Mon Jun 24 10:08:27 2013
    ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
    Mon Jun 24 10:08:27 2013
    ALTER SYSTEM ARCHIVE LOG
    Mon Jun 24 10:08:27 2013
    Thread 1 cannot allocate new log, sequence 1062
    Private strand flush not complete
      Current log# 2 seq# 1061 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO02.LOG
    LNS1 started with pid=29, OS id=4204
    Mon Jun 24 10:08:31 2013
    Thread 1 advanced to log sequence 1062 (LGWR switch)
      Current log# 3 seq# 1062 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
    Mon Jun 24 10:08:31 2013
    Error 12514 received logging on to the standby
    LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    Mon Jun 24 10:08:31 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_4204.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    LNS: Failed to archive log 3 thread 1 sequence 1062 (12514)
    Mon Jun 24 10:08:59 2013
    Error 12514 received logging on to the standby
    Mon Jun 24 10:08:59 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    FAL[server, ARC1]: FAL archive failed, see trace file.
    Mon Jun 24 10:08:59 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing
    Mon Jun 24 10:14:57 2013
    Error 12514 received logging on to the standby
    Mon Jun 24 10:14:57 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    PING[ARC1]: Heartbeat failed to connect to standby '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'. Error is 12514.
    Mon Jun 24 10:18:46 2013
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    Mon Jun 24 10:19:23 2013
    ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"','   LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180  valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
    Mon Jun 24 10:19:23 2013
    ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
    Mon Jun 24 10:19:23 2013
    ALTER SYSTEM ARCHIVE LOG
    Mon Jun 24 10:19:24 2013
    Thread 1 cannot allocate new log, sequence 1063
    Private strand flush not complete
      Current log# 3 seq# 1062 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
    LNS1 started with pid=18, OS id=4300
    Mon Jun 24 10:19:28 2013
    Thread 1 advanced to log sequence 1063 (LGWR switch)
      Current log# 1 seq# 1063 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
    Mon Jun 24 10:19:28 2013
    LNS: Standby redo logfile selected for thread 1 sequence 1063 for destination LOG_ARCHIVE_DEST_2
    Mon Jun 24 10:19:58 2013
    ARC1: Standby redo logfile selected for thread 1 sequence 1062 for destination LOG_ARCHIVE_DEST_2
    Well there seems to be some connectivity issue on Primary DB (I Guess!!!).
    But when I issue tnsping from Primary Database, the result is
    SQL> host tnsping umisbk (Standy DB Name)  --->   Status: OK [10-30msec]
    And when I issue tnsping from Standby Database, the result is
    SQL> host tnsping umis (Primary DB Name)    --->   Status: OK [10-30msec]
    So what your Recommendation.
    Kind Regards
    Thuhnder2777

  • Online redo log files being removed physically

    Grid Infra version: 11.2.0.4
    RDBMS Version: 11.2.0.4
    Although this is a RAC DB, this is not a RAC-specific question. Hence posting it here.
    Few months back, I remember issuing a command similair to below (DROP LOGFILE GROUP ...) and the redo log files were still physically present in the diskgroup.
    If I remember correctly, the file is not deleted physical so that we can use the REUSE functionality (ALTER DATABASE ADD LOGFILE MEMBER '+REDO/orcl/onlinelog/redo1b.log' reuse to group 11; ) ie. you can use the REUSE command to add the logfile of the same name which is physically present in OS Filesystem/Diksgroup to redo log group.
    But today, after I issued the below command, I checked the diskgroup location from ASMCMD
    SQL> alter database drop logfile group 31;
    Database altered.
    From ASMCMD, I can that the file has disappeared physically. Is this a new feature with 11.2.0.4 or am I missing something here ?
    ASMCMD> ls +DATA/msblprd/onlinelog/group_31.548.833154995
    ASMCMD-8002: entry 'group_31.548.833154995' does not exist in directory '+DATA/msblprd/onlinelog/'

    Just to add to what Aman has said.
    It is a bad practice not to let OMF decide the placement of Online redo logs because of this issue especially when you use ASM.
    Executing rm command in Linux/Unix is easy but Dropping ASM aliases in the disk group can be a hassle.
    This is documented.
    "When a redo log member is dropped from the database, the operating system file is not deleted from disk. Rather, the control files of the associated database are updated to drop the member from the database structure. After dropping a redo log file, ensure that the drop completed successfully, and then use the appropriate operating system command to delete the dropped redo log file."
    http://docs.oracle.com/cd/E11882_01/server.112/e25494/onlineredo.htm#ADMIN11324
    BTW . You don't even need to set  db_create_online_log_dest_n to enable OMF for ORLs.
    SQL> show parameter log_dest
    NAME                                 TYPE        VALUE
    db_create_online_log_dest_1          string
    db_create_online_log_dest_2          string
    db_create_online_log_dest_3          string
    db_create_online_log_dest_4          string
    db_create_online_log_dest_5          string
    SQL> show parameter db_create_file_dest
    NAME                                 TYPE        VALUE
    db_create_file_dest                  string      +MBL_DATA
    alter database add logfile thread 4
    group 31 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 32 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 33 ('+MBL_DATA','+MBL_FRA') size 4096M,
    group 34 ('+MBL_DATA','+MBL_FRA') size 4096M ;
    Database altered.
    And redo logs will be neatly placed as shown below
       INST     GROUP# MEMBER                                             STATUS           ARC
             4         31 +MBL_DATA/bsblprd/onlinelog/group_31.276.832605441 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_31.297.832605445  UNUSED           YES
                       32 +MBL_DATA/bsblprd/onlinelog/group_32.547.832605451 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_32.372.832605457  UNUSED           YES
                       33 +MBL_DATA/bsblprd/onlinelog/group_33.548.832605463 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_33.284.832605469  UNUSED           YES
                       34 +MBL_DATA/bsblprd/onlinelog/group_34.549.832605475 UNUSED           YES
                          +MBL_FRA/bsblprd/onlinelog/group_34.359.832605481  UNUSED           YES

  • Recover database without controlfile and redo logs

    Hi guys,
    I am doing a testing with an Oracle Database 11.1.0.7.0, I want recover a database in this scenario without using RMAN:
    -All controlfiles are missing
    -All redo logs are missing
    -I have a Backup Controlfile To Trace Resetlogs (bkp_controlfile.sql)
    -The database is in archivelog mode
    -The database was created with OMF (Oracle Managed Files)
    So I have done this steps:
    1) When the database was opened I rename all controlfiles and all redo logs
    2) Shutdown Abort
    3) I run the bkp_controlfile.sql, here I have a problem...
    The database put in NOMOUNT, the controlfile was created and started the RECOVER DATABASE USING BACKUP CONTROLFILE, but when run ALTER DATABASE OPEN RESETLOGS; appear this:
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1:
    '/u02/app/oracle/oradata/OMF/datafile/o1_mf_system_68hzcb2z_.dbf'I wasn´t expect this because I don´t want recover a datafile, I only want open with resetlogs.
    Any suggestion to help me?
    Thanks a lot.

    Excelent! Thanks for your answers Markus and Hemant.
    In conclusion...
    - If we have all redo logs availables we can recreate the control file and recover the database without any problems using backup controlfile to trace noresetlogs*.
    - if we haven´t all redo logs availables, there are 2 situations:
    1) If the database shutdown properly:_ We will be able to open the database using recover database using backup controlfile until cancel*.
    2) If the database doesn´t shutdown properly:_ We won´t be able to open the database with only a backup controlfile to trace.
    With all this I close this thread. Was very good experience.
    If anyone would add something will be welcome.
    Thanks for all
    I wish add the results of one of my tests: if I did all the steps in only one session of sqlplus I can shutdown properly the database, but if do the shutdown immediate* in a new session I can´t shutdown properly the database. Here I post the output:
    ALL IN ONE SESSION*
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Database mounted.
    Database opened.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> @/home/oracle/bkp_controlfile.sql
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Control file created.
    SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
    ORA-00279: change 398764 generated at 09/22/2010 14:09:49 needed for thread 1
    ORA-00289: suggestion :
    /u02/app/oracle/flash_recovery_area/OMF/archivelog/2010_09_22/o1_mf_1_40_%u_.arc
    ORA-00280: change 398764 for thread 1 is in sequence #40
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    Media recovery cancelled.
    SQL> ALTER DATABASE OPEN RESETLOGS;
    Database altered.
    SQL> ALTER TABLESPACE TEMP ADD TEMPFILE '/u02/app/oracle/oradata/OMF/datafile/o1_mf_temp_69n3z3vv_.tmp' SIZE 50331648  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
    Tablespace altered.
    SQL>
    ALL IN DIFERENT SESSIONS*
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:55:47 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/home/oracle/bkp_controlfile.sql' RESETLOGS;
    Database altered.
    SQL> SHUTDOWN IMMEDIATE
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP MOUNT
    ORACLE instance started.
    Total System Global Area  631914496 bytes
    Fixed Size                  1315224 bytes
    Variable Size             377491048 bytes
    Database Buffers          247463936 bytes
    Redo Buffers                5644288 bytes
    Database mounted.
    SQL> ALTER DATABASE ARCHIVELOG;
    Database altered.
    SQL> ALTER DATABASE OPEN;
    Database altered.
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    System altered.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@prueba ~]$ $ORACLE_HOME/bin/sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Wed Sep 22 13:58:10 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> SHUTDOWN IMMEDIATE
    ORA-00210: cannot open the specified control file
    ORA-00202: control file: '/u02/app/oracle/oradata/OMF/controlfile/o1_mf_69n3x6n5_.ctl'
    ORA-27041: unable to open file
    Linux Error: 2: No such file or directory
    Additional information: 3

  • [DG Physical] ORA-00368: checksum error in redo log block

    Hi all,
    I'm building a DR solution with 1 primary & 2 DR site (Physical).
    All DBs use Oracle 10.2.0.3.0 on Solaris 64bit.
    The first one ran fine for some days (6), then I installed the 2nd. After restoring the DB (DUPLICATE TARGET DATABASE FOR STANDBY) & ready to apply redo. The DB fetched missing arc gaps & I got the following error:
    ==================
    Media Recovery Log /global/u04/recovery/billhcm/archive/2_32544_653998293.dbf
    Errors with log /global/u04/recovery/billhcm/archive/2_32544_653998293.dbf
    MRP0: Detected read corruption! Retry recovery once log is re-fetched...
    Wed Jan 27 21:46:25 2010
    Errors in file /u01/oracle/admin/billhcm/bdump/billhcm1_mrp0_12606.trc:
    ORA-00368: checksum error in redo log block
    ORA-00353: log corruption near block 1175553 change 8236247256146 time 01/27/2010 18:33:51
    ORA-00334: archived log: '/global/u04/recovery/billhcm/archive/1_47258_653998293.dbf'
    Managed Standby Recovery not using Real Time Apply
    Recovery interrupted!
    Recovered data files to a consistent state at change 8236247255373
    ===================
    I see that may be RFS get the file incorrectly so I ftp to get this file & continue the apply, it pass. Comparison the RFS file & ftp is difference. At that time, I think that something wrong with the RFS because the content of arc is not right. (I used BACKUP VALIDATE ARCHIVELOG SEQUENCE BETWEEN N1 AND N2 THREAD X to check all arcs the RFS fetched, there was corrupt in every file);
    I restore the DR DB again & apply incremental backup from the primary, now it run well. I don't know what's happening as I did the same procedures for all DR DB.
    Yesterday night, I have to stop & restart DR site 1. Today, I check and it got the same error as the 2nd site, with corrupted redo. I try to delete the arcs, & let RFS to reget it, but the files were corrupt too.
    If this continue to happen with the 2nd site again, that'll be a big problem.
    The DR site 1 & Primary is linked by a GB switch, site 2 by a 155Mbps connection (far enough for my db load at about 1.5MB/s avg apply rate).
    I seach Oracle support (metalink) but no luck, there is a case but it mentions max_connection>1 (mine is default =1)
    Can someone show me how to troubleshooting/debug/trace this problem.
    That would be a great help!
    Thank you very much.

    This (Replication) is the wrong forum for your posting.
    Please post to the "Database - General" forum at
    General Database Discussions
    But, first, log an SR with Oracle Support.
    Hemant K Chitale

  • Mv control files, redo.log, database fies

    Hello,
    I installed Oracle 10.2. on Unix.
    we have created file systems for our data/control files.
    some how we missed that part to define location for dbf, control & redo.log files during installation.
    My question is how to mv all control files, redo.log and dbf files to one location to another.
    for. eg:
    currently there are installed in /opt/oracle/oradata.
    now i want o move in /u03/oradata.
    Please note:
    Prior to that I'd like to put in archive log mode.
    shutdown immediate;
    startup mount;
    alter database archivelog;
    alter database open;
    DN

    For DB and Redo files
    conn / as sysdba
    shutdown immediate;
    startup mount
    host
    $ cp old_name new_name
    $ exit
    alter database rename file old_name
    to new_name;
    alter database open
    host
    $ rm old_name
    $ exitFor control files
    1. Shut down the database.
    2. Copy an existing control file to a different locations, using operating system commands.
    3. Edit the CONTROL_FILES parameter in the database's initialization parameter file to add the new control file's name, or to change the existing control filename.
    4. start the database.
    Message was edited by:
    tekicora

  • Removing Redo Log Files? What's Normal?

    Hello,
    I'm new to Oracle and I've been using Informix for years. We currently have Oracle 9.2 running on Windows 2000 Server machine and apparently the redo log files keep filling up the disk drives they reside on. This is happening about every two weeks since we go out and delete the files when we remember.
    My question is does Oracle have a "normal" way of removing old redo logs automatically rather than having to remove them manually? In the Informix world I can set the logical logs so that they write over previously used logs once they are no longer used. Is there a similar way to configure Oracle?
    Thanks for helping out.
    Gregg Walker

    Do not delete your old log files: you need them.
    That's how Oracle does recovery when you lose a datafile or a drive. You copy over the missing stuff from your back-up and then Oracle re-applies the chnages from the REDO logs thereby bringing your database back up to date. No work lost. Result!
    Of course, if you don't take up a backup then holding on to REDO logs is pointless. In which case, set the database to run in NOARCHIVELOG mode.
    However, I strongly advise you to run in ARCHIVELOG mode. You may find this part of the administrator's guide informative: http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96521/archredo.htm#4553
    Cheers, APC

  • Logmnr/capure error b'coz of corruption of redo log block

    Hi,
    We all know that capture process reads the REDO entries from redo log files or archived log files. Therefore we need to ahev db in ARCHIVELOG mode.
    In alert log file, I found error saying :
    Creating archive destination LOG_ARCHIVE_DEST_1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION01\1_36.ARC'
    ARC0: Log corruption near block 66922 change 0 time ?
    ARC0: All Archive destinations made inactive due to error 354
    Fri Apr 04 12:57:44 2003
    Errors in file e:\oracle\admin\repf\bdump\trishul_arc0_1724.trc:
    ORA-00354: corrupt redo log block header
    ORA-00353: log corruption near block 66922 change 0 time 04/04/2003 11:05:40
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    As a normal practice, we do have multiplexing of redo log files at diff location, but even that second copy of redo log is of no use to recover the redo log. This explains redo log could not be archived, since it can't be read. Same is true even for Logmnr process, it could not read the redo log file and it failed. Now, we have wae to recover from this situation (as far as DB is concern, not Stream Replication), since the shutdown after this error was IMMEDIATE causing checkpoing, and rollback/rollforward is not required during system startup. (No instance recovery) We can make db NOARCHIVELOG mode, drop that particular group, and create new one, and turn db to ARCHIVELOG mode This will certainly serve the purpose as far as consistency of DB is concern.
    Here is a catch for Stream Replication. The redo log that got corrupted must be having few transaction which are not being archived, and each will be having corresponding SCN. Now, Capture Process read the info sequentially in order of SCN. Few transaction are now missed, and Capture process can't jump to next SCN skipping few SCN in between. So, we have to re-instantiate the objects on the another system which has no erros, and start working on it. My botheration is what will happen to those missed transaction on the another database. It's absolete loss of the data. In development I can manage that. But in real time Production stage, this is a critical situation. How to recover from this situation to get back the corrupted info from redo log ?
    I have not dropped any of the log group yet. B'coz I would like to recover from this situation without LOSS of data.
    Thanx, & regards,
    Kamlesh Chaudhary
    Content of trace files :
    Dump file e:\oracle\admin\repf\bdump\trishul_arc0_1724.trc
    Fri Apr 04 12:57:31 2003
    ORACLE V9.2.0.2.1 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.2.0 - Production
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Instance name: trishul
    Redo thread mounted by this instance: 1
    Oracle process number: 16
    Windows thread id: 1724, image: ORACLE.EXE
    *** SESSION ID:(13.1) 2003-04-04 12:57:31.000
    - Created archivelog as 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION02\1_36.ARC'
    - Created archivelog as 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION01\1_36.ARC'
    *** 2003-04-04 12:57:44.000
    ARC0: All Archive destinations made inactive due to error 354
    *** 2003-04-04 12:57:44.000
    kcrrfail: dest:2 err:354 force:0
    *** 2003-04-04 12:57:44.000
    kcrrfail: dest:1 err:354 force:0
    ORA-00354: corrupt redo log block header
    ORA-00353: log corruption near block 66922 change 0 time 04/04/2003 11:05:40
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    *** 2003-04-04 12:57:44.000
    ARC0: Archiving not possible: error count exceeded
    ORA-16038: log 2 sequence# 36 cannot be archived
    ORA-00354: corrupt redo log block header
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG
    Dump file e:\oracle\admin\repf\udump\trishul_cp01_2048.trc
    Fri Apr 04 12:57:27 2003
    ORACLE V9.2.0.2.1 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.2.0 - Production
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Instance name: trishul
    Redo thread mounted by this instance: 1
    Oracle process number: 30
    Windows thread id: 2048, image: ORACLE.EXE (CP01)
    *** 2003-04-04 12:57:28.000
    *** SESSION ID:(27.42) 2003-04-04 12:57:27.000
    TLCR process death detected. Shutting down TLCR
    error 1280 in STREAMS process
    ORA-01280: Fatal LogMiner Error.
    OPIRIP: Uncaught error 447. Error stack:
    ORA-00447: fatal error in background process
    ORA-01280: Fatal LogMiner Error
    **********************

    I have the similar problem - I am using Steams environment, and have got this
    "ORA-00353: log corruption near block" errors in the alert.log file
    during capture the changes on the primary database, and Capture
    process became aborted after that.
    Was that transactions lost, or after i've started the Capture process
    again the were captured and send to the target database?
    Have anyone solved that problem?
    Can you help me with it?

Maybe you are looking for

  • No longer able to authorize or deauthorize account

    Everything was working fine until I did a fresh install. COMPLETE CLEAN install (no residue of that pesky old install!) Now I cannot Authorize/Deauthorize/Buy or access my account in any way. All I get is a never-ending "Accessing iTunes Store-". I c

  • Dynamic variable names and invalid_character_err

    I'm neither an expert at structure notation nor dynamic variable naming conventions and would appreciate any help with the following. Thanks! This code works fine. <cfset idx="123"> <cfset form.product[idx]=StructNew()> <cfparam name="form.product[id

  • The Prompt on combo box is not disappearing after a value is selected.

    Hi guys, I am putting in the prompt "Course Category" which starts off black and when a value is selected it turns grey but doesn't disappear, obscuring the selected value. I have tried putting in the line course_step1.prompt = ""; in the post select

  • Remove unnecessary files on disk

    I keep getting messages to make more room on disk, but cannot firgure out how to do that

  • Need a procedure or a pl/sql block

    Dear all, I have a 2tables emp_address, address as below: create table emp_address(emp_id varchar2(10),address varchar2(100)); Insert into EMP_ADDRESS (EMP_ID, ADDRESS) Values ('101', 'street1     fremont     CA     94538'); Insert into EMP_ADDRESS (