ORA-00258: manual archiving in NOARCHIVELOG mode must identify log

Hi I am new to oracle streams. I am trying to setup a one way replication from one database to another using Oracle 10g (10.2.0.1.0) on Windows XP SP3 (32 bit).
I ran the following proc as the streams admin schema:
begin
dbms_streams_adm.maintain_schemas(
schema_names => 'XXCOW',
source_directory_object => 'repl_exp_dir',
destination_directory_object => 'repl_imp_dir',
source_database => 'PWBSD',
destination_database => 'PDVSD',
perform_actions => true,
dump_file_name => 'exp_app23.dmp',
capture_queue_table => 'rep_capt_table',
capture_queue_name => 'rep_capt_queue',
capture_queue_user => NULL,
apply_queue_table => 'rep_dest_table',
apply_queue_name => 'rep_dest_queue',
apply_queue_user => NULL,
capture_name => 'capture_pubs',
propagation_name => 'prop_pubs',
apply_name => 'apply_pubs',
log_file => 'exp_app23.log',
bi_directional => false,
include_ddl => true,
instantiation => dbms_streams_adm.instantiation_schema);
end;
The script failed the first time because i forgot to configure the source database in archive log mode.
The steps i followed to change to archivelog mode:
SQL> select name from v$database;
NAME
PWBSD
SQL> alter system set LOG_ARCHIVE_DEST = 'D:\data\oracle\oradata\PWBSD\archive' scope=both;
System altered.
SQL> conn sys/sys@pwbsd as sysdba
Connected.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 197135236 bytes
Database Buffers 406847488 bytes
Redo Buffers 7135232 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL>
I configured it in archive log mode and ran the proc above again.
I got the following output this time:
job finished
begin
ERROR at line 1:
ORA-23616: Failure in executing block 90 for script
959ECF1D1159402A8C16687AE5E3B5CD
ORA-06512: at "SYS.DBMS_RECOVERABLE_SCRIPT", line 457
ORA-06512: at "SYS.DBMS_STREAMS_MT", line 2201
ORA-06512: at "SYS.DBMS_STREAMS_MT", line 7486
ORA-06512: at "SYS.DBMS_STREAMS_ADM", line 2624
ORA-06512: at "SYS.DBMS_STREAMS_ADM", line 2685
ORA-06512: at line 2
I ran the following to check the error:
select * from dba_recoverable_script_errors;
The output is:
SCRIPT ID: 959ECF1D1159402A8C16687AE5E3B5CD
BLOCK NUM: 90
ERROR_NUMBER: -258
ERROR_MESSAGE: ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
ORA-06512: at "SYS.DBMS_RECO_SCRIPT_INVOK", line 129
ORA-06512: at "SYS.DBMS_STREAMS_RPC", line 358
It seemed like it was still complaining about archive log mode,
I verified that the PWBSD db is in archivelog mode by running the following:
select name, log_mode from v$database;
NAME: PWBSD
LOG_MODE: ARCHIVELOG
What could be the problem and how do i proceed to fix it?

Hi Parthiv,
The steps given by you is not clear.
please try to fallow the steps given in the below link. It may be helpful to you to setup schema level streams:
http://gssdba.wordpress.com/2011/04/20/steps-to-implement-schema-level-oracle-streams/
Thanks and Regards,
Satish.G.S
gssdba.wordpress.com

Similar Messages

  • Change Data Capture on a db in NoArchivelog mode

    I am trying to test an implementation of CDC on a database in noarchivelog mode, but I'm not having much success. All the documentation I've read does not make it sound like it is required, but there are no guides on doing it. I am attempting to use the Asynchronous HotLog method on a 10.2 instance. The (first) error I am running into occurs after trying to create a change set via DMBS_CDC_PUBLISH.CREATE_CHANGE_SET:
    ERROR at line 1:
    ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
    ORA-06512: at "SYS.DBMS_CAPTURE_ADM_INTERNAL", line 121
    ORA-06512: at line 1
    ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 560
    ORA-06512: at line 2

    I'm afraid this is not possible!!!!

  • ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

    Hi All
    Its my first time to use RMAN in our ERP EBSR12
    our database version is 11g
    Please help how to resolv and make successfully backup
    RMAN> backup database;
    Starting backup at 24-JAN-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/24/2011 11:18: 25
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    continuing other job steps, job failed will not be re-run
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    channel ORA_DISK_1: starting piece 1 at 24-JAN-11
    channel ORA_DISK_1: finished piece 1 at 24-JAN-11
    piece handle=/oracle/mybackup_db/PROD2/backupset/2011_01_24/o1_mf_ncnnf_TAG20110 124T111824_6msvw4cv_.bkp tag=TAG20110124T111824 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/24/2011 11:18: 25
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    RMAN>
    Thanks

    ORA-19602: cannot backup or copy active file in NOARCHIVELOG modeIs your database in archivelog or noarchivelog mode?
    How to Turn Archiving ON and OFF [ID 69739.1]
    Please also see these docs/links.
    ORA-19602 Using RMAN to Backup Database [ID 246183.1]
    COLD RMAN backup fails: Ora-19602 even after SHUTDOWN IMMEDIATE and STARTUP MOUNT [ID 373828.1]
    Backup & Recovery
    http://www.oracle.com/pls/db112/portal.portal_db?selected=14&frame=#backup_and_recovery
    Thanks,
    Hussein

  • ORA-01152 when restoring from RMAN backupset in NOARCHIVELOG mode

    Hi all,
    I got the error ORA-01152 when I tried restoring an Oracle 10g R1 database from an RMAN backupset into a new server. The error returned when it reached to the level of opening the database in resetlogs.
    The database runs on NOARCHIVELOG mode and on Windows 2003 Server SP2 32-bit.
    Following is what I did in RMAN:
    set ORACLE_HOME=D:\oracle\product\10.1.0\db_1
    set ORACLE_SID=DAWA
    set PATH=D:\oracle\product\10.1.0\db_1\bin;%PATH%
    cd %ORACLE_HOME%\bin
    rman target sys/mypassword
    Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 13 00:36:55 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database (not started)
    RMAN> startup nomount pfile=X:\temp\DawaPFILE.ORA
    connected to target database (not started)
    Oracle instance started
    Total System Global Area 1048576000 bytes
    Fixed Size 792200 bytes
    Variable Size 551807352 bytes
    Database Buffers 494927872 bytes
    Redo Buffers 1048576 bytes
    RMAN> restore controlfile from
    'X:\temp\Flash_Rec\DAWA\AUTOBACKUP\2011_07_16\O1_
    MF_S_756655133_7226R018_.BKP';
    Starting restore at 19-JUL-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=270 devtype=DISK
    channel ORA_DISK_1: restoring controlfile
    channel ORA_DISK_1: restore complete
    output filename=D:\ORACLE\ORADATA\DAWA\CONTROL01.CTL
    output filename=D:\ORACLE\ORADATA\DAWA\CONTROL02.CTL
    output filename=D:\ORACLE\ORADATA\DAWA\CONTROL03.CTL
    Finished restore at 17-AUG-11
    alter database mount;
    database mounted
    catalog backuppiece 'X:\temp\PUMHJATD_1_1';
    catalog backuppiece 'X:\temp\PTMHJ91Q_1_1';
    /* Rename the Redologfiles,so that they can be created in new locations
    the database is opened in resetlogs */
    SQL>conn sys as sysdba
    -- get registered files from SELECT * FROM V$LOGFILE
    SQL> alter database rename file
    'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO01.LOG' to
    'X:\oracle\oradata\dawa\REDO01.LOG';
    alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO02.LOG'
    to 'X:\oracle\oradata\dawa\REDO02.LOG';
    alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO03.LOG'
    to 'X:\oracle\oradata\dawa\REDO03.LOG';
    alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO04.LOG'
    to 'X:\oracle\oradata\dawa\REDO04.LOG';
    alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO05.LOG'
    to 'X:\oracle\oradata\dawa\REDO05.LOG';
    alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO06.LOG'
    to 'X:\oracle\oradata\dawa\REDO06.LOG';
    alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO07.LOG'
    to 'X:\oracle\oradata\dawa\REDO07.LOG';
    /* Now in RMAN: restore the datafiles
        to new locations and recover. */
    RMAN> run{
    set newname for datafile
    'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS201' TO
    'D:\oracle\oradata\dawa\UNDOTBS201';
    set newname for datafile
    'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS202' TO
    'D:\oracle\oradata\dawa\UNDOTBS202';
    restore database;
    switch datafile all;
    alter database open resetlogs;
    .../*  alter database open resetlogs returned the errors: */
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 08/18/2011 08:44:45
    ORA-01152: file 2 was not restored from a sufficiently old backup
    ORA-01110: data file 2: 'D:\ORACLE\ORADATA\DAWA\UNDOTBS206'Thanks in advance.

    SYS @ DAWA> shutdown immediate
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SYS @ DAWA> startup mount
    ORACLE instance started.
    Total System Global Area 1048576000 bytes
    Fixed Size                   792200 bytes
    Variable Size             551807352 bytes
    Database Buffers          494927872 bytes
    Redo Buffers                1048576 bytes
    Database mounted.
    SYS @ DAWA> recover database using backup controlfile until cancel;
    ORA-00279: change 329012 generated at 03/08/2005 16:24:46 needed for thread 1
    ORA-00289: suggestion :
    X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC
    ORA-00280: change 329012 for thread 1 is in sequence #6
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log
    'X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: 'X:\ORACLE\ORADATA\DAWA\SYSTEM01.DBF'You can download the alert log from here:
    http://ahmedbaraka.com/temp/alertdawa.log

  • ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode

    Hi All,
    Need help from the gurus.
    Currently we are in state unable to do anything.
    Was using a database and all of a sudden it crashed. Tried to mount the database, open it, it failed. Also tried the recover and alter database open, even that failed. Errors are as follows.
    Errors in file e:\oracle\product\10.2.0 \admin\devrevdb\bdump\devrevdb_p000_2620.trc:
    ORA-00603: ORACLE server session terminated by fatal error
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-00449: background process 'DBW0' unexpectedly terminated with error 1242
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    In my spfile, the administrator has set only two control files and there is no mirroring and hence do not have another control file that will help me boot the db.
    Please let me know how I should go about it. I am only a timebeing person trying to carryout a db activity. Any help would be of great help.

    Hemant,
    thanks for the reply.
    I tried the way you suggested and it threw an error.
    ORA-01145: offline immediate disallowed unless media recovery enabled
    I searched and found that an additional tag of drop needs to be added to the command which you suggested.
    ALTER DATABASE DATAFILE '<filename>' OFFLINE DROP.
    i don't know what will the drop command have an effect ?
    i have copied the data file to another location. Since i don't know much, i just want to be sure of what im doing.
    if the above command is successfull, will it drop the datafile or the tablespace and i can no more use it. How can i use the copied datafile.
    Thanks,
    Sachin
    I

  • Taking the datafile offline when the database is in NOARCHIVELOG mode

    My question is when the database is in No Archive log mode i'm not able to take the datafile offline.
    When i tried in my computer i have noticed fallowing.
    case1:
    SYS>alter database datafile 5 offline;
    ERROR at line1;
    ORA-01145:offline immediate disallowed unless media recovery enabled.
    case 2:
    SYS>alter database datafile 5 offline immediate;
    ERROR at line 1;
    ORA-00933:SQL command not properly ended
    case3:
    I have tried the command alter database datafile 6 offline drop; (in NOARCHIVELOG mode) and it is showing the same effect as alter database datafile 6 offline; ( in ARCHIVELOG mode).
    *In the NOARCHIVELOG mode are we really dropping the datafile to take the datafile offline? Will you please tell me the effect of keyword drop.

    JohnWatson wrote:
    You've marked your question answered - was that a mistake?
    The answer is that you cannot directly take a datafile offline in noarchivelog mode. You must take the tablespace offline:
    Hmm, are you certain about that? Perhaps I'm missing something.
    SQL> select file_id, file_name, online_status, status from dba_data_files where tablespace_name = 'USERS';
       FILE_ID FILE_NAME                                          ONLINE_ STATUS
             4 /u01/app/oracle/oradata/TEST/users01.dbf           ONLINE  AVAILABLE
    SQL> select log_mode from v$database;
    LOG_MODE
    NOARCHIVELOG
    SQL> alter database datafile 4 offline drop;
    Database altered.
    SQL> select file_id, file_name, online_status, status from dba_data_files where tablespace_name = 'USERS';
       FILE_ID FILE_NAME                                          ONLINE_ STATUS
             4 /u01/app/oracle/oradata/TEST/users01.dbf           RECOVER AVAILABLE
    SQL>  ALTER SYSTEM FLUSH BUFFER_CACHE;  <-- may not have been necessary
    System altered.
    SQL> select count(*) from scott.emp;
    select count(*) from scott.emp
    ERROR at line 1:
    ORA-00376: file 4 cannot be read at this time
    ORA-01110: data file 4: '/u01/app/oracle/oradata/TEST/users01.dbf'
    SQL> recover datafile 4;
    Media recovery complete.
    SQL> select file_id, file_name, online_status, status from dba_data_files where tablespace_name = 'USERS';
       FILE_ID FILE_NAME                                          ONLINE_ STATUS
             4 /u01/app/oracle/oradata/TEST/users01.dbf           OFFLINE AVAILABLE
    SQL> alter database datafile 4 online;
    Database altered.
    SQL> select file_id, file_name, online_status, status from dba_data_files where tablespace_name = 'USERS';
       FILE_ID FILE_NAME                                          ONLINE_ STATUS
             4 /u01/app/oracle/oradata/TEST/users01.dbf           ONLINE  AVAILABLE
    SQL> select count(*) from scott.emp;
      COUNT(*)
            14
    Also, please see the following link from the manual which discusses altering data file availability in noarchivelog mode.
    Altering Datafile Availability

  • ORA-00255: error archiving log

    When i changing noarchivelog mode on archivelog and online logs must archiveing
    I send this message from trace file.
    *** SESSION ID:(3.1) 2005.02.15.12.09.15.000
    ARCH: Archival stopped, error occurred. Will continue retrying
    ARCH:
    ORA-00255: error archiving log 1 of thread 1, sequence # 51
    ORA-00312: online log 1 thread 1: 'WORK:ORANW803\DATABASE\TEST\LOG1TEST.ORA'
    ORA-00312: online log 1 thread 1: 'WORK:ORANW803\DATABASE\TEST\LOG2TEST.ORA'
    ORA-00334: archived log: 'WORK:ORANW803\DATABASE\TEST\ARCHIVE\TESTT001S00051.ARC'
    ORA-00270: error creating archive log WORK:ORANW803\DATABASE\TEST\ARCHIVE\TESTT001S00051.ARC
    ORA-19504: failed to create file "WORK:ORANW803\DATABASE\TEST\ARCHIVE\TESTT001S00051.ARC"
    ORA-09200: sfccf: error creating file
    OSD-02070: unable to create file (OS 1)
    Tue Feb 15 12:10:02 2005 -

    well, your question was not clear, though, what I understand is, you want to move your DB from archivelog mode to NOARCHIVELOG mode, right?
    First of all, check whether do you have sufficient space to archiving on your hard-disk.
    Secondly, try the following, alter system archive log all;
    also, give the steps that you are implementing or implemented to switch from ARCHIVELOG TO NOARCHIVELOG.
    SJH
    OCP DBA

  • How do I manually archive 1 redo log at a time?

    The database is configured in archive mode, but automatic archiving is turned off.
    For both Oracle 901 and 920 on Windows, when I try to manually archive a single redo log, the database
    archives as many logs as it can up to the log just before the current log:
    For example:
    SQL> select * from v$log order by sequence#;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
    1 1 14 104857600 1 NO INACTIVE 424246 19-JAN-05
    2 1 15 104857600 1 NO INACTIVE 425087 28-MAR-05
    3 1 16 104857600 1 NO INACTIVE 425088 28-MAR-05
    4 1 17 512000 1 NO INACTIVE 425092 28-MAR-05
    5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
    6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
    6 rows selected.
    SQL> alter system archive log next;
    System altered.
    SQL> select * from v$log order by sequence#;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
    1 1 14 104857600 1 YES INACTIVE 424246 19-JAN-05
    2 1 15 104857600 1 YES INACTIVE 425087 28-MAR-05
    3 1 16 104857600 1 YES INACTIVE 425088 28-MAR-05
    4 1 17 512000 1 YES INACTIVE 425092 28-MAR-05
    5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
    6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
    See - instead of only 1 log being archive, 4 of them were. Oracle behaves the same way if I use the "sequence" option:
    SQL> select * from v$log order by sequence#;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
    1 1 14 104857600 1 NO INACTIVE 424246 19-JAN-05
    2 1 15 104857600 1 NO INACTIVE 425087 28-MAR-05
    3 1 16 104857600 1 NO INACTIVE 425088 28-MAR-05
    4 1 17 512000 1 NO INACTIVE 425092 28-MAR-05
    5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
    6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
    6 rows selected.
    SQL> alter system archive log next;
    System altered.
    SQL> select * from v$log order by sequence#;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
    1 1 14 104857600 1 YES INACTIVE 424246 19-JAN-05
    2 1 15 104857600 1 YES INACTIVE 425087 28-MAR-05
    3 1 16 104857600 1 YES INACTIVE 425088 28-MAR-05
    4 1 17 512000 1 YES INACTIVE 425092 28-MAR-05
    5 1 18 512000 1 NO INACTIVE 425100 28-MAR-05
    6 1 19 512000 1 NO CURRENT 425102 28-MAR-05
    Is there some default system configuration property telling Oracle to archive as many logs as it can?
    Thanks,
    DGR

    Thanks Yoann (and Syed Jaffar Jaffar Hussain too),
    but I don't have a problem finding the group to archive or executing the alter system archive log command.
    My problem is that Oracle doesn't work as I expect it.
    This comes from the Oracle 9.2 online doc:
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_23a.htm#2053642
    "Specify SEQUENCE to manually archive the online redo log file group identified by the log sequence number integer in the specified thread."
    This implies that Oracle will only archive the log group identified by the log sequence number I specify in the alter system archive log sequence statement. However, Oracle is archiving almost all of the log groups (see my first post for an example).
    This appears to be a bug, unless there is some other system parameter that is configured (by default) to allow Oracle to archive as many log groups as possible.
    As to the reason why - it is an application requirement. The Oracle db must be in archive mode, automatic archiving must be disabled and the application must control online redo log archiving.
    DGR

  • How to set the database in NOARCHIVELOG mode

    hellow world,
    I knewly joined this organization.
    Our database is very small < 4GB data.
    Database is running in ARCHIVELOG MODE.
    since we are not keeping any physical backup, so I opted to run the datbase in NOARCHIVELOG mode.
    For bringing the database in NOARCHIVE MODE, I simply changed the init.ora parameter LOG_ARCHIVE_START = FALSE and restart the database.
    offcourse the archiving stopped, but to my strange after 30 to 40 minutes my all log files filled an error message is being displayed to the server, saying
    log files are filled, waiting for the archiving, Oh my God, What has happened, All users came to my head, DATABASE HANGED, NOT RESPONSING.
    SIR, MY QUESTION IS
    WHAT FOR ALL LOG FILES WAITING?
    when i am saying NOARCHIEVE than
    please explain me, where i committed mistake. I am new to ADMINISTRATION.

    1. Not keeping any physical backup is all the more reason to stay in archivelog mode.
    2. You need to shutdown the database, startup mount, and issue 'alter database noarchivelog', the alter database open.

  • Start database in NOARCHIVELOG mode

    Hi,
    I would like to know if there is a way to set some oracle paramete so that each time database is restarted, it comes up in NOARCHIEVELOG mode.
    Regards,
    Andrija

    your answer is completelly wrong.
    Please check description of log_archive_start parameter in documentation:
    LOG_ARCHIVE_START
    Parameter type
    Boolean
    Default value
    false
    Parameter class
    Static
    Range of values
    true | false
    Real Application Clusters
    Multiple instances can have different values.
    LOG_ARCHIVE_START is applicable only when you use the redo log in ARCHIVELOG mode. It indicates whether archiving should be automatic or manual when the instance starts up.
    Values:
    true
    Indicates that archiving is automatic
    false
    Indicates that the database administrator will archive filled redo log files manually
    The SQL*Plus statements ARCHIVE LOG START or ARCHIVE LOG STOP override this parameter.
    In ARCHIVELOG mode, if all online redo log files fill without being archived, Oracle issues an error and suspends instance operations until the necessary archiving is performed. This delay is more likely if you use manual archiving. You can reduce its likelihood by increasing the number of online redo log files.
    To use ARCHIVELOG mode while creating a database, set this parameter to true. Normally, a database is created in NOARCHIVELOG mode and then altered to ARCHIVELOG mode after creation.

  • Oracle recovery in noarchivelog mode

    Hello,
    SAP Release : ECC6
    Oracle 10G
    Solaris 10g
    Our SAP system is in noarchivelog mode (formation environnement, with frequent client copies).
    We frequently perform an offline backup.
    The solaris server that is hosting our Sap system, has been brutally shutdown this morning,
    due to a network issue.
    Afterwards, we had to restart the sap system.
    A fisrt error occured ; inconsistency between the control files ...
    ORA-00205: error in identifying control file, check alert log for more info
    In alert log :
    ORA-00202: control file: '/oracle/ZMA/origlogA/cntrl/cntlrZMA.dbf'
    ORA-27037: unable to obtain file status
    We regenerated a new control file and replaced it.
    The error was solved.
    Then a second error occured :
    SQL> startup
    ORACLE instance started.
    Total System Global Area 1660944384 bytes
    Fixed Size                  2268216 bytes
    Variable Size             851207112 bytes
    Database Buffers          805306368 bytes
    Redo Buffers                2162688 bytes
    Database mounted.
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> alter database open resetlogs ;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/oracle/ZMA/sapdata1/system_1/system.data1'
    SQL> recover database using backup controlfile until cancel ;
    ORA-00279: change 647063400 generated at 04/28/2008 11:10:01 needed for thread
    1
    ORA-00289: suggestion : /oracle/ZMA/oraarch/ZMAarch1_76005_618576658.dbf
    ORA-00280: change 647063400 for thread 1 is in sequence #76005
    The redo log #76005 is no more available; I tried to apply the online redo logs, but it didn't help.
    We had to restore the whole database from the offline backup.
    1/ I still have problems understanding why Oracle is asking for a recovery, when we tried to reopen the database ? The database was consistent this morning, how is it that the file '/oracle/ZMA/sapdata1/system_1/system.data1' became inconsistent ?
    2/ In sap note 863417 "If the database operates in NOARCHIVELOG mode, the database can ONLY be completely recovered from instance failure but not from media failure. "
    What is exactly the difference between media failure and instance failure ?
    Does a network problem and then a reboot of the host is considered a media failure ?
    Best Regards.
    thank you for your help .

    > 1/ I still have problems understanding why Oracle is asking for a recovery, when we tried to reopen the database ? The database was consistent this morning, how is it that the file '/oracle/ZMA/sapdata1/system_1/system.data1' became inconsistent ?
    Because the database was not shut down cleanly. An open database is by definition "inconsistent" without the proper logfiles.
    > 2/ In sap note 863417 "If the database operates in NOARCHIVELOG mode, the database can ONLY be completely recovered from instance failure but not from media failure. "
    > What is exactly the difference between media failure and instance failure ?
    Media = File/Raw-Device. If you database is crashing due to a software error it can be recovered, if a file is corrupt it can't be (since you have no redo logs).
    > Does a network problem and then a reboot of the host is considered a media failure ?
    A corrupt control file (e. g.) is a media failure.
    Markus

  • Standby in Noarchivelog mode

    Hello,
    Standby Redo Log must be archived before the redo data can be applied to the standby database. If we put our standby database in noarchivelog mode, then standby database does not generate any archive.Because of this Redo data wont apply to the standby database. Right? Is this the reason why we put standby database in archivelog mode?
    Thanks

    Hello;
    Standby Redo Log must be archived before the redo data can be applied to the standby database.That statement is not correct.
    If we put our standby database in noarchivelog mode, then standby database does not generate any archive. Because of this Redo data wont apply to the standby database. Right?That statement is not correct either. While Standby can use a process which is like generating archive, archive is really being transported from the Primary database.
    Is this the reason why we put standby database in archivelog mode?Yes. If you switch modes the standby becomes the primary and needs to be in archivelog mode.
    Failover
    If you do a failover there are two main methods for recovery, RMAN and Flashback. You want your Standby database to be ready for use as a Primary, otherwise why have it? So you need to have it ready for anything including recovery.
    I debated the archive question with somebody here last year. They claim the Standby produces Archive because such and such a process does this. I disagree. In Standby mode the database is not doing what a Primary mode database does. Those Oracle processes don't create new archive, they complete the transfer of archive from a Primary. The Sequence number was created on the Primary.
    From Oracle document
    "If all databases in a distributed database operate in ARCHIVELOG mode, you can perform coordinated distributed database recovery. However, if any database in a distributed database is in NOARCHIVELOG mode, recovery of a global distributed database (to make all databases consistent) is limited by the last full backup of any database operating in NOARCHIVELOG mode."
    If you search this document
    Data Guard Concepts and Administration 11g Release 2 (11.2) E10700-02
    For "ARCHIVELOG" you get several hits.
    If you search for "NOARCHIVELOG" you get none.
    I suppose in theory you could run a Standby in "NOARCHIVELOG" but you gain nothing. If you ever have a switchover or failover you need to fix this ASAP. I see no reason to add that item to my checklist. It just an extra step and in the event of a failover one I could be very unhappy about.
    Best Regards
    mseberg
    Edited by: mseberg on Mar 15, 2013 1:25 PM

  • Database Recovery in NOARCHIVELOG Mode

    Hi All,
    I was trying to 'startup' my database & encountered the following error in the alert.log
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01122: database file 469 failed verification check
    ORA-01110: data file 469: '/ora/ctcm_uat02/CMOLP1/undo/CMOLP1_undots_30.dbf'
    ORA-01209: data file is from before the last RESETLOGS
    I then looked up on the internet and since the error was related to the UNDO TABLESPACE, i did the following:
    sql>startup mount
    sql>alter database datafile '/ora/ctcm_uat02/CMOLP1/undo/CMOLP1_undots_30.dbf' offline drop;
    sql>alter database open
    Thereafter the database kept on erroring on all the datafiles belonging to the undo tablespaces and i dropped all the datafiles belonging to the undo tablespace using the above command. (alter database datafile ....offline drop).
    Next, i tried to open the database and got the following error from the alert log:
    Tue May 12 18:15:24 2009
    alter database open
    Tue May 12 18:15:33 2009
    Beginning crash recovery of 1 threads
    Tue May 12 18:15:33 2009
    Started redo scan
    Tue May 12 18:15:33 2009
    Completed redo scan
    21 redo blocks read, 3 data blocks need recovery
    Tue May 12 18:15:33 2009
    Started recovery at
    Thread 1: logseq 252, block 2, scn 1917.14626262
    Tue May 12 18:15:33 2009
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 252 Reading mem 0
    Mem# 0 errs 0: /ora/ctcm_dev/CMOLP1/redo/CMOLP1_redo03a.dbf
    Tue May 12 18:15:33 2009
    Completed redo application
    Tue May 12 18:15:33 2009
    Ended recovery at
    Thread 1: logseq 252, block 23, scn 1917.14646284
    3 data blocks read, 3 data blocks written, 21 redo blocks read
    Crash recovery completed successfully
    Tue May 12 18:15:35 2009
    Thread 1 advanced to log sequence 253
    Thread 1 opened at log sequence 253
    Current log# 4 seq# 253 mem# 0: /ora/ctcm_dev/CMOLP1/redo/CMOLP1_redo04a.dbf
    Successful open of redo thread 1
    Tue May 12 18:15:38 2009
    LOG_CHECKPOINT_INTERVAL was set when MTTR advisory was switched on.
    Tue May 12 18:15:38 2009
    SMON: enabling cache recovery
    Tue May 12 18:15:38 2009
    Successfully onlined Undo Tablespace 1.
    Tue May 12 18:15:39 2009
    SMON: enabling tx recovery
    Tue May 12 18:15:39 2009
    Database Characterset is US7ASCII
    Tue May 12 18:15:39 2009
    SMON: about to recover undo segment 1
    Can someone please help me on this issue? Thanks and Regards

    Hi ERROR,
    I think i figured out the hidden parameter that you were referring to.
    (1) I set the allowresetlogs_corruption=TRUE and commented undo_management. Then opened the database using--> alter database open resetlogs;
    But still was not able to start the database. The alert log entries are as below:
    ALTER DATABASE   MOUNT
    Thu May 14 18:11:56 2009
    Successful mount of redo thread 1, with mount id 4113112614
    Thu May 14 18:11:56 2009
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE   MOUNT
    Shutting down instance: further logons disabled
    Shutting down instance (immediate)
    License high water mark = 2
    Thu May 14 18:12:05 2009
    ALTER DATABASE CLOSE NORMAL
    ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
    Thu May 14 18:12:05 2009
    ALTER DATABASE DISMOUNT
    Completed: ALTER DATABASE DISMOUNT
    ARCH: Archiving is disabled
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archiving is disabled
    Would be great if you can help me further on this.
    Regards,
    Fuzzy

  • Manual archiving of redo log files....

    Hi ,
    If the database is running in NOARCHIVELOG mode , is it possible to archive the redo log files manually.... and how..????
    Note: I use Oracle 10g v.2
    Many thanks,
    Simon

    Having issued the command , i noticed that the USE_DB_RECOVERY_FILE_DEST is the destination of LOG_ARCHIVE_DEST_10:
    SQL> select dest_id,dest_name,status,destination from V$ARCHIVE_DEST;
       DEST_ID DEST_NAME                                                                        STATUS    DESTINATION
             1 LOG_ARCHIVE_DEST_1                                                               VALID     C:\oracle\product\10.2.0\flash_recovery_area\EPESY\ARCHIVELOG\
             2 LOG_ARCHIVE_DEST_2                                                               INACTIVE 
             3 LOG_ARCHIVE_DEST_3                                                               INACTIVE 
             4 LOG_ARCHIVE_DEST_4                                                               INACTIVE 
             5 LOG_ARCHIVE_DEST_5                                                               INACTIVE 
             6 LOG_ARCHIVE_DEST_6                                                               INACTIVE 
             7 LOG_ARCHIVE_DEST_7                                                               INACTIVE 
             8 LOG_ARCHIVE_DEST_8                                                               INACTIVE 
             9 LOG_ARCHIVE_DEST_9                                                               INACTIVE 
            10 LOG_ARCHIVE_DEST_10                                                              VALID     USE_DB_RECOVERY_FILE_DESTBut... i have set the LOG_ARCHIVE_DEST parameter not ...._10.
    How the system will point to the directory i've set in my previous alter system command...- when i use the archive log list???
    Many thanks,
    Simon

  • Restore using incremental backup with noarchivelog mode

    Hello experts,
    We are running SAP on Oracle databse(IN NOARCHIVELOG MODE) for which we are having full offline backup on every sunday and post which incremental backups on rest of the days. We have scenario to do restore db to the state till last friday's incremental backup.
    Please let us know the procedure for restoring till that point. If possible using brtools utility(which is SAP specific).
    Thank You
    Regards,
    Venkateshwar

    If you do not want to read the whole doc This is the snippet for you.
    Recovering a NOARCHIVELOG Database with Incremental Backups
    Restoring a database running in NOARCHIVELOG mode is similar to restoring a database in ARCHIVELOG mode. The main differences are:
    Only consistent backups can be used in restoring a database in NOARCHIVELOG mode.
    Media recovery is not possible because no archived redo logs exist.
    You can perform limited recovery of changes to a database running in NOARCHIVELOG mode by applying incremental backups. The incremental backups must be consistent, like all backups of a database run in NOARCHIVELOG mode, so you cannot make backups of the database when it is open.
    When you are recovering a NOARCHIVELOG database, specify the NOREDO option on the RECOVER command to indicate that RMAN should not attempt to apply archived redo logs. Otherwise, RMAN returns an error.
    To recover a NOARCHIVELOG database with incremental backups:
    After connecting to the target database and the recovery catalog, place the database in a mounted state:
    STARTUP FORCE MOUNT
    Restore and recover the database.
    For example, you can perform incomplete recovery with the following commands:
    RESTORE DATABASE
    FROM TAG "consistent_whole_backup";
    RECOVER DATABASE NOREDO;
    Open the database with the RESETLOGS option.
    For example, enter the following command:
    ALTER DATABASE OPEN RESETLOGS;

Maybe you are looking for

  • How to activate Front Panel Wait in LV7.1?

    Dear list,      I am a new comer here. Thank you for your help.     I have a question: when I try to use the "Wait for Front Panel Activity", the time sequence looks just skipping this without doing anything. Can someone help me to take a look at the

  • How to prevent developers from modifying the structure of DB

    We are developing an application and using Oracle 8i as DB server. I don't want the developers to modify the structure of tables. They should only be able to insert/update/delete rows of the tables. How can I make it? Any suggestions will be apprecia

  • Need BADI/exit OR ORHER SOLUTIONS FOR miro BEFORE POSTING A ACCOUNTING DOCU

    Dear Expert, How can i find a FI document number Material Line Items Before MIRO posting. so that along with miro posting another FI document can be posted by taking reference of the above.

  • Restore factory settings?

    iPod shuffle keeps trying to restore original factory settings....is it me or the shuffle?  no known damage.  was working just fine.  I have rescharged it (was not dead to start with), rebooted iMac and still does this.

  • Is it possible to quickly delete all processed messages from XI

    Hi all, In our project systems I would like to remove all messages from the system after testing phase. We run XI 3.0 sp18 (soon sp20). I do know about archiving but it seems we cannot start the archiving because of some large message being stuck. I