The archive logs shipped but more old logs do not applied...

Environment:

Oracle on Solaris 11.2.0.3 10.5

The Data Guard environment working fine for 6 months.

I recently had problems with disk space on the day before and had to copy some files from newspapers of the archives to a mount point different that had been shipped to the waiting, but not yet applied because I had to cancel the paper application process.

After having cleared the space problem and start log shipping and return application log on (change database recovery managed to sleep...) I have the new logs shipped but my watch is a bunch of log files behind. I can see it in the V$ ARCHIVED_LOG on intelligence, where the last seq # applied is 8083 in my case and the more current seq # is currently more than 8200.

I have all the archives always connects in 'other' the mount point and can move back the directory the correct archive according to needs.

Since the next file that the application requires is seq # 8084, I moved this file in the/arch directory awaits the day before 'see' and apply it. No luck.

By searching in the alert log just before after execution of the 'alter database recover managed standby database disconnect;' I see the following:
Media Recovery Waiting for thread 1 sequence 8084
and also:
Fetching gap sequence in thread 1, gap sequence 8084-8084
and just below that:
FAL[client]: Error fetching gap sequence, no FAL server specified
I thought I read in the docs that the FAL_SERVER and the FAL_CLIENT are no longer needed. (?)

I also found a CKPT script that lists information about DG Environment. For the primary side to hang on, but the day before one produces this output:
NAME                           DISPLAY_VALUE
------------------------------ ------------------------------
db_file_name_convert           /u01/oradata/APSMDMP1, /u01/or
                               adata/APSMDMP1, /u02/oradata/A
                               PSMDMP1, /u02/oradata/APSMDMP1
                               , /u03/oradata/APSMDMP1, /u03/
                               oradata/APSMDMP1, /u04/oradata
                               /APSMDMP1, /u04/oradata/APSMDM
                               P1

db_name                        APSMDMP1
db_unique_name                 APSMDMP1STBY
dg_broker_config_file1         /u01/app/oracle/product/11203/
                               db_2/dbs/dr1APSMDMP1STBY.dat

dg_broker_config_file2         /u01/app/oracle/product/11203/
                               db_2/dbs/dr2APSMDMP1STBY.dat

dg_broker_start                FALSE
fal_client
fal_server
local_listener
log_archive_config             DG_CONFIG=(APSMDMP1,APSMDMP1ST
                               BY)

log_archive_dest_2             SERVICE=APSMDMP1 ASYNC VALID_F
                               OR=(ONLINE_LOGFILES,PRIMARY_RO
                               LE) DB_UNIQUE_NAME=APSMDMP1 MA
                               X_CONNECTIONS=2

log_archive_dest_state_2       ENABLE
log_archive_max_processes      4
log_file_name_convert          /u01/oradata/APSMDMP1, /u01/or
                               adata/APSMDMP1

remote_login_passwordfile      EXCLUSIVE
standby_archive_dest           ?/dbs/arch
standby_file_management        AUTO

NAME       DB_UNIQUE_NAME                 PROTECTION_MODE DATABASE_R OPEN_MODE
---------- ------------------------------ --------------- ---------- --------------------
APSMDMP1   APSMDMP1STBY                   MAXIMUM PERFORM PHYSICAL S READ ONLY WITH APPLY
                                          ANCE            TANDBY


   THREAD# MAX(SEQUENCE#)
---------- --------------
         1           8083

PROCESS   STATUS          THREAD#  SEQUENCE#
--------- ------------ ---------- ----------
ARCH      CLOSING               1       7585
ARCH      CLOSING               1       7588
ARCH      CLOSING               1       6726
ARCH      CLOSING               1       7581
RFS       RECEIVING             1       8462
MRP0      WAIT_FOR_GAP          1       8084
RFS       IDLE                  0          0

NAME                           VALUE      UNIT                           TIME_COMPUTED                  DATUM_TIME
------------------------------ ---------- ------------------------------ ------------------------------ ------------------------------
transport lag                  +00 00:01: day(2) to second(0) interval   08/16/2012 13:24:04            08/16/2012 13:23:35
                               59

apply lag                      +01 23:08: day(2) to second(0) interval   08/16/2012 13:24:04            08/16/2012 13:23:35
                               43

apply finish time              +00 00:17: day(2) to second(3) interval   08/16/2012 13:24:04
                               21.072

estimated startup time         15         second                         08/16/2012 13:24:04

NAME                                                            Size MB    Used MB
------------------------------------------------------------ ---------- ----------
                                                                      0          0
I do not use a fast recovery area.

What should I do to get the old logs to check-in begins to apply again?

The alert log says something about "Adding value to the media", but I don't know why I would need that since I have the log files itself.

Any help is appreciated.

Also, I spend a significant amount of time to read through this forum and many articles on the web but couldn't find exactly the solution I was looking for.

Thank you very much!!

-gary

Try to save the log file

alter database register logfile 'full path for the 8074 sequence.

and check select message from v$ dataguard_status;

Tags: Database

Similar Questions

  • ORA-19504: failed to create the file, ORA-00270: creation of the archiving log error

    Hello

    Oracle 11 g 2 on windows 7, I of primary and standby on the same system (learning).

    When I check on status of primary and secondary use under request it gives applied log is 'NO '.

    SQL > select sequence #, used from v$ archived_log;

    SEQUENCE # APPLIED
    ---------- ---------
    516 NO.
    517 NO.
    NO. 523
    NO. 524
    525 NO.
    531 NO.
    NO. 532
    533 NO.
    NO. 541
    544 NO.

    When I checked error on DB primary .he give me more erro.
    SQL > SELECT 'ID', 'DB_status' STATUS DEST_ID, EXCURSION place "Archive_dest', 'ERROR' OF V$ ARCHIVE_DEST WHERE DEST_ID < = 5;
    ---------- ---------
    Error Archive_dest
    ------------------------------------------------------------------------------------------------------------------------------------------------------
    1 D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG ORA-19504: cannot create the file «»

    2 STAND ORA-00270: creation of the archiving log error

    I checked the space on the system... is there enough free space on the disk.

    On primary DB (destination of the journal archive)

    SQL > list of archive logs
    Database log mode Archive Mode
    Active AutoArchive
    Destination of archive D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG
    More old sequence of journal online 564
    Log sequence archive 566
    Current log sequence 566

    On standby DB (list of newspapers of record)

    SQL > list of archive logs
    Database log mode Archive Mode
    Active AutoArchive
    Destination of archive D:\app\kamdarvg\flash_recovery_area\test\ARCHIVELOG
    More old sequence of journal online 564
    Log sequence archive 566
    Current log sequence 566

    Please guide it's because of the destination of the journal archive even shared by the standby and primary?

    If yes how do I change the destination of the newspaper archive on standby DB?

    Thank you.

    Edited by: 977220 April 18, 2013 20:49

    change initialization parameter

  • Problem with the archive log when you use RMAN for backup and restore (11g 2)

    Hello world
    Please help me solve this problem.
    I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
    -First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:
    run{
    allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ;
    backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile;
    backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
    crosscheck archivelog all;
    crosscheck backup;
    delete noprompt obsolete;
    release channel bkp;
    }


    D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:

    run{
    allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ;
    backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile;
    backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input;
    crosscheck archivelog all;
    crosscheck backup;
    delete noprompt obsolete;
    release channel bkp;
    }

    Repeat 7 times (Monday-> Saturday). And I got these files:

    [oracle@rac ~]$ ls -l /u01/backup/
    total 400280
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 07:23 c-1428943247-20160120-01
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:04 c-1428943247-20160120-02
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:05 c-1428943247-20160120-03
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:06 c-1428943247-20160120-04
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-05
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-06
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:09 c-1428943247-20160120-07
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:32 c-1428943247-20160120-08
    -rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1
    -rw-r----- 1 oracle oinstall   2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1
    -rw-r----- 1 oracle oinstall   4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1
    -rw-r----- 1 oracle oinstall  11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1
    -rw-r----- 1 oracle oinstall    146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1
    -rw-r----- 1 oracle oinstall    884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1
    -rw-r----- 1 oracle oinstall     82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1
    -rw-r----- 1 oracle oinstall    294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1
    -rw-r----- 1 oracle oinstall     18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1
    -rw-r----- 1 oracle oinstall    155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1
    -rw-r----- 1 oracle oinstall    131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1
    -rw-r----- 1 oracle oinstall    647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1
    -rw-r----- 1 oracle oinstall      8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1
    -rw-r----- 1 oracle oinstall   2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1
    -rw-r----- 1 oracle oinstall   1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1
    -rw-r----- 1 oracle oinstall    327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1

    And
    RMAN> list backup summary;
    List of Backups
    ===============
    Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
    ------- -- -- - ----------- --------------- ------- ------- ---------- ---
    80      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
    81      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
    82      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
    83      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
    84      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
    85      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T072332
    86      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    87      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    88      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    89      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080440
    90      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    91      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    92      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    93      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080545
    94      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    95      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    96      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    97      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080657
    98      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    99      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    100     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    101     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080801
    102     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    103     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    104     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    105     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080844
    106     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    107     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    108     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC

    My configuration of rman:
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name ORCL are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/u01/backup/backup_df%t_s%s_s%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default

    - Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here.
    RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08';
    Starting restore at 20-JAN-16
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=18 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=20 device type=DISK
    channel ORA_DISK_2: skipped, AUTOBACKUP already found
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:09
    output file name=/u01/app/oracle/oradata/orcl/control01.ctl
    output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl
    Finished restore at 20-JAN-16

    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    released channel: ORA_DISK_2

    RMAN> restore database;
    Starting restore at 20-JAN-16
    Starting implicit crosscheck backup at 20-JAN-16
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=20 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=18 device type=DISK
    Crosschecked 29 objects
    Finished implicit crosscheck backup at 20-JAN-16

    Starting implicit crosscheck copy at 20-JAN-16
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    Finished implicit crosscheck copy at 20-JAN-16

    searching for all files in the recovery area
    cataloging files...
    no files cataloged

    using channel ORA_DISK_1
    using channel ORA_DISK_2

    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
    channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
    channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
    channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1
    channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
    Finished restore at 20-JAN-16

    -Fourth, the problem here, I got the database;
    .. .every oky until this line...
    starting media recovery

    channel ORA_DISK_1: starting archived log restore to default destination
    channel ORA_DISK_1: restoring archived log
    archived log thread=1 sequence=15
    channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1
    channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15
    unable to find archived log
    archived log thread=1 sequence=1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/20/2016 08:50:22
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841

    The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?)
    RMAN> list backup of archivelog all;
    List of Backup Sets
    ===================
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    82      2.16M      DISK        00:00:00     20-JAN-16     
            BP Key: 82   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
            Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1

      List of Archived Logs in backup set 82
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
    1    1       1154833    20-JAN-16 1177422    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    83      3.88M      DISK        00:00:00     20-JAN-16     
            BP Key: 83   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
            Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1

      List of Archived Logs in backup set 83
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
    1    1       1162729    20-JAN-16 1188784    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    84      10.68M     DISK        00:00:01     20-JAN-16     
            BP Key: 84   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
            Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1

      List of Archived Logs in backup set 84
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    2       1177422    20-JAN-16 1201833    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    88      1.81M      DISK        00:00:01     20-JAN-16     
            BP Key: 88   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1

      List of Archived Logs in backup set 88
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    3       1201833    20-JAN-16 1204844    20-JAN-16
      1    4       1204844    20-JAN-16 1204893    20-JAN-16
      1    5       1204893    20-JAN-16 1204958    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    92      143.00K    DISK        00:00:00     20-JAN-16     
            BP Key: 92   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1

      List of Archived Logs in backup set 92
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    6       1204958    20-JAN-16 1205034    20-JAN-16
      1    7       1205034    20-JAN-16 1205253    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    96      80.00K     DISK        00:00:00     20-JAN-16     
            BP Key: 96   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1

      List of Archived Logs in backup set 96
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    8       1205253    20-JAN-16 1205354    20-JAN-16
      1    9       1205354    20-JAN-16 1205433    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    100     18.00K     DISK        00:00:00     20-JAN-16     
            BP Key: 100   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1

      List of Archived Logs in backup set 100
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    10      1205433    20-JAN-16 1205519    20-JAN-16
      1    11      1205519    20-JAN-16 1205559    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    104     128.00K    DISK        00:00:00     20-JAN-16     
            BP Key: 104   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1

      List of Archived Logs in backup set 104
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    12      1205559    20-JAN-16 1205624    20-JAN-16
      1    13      1205624    20-JAN-16 1205739    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    108     8.00K      DISK        00:00:00     20-JAN-16     
            BP Key: 108   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1

      List of Archived Logs in backup set 108
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    14      1205739    20-JAN-16 1205796    20-JAN-16
      1    15      1205796    20-JAN-16 1205840    20-JAN-16


    If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.

    Sorry for a long post.

    > 1 and from the 1205841 SNA sequence

    The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840).

    The message

    channel ORA_DISK_1: restoring archives Journal

    Archives journal thread = 1 sequence = 15

    channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading

    channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC

    indicates that he has restored the sequence up to 15

    You can check the log file alert database instance for messages on the fact of recovery.

    He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15.

    Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve.  An uncomitted transaction is cancelled.

    Hemant K Collette

  • Rconfig fails with "DEST ARCHIVE LOG does not exist on all nodes of the cl.

    Dear Sir

    I am to convert a single instance database RAC
    Next Note:
    Using Oracle 10 g Release 2 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
    DOC - ID: 388577.1


    the trial seems fine until I got this error.
    This directory is only one instance and the binary FCAC did not have a configuration database, and then how do I receive this error
    < Microsoft.PowerShell.Commands.GetChildItemCommand >
    U01/Oracle/Gold/DB/apps_st/Data DEST ARCHIVE LOG does not exist on all nodes of the cluster

    Please give us a solution.
    Thanks in advance.


    Here is the ConvertToRAC.xml

    [dgold@ebs64 u01] $ ConvertToRAC.xml more
    <? XML version = "1.0" encoding = "UTF-8"? >
    < n: RConfig xmlns:n = "http://www.oracle.com/rconfig".
    xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance".
    xsi: schemaLocation = "http://www.oracle.com/rconfig" >
    < n: ConvertToRAC >
    <!-check is a precheck to ensure that all prerequisites are met, before the con
    version is attempted. The allowed values are: YES | NO. | ONLY->
    < n: Convert check 'ONLY' = >
    <!-specify current database OracleHome no cars to-> SourceDBHome
    < n: SourceDBHome > /u01/oracle/GOLD/db/tech_st/10.2.0 < / n: SourceDBHome
    >
    <!-OracleHome specify where should be configured in the rac database. It may be in Africa
    me as a SourceDBHome->
    < n: TargetDBHome > / u01/ora/GOLD/db < / n: TargetDBHome >
    <!-SID specify no rac database and credentials. User with the sysdba role is req
    receipt to achieve a conversion->
    < n: SourceDBInfo SID 'OR' = >
    < n: Credentials >
    sys < n: User > < / n: User >
    Oracle of < n: Password > < / n: Password >
    SYSDBA < n: Role > < / n: Role >
    < / Credentials: n >
    < / n: SourceDBInfo >
    <!-ASMInfo element is required only if the active non-rac database uses ASM St
    Storm->
    < n: ASMInfo SID = '+ ASM1' >
    < n: Credentials >
    sys < n: User > < / n: User >
    ASM < n: Password > < / n: Password >
    SYSDBA < n: Role > < / n: Role >
    < / Credentials: n >
    < / n: ASMInfo >
    <!-specify the list of nodes that should have instances of cars running. LocalNode
    should be the first node in the nodelist. ->
    < n: NodeList >
    < name n: Node = "ebs64" / >
    < name n: Node = "ebs641" / >
    < / n: NodeList >
    <!-specifies the prefix for the rac instances. It may be same as instance name for no
    database n - cars or different. The instance number will be attached to this prefix
    . ->
    < n: InstancePrefix > RAC < / n: InstancePrefix >
    <!-specify the port for the listener is configured for the rac database. If ports ="",
    alistener existing on the local host will be used for the rac database. The listener will be
    be extended to all the nodes in the nodelist->
    < n: Listener port = "" / >
    <!-specify the type of storage to serve as rac database. The allowed values are
    CFS | ASM. The non-rac database must have the same type of storage. ->
    < n: SharedStorage type = "ASM" >
    <!-location of database field specify is configured for the rac database. If this fie
    LD is left blank, current storage will be used for the rac database. For CFS, this f
    ield will be the directory path. ->
    < n: TargetDatabaseArea > + DATA < / n: TargetDatabaseArea >
    <!-specify the Flash recovery area is set up for the rac database. If this field
    is left empty, current data base retrieval area no cars will be set to
    RAC database. If current database uses no recovery area, FCAC resulting
    database will not be a recovery zone. ->
    < n: TargetFlashRecoveryArea > + DATA < / n: TargetFlashRecoveryArea >
    < / n: SharedStorage >
    < / n: Convert >
    < / n: ConvertToRAC >
    < / n: RConfig >

    Hello

    Do you mean that it is no longer a problem?

    Kind regards
    Hussein

  • delete the archive logs after cold backup?

    Hi all
    my database is in archivelog mode, I do COLD backup every night, can I just remove the archive logs after I do my cold backup, because there is no need of them, as the closed DB should have all the info in the archived papers

    and archive connected is needed only during the day, if a sudden power outage that happened.

    Thank you very much

    The ArchiveLogs allow you RollForward a backup restored to a specific point in time.

    Assuming that stop you your database at 23:00 (2300) every night and backup up to 11 h 45 (2345) tracks...

    Significant transactions entered between 15:00 and 16:00 on Friday, but a person deleted by mistake the lines (or some other lines) at 17:00

    your current backup strategy of "restoration" of the database only allows 23:00 Thursday night. If you also back up your archivelogs (in this case, the backup of Friday night would the archivelogs), you restore Thursday night backup 'cold' and "rollforward" by publishing a RECOVER database with the HELP of BACKUP CONTROLFILE until 16:00 Friday.

  • Problem with the Archive log in Oracle 11 g

    Hi gurus,

    I'm new in the DBA role and I have real problems with the archive logs - they are written to the wrong place.
    This is my environment:
    Windows Server 2003 Enterprise x 64 Edition; Oracle 11g EE + ASM;
    I did everything according to the instructions.
    I did the following:
    1. install Oracle 11 g software
    2 instance created using DBCA for ASM in the same House and added a no formatted disk as a DATA disk group
    3 database instance created using DBCA mode archive using ASM for data files. I've mirrored controlfiles and redo online records on the C: drive. I created flash_recovery_area and a reference to it when the instance was created.
    4. start to import the data.

    And here's the problem - for an unknown to me reason archive logs are written on 2 places: 1. in the flash_recovery_area, 2; IN MY ORACLE_HOME!

    I opened with EM dbconsole init settings and found that there is a single parameter, that points to this place (standby_archive_dest =' docs in the % ORACLE_HOME%\RDBMS, it is written that it is an obsolete parameter). Is another parameter that I found (LOG_ARCHIVE_LOCAL_FIRST = TRUE - I put it to FALSE), but nothing to help continue to write in ORACLE_HOME.

    How can I stop it? If I can't stop, so what happens in production? Should I manually delete all newspapers of this Archive - it will be madness!

    Try to set log_archive_dest_1 specifically. Example: -.

    ALTER system set db_recovery_file_dest_size = 400G;
    ALTER system set db_recovery_file_dest = '+ ASM_ORADATA42;
    ALTER system set log_archive_dest_state_1 = reporter;
    ALTER system set LOG_ARCHIVE_DEST_1 is 'LOCATION = USE_DB_RECOVERY_FILE_DEST VALID_FOR =(ONLINE_LOGFILE,ALL_ROLES)';.
    ALTER system set log_archive_dest_state_1 = enable;

  • Remove the archive logs from before the resetlogs

    Hello

    I use a cleanupscript to my archive logs. I work with a database of return of flame and running of tests, so I did a bit of resetlogs open in my DB.

    However, this script does not seem to take the archive logs away from before the resetlogs. Is there a way I can always make a backup of these easily?


    Run {}
    allocate channel t1 type disk;
    OVERLAP archivelog all;
    format of entry archivelog backup to remove sequences 5 ' / oracle/RMAN/backups/${SID}/backups/DISK_ARC_%d_%s.%p';
    current backup controlfile as ' / oracle/RMAN/backups/${SID}/backups/DISK_CTL_%d_%s.%p';
    output channel t1;
    }


    (until the 5:5 sequence is the last log applied on standby)

    If, once that you the database in resetlogs. can no longer needed the repository information, you tell me what you will do with these archives?

    still, you can keep in the repository as

    RMAN > catalogue archivelog 'archive_file ';

    then it will be registered in the repository

  • the fax log is not up-to-date.

    I have a HP Officejet 4500 Desktop which I am running with a Windows XP system.  The fax log is not up-to-date.  How can I get the software to update the journal?  Everything seems to work fine, just does not update the log when faxes are sent or received.

    The software does not control the log of faxes.  The printer's firmware.  If not keep along as it should, there is something glitching in the firmware, or the internal connetion of the newspaper's fax modem has been disrupted.  If the internal connection was cut off, there is nothing that can be done, so let's try everything that can be done for the firmware.  There is no updated firmware for this printer, in order to fix this way came out.  The next thing to try is a couple of resets.  A hard reset first and a partial reset if the hard reset does not fix.

    To do a hard reset:

    1. Make sure that the printer is turned on.
    2. Pull out the power cord from the printer.
    3. Pull out the power cord from the wall.
    4. Wait 30 seconds.
    5. Plug back in the printer and turn it on.

    To make a partial reset:

    1. Follow steps 1-4 for a hard reset, but will not go past step 4.
    2. Plug the power cord into the wall, but connect are not in the printer.
    3. Press and hold the # and 3 buttons.
    4. While now the buttons, plug in the printer.
    5. When the lights come on, release the buttons.

    If reset does not solve the problem, then the connection was cut off, and there is nothing more we can do.

  • I bought the new iphone 6 s more and I have not configured, I just opened the phone and charged, but after some time it stop by itself, is this normal or I have a problem with my phone?

    I bought the new iphone 6 s more and I have not configured, I just opened the phone and charged, but after some time it stop by itself, is this normal or I have a problem with my phone?

    You need to activate the phone. There is nothing that the phone can not be activated.

  • I downloaded the demo of Illustrator, but it says it does not open: in this kind of mac: whats going on?

    I downloaded the demo of Illustrator, but it says it does not open: in this kind of mac: whats going on?

    This means that it is said: If the installation program does not start again, your machine is too old and has a processor not supported.

    Mylenium

  • I can't get the Microsoft wired keyboard 500 to work on my laptop. I bought a PS2 Connector USB to actually connect to laptop. I also downloaded the software from Microsoft, but still nothing. Does not work.

    Remember - this is a public forum so never post the private information such as email or phI cannot get the Microsoft wired keyboard 500 to work on my laptop. I bought a PS2 Connector USB to actually connect to laptop. I also downloaded the software from Microsoft, but still nothing. Do not work.one numbers!

    Ideas:

    • You have problems with programs
    • Error messages
    • Recent changes to your computer
    • What you have already tried to solve the problem

    Hi Louise South,.

    Follow the instructions below that may help you resolve the issue.

    Method 1:

    I suggest you to uninstall the software and reinstall it from the link below.
    http://www.Microsoft.com/hardware/download/download.aspx?category=MK

    Check whether the problem is resolved.

    Method 2:

    Follow the instructions in the link below and check if the problem is resolved.

    Troubleshoot wired keyboards that do not or only the erroneous characters category
    http://support.Microsoft.com/kb/258826

    Please post back and let us know if it helped to solve your problem.

    Kind regards
    KarthiK TP

  • Lost my copy and I tried to download the iso from the Microsoft web site, but my product key will not validate, pass this message: we had a problem with the validation query

    Original title: error Windows 7 installation files

    I bought a copy of Windows 7 at Tiger Direct on 22/05/2014.  I lost my copy and I tried to download the iso from the Microsoft web site, but my product key is not valid.  I get this error message

    We had a problem with the request for approval.

    FAQ

    See for other directions:

    http://answers.Microsoft.com/en-us/Windows/wiki/Windows_7-update/how-to-what-are-my-options-for-obtaining-Windows-7/528163c1-0b2e-4AD2-a26d-7112851d1dc2

  • Automatic shipping of the archiving log

    Hello

    I use Oracle 10 g (10.2.0.1) in RHEL 5 server. I have reproduced my prod standby database, and I want my archive logs to be shipped automatically. I used the alter system log_archive_dest_2 = 'service = reopen optional STANDBY = 20' in my prod database but the Archives of newspapers are not provided automatically. What could be the reason?

    Kind regards

    007

    Hello

    ORA-16191: customer main newspaper not connected waiting for shipment
    Cause: An attempt to ship again standby without connect to standby or invalid user credentials.

    Action: Make sure that primary and standby use password and that primary and standby files have the same SYS password. Restart primary or standby after making sure that the password file is accessible and parameter initialization REMOTE_LOGIN_PASSWORDFILE shared or EXCLUSIVE.

    Mseberg provides you with the solution. Copy the password of the primary database to the standby server and rename it in the format 'orapw.

  • With RMAN for backup, but not with the archive logs

    We run a 10.2.0.4 database and the rest 11.2.0.3. All databases are on RHEL 5.7.

    Our backups are via RMAN, with the data files, controlfiles and spfile saved to disk, then each day, it is copied off site to a backup server.

    My question is around logs archiving and RMAN.
    Our current situation is:
    -We do not save the logs to archive via RMAN. for example: backup of the list of the archivelog all; gives "specification does not match backups in the repository.
    -We set the archive_lag_target so archiving logs is produced every 30 minutes.
    -a cron job running on a remote server runs periodically to synchronize data (rsync server) the directory of archives with a remote control.
    -daily archive logs on the server host are bzip. Purge of these newspapers is scheduled for more than 3 days rman 'window of recovery '.

    I'm interested in feedback as to if our strategy around archiving logs is correct or not.

    Should we be backup logs archiving via RMAN? Are there potential problems with our approach?
    We just kept our backups in this way the DBA in the past want to see newspapers archived as opposed to it while a backupset.

    Curious to know what others are doing.

    Hello

    Welcome to OTN!

    Archivelogs with RMAN backup is a better option. When the archives are supported by RMAN, RMAN would be aware of the backup items which are required at the time of the recovery archives. You don't have to do it manually.

    On the disk space, you can delete the archives once they were saved by RMAN.

    RMAN > delete any backup archivelog entry;

    This supports the archivelogs and then remove the archives from the disk.

    If you have a dataguard configured, you can set the deletion policy 'applied on Eve', which removes the archives as and when they are applied to the database ensures there by the management of disk space again.

    RMAN > configure archivelog political of deletion to applied pending;

  • Archive log deletion with no backup of the archive logs

    I suffer from enormous size archive of the newspaper. In my previous post, I asked for help. I almost 480 GB archive log every day in our database of 11 2 under redhat linux 5.8 GR. Now, if you please help me in another case.

    If I take backup of archive logs and run delete archivelog everything until ' sysdate-1' with each backup database of day how it affects. " In my opinion there should be no problem in that I have the last incremental backup and recovery 1 days archive log in archivelog destination. If I do not archive log backups to how it will be different. Help, please.

    >

    Hello

    Sir, I know how to remove. But in my opinion delete up to sysdate-1 and taking no backup of the Archives of newspapers will
    no effect. Is in my opinion is right or wrong, that is the question.

    What I read in your original post, is that you take a daily incremental backup - Yes? I'm assuming that you also take
    a full backup on a regular basis (Sunday?).

    I was working on the assumption that the foregoing is available? I worked on a project where installation has been similar. We
    tested regularly backups - I hope that you do the same thing?

    What we used to do was FTP (script Unix - cron job - if you Google you will find Python or Perl to do the same thing - that is)
    what I wanted to, but was cancelled - very 1980, anyway) the archived redo logs on to a specific computer that holds only these files.
    After FTP "d - they have been removed from the server, freeing up space.

    Now, you say you have TB 0.5 per day - while more than a week, you will need a machine with ~ 3 TB of disk - if you can get a kind
    the scenario as this place and running, then you will have both your incremental backup and your archived redo logs for the last
    24 hours and the full backup with recovery archived records dating back to this full backup. You can also always archive on tape if
    suits. So, you will have redundant coverage - 'belt and braces' as the Americans say.

    But, to answer your question directly, "take no backup of archive logs have no effect" - that is true - it
    will not affect the operation of the database server, but if I were you, I would hang on to enough archived redo log to return to the
    last backup. That's just my humble OPINION.

    HTH,

    Paul...

    Published by: Paulie July 21, 2012 19:28

Maybe you are looking for