Cross Pltform Archive Log Application.

Hi !!!
In my organisation we have installed Oracle 10g on HP Unix & Oracle 10g on Windows 2000 Server, we are on OLTP. Now I want to get the ARCHIVE LOGS created from ORACLE 10g - HP UNIX on to ORACLE 10g - Windows 2000 Server. Can this be done, require urgent help on this.
Thank's
Rajeev.

You cannot use the archivelogs of oracle onHP in oracle on Win2K.
Are you planning to have a clone of your HP database or Win2k?
Or
Plannnig to use Win2K server as standby?

Similar Messages

  • Any way to undo archive log application?

    While cloning the target from the source, we were supposed to restore till log sequence x and we restored it till x+1. Is there any way to undo an archive log application till sequence x. Our database version is 10.2.0.2

    1) However, Is it possible to flashback the database to a point before the resetlogs in 10g?
    If you meant that after doing flashback databse and resetlogs, can you do it for the point past the resetlogs than yes you can.See this.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_9011.htm#SQLRF01801
    2) Do we have any other options apart from flash back since it is disabled.
    Not that which I can think of.If you don't have flashback database,the other option will be to manualy undo the changes.
    Aman....

  • Archived log application to a cold backup fails with ora-00328

    I am testing backup and recovery scenario as mentioned in Metalink Doc id:69468.1 where a cold backup of one production server is restored on a separate machine. Some activity, say a table creation in some schema and insertion of rows in it is followed by a few log switches. Next I moved just the archived logs ( newly generated) to the test machine and proceed as follow to recover but log application is failing as below,any help would be appreciated!
    SQL> startup mount;
    ORACLE instance started.
    Total System Global Area 205520896 bytes
    Fixed Size 1248116 bytes
    Variable Size 71304332 bytes
    Database Buffers 130023424 bytes
    Redo Buffers 2945024 bytes
    Database mounted.
    SQL> recover database until cancel using backup controlfile;
    ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
    ORA-00289: suggestion :
    C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
    ORA-00280: change 581754 for thread 1 is in sequence #1
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00328: archived log ends at change 581535, need later change 581754
    ORA-00334: archived log:
    'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
    SQL> recover database until cancel;
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    SQL> recover database until cancel using backup controlfile;
    ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
    ORA-00289: suggestion :
    C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
    ORA-00280: change 581754 for thread 1 is in sequence #1
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
    ORA-00328: archived log ends at change 581535, need later change 581754
    ORA-00334: archived log:
    'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
    SQL> recover database using backup controlfile;
    ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
    ORA-00289: suggestion :
    C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
    ORA-00280: change 581754 for thread 1 is in sequence #1
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
    ORA-00328: archived log ends at change 581541, need later change 581754
    ORA-00334: archived log:
    'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
    Please Help

    The error displayed stated you are required to have an specific sequence:
    ORA-00280: change 581754 for thread 1 is in sequence #1
    Check the contents of the v$recover_file dynamic view and verify if you really have all required archivelog files.
    ~ Madrid

  • Question about Archive Log Deletion policy

    I've a problem to understand the Archive Log Deletion policy, and I I'd like to this problem explain with the following example.
    Messages of the database are in German, but I guess you'll understand them.
    SQL> startup
    ORACLE-Instance hochgefahren.
    Total System Global Area 5344731136 bytes
    Fixed Size                  2129240 bytes
    Variable Size            2684355240 bytes
    Database Buffers         2617245696 bytes
    Redo Buffers               41000960 bytes
    Datenbank mounted.
    Datenbank geöffnet.
    SQL> archive log list
    Datenbank-Log-Modus              Archive-Modus
    Automatische Archivierung             Aktiviert
    Archivierungsziel            E:\oracle\thetis_iv\arch
    Älteste Online-Log-Sequenz     17917
    Nächste zu archivierende Log-Sequenz   17919
    Aktuelle Log-Sequenz           17919
    SQL> alter system switch logfile;
    System wurde geändert.I created a brand new archive log.
    SQL> exit
    Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
    D:\OracleDB\product\11.1.0\db_1\BIN>dir E:\oracle\thetis_iv\arch
    Datenträger in Laufwerk E: ist Volume
    Volumeseriennummer: 3EBD-77E5
    Verzeichnis von E:\oracle\thetis_iv\arch
    06.04.2011  15:04    <DIR>          .
    06.04.2011  15:04    <DIR>          ..
    06.04.2011  15:04        17.137.152 ARC17919_0721667907.001
                   1 Datei(en),     17.137.152 Bytes
                   2 Verzeichnis(se), 41.073.258.496 Bytes freiand this is the only archive log in the directory. Now I start rman:
    D:\OracleDB\product\11.1.0\db_1\BIN>rman target / catalog rmanrepo@rmanrepo
    Recovery Manager: Release 11.1.0.7.0 - Production on Mi Apr 6 15:05:35 2011
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    Mit Ziel-Datenbank verbunden: ENTWIV (DBID=21045568)
    Kennwort für Recovery-Katalog-Datenbank:
    Verbindung mit Datenbank des Recovery-Katalogs
    RMAN> show all;
    RMAN-Konfigurationsparameter für Datenbank mit db_unique_name ENTWIV sind:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\oracle\thetis_iv\backup\CF_%F_ENTWIV.ORA';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
    CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'ENV=(TPDO_OPTFILE=D:\Services\Tivoli\TSM\AgentOBA64\tpdo.opt)';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLEDB\PRODUCT\11.1.0\DB_1\DATABASE\SNCFENTWIV.ORA'; # defaultThe archive log deletion policy says the the logfiles have to be backed up for two times before they get deleted.
    Now I backup all archive logs, that havn't been backed up for at least two times.
    RMAN> run { backup archivelog all not backed up 2 times
    2>       format '%d_AR_%Y%M%D_%s_%t'
    3>       tag 'ARCHIVE LOGS'
    4>       DELETE ALL INPUT;
    5>     }
    Starten backup um 06.04.2011 15:08:01
    Aktuelles Log archiviert
    Zugewiesener Kanal: ORA_SBT_TAPE_1
    Kanal ORA_SBT_TAPE_1: SID=253 Device-Typ=SBT_TAPE
    Kanal ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
    Kanal ORA_SBT_TAPE_1: Backup Set für Archive Log wird begonnen
    Kanal ORA_SBT_TAPE_1: Archive Logs in Backup Set werden angegeben
    Eingabe-Archive-Log-Thread=1 Sequence=17919 RECID=147 STAMP=747759899
    Eingabe-Archive-Log-Thread=1 Sequence=17920 RECID=148 STAMP=747760081
    Kanal ORA_SBT_TAPE_1: Piece 1 wird auf 06.04.2011 15:08:02 begonnen
    Kanal ORA_SBT_TAPE_1: Piece 1 auf 06.04.2011 15:08:09 beendet
    Piece Handle=ENTWIV_AR_20110406_23_747760082 Tag=ARCHIVE LOGS Kommentar=API Version 2.0,MMS Version 5.5.1.0
    Kanal ORA_SBT_TAPE_1: Backup Set vollstõndig, abgelaufene Zeit: 00:00:08
    Kanal ORA_SBT_TAPE_1: Archive Logs werden gel÷scht
    Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17919_0721667907.001 RECID=147 STAMP=747759899
    Archive Log-Dateiname=E:\ORACLE\THETIS_IV\ARCH\ARC17920_0721667907.001 RECID=148 STAMP=747760081
    Beendet backup um 06.04.2011 15:08:10
    RMAN> exit
    Recovery Manager abgeschlossen.
    D:\OracleDB\product\11.1.0\db_1\BIN> dir E:\oracle\thetis_iv\arch
    Datenträger in Laufwerk E: ist Volume
    Volumeseriennummer: 3EBD-77E5
    Verzeichnis von E:\oracle\thetis_iv\arch
    06.04.2011  15:08    <DIR>          .
    06.04.2011  15:08    <DIR>          ..
                   0 Datei(en),              0 Bytes
                   2 Verzeichnis(se), 41.090.396.160 Bytes freirman deleted all archive logs, even I they are on tape only once by now.
    Thats not what I expected. Where is my mistake?

    Hi,
    I do new tests it's very strange.
    BACKUP ARCHIVELOG command is not obeying the policy of archivelog.
    You can open a SR on MOS. (to check bugs)
    I reproduce the same test and the result was the same, it seems that this is a bug.
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
    RMAN> backup archivelog all not backed up 2 times delete all input;
    Starting backup at 06-APR-11
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=15 RECID=16 STAMP=747753711
    input archived log thread=2 sequence=20 RECID=17 STAMP=747753714
    input archived log thread=1 sequence=16 RECID=19 STAMP=747753729
    input archived log thread=2 sequence=21 RECID=18 STAMP=747753729
    channel ORA_DISK_1: starting piece 1 at 06-APR-11
    channel ORA_DISK_1: finished piece 1 at 06-APR-11
    piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t132210_0.304.747753731 tag=TAG20110406T132210 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_15.293.747753711 RECID=16 STAMP=747753711
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_20.295.747753715 RECID=17 STAMP=747753714
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_16.294.747753729 RECID=19 STAMP=747753729
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_21.298.747753729 RECID=18 STAMP=747753729
    Finished backup at 06-APR-11
    RMAN> list archivelog all;
    specification does not match any archived log in the repositoryOracle Docs Says:
    The BACKUP ARCHIVELOG ... DELETE INPUT command deletes archived log files after they are backed up.
    This command eliminates the separate step of manually deleting archived redo logs.
    With DELETE INPUT, RMAN deletes only the specific copy of the archived log chosen for the backup set.
    With DELETE ALL INPUT, RMAN deletes each backed-up archived redo log file from all log archiving destinations.
    As explained in "Configuring an Archived Redo Log Deletion Policy",
    the BACKUP ... DELETE INPUT and DELETE ARCHIVELOG commands obey the archived redo log deletion policy
    for logs in all archiving locations. For example, if you specify that logs should only be deleted when backed
    up at least twice to tape, then BACKUP ... DELETE honors this policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmbckba.htm#BRADV89524
    But in ours case it's not honors this policy.
    Only with the FORCE command should this happen. But it is not our case.
    Oracle Docs:
    If FORCE is not specified on the deletion commands,
    then these deletion commands obey the archived log deletion policy.
    If FORCE is specified, then the deletion commands ignore the archived log deletion policy.http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta010.htm#RCMRF113
    Alternatively you can do the following:
    Set the commands separately.
    Check this:
    RMAN>  run {
    2> backup archivelog all not backed up 2 times ;
    3> delete archivelog all backed up 2 times to disk;
    4> }
    Starting backup at 06-APR-11
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=2 sequence=22 RECID=21 STAMP=747755128
    input archived log thread=1 sequence=17 RECID=20 STAMP=747755127
    channel ORA_DISK_1: starting piece 1 at 06-APR-11
    channel ORA_DISK_1: finished piece 1 at 06-APR-11
    piece handle=+DATA/orcl/backupset/2011_04_06/annnf0_tag20110406t134528_0.295.747755129 tag=TAG20110406T134528 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 06-APR-11
    released channel: ORA_DISK_1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=78 instance=orcl1 device type=DISK
    RMAN-08138: WARNING: archived log not deleted - must create more backups
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_1_seq_17.298.747755127 thread=1 sequence=17
    RMAN-08138: WARNING: archived log not deleted - must create more backups
    archived log file name=+DATA/orcl/archivelog/2011_04_06/thread_2_seq_22.294.747755129 thread=2 sequence=22
    RMAN>Edited by: Levi Pereira on Apr 6, 2011 1:35 PM

  • Missing archived logs in v$archived_log

    I want to monitor if system accounts such as system, sys or other DBA accounts
    did any DML in my application schema. What are the minimal audit statements?
    needed to accomplish this. I know using Oracle Database Vault one can set realm to restrict this but I do
    not have Data Vault, just looking to audit this using Oracle’s database auditing.
    My organization also has Oracle Audi Vault, but Database Auditing Events have to be set in database
    first for collection agent to pass this information to Oracle Audit Vault server.
    Thanks a lot.

    Duplicate post
    Please ignore
    Missing archived logs in v$archived_log
    Handle:      user632098
    Status Level:      Newbie
    Registered:      Apr 20, 2008
    Total Posts:      115
    Total Questions:      29 (28 unresolved)
    Edited by: sb92075 on Dec 19, 2009 4:49 PM

  • ORA-19571: archived-log recid 118360 stamp not found in control file - help

    Hi
    Every backup I do I am getting an error like below at the bottom :, every backup I do, it's complaaining about DIFFERENT archive log.
    ORA-19571: archived-log recid 118360 stamp 705446770 not found in control file.
    I have set keep control file info to 14 days, my retention is 7 days in RMAN, so I don't know why it's complaining, below is the full log.
    It seeems to be having problems with archive logs that have just been generated while it's doing the backup I think??
    channel d3: specifying archive log(s) in backup set
    input archive log thread=1 sequence=705 recid=124248 stamp=707103829
    input archive log thread=1 sequence=706 recid=124249 stamp=707103830
    input archive log thread=1 sequence=707 recid=124250 stamp=707103831
    input archive log thread=1 sequence=708 recid=124251 stamp=707103831
    input archive log thread=1 sequence=709 recid=124252 stamp=707103832
    input archive log thread=1 sequence=710 recid=124253 stamp=707103832
    input archive log thread=1 sequence=711 recid=124254 stamp=707103833
    input archive log thread=1 sequence=712 recid=124255 stamp=707103833
    input archive log thread=1 sequence=713 recid=124256 stamp=707103834
    input archive log thread=1 sequence=714 recid=124257 stamp=707103835
    input archive log thread=1 sequence=715 recid=124258 stamp=707103835
    input archive log thread=1 sequence=716 recid=124259 stamp=707103836
    input archive log thread=1 sequence=717 recid=124260 stamp=707103836
    input archive log thread=1 sequence=718 recid=124261 stamp=707103837
    input archive log thread=1 sequence=719 recid=124262 stamp=707103837
    input archive log thread=1 sequence=720 recid=124263 stamp=707103838
    input archive log thread=1 sequence=721 recid=124264 stamp=707103838
    input archive log thread=1 sequence=722 recid=124265 stamp=707103839
    input archive log thread=1 sequence=723 recid=124266 stamp=707103840
    input archive log thread=1 sequence=724 recid=124267 stamp=707103840
    input archive log thread=1 sequence=725 recid=124268 stamp=707103841
    input archive log thread=1 sequence=726 recid=124269 stamp=707103841
    RMAN-03009: failure of backup command on d3 channel at 01/01/2010 02:11:33
    ORA-19571: archived-log recid 118360 stamp 705446770 not found in control file
    continuing other job steps, job failed will not be re-run
    channel d6: starting compressed archive log backupset
    channel d6: specifying archive log(s) in backup set
    input archive log thread=1 sequence=641 recid=124034 stamp=707077994
    input archive log thread=1 sequence=642 recid=124035 stamp=707077994
    ...

    It's a rac, so shall I restart one instance at a time?? Or the whole thing? I am using an recovery catalog, so should I be connected to the recovery catalog Or control file to do a cross check backup, also when it's doing the backup do u recon it can't fing archivelog in controlfile file as it's not done a resync, should I force it to do a resync after a backup then backup the archive logs??? I really don't want to bounce the db as it's 24/7

  • Question about import in archive log mode

    Hello.
    I am a developer, I have ordered to write a script that makes the import of a schema of a database (release 9.2.0.7). That import will be done once a day. I have seen that in my development environment the import creates 54 archivers files (10M aprox. each), that means more that half a Gb a day, it seems too much to me.
    I cannot see why all those archivers can be useful. Would a good way of proceeding the following?
    1. Forcing an archiver just before the import (I do not know how to do that) so that a backup could be done to the state before the import.
    2. Disabling archive log mode during the import and enabling it just after the import (I do not know how to do that).
    3. Forcing a new archiver just after the import (I do not know how to do that).
    Thanks in advance.

    540M is not that much.
    One would question why you need to import every day,
    there must be better ways to do this.
    The three steps you propose look like an awful
    scenario, as it would require the database to switch
    from archivelog to noarchivelog and vice versa.
    This would require the database to close twice a
    day.
    The scenario is also incomplete as one would need to
    take a backup after the import
    If you can convince your DBA to close the database
    twice a day, he should write the script, which he can
    easily derive from the docs.
    But likely he will visit Billy Verreynne to borrow
    his lead pipe, and rightly so ;)
    Sybrand Bakker
    Senior Oracle DBAThanks for the answer.
    A few things:
    - Sorry for my ignorance, I have no experience in database backups, I do not understand why I need to backup just after the import.
    - That database is not critical, it is just for a team who will test on that database several applications, so the database will only need to be open during the office schedule.
    - I have no dba. The client has a dba for several databases but I have no contact with him/her nor my boss has.

  • Archive log problem

    Hi:
    I've changed my database (small db... 4GB data) to go archivelog mode. The problem is that in 5 minutes it generated hundreds of files in the archivelog destionation...
    [root@server archivelog]# ls -lht
    total 2.2G
    -rw-r----- 1 oracle oinstall 9.1M Dez 14 17:20 arch_523640043_1_46517.arc
    -rw-r----- 1 oracle oinstall 9.1M Dez 14 17:20 arch_523640043_1_46516.arc
    -rw-r----- 1 oracle oinstall 9.1M Dez 14 17:20 arch_523640043_1_46514.arc
    and hundreds more...
    What's happening here?
    BR,
    Joao

    Hi Sape and Tekicora:
    No, I am not loading lots of data. And I can guaranteeed that there are no insert or updates on my application at the time I activated the archive log. My redologs are 100MB each... and I have 3 REDO LOGS.
    So, this is no surelly normal i guess... This is really strange!
    parameters:
    fast_start_io_target          integer     0
    fast_start_mttr_target          integer     0
    fast_start_parallel_rollback     string     LOW
    log_archive_format          string     %t_%s_%r.dbf
    log_archive_local_first      boolean     TRUE
    log_archive_max_processes     integer     2
    log_archive_min_succeed_dest     integer     1
    log_archive_start          boolean     FALSE
    log_archive_trace          integer     0
    log_buffer               integer     1048576
    log_checkpoint_interval      integer     0
    log_checkpoints_to_alert     boolean     FALSE
    log_checkpoint_timeout          integer     1800
    log_file_name_convert          string
    br,
    Joao

  • Archive log gap is created is standby when ever audit trail is set to DB

    Hi
    I am a new dba. I am facing a problem at production server that whenever audit_trail parameter is set to db , archive log gap is created at the standby site.
    My database version is 10.2.0.4
    Os is windows 2003 R2
    Audit_trail parameter is set to db only in primary site, after setting the parameter as db when I bounced the database and switched the logfile , archive log gap is created in the standby..I am using LGWR mode of log transport.
    Is there any relation beteen audit_trail and log transport ?
    Please note that my archive log location of both the sites has sufficient disk space and the drive is working fine.Also my primary and standby is in WAN.
    Please help me in this.Any help will be highly appreciated.
    Here a trace file which may be helpful to give any opinion.
    Dump file d:\oracle\admin\sbiofac\bdump\sbiofac_lns1_6480.trc
    Tue 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 the Partitioning, OLAP, Data Mining and Real Application Testing options
    Windows Server 2003 Version V5.2 Service Pack 2
    CPU : 2 - type 586, 1 Physical Cores
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:16504M/18420M, Ph+PgF:41103M/45775M, VA:311M/2047M
    Instance name: sbiofac
    Redo thread mounted by this instance: 1
    Oracle process number: 21
    Windows thread id: 6480, image: ORACLE.EXE (LNS1)
    *** SERVICE NAME:() 2012-06-05 13:46:02.703
    *** SESSION ID:(534.1) 2012-06-05 13:46:02.703
    *** 2012-06-05 13:46:02.703 58902 kcrr.c
    LNS1: initializing for LGWR communication
    LNS1: connecting to KSR channel
    Success
    LNS1: subscribing to KSR channel
    Success
    *** 2012-06-05 13:46:02.750 58955 kcrr.c
    LNS1: initialized successfully ASYNC=1
    Destination is specified with ASYNC=61440
    *** 2012-06-05 13:46:02.875 73045 kcrr.c
    Sending online log thread 1 seq 2217 [logfile 1] to standby
    Redo shipping client performing standby login
    *** 2012-06-05 13:46:03.656 66535 kcrr.c
    Logged on to standby successfully
    Client logon and security negotiation successful!
    Archiving to destination sbiofacdr ASYNC blocks=20480
    Allocate ASYNC blocks: Previous blocks=0 New blocks=20480
    Log file opened [logno 1]
    *** 2012-06-05 13:46:44.046
    Error 272 writing standby archive log file at host 'sbiofacdr'
    ORA-00272: error writing archive log
    *** 2012-06-05 13:46:44.078 62692 kcrr.c
    LGWR: I/O error 272 archiving log 1 to 'sbiofacdr'
    *** 2012-06-05 13:46:44.078 60970 kcrr.c
    kcrrfail: dest:2 err:272 force:0 blast:1
    *** 2012-06-05 13:47:37.031
    *** 2012-06-05 13:47:37.031 73045 kcrr.c
    Sending online log thread 1 seq 2218 [logfile 2] to standby
    *** 2012-06-05 13:47:37.046 73221 kcrr.c
    Shutting down [due to no more ASYNC destination]
    Redo Push Server: Freeing ASYNC PGA buffer
    LNS1: Doing a channel reset for next time around...

    OK
    Great details thanks!!
    Are The SDU/TDU settings are configured in the Oracle Net files on both primary and standby ? I will see if I have an example.
    The parameters appear fine.
    There was an Oracle document 386417.1 on this, I have not double checked if its still available. ( CHECK - Oracle 9 but worth a galance )
    Will Check and post here.
    I have these listed too. ( Will check all three and see if they still exist )
    When to modify, when not to modify the Session data unit (SDU) [ID 99715.1] ( CHECK - still there but very old )
    SQL*Net Packet Sizes (SDU & TDU Parameters) [ID 44694.1] ( CHECK - Best by far WOULD REVIEW FIRST )
    Any chance your firewall limit the Packet size?
    Best Regards
    mseberg
    Edited by: mseberg on Jun 6, 2012 12:36 PM
    Edited by: mseberg on Jun 6, 2012 12:43 PM
    Additional document
    The relation between MTU (Maximum Transmission Unit) and SDU (Session Data Unit) [ID 274483.1]
    Edited by: mseberg on Jun 6, 2012 12:50 PM
    Still later
    Not sure if this helps but I played around will this on Oracle 11 a little, here that example:
    # listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/network/admin/listener.ora
    # Generated by Oracle configuration tools.
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = yourdomain.com)(PORT = 1521))
    SID_LIST_LISTENER = (SID_LIST =(SID_DESC =(SID_NAME = STANDBY)
                          (ORACLE_HOME = /u01/app/oracle/product/11.2.0)
                          (SDU=32767)
                          (GLOBAL_DBNAME = STANDBY_DGMGRL.yourdomain.com)))   
    ADR_BASE_LISTENER = /u01/app/oracle
    INBOUND_CONNECT_TIMEOUT_LISTENER=120Edited by: mseberg on Jun 6, 2012 12:57 PM
    Also of interest
    Redo is transporting in 10gR2 versions.
    http://www.oracle.com/technetwork/database/features/availability/maa-wp-10gr2-dataguardnetworkbestpr-134557.pdf
    Edited by: mseberg on Jun 6, 2012 1:11 PM

  • Question about ALTER SYSTEM ARCHIVE LOG START

    Good morning,
    I'm trying (unsuccessfully) to get my database to be in archive log mode.
    These are the steps I followed:
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount;
    ORACLE instance started.
    Total System Global Area  535662592 bytes
    Fixed Size                  1375792 bytes
    Variable Size             377487824 bytes
    Database Buffers          150994944 bytes
    Redo Buffers                5804032 bytes
    Database mounted.
    SQL> select log_mode from v$database;
    LOG_MODE
    ARCHIVELOG
    SQL> show parameter log_archive_start;
    NAME                                 TYPE        VALUE
    log_archive_start                    boolean     FALSE
    SQL> alter system archive log start;
    System altered.
    SQL> show parameter log_archive_start;
    NAME                                 TYPE        VALUE
    log_archive_start                    boolean     FALSE
    SQL>I've gone thru that process twice but, I don't seem to be able to get the ARCH process to start. (newbie mistake I'm sure...)
    Thank you for your help (again!),
    John.

    The parameter log_archive_start is no more needed John (as suggested already) and the best way to check the archive options is through the archive log list command.
    [oracle@edhdr2p0-orcl oui]$ sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.1.0 Production on Tue Aug 10 10:51:57 2010
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
    With the Partitioning, Automatic Storage Management, OLAP, Data Mining
    and Real Application Testing options
    SQL> archive log list
    Database log mode              No Archive Mode
    Automatic archival             Disabled
    Archive destination            USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     11
    Current log sequence           13
    SQL> shut immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area  418484224 bytes
    Fixed Size                  1336932 bytes
    Variable Size             318769564 bytes
    Database Buffers           92274688 bytes
    Redo Buffers                6103040 bytes
    Database mounted.
    SQL> select process,status from V$archive_processes;
       PROCESS STATUS
             0 STOPPED
             1 STOPPED
             2 STOPPED
             3 STOPPED
             4 STOPPED
             5 STOPPED
             6 STOPPED
             7 STOPPED
             8 STOPPED
             9 STOPPED
            10 STOPPED
       PROCESS STATUS
            11 STOPPED
            12 STOPPED
            13 STOPPED
            14 STOPPED
            15 STOPPED
            16 STOPPED
            17 STOPPED
            18 STOPPED
            19 STOPPED
            20 STOPPED
            21 STOPPED
       PROCESS STATUS
            22 STOPPED
            23 STOPPED
            24 STOPPED
            25 STOPPED
            26 STOPPED
            27 STOPPED
            28 STOPPED
            29 STOPPED
    30 rows selected.
    SQL>
    SQL> alter database archivelog;
    Database altered.
    SQL> alter database open;
    archive log list;
    Database altered.
    SQL> Database log mode         Archive Mode
    Automatic archival             Enabled
    Archive destination            USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     11
    Next log sequence to archive   13
    Current log sequence           13
    SQL>
    SQL> select * from V$archive_processes where status <> 'STOPPED';
       PROCESS STATUS     LOG_SEQUENCE STAT
             0 ACTIVE                0 IDLE
             1 ACTIVE                0 IDLE
             2 ACTIVE                0 IDLE
             3 ACTIVE                0 IDLEHTH
    Aman....

  • "recover database until cancel" asks for archive log file that do not exist

    Hello,
    Oracle Release : Oracle 10.2.0.2.0
    Last week we performed, a restore and then an Oracle recovery using the recover database until cancel command. (we didn't use backup control files) .It worked fine and we able to restart the SAP instances. However, I still have questions about Oracle behaviour using this command.
    First we restored, an online backup.
    We tried to restart the database, but got ORA-01113,ORA-01110 errors :
    sr3usr.data1 needed media recovery.
    Then we performed the recovery :
    According Oracel documentation, "recover database until cancel recovery" proceeds by prompting you with the suggested filenames of archived redo log files.
    The probleme is it  prompts for archive log file that do not exist.
    As you can see below, it asked for SMAarch1_10420_610186861.dbf that has never been created. Therefore, I cancelled manually the recovery, and restarted the database. We never got the message "media recovery complete"
    ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10417_61018686
    Fri Sep  7 14:09:45 2007
    ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf'
    Fri Sep  7 14:09:45 2007
    Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf
    ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_61018686
    Fri Sep  7 14:10:03 2007
    ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf'
    Fri Sep  7 14:10:03 2007
    Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf
    ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_61018686
    Fri Sep  7 14:10:13 2007
    ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf'
    Fri Sep  7 14:10:13 2007
    Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
    Errors with log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
    ORA-308 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_61018686
    Fri Sep  7 14:15:19 2007
    ALTER DATABASE RECOVER CANCEL
    Fri Sep  7 14:15:20 2007
    ORA-1013 signalled during: ALTER DATABASE RECOVER CANCEL ...
    Fri Sep  7 14:15:40 2007
    Shutting down instance: further logons disabled
    When restaring the database we could see that, a recovery of online redo log has been performed automatically, is it the normal behaviour of a recovery using "recover database until cancel"  command ?
    Started redo application at
    Thread 1: logseq 10416, block 482
    Fri Sep  7 14:24:55 2007
    Recovery of Online Redo Log: Thread 1 Group 4 Seq 10416 Reading mem 0
      Mem# 0 errs 0: /oracle/SMA/origlogB/log_g14m1.dbf
      Mem# 1 errs 0: /oracle/SMA/mirrlogB/log_g14m2.dbf
    Fri Sep  7 14:24:55 2007
    Completed redo application
    Fri Sep  7 14:24:55 2007
    Completed crash recovery at
    Thread 1: logseq 10416, block 525, scn 105140074
    0 data blocks read, 0 data blocks written, 43 redo blocks read
    Thank you very much for your help.
    Frod.

    Hi,
    Let me answer your query.
    =======================
    Your question: While performing the recovery, is it possible to locate which online redolog is needed, and then to apply the changes in these logs
    1.   When you have current controlfile and need complete data (no data loss),
          then do not go for until cancel recovery.
    2.   Oracle will apply all the redologs (including current redolog) while recovery
         process is    on.
    3.  During the recovery you need to have all the redologs which are listed in the    view    V$RECOVERY_LOG and all the unarchived and current redolog. By querying  V$RECOVERY_LOG  you    can find out about the redologs required.
    4. If the required sequence is not there in the archive destination, and if recovery process    asks for that sequence you can query V$LOG to see whether requested sequence is part of the    online redologs. If yes you can mention the path of the online redolog to complete the recovery.
    Hope this information helps.
    Regards,
    Madhukar

  • Database refresh using dump and archive logs

    Hi all,
    I have a full datapump dump taken from oracle 11g R2 database (PROD) running in HP-UX server.The dump was taken on March,1,2012.
    Also i have all the archive logs till today (March 13,2012).
    I want to clone it to a new database (TEST) in windows machine with this dump, and i want to refresh(restore) the database (TEST) using this archive logs to make the database sync with the (PROD) till today.
    I need your suggestions.

    raoofdba wrote:
    Hi all,
    I have a full datapump dump taken from oracle 11g R2 database (PROD) running in HP-UX server.The dump was taken on March,1,2012.
    Also i have all the archive logs till today (March 13,2012).
    I want to clone it to a new database (TEST) in windows machine with this dump, and i want to refresh(restore) the database (TEST) using this archive logs to make the database sync with the (PROD) till today.
    I need your suggestions.I suggest you to perform transport tablespace method.below is the link: -
    http://neeraj-dba.blogspot.in/2012/01/cross-platform-transportable.html

  • DB backup and removal of archive log files?

    I have an application that uses Oracle 10gR2 on Linux RedHat EL 4.5. The DB is fairly simple, so backing up daily or weekly by using expdp (Datapump) is fine for our needs. We have an install that uses Data Guard, which in archivelog mode is filling up the disks fast.
    What is the best way to clean up archive log files in a Data Guard configuration? I have seen posts that indicate RMAN is tough to work with and has problems with recovery, so I would rather avoid it.
    I would like script something on a daily or weekly basis.
    Thanks,

    RMAN not easy? Lets see how hard it is:
    rman target /
    RMAN> backup database;Surely that isn't too challenging.
    Now if you want to do it properly you are talking about setting up a repository ... much more complex:
    -- on the repository database server
    CREATE USER repos
    IDENTIFIED BY oracl1
    DEFAULT TABLESPACE users
    TEMPORARY TABLESPACE temp
    QUOTA UNLIMITED on users;
    GRANT create session, recovery_catalog_owner TO repos;
    -- on the target server (your production db)
    rman target / catalog repos/oracle1@<tnsnames_entry_for_your repository>
    RMAN> create catalog;
    RMAN> register database;
    RMAN> backup database;If this is too much perhaps you should look into MS Access. <g>
    All of this is documented at the top of the RMAN page in Morgan's Library at www.psoug.org so you can cut-and-paste your way through it if you want.
    How is an export not a backup you ask?
    The Oracle docs can be found at http://tahiti.oracle.com. You should consider reading them some time.
    As I said before ... an export can NOT be used to recover ... ever. That says it all.
    Your resistance to change. Your resistance to doing things properly. Your resistance to reading the docs. You'd better watch out. There are people who would like to have your job ... a lot of them.

  • OVM 3.0 Database Creating Lots of Archive Logs

    Greetings - ever since we initially installed OVM 3.0 earlier this fall (~October), the OVM database has generated archive logs at a very rapid rate. It continually threatens to fill up our 16 GB filesystem dedicated to archive logs, even after daily backup and purging.
    Our OVM database itself is about 4-6 GB large, and we would need to increase the archive log filesystem to about 20-25 GB in size, which we see as unreasonable for such a small database.
    What is causing OVM to generate so many redo logs? Our best guess is that OVM is continuously gathering guest VM CPU usage on each physical server.
    Is there a way to configure the OVM application in order to reduce the amount of redo/archive logs being created?
    We are currently running 3.0.3, having upgraded each time a 3.0.* patch was released. OVMM running on OEL 6.1, database running on latest HP-UX.

    majedian21 wrote:
    Greetings - ever since we initially installed OVM 3.0 earlier this fall (~October), the OVM database has generated archive logs at a very rapid rate. It continually threatens to fill up our 16 GB filesystem dedicated to archive logs, even after daily backup and purging.I would log an SR with Oracle Support for this, so that Development can look at it. Sounds like your environment has lots of VMs running and yes, collecting usage stats for all of those environments. However, there may be some old data from the previous versions that's causing more stats to be collected than necessary.

  • How to removed the 300GB old archive logs???

    Dear Gurus
    Site-A
    Our Environment:
    Live Production 2-Node RAC Oracle10g r2 10.2.0.4
    Data and Archive is stored in Oracle ASM
    Operating System: Sun Solaris10 64bit
    We have two databases.
    ==>db-1(Site-A db-1 is Oracle streaming with Site-B db-1,so archive logs should not be deleted which is required for oracle streaming)
    ==>db-2
    Existing Backup and Recovery Strategy:
    Daily logical backup of application schema using DATA PUMP.
    We have not taken any RMAN Backup still.
    Please find the status of Shared Storage.
    -bash-3.00$ asmcmd
    ASMCMD> lsdg
    State Type Rebal Unbal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Name
    MOUNTED EXTERN N N 512 4096 1048576 614256 577801 0 577801 0 DATA/
    MOUNTED EXTERN N N 512 4096 1048576 298948 38635 0 38635 0 FLASH/
    We want to removed the old archive logs?
    Please suggest the best way of removed the old archive logs for db-2 and db-1?
    Can you Please suggest that how many time and how many space it's required for completed the backup?
    Regards
    Hitesh Gondalia
    Edited by: hitgon on Oct 1, 2011 9:50 PM
    Edited by: hitgon on Oct 1, 2011 10:09 PM
    Edited by: hitgon on Oct 1, 2011 10:13 PM

    You should consider using RMAN for backup/recovery. Logical exports (Data Pump) are useful for some purposes, but are not the preferred way to go for your backup and recovery needs. RMAN will give you better performance and so much more options.
    Long-term, a great way to delete archivelog backups is via RMAN “backup archivelog …. delete input” and/or “delete archivelog … “commands.
    Please delete archivelogs only after they are already backed up. RMAN will also take into consideration if the backups are needed for Streams and/or Standby.
    About the backup space – a full RMAN backup is typically smaller than the size of your DB. You need to run a test to see the exact size. The frequency and type of backup should be based on your SLE for this DB.
    Iordan Iotzov
    http://iiotzov.wordpress.com/

Maybe you are looking for

  • User Exit or BADI for Material,BOM,Customer,Vendor

    Dear All, I have requirement where if User A changes a Material X .It should go for approval by workflow. When the Material X is waiting for approval no other User should be able to change the material .It should give him a message and restrict him f

  • IPod touch with older Powermac G4

    I have a Powermac G4 with usb 1.1 and 733Mhz processor. Is it possible to use the iPod touch without upgrading to a new Mac with usb 2.0? I am ok with slow syncing if that is all I will have to deal with until I can afford a new Mac.

  • SQL*Loader halt loading large varray object

    I was using sql*loader of Oracle 8i NT, trying to load some records with varray (some records have lots of array elements, up to several thousands). however, after several hundreds records loaded, sql*loader became very slow, and virtually stopped at

  • Incorrect Trail Balance Generation

    Hello I am having problem in finalizing the trial balance. Problems are - Opening Stock Value of Raw Materials , Consumable Stores, Component and Finished Goods are not coming in Opening value of Trial Balance.    Due to this reason we are unable to

  • Bug report: import button shows incorrect state for Photo CDs

    When inserting a Kodak Photo CD, a graphic of a CD instead of the array of photos appears (that's fine). The button in the lower right portion of the window says "Stop Import". When pressed with the mouse, import begins. If pressed during the import,