When ALTER SYSTEM ARCHIVE LOG happens implicitly...

Hello

When you scan the v$ archived_log SIDE primary SCHOOL, I saw below output

NAME OF CREATOR REGISTR SEQUENCE # FAL
-------------------------- ------- ------------ ----------------- ---
/U05/prod/archivelogs/ARC_816992406_1_22885.dbf ARCH ARCH 22885 No.
/U05/prod/archivelogs/ARC_816992406_1_22886.dbf FGRD FGRD 22886 No.


Then I went to the alert log file and search for the sequence #, I found that

When the newspaper switch happens through * ALTER SYSTEM ARCHIVE LOG *, then this sequence archive log CREATOR and REGISTRAR will be FGRD.
What command of newspaper happens automatically (90% complete log file), then this sequence archive log CREATOR and REGISTRAR will be ARCH.


If * ALTER SYSTEM ARCHIVE LOG * happens synchronously means control will not return to the process unless and until the underlying log file has been
archived completely, so the CREATOR and the REGISTRAR is FGRD.

My question is, under what circumstances * ALTER SYSTEM ARCHIVE LOG * happen implicitly.


Thank you

Hello

user9085814 wrote:
Thanks for the reply...

I agree with you.

The environment that I take abt is DATAGUARD Enviornment.

I have not published ALTER SYSTEM ARCHIVE LOG CURRENT of any session (foreground process) of the primary DB.
But I can still see ALTER SYSTEM ARCHIVE LOG in the log to alter.

When you call the command ALTER SYSTEM ARCHIVE LOG CURRENT , then oracle write in the journal of the alerts as:

On primary


 Wed May 15 09:16:56 2013
 Archived Log entry 789 added for thread 1 sequence 396 ID 0xf23a6e3f dest 1:
 *ALTER SYSTEM ARCHIVE LOG*
 Thread 1 cannot allocate new log, sequence 398

>

So my question on what scenario ALTER SYSTEM ARCHIVE LOG will be captured in the log of alerts.
because it's a mistake to run foreground process ALTER SYSTEM ARCHIVE LOG .

Have you had a logs archived backup RMAN script which is called ALTER SYSTEM ARCHIVE LOG CURRENT

 RMAN> run
           {
              sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
              backup  archivelog all delete all input;
           }

If you try the command ALTER SYSTEM ARCHIVE LOG CURRENT on stanby, you get error ORA-01109: database is not open. This means database is not open READ/WRITE mode.
Then we can use ALTER SYSTEM ARCHIVE LOG CURRENT on the standby database.

Thanks for the interesting thread
Mr. Mahir Quluzade
http://www.Mahir-quluzade.com

Tags: Database

Similar Questions

  • RMAN alert log Message: ALTER SYSTEM ARCHIVE LOG

    Creates a new database Oracle 10.2.0.4 and now see "ALTER SYSTEM ARCHIVE LOG" in the journal of the alerts that when online RMAN backup is executed:
    Wed Sep 26 21:52:03 2009
    ALTER SYSTEM ARCHIVE LOG
    Wed Sep 26 21:52:03 2009
    Thread 1 Advanced to record the sequence of 35 (switch LGWR)
    Currently Journal # 2 seq # 35 mem # 0: /u01/app/oracle/oradata/aatest/redo02.log
    Currently Journal # 2 seq # 35 mem # 1: /u03/oradata/aatest/redo02a.log
    Wed Sep 26 21:53:37 2009
    ALTER SYSTEM ARCHIVE LOG
    Wed Sep 26 21:53:37 2009
    Thread 1 Advanced to record the sequence of 36 (switch LGWR)
    Currently Journal # 3 seq # 36 mem # 0: /u01/app/oracle/oradata/aatest/redo03.log
    Currently Journal # 3 seq # 36 mem # 1: /u03/oradata/aatest/redo03a.log
    Wed Sep 26 21:53:40 2009
    From control autobackup
    Autobackup written control disk device
    handle ' / u03/exports/backups/aatest/c-2538018370-20090826-00'.

    I not publish a swiitch log command. The RMAN commands, I am running are:
    CONFIGURE REDUNDANCY 2 RETENTION STRATEGY;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / u03/exports/backups/aatest/%F';
    SET UP THE DEVICE TYPE DISK TYPE OF BACKUP TO COMPRESSED BACKUPSET;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / u03/exports/backups/aatest/%d_%U';
    BACKUP DATABASE MORE ARCHIVELOG;
    DELETE NOPROMPT OBSOLETE;
    DELETE NOPROMPT ARCHIVELOG UNTIL ' SYSDATE-2';

    I do not see this message on any other 10.2.0.4 instances. Someone has seen this and if yes why it shows in the log?

    Thank you

    Curt Swartzlander

    There is no problem with the log command. Please refer to the documentation for more information on the syntax 'PLUS ARCHIVELOG '.

    http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14192/bkup003.htm#sthref377

    Adding BACKUP... MORE ARCHIVELOG causes RMAN, follow these steps:

    * 1. Executes the ALTER SYSTEM ARCHIVE LOG CURRENT command.*

    * 2. All runs THE BACKUP ARCHIVELOG. Note that if backup optimization is enabled, then RMAN passes the newspapers that he has already saved to the specified device

    * 3. Backup the rest of the files specified in BACKUP command.*

    * 4. Executes the ALTER SYSTEM ARCHIVE LOG CURRENT command.*

    * 5. Backup of all remaining archived logs generated during the backup.*

    This ensures that backups of data taken when the command file is recoverable in a consistent state.

  • Multiplex Archived Logs

    With the help of 11.2.0.4.0

    I am trying to mux the newspapers archived (duplicate); However, do not know if I'm doing things.

    I followed this http://docs.oracle.com/cd/B28359_01/server.111/b28310/archredo004.htm and made the following

    LOG_ARCHIVE_DEST_1 = 'LOCATION=Z:\FlashRecoveryArea\archlogs\'

    LOG_ARCHIVE_DEST_2 = 'LOCATION=\\backupserver\archlogs_location'

    I thought I was doing the right thing with handwritten copies in both places when I run

    "alter newspaper archive of the current system. However, to take a closer look, looks like maybe it's different.

    Z:\FlashRecoveryArea\archlogs has the logs archived LOG_1_68_xxxx. ARC and LOG_1_71_xxxx. ARC

    \\backupserver\archlogs_location archived LOG_1_69_xxxx newspapers. ARC, LOG_1_70_xxxx. ARC and LOG_1_71_xxxx. ARC

    I misunderstood the document? This is not duplication of archived newspapers?

    Thank you

    I think your problem is the backup archivelog and remove that happens at the same time as the journal was cheating (i.e. newspaper is too slow).

    Just do this - see crossouts and "BOLD" text 'everything '...

    RUN

    {

    SQL "alter session set nls_date_format = 'MON-DD-YYYY HH24:MI:SS' ';"

    overlap archivelog all;

    cross-checking of backup;

    SQL 'alter system archive log current';

    SQL 'alter system archive log current';

    backup

    (database FORMAT '\backupserver\full\FULLBKUP_%d.DBID%I.%T.%s.%p.rman')

    more all archivelog delete all input FORMAT '\\backupserver\full\ARCHLOGBKUP_%d.%e.DBID%I.%T.%s.%p.rman' TAG = "FULLBKUP_PLUS_ARCHLOG";

    window recovery obsolete report of 5 days;

    delete noprompt obsolete recovery window of 5 days;

    SPFile FORMAT '\\backupserver\full\SPFILE_BKUP_%d.DBID%I.%T.%s.%p.rman' label backup = "BKUP_SPFILE";

    SQL 'alter controlfile backup database path as "\\backupserver\full\ctlfilePROD.txt" RE-USE";

    SQL "' create pfile =" \\backupserver\full\pfile_PROD.ora "of spfile"; "

    SQL 'alter system archive log current';

    SQL 'alter system archive log current';

    backup FORMAT '\\backupserver\full\ARCHLOGBKUP_%d.%e.DBID%I.%T.%s.%p.rman' archivelog delete all all the entries TAG = "BKUP_ARCHLOG";

    backup current controlfile FORMAT '\\backupserver\full\CTLFILE_BKUP_%d.DBID%I.%T.%s.%p.rman' TAG = "BKUP_CTLFILE";

    }

  • Why archive log file size constantly change?

    I have a question related to the size of the archive log file:
    I constantly receive a different size to the size of the log file archive, of course, they are smaller than to the size of the log file.
    A guru can explain to me: what possible reason could be?
    Thanks in advance!

    It can happen due to several reasons:

    When you perform a manual archive (via ALTER SYSTEM ARCHIVE LOG CURRENT/ALL)
    When Oracle must respect your ARCHIVE_LAG_TARGET (defined in seconds)

    Unless you do a manual check-in, your parameter ARCHIVE_LAG_TARGET is the reason why you see Archives of logs with different sizes as Oracle has archived the redo log as soon as the time ARCHIVE_LAG_TARGET is reached. Even if the redo log is not full, Oracle will always have to archive the redo log.

  • Arc1: 19504 error creating archive log file... after the NFS configuration

    I use an Oracle 11.2.0.3 on RHEL 5.7 (no ASM or RAC) database

    We have our archiving logs off copied to a backup location external via a cron job and rsync command, and I want to switch to NFS.
    NAME                         TYPE      VALUE
    ------------------------------------ ----------- ------------------------------
    log_archive_format               string      RCAT_%t_%s_%r.arc
    log_archive_dest_1               string      location=USE_DB_RECOVERY_FILE_DEST
    
    SQL> !df -h
    Filesystem                 Size  Used Avail Use% Mounted on
    ...
    ...
    backups:/ARCHLOG/rman       12T  7.8T  3.5T  70% /mnt/nfs_archlog
    
    SQL> alter system set log_archive_dest_2='LOCATION=/mnt/nfs_archlog optional' scope=both;
    
    System altered.
    When I run 'alter system archive log current', I see the error message archiver in the alert below log...
    Wed Aug 29 14:42:08 2012
    ALTER SYSTEM ARCHIVE LOG
    Wed Aug 29 14:42:08 2012
    Thread 1 advanced to log sequence 23044 (LGWR switch)
      Current log# 4 seq# 23044 mem# 0: /u01/oradata/RCAT/redo_4a.dbf
      Current log# 4 seq# 23044 mem# 1: /u02/oradata/RCAT/redo_4b.dbf
    Wed Aug 29 14:42:14 2012
    ARC1: Error 19504 Creating archive log file to '/mnt/nfs_archlog/RCAT_1_23043_602355789.arc'
    Archived Log entry 24282 added for thread 1 sequence 23043 ID 0x165341cd dest 1:
    However, when I check the NFS location I see that the file is there.
    [oracle@rman nfs_archlog]$ ls -la
    total 72
    drwxr-x--- 14 oracle oinstall   4096 Aug 29 14:42 .
    drwxr-xr-x  3 root   root       4096 Aug 29 14:16 ..
    -rw-r-----  1 oracle oinstall 204288 Aug 29 14:42 RCAT_1_23043_602355789.arc
    On the NFS host, I see
    [root@backups archivelog]# ls -la
    total 68
    drwxr-x---. 14 500 500   4096 Aug 29 14:42 .
    drwxrwxr--.  3 500 500   4096 May  8 13:54 ..
    -rw-r-----.  1 500 500 204288 Aug 29 14:42 RCAT_1_23043_602355789.arc
    The/etc/exports on NFS host has the permissions set to read/write, no_root_squash.

    Is there something obvious that I'm missing?

    the folder is created by newspaper archive must have atleat authorisation from 770.

  • Oracle database archive logs

    Hi all

    I searched the Oracle and Internet Documents. It is really hard to get information on the management of the archive Log, so I thought to post it here:

    Now, our Database 9i (EBS 11.5.x) was in no archive mode, so I allowed him to archive mode.

    Edit the pfile $ORACLE_HOME/admin/SID/pfile who will be /oracle/proddb/9.2.0/dbs/initPROD.ora

    ############################

    # Archive Log Destinations-benr(10/15/04)

    ############################

    Log_archive_dest_1 = ' location = / Uncordon / archive.

    log_archive_start = TRUE


    then connect to the database





    SQL > shutdown normal;

    SQL > startup mount exclusive;

    SQL > alter system set log_archive_start = TRUE scope = spfile;
    SQL > alter system set log_archive_dest_1='LOCATION= /oracle/archivelog '
    scope=both;
    SQL > alter archivelog database;
    SQL > CHANGE the START of the SYSTEM ARCHIVE LOG;
    SQL > alter database open;
    SQL > alter system archive log all;
    SQL > change the start of the archive log system;
    SQL > archive log start;


    The next day, I checked the location of archive and sparked an archive of 1 GB even if there is no activity on the database.

    root@test4:/oracle/archivelog>ls
    1_844.dbf   1_862.dbf   1_880.dbf   1_898.dbf   1_916.dbf   1_934.dbf
    1_845.dbf   1_863.dbf   1_881.dbf   1_899.dbf   1_917.dbf   1_935.dbf
    1_846.dbf   1_864.dbf   1_882.dbf   1_900.dbf   1_918.dbf   1_936.dbf
    1_847.dbf   1_865.dbf   1_883.dbf   1_901.dbf   1_919.dbf   1_937.dbf
    1_848.dbf   1_866.dbf   1_884.dbf   1_902.dbf   1_920.dbf   1_938.dbf
    1_849.dbf   1_867.dbf   1_885.dbf   1_903.dbf   1_921.dbf   1_939.dbf
    1_850.dbf   1_868.dbf   1_886.dbf   1_904.dbf   1_922.dbf   1_940.dbf
    1_851.dbf   1_869.dbf   1_887.dbf   1_905.dbf   1_923.dbf   1_941.dbf
    1_852.dbf   1_870.dbf   1_888.dbf   1_906.dbf   1_924.dbf   1_942.dbf
    1_853.dbf   1_871.dbf   1_889.dbf   1_907.dbf   1_925.dbf   1_943.dbf
    1_854.dbf   1_872.dbf   1_890.dbf   1_908.dbf   1_926.dbf   1_944.dbf
    1_855.dbf   1_873.dbf   1_891.dbf   1_909.dbf   1_927.dbf   1_945.dbf
    1_856.dbf   1_874.dbf   1_892.dbf   1_910.dbf   1_928.dbf   1_946.dbf
    1_857.dbf   1_875.dbf   1_893.dbf   1_911.dbf   1_929.dbf   1_947.dbf
    1_858.dbf   1_876.dbf   1_894.dbf   1_912.dbf   1_930.dbf   lost+found
    1_859.dbf   1_877.dbf   1_895.dbf   1_913.dbf   1_931.dbf   test.txt
    1_860.dbf   1_878.dbf   1_896.dbf   1_914.dbf   1_932.dbf
    1_861.dbf   1_879.dbf   1_897.dbf   1_915.dbf   1_933.dbf
    

    Question

    1. How can I delete old logs archiving without using RMAN?

    2. How should I know which Archives connects to keep and delete?

    3. is there a way to know why the database generates so many newspapers to check-in?

    Hello

    Yes, you must keep this archive. You can schedule the job to compress files to archive (record use of space) and move it to another place as a backup.

    You can schedule both COLD backup once a week, in this case it is scabies archive for a week.

    HTH

  • RMAN-03009 and ORA-01858 everything by backing up archiving logs

    Hello!

    Since today, I get the above errors to backup the fra tape archiving logs. I tried the following: error ORA-01858 in RMAN during backup backupset format ' / test/rman/%U'
    If I manually do the backup for a client, it works!

    environment:
    Server: windows 2008 standard server
    Oracle: 10.2.0.4.0

    configuration of RMAN:
    CONFIGURE RETENTION POLICY TO THE 5 DAY RECOVERY WINDOW;
    CONFIGURE BACKUP OPTIMIZATION
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFAPEX. ORA'; # by default

    Error log:
    Recovery Manager: Release 10.2.0.4.0 - Production on Thu Oct 1 04:30 2009

    Copyright (c) 1982, 2007, Oracle. All rights reserved.

    connected to target database: APEX (DBID = 1331326226)
    connected to the recovery catalog database

    RMAN > sql 'alter system archive log current;
    2 > run {}
    3 > #-> drive backup
    4 > backup archivelog all;
    5 > # FRA-> band
    6 > allocate channel ch1 type 'sbt_tape '.
    7 > PARMS = "BLKSIZE = 262144, ENV = (CvClientName = ora5neu, CvInstanceName = Instance001)"; "
    8 > save the recovery area.
    {9 >}
    10 >
    SQL statement: alter system archive log current

    From backup 1st October 09
    Current archived log
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid = devtype 81 = DISK
    skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_09_10\O1_MF_1_2720_5BKO9BOL_. ARC; already saved 1 time
    ...
    skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_10_01\O1_MF_1_2981_5D7PZDXX_. ARC; already saved 1 time
    channel ORA_DISK_1: from archive newspaper backupset
    channel ORA_DISK_1: specification of archive log backup set
    archive log entry thread = 1 sequence = 2733 recid = 2733 stamp = 697286083
    archive log entry thread = 1 sequence = 2734 recid = 2734 stamp = 697293002
    archive log entry thread = 1 sequence = 2735 recid = 2735 stamp = 697293004
    archive log entry thread = 1 sequence = 2856 recid = 2856 stamp = 698142602
    archive log entry thread = 1 sequence = 2857 recid = 2857 stamp = 698142603
    archive log entry thread = 1 sequence = 2982 recid = 2982 stamp = 699078603
    archive log entry thread = 1 sequence = 2983 recid = 2983 stamp = 699078605
    channel ORA_DISK_1: starting piece 1 to October 1 09
    channel ORA_DISK_1: finished piece 1 to October 1 09
    piece handle = D:\FRA\APEX\BACKUPSET\2009_10_01\O1_MF_ANNNN_TAG20091001T043006_5D8520K4_. Tag BKP = comment TAG20091001T043006 = NONE
    channel ORA_DISK_1: complete set of backups, time: 00:00:03
    Backup finished on 1st October 09

    From control file and SPFILE Autobackup 1st October 09
    piece handle = D:\FRA\APEX\AUTOBACKUP\2009_10_01\O1_MF_S_699078626_5D8522W8_. Comment BKP = NONE
    File control finished and SPFILE Autobackup to on 1 October 09

    output channel: ORA_DISK_1
    allocated channel: ch1
    channel ch1: sid = 81 = SBT_TAPE devtype
    channel ch1: CommVault Systems for Oracle: Version 7.0.0 (BUILD76)

    From backup 1st October 09
    specification does not match any data file copy in the repository
    skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_09_10\O1_MF_1_2720_5BKO9BOL_. ARC; already saved 4 times
    ...
    jump key 5203 backupset; already saved 1 time
    channel ch1: from archive newspaper backupset
    channel ch1: specification of archive log backup set
    archive log entry thread = 1 sequence = 2982 recid = 2982 stamp = 699078603
    archive log entry thread = 1 sequence = 2983 recid = 2983 stamp = 699078605
    channel ch1: starting piece 1 to October 1 09
    channel ch1: finished piece 1 to October 1 09
    piece handle = i2kqm5vv_1_1 tag = comment TAG20091001T043031 = API 2.0, MMS Version 7.0.0.76 Version
    channel ch1: complete set of backups, time: 00:00:16
    entry count = 4670 stamp = 699064230 = creation_time backupset 1st October 09
    channel ch1: starting piece 1 to October 1 09
    RMAN-03009: failure of the backup command on channel ch1 at 2009-10-01 04:31:19
    ORA-01858: a non-digit character was found here where was waiting for a digital
    continue other job steps, not a not working will not re-run
    entry count = 4672 stamp = 699078622 = creation_time backupset 1st October 09
    channel ch1: starting piece 1 to October 1 09
    channel ch1: backup D:\FRA\APEX\BACKUPSET\2009_10_01\O1_MF_ANNNN_TAG20091001T043006_5D8520K4_ piece. BKP
    piece handle = i0kqm5uu_1_2 comment = API Version 2.0, Version MMS 7.0.0.76
    channel ch1: finished piece 1 to October 1 09
    channel ch1: complete set of backups, time: 00:00:07
    entry count = 4673 stamp = 699078626 = creation_time backupset 1st October 09
    channel ch1: starting piece 1 to October 1 09
    output channel: ch1
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03009: failure of the backup command on channel ch1 at 01/10/2009 04:31:35
    ORA-01858: a non-digit character was found here where was waiting for a digital

    Complete recovery manager.

    Thanks for your help!

    Ciao,.
    Christian

    See my note of the Support of Oracle:

    Subject: RMAN backup fails with RMAN-03009 ORA-01858 ORA-01861
    DOC - ID: 744047.1 Type: PROBLEM
    Modification date: 20 March 2009 status: MODERATE

    This could be a NLS_DATE_FORMAT / NLS_LANG questioned.

  • Archive log gap is asleep when the audit function is set to DB

    Hello

    I'm a new dba. I am facing a problem to the production server, that whenever audit_trail is set to db, gap journal archive is created on the site of the previous day.

    My version of the database is 10.2.0.4
    Operating system is windows 2003 R2

    Audit_trail is set to db only to the main site, after you have set the parameter DB when I bounced the database and set the log file, gap journal archive is created in the waiting... I use the LGWR log transport mode.

    Is there any transport of newspapers and relationship beteen audit_trail?
    Please note that my log location archive two sites has enough disk space and the drive works very well. Also my primary and standby is in WAN.

    Please help me in this. Any help will be much appreciated.

    Here's a trace file that can be useful to give an opinion.


    D:\oracle\admin\sbiofac\bdump\sbiofac_lns1_6480.TRC dump file
    Kill Jun 05 13:46:02 2012
    ORACLE V10.2.0.4.0 - Production vsnsta = 0
    vsnsql = 14 vsnxtr = 3
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
    With partitioning, OLAP, Data Mining and Real Application Testing options
    Windows Server 2003 V5.2 Service Pack 2 Version
    CPU: 2 - type 586, physical cores 1
    Process affinity: 0x00000000
    Memory (success/Total): Ph: 16504 M / 18420 M, Ph + FCP: 41103/45775 mafuta, GOES: 311 M / 2047 M
    Instance name: sbiofac

    Redo thread mounted by this instance: 1

    Oracle process number: 21

    Windows thread ID: 6480, image: ORACLE. EXE (LNS1)


    NAME OF THE SERVICE :() 13:46:02.703 2012-06-05
    SESSION ID: (534.1) 2012-06-05 13:46:02.703
    kcrr.c 13:46:02.703 58902 2012-06-05
    LNS1: initialization of communication LGWR
    LNS1: connection to the KSR channel
    Success
    LNS1: subscribe to channel KSR
    Success
    2012-06-05 13:46:02.750 58955 kcrr.c
    LNS1: successfully initialized ASYNC = 1
    Destination is specified with ASYNC = 61440
    kcrr.c 13:46:02.875 73045 2012-06-05
    Sending thread 1 seq 2217 online journal [1 logfile] in standby mode
    Repeat customer shipping performing a pending connection
    kcrr.c 13:46:03.656 66535 2012-06-05
    Connected mode standby successfully
    Customer logon and security successful trading!
    Archiving on blocks of destination sbiofacdr ASYNC = 20480
    Allocation of blocks of ASYNC: previous blocks = 0 new blocks = 20480
    Open log file [logno 1]
    2012-06-05 13:46:44.046
    Error 272 writing log file archive ensures the host 'sbiofacdr '.
    ORA-00272: the archive log write error
    kcrr.c 13:46:44.078 62692 2012-06-05
    LGWR: I/O error 272 archiving log 1 to 'sbiofacdr '.
    kcrr.c 13:46:44.078 60970 2012-06-05
    kcrrfail: err dest:2: 272 explosion of strength: 0:1
    2012-06-05 13:47:37.031
    kcrr.c 13:47:37.031 73045 2012-06-05
    Log fil 1 seq 2218 online shipping [logfile 2] in standby mode
    kcrr.c 13:47:37.046 73221 2012-06-05
    Stop [due to no ASYNC destination more]
    Again Push Server: Release the buffer ASYNC PGA
    LNS1: Make a channel of delivery for the next time around...

    Hello again;

    I believe you can discover that restore you rates of production using LOG_ARCHIVE_TRACE:

    SQL > show parameter LOG_ARCHIVE_TRACE

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    log_archive_trace integer 0

    http://docs.Oracle.com/CD/B19306_01/server.102/b14237/initparams107.htm

    In addition to the SDU, you can define SEND_BUF_SIZE and RECV_BUF_SIZE

    This is the Oracle document on this:

    http://docs.Oracle.com/CD/B19306_01/network.102/b14212/performance.htm

    You can define SDU in the tnsnames.ora thus:

    PRIMARY =
      (DESCRIPTION =
        (SDU=32767)
           (ADDRESS=(PROTOCOL=tcp) (HOST=) (PORT=1521)0
        (CONNECT_DATA=
          (SERVICE_NAME=PRIMARY.hostname))
    )
    

    The 'database Net Services Administrator's Guide' post above link is probably the best source of information.

    Best regards

    mseberg

  • Do we need apostrophes when you set values with ALTER SYSTEM?

    DB version: 11.2, 10.2
    Version: AIX

    What logs the values of character with ALTER SYSTEM, do I have to enclose the value within single quotes.


    Both the below worked. So I'm a bit confused.
    SQL> ALTER system set audit_trail=NONE scope=spfile;
    
    System altered.
    
    -- Tested with single quotes on another DB
    SQL> ALTER system set audit_trail='NONE' scope=spfile;
    
    System altered.

    What logs the values of character with ALTER SYSTEM, do I have to enclose the value within single quotes.

    When you pass several parameters, you can use single quotes, in other cases sound option.

    If you have multiple databases on hold, you must configure by separating with single quotes.
    For example,.
    (1) fal_client = "STBY1", "STBY2", "STBY3" and so on.
    (2) log_archive_dest_2 = "service = stby lgwr async... '

    If you see under SPFILE settings, here, some are mentioned with single quotes & SEC_CASE_SESITIVE_LOGIN is not in quotes. But the value is always the same.

    From SPFILE;

    *.remote_login_passwordfile='EXCLUSIVE'
    *.sec_case_sensitive_logon=FALSE                                       "used NO QUOTES"
    *.sga_max_size=16106127360
    *.star_transformation_enabled='TRUE'                                        "QUOTES"
    
    SQL> show parameter remote_login
    
    NAME                                 TYPE        VALUE
    ------------------------------------ ----------- ------------------------------
    remote_login_passwordfile            string      EXCLUSIVE
    SQL> show parameter sec_case
    
    NAME                                 TYPE        VALUE
    ------------------------------------ ----------- ------------------------------
    sec_case_sensitive_logon             boolean     FALSE                                     "used NO QUOTES"
    SQL> show parameter sga_max_
    
    NAME                                 TYPE        VALUE
    ------------------------------------ ----------- ------------------------------
    sga_max_size                         big integer 15G
    SQL> show parameter star_tran
    
    NAME                                 TYPE        VALUE
    ------------------------------------ ----------- ------------------------------
    star_transformation_enabled          string      TRUE                                         "QUOTES"
    SQL>
    
  • When I click on dump debugging, system, thumbnails and files dump files memory system archive of windows error reporting

    When I click on dump debugging, system, thumbnails and files dump files memory system archive of windows error reporting
    They does not clear my cleaning disc on my computer at home. If someone could help
    deal with this problem?

    * original title - disc clean up problem *.

    You are welcome.

  • 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

  • The user name is incorrect on my system, so when I try to log in the password is incorrect.

    User login problem

    I have only one user, and the user name is messed up, so when I try to log on the user name does not match the password. So, I just can't. I tried the F8 key it didn't have anything to help me. All the answers? Please, I beg you. I have my Vista Ultimate cd, but I have a lot of photos and stories I wrote. I don't want to lose these.

    Hello

     
    I suggest you go through the following links.
    Microsoft's strategy concerning lost or forgotten passwords
    http://support.Microsoft.com/kb/189126
     
  • 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;

  • How do duplex CARS DB archiving logs?

    Hello

    I need to set up the location on the spare, local disk for archiving for two nodes RAC, apart from ASMjournals.
    The reason behind this is to transfer the logs (as well as full backups) at a remote location to ensure the security of the data.
    I have traced same remote directory a: Drive on both nodes.

    2-node RAC Standard Database 11.2.0.2
    Windows 2008 R2 Standard
    + ASM DATA storage

    SYS@proton2x1 > list of archive logs
    Database log mode Archive Mode
    Active AutoArchive
    Destination of archive USE_DB_RECOVERY_FILE_DEST
    Sequence of journal online oldest 1750
    Log sequence archive 1752
    Current log sequence 1752

    SYS@proton2x1 > display recov
    VALUE OF TYPE NAME
    db_recovery_file_dest chain + DATA

    ----

    The problem is when I put in duplex rental:
    SQL > alter system set log_archive_duplex_dest =' LOCATION = R:' SCOPE = spfile;
    nodes to restart and go online newspapers 3 times it crashes and no archiive of newspapers are written in the R:\ directory.
    Alert log says:
    LGWR: Error 16017 validate archivelog destination information

    I played in a manner similar to other parameters:
    ALTER system set log_archive_dest_1 =' LOCATION = + DATA REQUIRED ' SCOPE = spfile;
    ALTER system set log_archive_dest_2 =' LOCATION = R: OPTIONAL ' SCOPE = spfile;

    with the same question.

    The question is, how to set up the second location of the archivelogs, ASM storage?
    or maybe someone has another idea how do to transfer/copy archivelogs to remote storage?
    I have of course command "cp" on asmcmd tool, but it would be difficult to synchronize the source and target locations.

    I thhink you cannot use a drive mapped in the Windows environment. Search the metalink if there is a way to mount the drive.
    The error says that the device is not accessible.

    ********************************

    ERROR on line 1:

    ORA-02097: the parameter cannot be changed because specified value is not valid

    ORA-16032: parameter LOG_ARCHIVE_DEST_2 destination string cannot be translated.

    ORA-09291: sksachk: invalid device specified for the destination of archive

    OSD-04018: cannot access the specified directory or device.

    S/O-error: (OS 3) the system cannot find the path specified.
    **************************************

    Try to use a local disk folder just to test and eliminate the issue mounted.

    Let us know if on a local disk, the log_archive_dest_2 is working.sf

    Edited by: ADaniel March 20, 2012 20:53

  • Archive log generations statistics

    Hello

    1. I find the number of archive logs generated during 1 month in my 11 g (11.1.0.6) of the Oracle database. How do I find that?

    4 h is it possible to change the location of the Archive log when the database is in 11g (11.1.0.6)?

    Kind regards

    007

    007 wrote:
    Hello

    1. I find the number of archive logs generated during 1 month in my 11 g (11.1.0.6) of the Oracle database. How do I find that?

    You cannot get out of the database, unless you build something for her. History of ARCHIVELOG is kep for about 14 days
    I have to use the query to see the amount of archiving a day below:

    Select to_char (first_time, 'dd-mm-yyyy') reference, Go Archives 'round (sum(blocks*block_size)/1024/1024/1024,2).
    v $ archived_log where first_time > trunc (sysdate)-10
    To_char Group (first_time, 'dd-mm-yyyy') order by 1;

    4 h is it possible to change the location of the Archive log when the database is in 11g (11.1.0.6)?

    Yes.
    Use

    ALTER SYSTEM SET LOG_ARCHIVE_DEST_1 =' LOCATION =';

    Make sure that the new location exists and is writable

    See you soon,.
    FJFranken

Maybe you are looking for