Role SAP_JAVA_NWADMIN_LOCAL_READONLY - no archived logs, no performance

Hi everybody,
I have a user "read_only" with SAP_JAVA_NWADMIN_LOCAL_READONLY role in NWA.
When I try to see <i>Archives</i> in the <i>Predefined Views</i> under menu System Management >> Monioring >> Logs and Traces it says "No archives".
If I do the same with the standard "Administrator" there are Archives displayed...!?
Also with "read_only" user I don't see anything under Analysis >> Performance...
The role SAP_JAVA_NWADMIN_LOCAL_READONLY contains the actions "Performance_Display" and "Logs_Display" - so why is it not working??
Anyone experienced this behavior too and has a solution for me?
Thx,
Michael

Hi Michael,
                     This is only because of authorization problem, your administrator is having complete rights where as your SAP_JAVA_NWADMIN_LOCAL_READONLY
role is not having complete authorization.
For your solution try to login as administrator and increase the create /change/display rights to your SAP_JAVA_NWADMIN_LOCAL_READONLY  role.
Regards,
Hari.

Similar Messages

  • Can archive log backup influence database performance?

    Hi,
    can archive log backup generally influence the database performance? I mean: users can view their query to go slowly during backup of archived redolog?

    Are you asking about backing up the archived redo logs via rman or directly to tape or the actual archive process where Oracle backs the online redo to disk?
    -- comments on archive process
    Normally the redo log archiving process should have no noticable effect on database performance. About the only way for the process to have a noticable performance impact while it is running is if you store all your online redo logs on the same physical disk. You would also want the backup to be on a different physical disk.
    Check your alert log to make sure you do not have error messages related to being unable to switch redo logs and checkpoint incomplete messages. These would be an indication that your online redo logs are defined too small and you are trying to cycle around before Oracle has finished archiving the older logs.
    -- comments on archived redo log backup
    Archived reodo logs should not be on the same disk as the database so using rman or an OS task to back these files up should not impact Oracle unless you server is itself near capacity and any additional task effects the server.
    HTH -- Mark D Powell --

  • Duplexing the Archive Log - is there a potential performance hit

    Good Afternoon Oracle People -
    I apologize if this question is silly or out of place.
    Basically, we are looking at options for implementing a (cheap) DR solution for our Oracle Database.
    Bottom line objective is to have a second copy of our production system (not running, offline) with a usable archive log to recover from at a remote site with a similar set of disk technologies etc. 
    The sites are linked by 100MBPs link - so any access to secondary site is relatively fast.
    What I was thinking of doing is creating an iSCSI target on the destination SAN and adding this as a disk into the production database.  Then, I was going to go in and define a duplex archive log destination to this iSCSI target.
    My fear is that if the archiver waits for the write to the destination, I would imagine that this would slow down database access.  Is this a valid concern?  Or does Oracle treat the Duplex as a replicated (slower) copy?
    Again, sorry if this question is stupid - i have tried the google machine but couldn't find anything, and it isn't all that clear from the documentation. 
    Kind Regards,
    Aleksei

    Or does Oracle treat the Duplex as a replicated (slower) copy?
    Oracle treats it in a way you tell Oracle to treat it – please take a look at LOG_ARCHIVE_DEST_n parameters such as MANDATORY and OPTIONAL, MAX_FAILURE, etc
    There are two major things to consider:
    ->Is the throughput of the destination enough to handle max archive log generation?
    You need to take a look at the size of archive logs and how frequently they are
    generated during peak load.
    ->What happens when the destination is not available?
    HTH,
    Iordan Iotzov

  • Import performance and archive logs

    Well we are working on Oracle 10 R2 on Solaris.
    During import (impdp) its generating huge volume of archive logs.
    Our database size is in terabytes.
    How to stop the archive log generation during import or atleast minimize the generation ??

    Hello,
    If you can restart your database then you may set your database in NOARCHIVELOG mode.
    Then, after the import is finished, you'll have to set back your database in ARCHIVELOG mode (you'll need to restart again the database).
    Afterwards, you'll have to Backup your database.
    Else, without changing the Archive mode of the database, you can Backup and compress your archived "logs".
    For instance, with RMAN:
    connect target /
    backup
      as compressed backupset
      device type disk
      tag 'BKP_ARCHIVE'
      archivelog all not backed up
      delete all input;
    exit;By that way you'll save space on disk.
    Hope this help.
    Best regards,
    Jean-Valentin

  • Standby database archive log apply in production server.

    Dear All,
    How I apply standby database archive log apply in production server.
    Please help me.
    Thanks,
    Manas

    How can i use standby database as primary for that 48 hour ?Perform a switchover (role transitions).
    First check if the standby is in sync with the primary database.
    Primary database:
    sql>select max(sequence#) from v$archived_log; ---> Value AStandby database:
    sql>select max(sequence#) from v$archived_log where applied='YES'; -----> Value BCheck if Value B is same as Value A.
    If the standby is in sycn with the primary database, then perform the switchover operation (refer the below link)
    http://www.articles.freemegazone.com/oracle-switchover-physical-standby-database.php
    http://docs.oracle.com/cd/B19306_01/server.102/b14230/sofo.htm
    http://www.oracle-base.com/articles/9i/DataGuard.php#DatabaseSwitchover
    manas
    Handle: manas
    Email: [email protected]
    Status Level: Newbie
    Registered: Jan 24, 2012
    Total Posts: 10
    Total Questions: 3 (3 unresolved)
    Name Manas
    Location kolkata Mark your questions as answered if you feel that you have got better answers rather than building up a heap of unanswered questions.

  • Generating lots of archive logs

    Hi Friends,
    We have an EBS 11i on AIX 5L ...which has just been setup and ready for UAT...but the AppsDBA/Functional Consultant who didi it are not around anymore to ask for questiones. I just noticed the there are archive logs generated everyday...like 30 logs...when in fact the application is not being used. Is there concurrent programs
    that has been setup to update data on a background process, just like recursive updating which is not really necessary. How do I check if there are updates being done.
    Thanks a lot

    Do not stop this concurrent program as it is used to synchronize the Workflow local tables with the user and role information stored in the product application tables until each affected product performs the synchronization automatically.
    More details can be found in the following note:
    Note: 171703.1 - 11.5.x: Implementing Oracle Workflow Directory Service Synchronization
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=171703.1
    Did you check the total size of the log files? I believe you should not be worried now until the system is delivered to the users, you can monitor the number of log files generated daily then and based on that start your investigation.

  • Changing the location of archive log from flash recovery area PLZ HELP!!!

    Hi All,
    My archive log is being stored in flash memory area which got full and the production server went down.
    alert log file details.....
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 43432960 bytes disk space from 2147483648 limit
    *** 2010-04-25 14:22:49.777 62692 kcrr.c
    ARCH: Error 19809 Creating archive log file to
    '/oracle/product/10.2.0/flash_rec
    overy_area/EDWREP/archivelog/2010_04_25/o1_mf_1_232_%u_.arc'
    *** 2010-04-25 14:22:49.777 60970 kcrr.c
    kcrrfail: dest:10 err:19809 force:0 blast:1I removed the files and started the database,
    Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
    I want to change the location of archive log files, can someone please guide me as to hiow to do that
    I changed the size of flash recovery area for the time being, but i am afraid it will be full again!!
    SQL> select * from v$flash_recovery_area_usage;
    FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
    CONTROLFILE                   0                         0               0
    ONLINELOG                     0                         0               0
    ARCHIVELOG                99.44                         0              57
    BACKUPPIECE                   0                         0               0
    IMAGECOPY                     0                         0               0
    FLASHBACKLOG                  0                         0               0
    6 rows selected.
    SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = 4G ;
    System altered.
    SQL> select * from v$flash_recovery_area_usage;
    FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
    CONTROLFILE                   0                         0               0
    ONLINELOG                     0                         0               0
    ARCHIVELOG                49.72                         0              57
    BACKUPPIECE                   0                         0               0
    IMAGECOPY                     0                         0               0
    FLASHBACKLOG                  0                         0               0
    6 rows selected.regards,
    Edited by: user10243788 on Apr 25, 2010 6:12 AM

    user10243788 wrote:
    Hi All,
    My archive log is being stored in flash memory area which got full and the production server went down.
    alert log file details.....
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 43432960 bytes disk space from 2147483648 limit
    *** 2010-04-25 14:22:49.777 62692 kcrr.c
    ARCH: Error 19809 Creating archive log file to
    '/oracle/product/10.2.0/flash_rec
    overy_area/EDWREP/archivelog/2010_04_25/o1_mf_1_232_%u_.arc'
    *** 2010-04-25 14:22:49.777 60970 kcrr.c
    kcrrfail: dest:10 err:19809 force:0 blast:1I removed the files and started the database,
    Can someone kindly tell me as to how to avoid this problem in future by keeping archive log destination in flash recovery area.
    I want to change the location of archive log files, can someone please guide me as to hiow to do that
    I changed the size of flash recovery area for the time being, but i am afraid it will be full again!!
    SQL> select * from v$flash_recovery_area_usage;
    FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
    CONTROLFILE                   0                         0               0
    ONLINELOG                     0                         0               0
    ARCHIVELOG                99.44                         0              57
    BACKUPPIECE                   0                         0               0
    IMAGECOPY                     0                         0               0
    FLASHBACKLOG                  0                         0               0
    6 rows selected.
    SQL> alter system set DB_RECOVERY_FILE_DEST_SIZE = 4G ;
    System altered.
    SQL> select * from v$flash_recovery_area_usage;
    FILE_TYPE    PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
    CONTROLFILE                   0                         0               0
    ONLINELOG                     0                         0               0
    ARCHIVELOG                49.72                         0              57
    BACKUPPIECE                   0                         0               0
    IMAGECOPY                     0                         0               0
    FLASHBACKLOG                  0                         0               0
    6 rows selected.regards,
    Edited by: user10243788 on Apr 25, 2010 6:12 AMPointing the archive log dest (and/or the FRA) to a new location, or enlarging them, will do no good if you are not performing regular housekeeping on the archivelogs. You will just keep knocking down the same problem over and over.
    If you simply delete the archivelogs at the OS level, the database will never know about it and it will continue to think the destination is full, based on records kept in the control file.
    For regular housekeeping, you need to be doing something similar to this in rman:
    run {
      backup archivelog all not backed up 1 times tag='bkup_vlnxora1_arch';
      delete noprompt archivelog all backed up 1 times to device type disk;
    run {
    delete noprompt obsolete;
    crosscheck archivelog all;
    delete noprompt expired archivelog all;

  • Archive Logs NOT APPLIED but transferred

    Hi Gurus,
    I have configured Primary & Standby databases in same Oracle Home. OS version is OEL 5. Database version is 10.2.0.1. I could get the archive logs in the standby site but they are not getting applied in the standby database. I don't have OLAP installed in my database version. Would this create this issue? However I attached my primary alert log details below for your reference:
    Thu Aug 30 23:55:37 2012
    Starting ORACLE instance (normal)
    Cannot determine all dependent dynamic libraries for /proc/self/exe
    Unable to find dynamic library libocr10.so in search paths
    RPATH = /ade/aime1_build2101/oracle/has/lib/:/ade/aime1_build2101/oracle/lib/:/ade/aime1_build2101/oracle/has/lib/:
    LD_LIBRARY_PATH is not set!
    The default library directories are /lib and /usr/lib
    Unable to find dynamic library libocrb10.so in search paths
    Unable to find dynamic library libocrutl10.so in search paths
    Unable to find dynamic library libocrutl10.so in search paths
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =18
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
    processes = 150
    sga_target = 289406976
    control_files = /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control01.ctl, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control02.ctl, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control03.ctl
    db_file_name_convert = /home/oracle/oracle/product/10.2.0/db_1/oradata/newstand, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim
    log_file_name_convert = /home/oracle/oracle/product/10.2.0/db_1/oradata/newstand, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim, /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/NEWSTAND/onlinelog, /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/NEWPRIM/onlinelog
    db_block_size = 8192
    compatible = 10.2.0.1.0
    log_archive_config = DG_CONFIG=(newprim,newstand)
    log_archive_dest_1 = LOCATION=/home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/arch/
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
    DB_UNIQUE_NAME=newprim
    log_archive_dest_2 = SERVICE=newstand LGWR ASYNC VALID_FOR=(online_logfiles,primary_role) DB_UNIQUE_NAME=newstand
    log_archive_dest_state_1 = enable
    log_archive_dest_state_2 = enable
    log_archive_max_processes= 30
    log_archive_format = %t_%s_%r.dbf
    fal_client = newprim
    fal_server = newstand
    db_file_multiblock_read_count= 16
    db_recovery_file_dest = /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area
    db_recovery_file_dest_size= 2147483648
    standby_file_management = AUTO
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    dispatchers = (PROTOCOL=TCP) (SERVICE=newprimXDB)
    job_queue_processes = 10
    background_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump
    user_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/udump
    core_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/cdump
    audit_file_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/adump
    db_name = newprim
    db_unique_name = newprim
    open_cursors = 300
    pga_aggregate_target = 95420416
    PMON started with pid=2, OS id=28091
    PSP0 started with pid=3, OS id=28093
    MMAN started with pid=4, OS id=28095
    DBW0 started with pid=5, OS id=28097
    LGWR started with pid=6, OS id=28100
    CKPT started with pid=7, OS id=28102
    SMON started with pid=8, OS id=28104
    RECO started with pid=9, OS id=28106
    CJQ0 started with pid=10, OS id=28108
    MMON started with pid=11, OS id=28110
    MMNL started with pid=12, OS id=28112
    Thu Aug 30 23:55:38 2012
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    starting up 1 shared server(s) ...
    Thu Aug 30 23:55:38 2012
    ALTER DATABASE MOUNT
    Thu Aug 30 23:55:42 2012
    Setting recovery target incarnation to 2
    Thu Aug 30 23:55:43 2012
    Successful mount of redo thread 1, with mount id 1090395834
    Thu Aug 30 23:55:43 2012
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE MOUNT
    Thu Aug 30 23:55:43 2012
    ALTER DATABASE OPEN
    Thu Aug 30 23:55:43 2012
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=16, OS id=28122
    ARC1 started with pid=17, OS id=28124
    ARC2 started with pid=18, OS id=28126
    ARC3 started with pid=19, OS id=28128
    ARC4 started with pid=20, OS id=28133
    ARC5 started with pid=21, OS id=28135
    ARC6 started with pid=22, OS id=28137
    ARC7 started with pid=23, OS id=28139
    ARC8 started with pid=24, OS id=28141
    ARC9 started with pid=25, OS id=28143
    ARCa started with pid=26, OS id=28145
    ARCb started with pid=27, OS id=28147
    ARCc started with pid=28, OS id=28149
    ARCd started with pid=29, OS id=28151
    ARCe started with pid=30, OS id=28153
    ARCf started with pid=31, OS id=28155
    ARCg started with pid=32, OS id=28157
    ARCh started with pid=33, OS id=28159
    ARCi started with pid=34, OS id=28161
    ARCj started with pid=35, OS id=28163
    ARCk started with pid=36, OS id=28165
    ARCl started with pid=37, OS id=28167
    ARCm started with pid=38, OS id=28169
    ARCn started with pid=39, OS id=28171
    ARCo started with pid=40, OS id=28173
    ARCp started with pid=41, OS id=28175
    ARCq started with pid=42, OS id=28177
    ARCr started with pid=43, OS id=28179
    ARCs started with pid=44, OS id=28181
    Thu Aug 30 23:55:44 2012
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    ARCt started with pid=45, OS id=28183
    LNS1 started with pid=46, OS id=28185
    Thu Aug 30 23:55:48 2012
    Thread 1 advanced to log sequence 68
    Thu Aug 30 23:55:48 2012
    ARCo: Becoming the 'no FAL' ARCH
    ARCo: Becoming the 'no SRL' ARCH
    Thu Aug 30 23:55:48 2012
    ARCp: Becoming the heartbeat ARCH
    Thu Aug 30 23:55:48 2012
    Thread 1 opened at log sequence 68
    Current log# 1 seq# 68 mem# 0: /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/redo01.log
    Successful open of redo thread 1
    Thu Aug 30 23:55:48 2012
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Thu Aug 30 23:55:48 2012
    SMON: enabling cache recovery
    Thu Aug 30 23:55:48 2012
    Successfully onlined Undo Tablespace 1.
    Thu Aug 30 23:55:48 2012
    SMON: enabling tx recovery
    Thu Aug 30 23:55:49 2012
    Database Characterset is WE8ISO8859P1
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=47, OS id=28205
    Thu Aug 30 23:55:49 2012
    Error 1034 received logging on to the standby
    Thu Aug 30 23:55:49 2012
    Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc:
    ORA-01034: ORACLE not available
    FAL[server, ARC1]: Error 1034 creating remote archivelog file 'newstand'
    FAL[server, ARC1]: FAL archive failed, see trace file.
    Thu Aug 30 23:55:49 2012
    Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing
    Thu Aug 30 23:55:49 2012
    ORACLE Instance newprim - Archival Error. Archiver continuing.
    Thu Aug 30 23:55:49 2012
    db_recovery_file_dest_size of 2048 MB is 9.77% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Thu Aug 30 23:55:50 2012
    Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/udump/newprim_ora_28120.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-12663: Services required by client not available on the server
    ORA-36961: Oracle OLAP is not available.
    ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
    ORA-06512: at line 15
    Thu Aug 30 23:55:50 2012
    Completed: ALTER DATABASE OPEN
    Thu Aug 30 23:56:33 2012
    FAL[server]: Fail to queue the whole FAL gap
    GAP - thread 1 sequence 1-33
    DBID 1090398314 branch 792689455
    Kindly, guide me please..
    -Vimal.

    CKPT: The trace file details are added below for your reference;
    /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning and Data Mining options
    ORACLE_HOME = /home/oracle/oracle/product/10.2.0/db_1
    System name:     Linux
    Node name:     localhost.localdomain
    Release:     2.6.18-8.el5PAE
    Version:     #1 SMP Tue Jun 5 23:39:57 EDT 2007
    Machine:     i686
    Instance name: newprim
    Redo thread mounted by this instance: 1
    Oracle process number: 17
    Unix process pid: 28124, image: [email protected] (ARC1)
    *** SERVICE NAME:() 2012-08-30 23:55:48.314
    *** SESSION ID:(155.1) 2012-08-30 23:55:48.314
    kcrrwkx: nothing to do (start)
    Redo shipping client performing standby login
    OCISessionBegin failed -1
    .. Detailed OCI error val is 1034 and errmsg is 'ORA-01034: ORACLE not available
    *** 2012-08-30 23:55:49.723 60679 kcrr.c
    Error 1034 received logging on to the standby
    Error 1034 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'newstand'
    Error 1034 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'newstand'
    ORA-01034: ORACLE not available
    *** 2012-08-30 23:55:49.723 58941 kcrr.c
    kcrrfail: dest:2 err:1034 force:0 blast:1
    kcrrwkx: unknown error:1034
    ORA-16055: FAL request rejected
    ARCH: Connecting to console port...
    ARCH: Connecting to console port...
    kcrrwkx: nothing to do (end)
    *** 2012-08-31 00:00:43.417
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:05:43.348
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:10:43.280
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:15:43.217
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:20:43.160
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:25:43.092
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:30:43.031
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:35:42.961
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:40:42.890
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:45:42.820
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:50:42.755
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 00:55:42.686
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 01:00:42.631
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 01:05:42.565
    kcrrwkx: nothing to do (start)
    *** 2012-08-31 01:10:42.496
    kcrrwkx: nothing to do (start)
    Mahir: Yes I have my 4 standby redo logs!
    I created the standby manually without using RMAN.
    Hemant: if it asks for even first thread, then obviously it shows nothing is applied on Standby. By the way so it is not called a 'GAP', I think..!
    Thanks.

  • Create procedure is generating too many archive logs

    Hi
    The following procedure was run on one of our databases and it hung since there were too many archive logs being generated.
    What would be the answer? The db must remain in archivelog mode.
    I understand the nologging concept, but as I know this applies to creating tables, views, indexes and tablespaces. This script is creating procedure.
    CREATE OR REPLACE PROCEDURE APPS.Dfc_Payroll_Dw_Prc(Errbuf OUT VARCHAR2, Retcode OUT NUMBER
    ,P_GRE NUMBER
    ,P_SDATE VARCHAR2
    ,P_EDATE VARCHAR2
    ,P_ssn VARCHAR2
    ) IS
    CURSOR MainCsr IS
    SELECT DISTINCT
    PPF.NATIONAL_IDENTIFIER SSN
    ,ppf.full_name FULL_NAME
    ,ppa.effective_date Pay_date
    ,ppa.DATE_EARNED period_end
    ,pet.ELEMENT_NAME
    ,SUM(TO_NUMBER(prv.result_value)) VALOR
    ,PET.ELEMENT_INFORMATION_CATEGORY
    ,PET.CLASSIFICATION_ID
    ,PET.ELEMENT_INFORMATION1
    ,pet.ELEMENT_TYPE_ID
    ,paa.tax_unit_id
    ,PAf.ASSIGNMENT_ID ASSG_ID
    ,paf.ORGANIZATION_ID
    FROM
    pay_element_classifications pec
    , pay_element_types_f pet
    , pay_input_values_f piv
    , pay_run_result_values prv
    , pay_run_results prr
    , pay_assignment_actions paa
    , pay_payroll_actions ppa
    , APPS.pay_all_payrolls_f pap
    ,Per_Assignments_f paf
    ,per_people_f ppf
    WHERE
    ppa.effective_date BETWEEN TO_DATE(p_sdate) AND TO_DATE(p_edate)
    AND ppa.payroll_id = pap.payroll_id
    AND paa.tax_unit_id = NVL(p_GRE, paa.tax_unit_id)
    AND ppa.payroll_action_id = paa.payroll_action_id
    AND paa.action_status = 'C'
    AND ppa.action_type IN ('Q', 'R', 'V', 'B', 'I')
    AND ppa.action_status = 'C'
    --AND PEC.CLASSIFICATION_NAME IN ('Earnings','Alien/Expat Earnings','Supplemental Earnings','Imputed Earnings','Non-payroll Payments')
    AND paa.assignment_action_id = prr.assignment_action_id
    AND prr.run_result_id = prv.run_result_id
    AND prv.input_value_id = piv.input_value_id
    AND piv.name = 'Pay Value'
    AND piv.element_type_id = pet.element_type_id
    AND pet.element_type_id = prr.element_type_id
    AND pet.classification_id = pec.classification_id
    AND pec.non_payments_flag = 'N'
    AND prv.result_value &lt;&gt; '0'
    --AND( PET.ELEMENT_INFORMATION_CATEGORY LIKE '%EARNINGS'
    -- OR PET.element_type_id IN (1425, 1428, 1438, 1441, 1444, 1443) )
    AND NVL(PPA.DATE_EARNED, PPA.EFFECTIVE_DATE) BETWEEN PET.EFFECTIVE_START_DATE AND PET.EFFECTIVE_END_DATE
    AND NVL(PPA.DATE_EARNED, PPA.EFFECTIVE_DATE) BETWEEN PIV.EFFECTIVE_START_DATE AND PIV.EFFECTIVE_END_DATE --dcc
    AND NVL(PPA.DATE_EARNED, PPA.EFFECTIVE_DATE) BETWEEN Pap.EFFECTIVE_START_DATE AND Pap.EFFECTIVE_END_DATE --dcc
    AND paf.ASSIGNMENT_ID = paa.ASSIGNMENT_ID
    AND ppf.NATIONAL_IDENTIFIER = NVL(p_ssn, ppf.NATIONAL_IDENTIFIER)
    ------------------------------------------------------------------TO get emp.
    AND ppf.person_id = paf.person_id
    AND NVL(PPA.DATE_EARNED, PPA.EFFECTIVE_DATE) BETWEEN ppf.EFFECTIVE_START_DATE AND ppf.EFFECTIVE_END_DATE
    ------------------------------------------------------------------TO get emp. ASSIGNMENT
    --AND paf.assignment_status_type_id NOT IN (7,3)
    AND NVL(PPA.DATE_EARNED, PPA.EFFECTIVE_DATE) BETWEEN paf.effective_start_date AND paf.effective_end_date
    GROUP BY PPF.NATIONAL_IDENTIFIER
    ,ppf.full_name
    ,ppa.effective_date
    ,ppa.DATE_EARNED
    ,pet.ELEMENT_NAME
    ,PET.ELEMENT_INFORMATION_CATEGORY
    ,PET.CLASSIFICATION_ID
    ,PET.ELEMENT_INFORMATION1
    ,pet.ELEMENT_TYPE_ID
    ,paa.tax_unit_id
    ,PAF.ASSIGNMENT_ID
    ,paf.ORGANIZATION_ID
    BEGIN
    DELETE cust.DFC_PAYROLL_DW
    WHERE PAY_DATE BETWEEN TO_DATE(p_sdate) AND TO_DATE(p_edate)
    AND tax_unit_id = NVL(p_GRE, tax_unit_id)
    AND ssn = NVL(p_ssn, ssn)
    COMMIT;
    FOR V_REC IN MainCsr LOOP
    INSERT INTO cust.DFC_PAYROLL_DW(SSN, FULL_NAME, PAY_DATE, PERIOD_END, ELEMENT_NAME, ELEMENT_INFORMATION_CATEGORY, CLASSIFICATION_ID, ELEMENT_INFORMATION1, VALOR, TAX_UNIT_ID, ASSG_ID,ELEMENT_TYPE_ID,ORGANIZATION_ID)
    VALUES(V_REC.SSN,V_REC.FULL_NAME,v_rec.PAY_DATE,V_REC.PERIOD_END,V_REC.ELEMENT_NAME,V_REC.ELEMENT_INFORMATION_CATEGORY, V_REC.CLASSIFICATION_ID, V_REC.ELEMENT_INFORMATION1, V_REC.VALOR,V_REC.TAX_UNIT_ID,V_REC.ASSG_ID, v_rec.ELEMENT_TYPE_ID, v_rec.ORGANIZATION_ID);
    COMMIT;
    END LOOP;
    END ;
    So, how could I assist our developer with this, so that she can run it again without it generating a ton of logs ? ?
    Thanks
    Oracle 9.2.0.5
    AIX 5.2

    The amount of redo generated is a direct function of how much data is changing. If you insert 'x' number of rows, you are going to generate 'y' mbytes of redo. If your procedure is destined to insert 1000 rows, then it is destined to create a certain amount of redo. Period.
    I would question the <i>performance</i> of the procedure shown ... using a cursor loop with a commit after every row is going to be a slug on performance but that doesn't change the fact 'x' inserts will always generate 'y' redo.

  • Error when I backup with rman plus archive log

    Hi All,
    I tried below command
    run {
    SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
    BACKUP DATABASE INCLUDE CURRENT CONTROLFILE PLUS ARCHIVELOG DELETE ALL INPUT;
    and that show below error
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_95_698703544.arc RECID=128 STAMP=706186164
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_96_698703544.arc RECID=130 STAMP=706186173
    Finished backup at 21-DEC-09
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    Starting backup at 21-DEC-09
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=259 instance=pimdb1 device type=DISK
    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=153 RECID=113 STAMP=705896703
    input archived log thread=1 sequence=154 RECID=116 STAMP=705983105
    input archived log thread=1 sequence=155 RECID=119 STAMP=706069504
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_95_698703544.arc RECID=128 STAMP=706186164
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_96_698703544.arc RECID=130 STAMP=706186173
    Finished backup at 21-DEC-09
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    Starting backup at 21-DEC-09
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    ORA-03114: not connected to ORACLE
    RMAN-03002: failure of backup plus archivelog command at 12/21/2009 11:00:18
    ORA-03114: not connected to ORACLE
    There are RAC 11.1.0.6.0 on AIX 5.3 with ASM.
    Please advise,
    Thank you,
    Hiko

    ็Hi All,
    I tried backup archivelog again and show same error,
    Line: -----
    rman target /
    Recovery Manager: Release 11.1.0.6.0 - Production on Mon Dec 21 14:48:29 2009
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: PIMDB (DBID=3834713912)
    RMAN> run
    2> {
    3> backup archivelog all;
    4> }
    Starting backup at 21-DEC-09
    current log archived
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=275 instance=pimdb1 device type=DISK
    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=161 RECID=131 STAMP=706190624
    input archived log thread=1 sequence=162 RECID=133 STAMP=706200525
    input archived log thread=2 sequence=97 RECID=132 STAMP=706190625
    input archived log thread=2 sequence=98 RECID=134 STAMP=706200526
    channel ORA_DISK_1: starting piece 1 at 21-DEC-09
    channel ORA_DISK_1: finished piece 1 at 21-DEC-09
    piece handle=/oradata/backup/pimdb/rman/pimdb_Fulldata_20091221_97_1.bck tag=TAG20091221T144854 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 21-DEC-09
    Starting Control File and SPFILE Autobackup at 21-DEC-09
    piece handle=/oradata/backup/pimdb/rman/pimdb_Controlfile_c-3834713912-20091221-02 comment=NONE
    Finished Control File and SPFILE Autobackup at 21-DEC-09
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    ORA-03114: not connected to ORACLE
    RMAN-03009: failure of REFAF command on default channel at 12/21/2009 14:59:33
    ORA-03114: not connected to ORACLE
    RMAN> exit
    Recovery Manager complete.
    Line: -----
    And I check in alert log file that show below error
    Line: -----
    Mon Dec 21 14:48:44 2009
    Thread 1 advanced to log sequence 163
    Current log# 1 seq# 163 mem# 0: +DATA/pimdb/onlinelog/group_1.282.698703549
    Mon Dec 21 14:49:17 2009
    Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3E00000000] [PC:0x10180AA48, kxfpg1srv()+04e8]
    Errors in file /oracle/diag/rdbms/pimdb/pimdb1/trace/pimdb1_ora_5095646.trc (incident=64044):
    ORA-07445: exception encountered: core dump [kxfpg1srv()+04e8] [SIGSEGV] [ADDR:0x3E00000000] [PC:0x10180AA48] [Address not mapped to object] []
    Incident details in: /oracle/diag/rdbms/pimdb/pimdb1/incident/incdir_64044/pimdb1_ora_5095646_i64044.trc
    Mon Dec 21 14:49:31 2009
    Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3E00000000] [PC:0x10180AA48, kxfpg1srv()+04e8]
    Errors in file /oracle/diag/rdbms/pimdb/pimdb1/trace/pimdb1_m000_1831050.trc (incident=64163):
    ORA-07445: exception encountered: core dump [kxfpg1srv()+04e8] [SIGSEGV] [ADDR:0x3E00000000] [PC:0x10180AA48] [Address not mapped to object] []
    Incident details in: /oracle/diag/rdbms/pimdb/pimdb1/incident/incdir_64163/pimdb1_m000_1831050_i64163.trc
    Mon Dec 21 14:49:33 2009
    Trace dumping is performing id=[cdmp_20091221144933]
    Mon Dec 21 14:49:34 2009
    Sweep Incident[64163]: completed
    Mon Dec 21 14:59:33 2009
    Process 0x70000020477df88 appears to be hung while dumping
    Current time = 1584185732, process death time = 1584124482 interval = 60000
    Attempting to kill process 0x70000020477df88 with OS pid = 5095646
    OSD kill succeeded for process 70000020477df88
    Line: -----
    Please advice,
    Thank you
    Hiko

  • I have one problem with Data Guard. My archive log files are not applied.

    I have one problem with Data Guard. My archive log files are not applied. However I have received all archive log files to my physical Standby db
    I have created a Physical Standby database on Oracle 10gR2 (Windows XP professional). Primary database is on another computer.
    In Enterprise Manager on Primary database it looks ok. I get the following message “Data Guard status Normal”
    But as I wrote above ”the archive log files are not applied”
    After I created the Physical Standby database, I have also done:
    1. I connected to the Physical Standby database instance.
    CONNECT SYS/SYS@luda AS SYSDBA
    2. I started the Oracle instance at the Physical Standby database without mounting the database.
    STARTUP NOMOUNT PFILE=C:\oracle\product\10.2.0\db_1\database\initluda.ora
    3. I mounted the Physical Standby database:
    ALTER DATABASE MOUNT STANDBY DATABASE
    4. I started redo apply on Physical Standby database
    alter database recover managed standby database disconnect from session
    5. I switched the log files on Physical Standby database
    alter system switch logfile
    6. I verified the redo data was received and archived on Physical Standby database
    select sequence#, first_time, next_time from v$archived_log order by sequence#
    SEQUENCE# FIRST_TIME NEXT_TIME
    3 2006-06-27 2006-06-27
    4 2006-06-27 2006-06-27
    5 2006-06-27 2006-06-27
    6 2006-06-27 2006-06-27
    7 2006-06-27 2006-06-27
    8 2006-06-27 2006-06-27
    7. I verified the archived redo log files were applied on Physical Standby database
    select sequence#,applied from v$archived_log;
    SEQUENCE# APP
    4 NO
    3 NO
    5 NO
    6 NO
    7 NO
    8 NO
    8. on Physical Standby database
    select * from v$archive_gap;
    No rows
    9. on Physical Standby database
    SELECT MESSAGE FROM V$DATAGUARD_STATUS;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    ARC1: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery not using Real Time Apply
    MRP0: Background Media Recovery terminated with error 1110
    MRP0: Background Media Recovery process shutdown
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 2148
    RFS[1]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[2]: Assigned to RFS process 2384
    RFS[2]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[3]: Assigned to RFS process 3188
    RFS[3]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM PERFORMANCE mode
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[4]: Assigned to RFS process 3168
    RFS[4]: Identified database type as 'physical standby'
    RFS[4]: No standby redo logfiles created
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    10. on Physical Standby database
    SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 1 9 13664 2
    RFS IDLE 0 0 0 0
    10) on Primary database:
    select message from v$dataguard_status;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARCm: Becoming the 'no FAL' ARCH
    ARCm: Becoming the 'no SRL' ARCH
    ARCd: Becoming the heartbeat ARCH
    Error 1034 received logging on to the standby
    Error 1034 received logging on to the standby
    LGWR: Error 1034 creating archivelog file 'luda'
    LNS: Failed to archive log 3 thread 1 sequence 7 (1034)
    FAL[server, ARCh]: Error 1034 creating remote archivelog file 'luda'
    11)on primary db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00004_0594204176.001 4 NO
    Luda 4 NO
    Luda 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00005_0594204176.001 5 NO
    Luda 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00006_0594204176.001 6 NO
    Luda 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00007_0594204176.001 7 NO
    Luda 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00008_0594204176.001 8 NO
    Luda 8 NO
    12) on standby db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00004_0594204176.001 4 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00005_0594204176.001 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00006_0594204176.001 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00007_0594204176.001 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00008_0594204176.001 8 NO
    13) my init.ora files
    On standby db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0\admin\luda\adump'
    *.background_dump_dest='C:\oracle\product\10.2.0\admin\luda\bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\luda\luda.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0\admin\luda\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_unique_name='luda'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='luda'
    *.fal_server='irina'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/luda/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_2='SERVICE=irina LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/irina/','C:/oracle/product/10.2.0/oradata/luda/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0\admin\luda\udump'
    On primary db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/irina/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/irina/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\irina\control01.ctl','C:\oracle\product\10.2.0\oradata\irina\control02.ctl','C:\oracle\product\10.2.0\oradata\irina\control03.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/irina/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='irina'
    *.fal_server='luda'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/irina/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_2='SERVICE=luda LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/luda/','C:/oracle/product/10.2.0/oradata/irina/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/irina/udump'
    Please help me!!!!

    Hi,
    After several tries my redo logs are applied now. I think in my case it had to do with the tnsnames.ora. At this moment I have both database in both tnsnames.ora files using the SID and not the SERVICE_NAME.
    Now I want to use DGMGRL. Adding a configuration and a stand-by database is working fine, but when I try to enable the configuration DGMGRL gives no feedback and it looks like it is hanging. The log, although says that it succeeded.
    In another session 'show configuration' results in the following, confirming that the enable succeeded.
    DGMGRL> show configuration
    Configuration
    Name: avhtest
    Enabled: YES
    Protection Mode: MaxPerformance
    Fast-Start Failover: DISABLED
    Databases:
    avhtest - Primary database
    avhtestls53 - Physical standby database
    Current status for "avhtest":
    Warning: ORA-16610: command 'ENABLE CONFIGURATION' in progress
    It there anybody that experienced the same problem and/or knows the solution to this?
    With kind regards,
    Martin Schaap

  • RMAN never deletes archive log backups

    Hi all,
    I have same problem as some of you have already faced.
    I have some instances 10.2.0.4 running un archive log mode.
    I take full hot backup daily.
    I setup a rman script to backup and delete obsolete backups according to the following policy:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    and then:
    run {
    ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
    BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/mnt/rman_202/pnetpres/db_pres_%U';
    CROSSCHECK ARCHIVELOG ALL;
    BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/mnt/rman_202/pnetpres/al_pres_%U';
    CROSSCHECK BACKUP;
    DELETE NOPROMPT OBSOLETE;
    DELETE NOPROMPT EXPIRED BACKUP;
    RELEASE CHANNEL RMAN_BACK_CH01;
    crosscheck archivelog all;
    delete noprompt archivelog all completed before 'sysdate -2';
    DB full backups are being deleted, however archive logs backups are not deleted.
    There are no tablespaces in backup or offline mode.
    How can I know the reason why some archive log backups are kept ?
    Even I clear the policy and perform a crosscheck and delete, those are not marked as obsolete neither deleted from disk.
    Thanks in advance.

    Hi Fernando,
    This are the ouputpus of the commands:
    RMAN> REPORT OBSOLETE;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    no obsolete backups found
    RMAN> LIST BACKUP OF ARCHIVELOG ALL;
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    1090 69.65M DISK 00:00:16 23-FEB-11
    BP Key: 1093 Status: AVAILABLE Compressed: YES Tag: TAG20110223T061511
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0jm5c6bf_1_1
    List of Archived Logs in backup set 1090
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 13 2173025156 21-FEB-11 2173028010 21-FEB-11
    1 14 2173028010 21-FEB-11 2173041730 21-FEB-11
    1 15 2173041730 21-FEB-11 2173041813 21-FEB-11
    1 16 2173041813 21-FEB-11 2173106066 22-FEB-11
    1 17 2173106066 22-FEB-11 2173108831 22-FEB-11
    1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
    1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
    1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
    1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1411 125.43M DISK 00:00:28 24-FEB-11
    BP Key: 1414 Status: AVAILABLE Compressed: YES Tag: TAG20110224T061643
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0mm5eqqb_1_1
    List of Archived Logs in backup set 1411
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
    1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
    1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
    1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1600 164.40M DISK 00:00:37 25-FEB-11
    BP Key: 1603 Status: AVAILABLE Compressed: YES Tag: TAG20110225T061643
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0pm5hf6b_1_1
    List of Archived Logs in backup set 1600
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1829 132.24M DISK 00:00:30 26-FEB-11
    BP Key: 1832 Status: AVAILABLE Compressed: YES Tag: TAG20110226T061627
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0sm5k3hr_1_1
    List of Archived Logs in backup set 1829
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2058 218.03M DISK 00:00:48 27-FEB-11
    BP Key: 2061 Status: AVAILABLE Compressed: YES Tag: TAG20110227T061628
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0vm5mnts_1_1
    List of Archived Logs in backup set 2058
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2298 205.39M DISK 00:00:45 28-FEB-11
    BP Key: 2301 Status: AVAILABLE Compressed: YES Tag: TAG20110228T061620
    Piece Name: /mnt/rman_202/pnetproy/al_pres_12m5pc9l_1_1
    List of Archived Logs in backup set 2298
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2546 180.29M DISK 00:00:39 01-MAR-11
    BP Key: 2549 Status: AVAILABLE Compressed: YES Tag: TAG20110301T061533
    Piece Name: /mnt/rman_202/pnetproy/al_pres_15m63to5_1_1
    List of Archived Logs in backup set 2546
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    2801 85.40M DISK 00:00:19 02-MAR-11
    BP Key: 2804 Status: AVAILABLE Compressed: YES Tag: TAG20110302T061613
    Piece Name: /mnt/rman_202/pnetproy/al_pres_18m66i5d_1_1
    List of Archived Logs in backup set 2801
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3058 137.93M DISK 00:00:30 03-MAR-11
    BP Key: 3061 Status: AVAILABLE Compressed: YES Tag: TAG20110303T061548
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1bm696gk_1_1
    List of Archived Logs in backup set 3058
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3324 138.96M DISK 00:00:31 04-MAR-11
    BP Key: 3327 Status: AVAILABLE Compressed: YES Tag: TAG20110304T061559
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1em6bqsv_1_1
    List of Archived Logs in backup set 3324
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3597 178.07M DISK 00:00:39 05-MAR-11
    BP Key: 3600 Status: AVAILABLE Compressed: YES Tag: TAG20110305T061543
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1hm6ef8f_1_1
    List of Archived Logs in backup set 3597
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3835 198.44M DISK 00:00:43 06-MAR-11
    BP Key: 3838 Status: AVAILABLE Compressed: YES Tag: TAG20110306T061548
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1km6h3kk_1_1
    List of Archived Logs in backup set 3835
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4131 185.94M DISK 00:00:40 07-MAR-11
    BP Key: 4134 Status: AVAILABLE Compressed: YES Tag: TAG20110307T061546
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1nm6jo0i_1_1
    List of Archived Logs in backup set 4131
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4435 161.37M DISK 00:00:35 08-MAR-11
    BP Key: 4438 Status: AVAILABLE Compressed: YES Tag: TAG20110308T061540
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1qm6mccc_1_1
    List of Archived Logs in backup set 4435
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4745 79.24M DISK 00:00:18 09-MAR-11
    BP Key: 4748 Status: AVAILABLE Compressed: YES Tag: TAG20110309T061555
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1tm6p0os_1_1
    List of Archived Logs in backup set 4745
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
    1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    5270 135.13M DISK 00:00:31 10-MAR-11
    BP Key: 5273 Status: AVAILABLE Compressed: YES Tag: TAG20110310T061603
    Piece Name: /mnt/rman_202/pnetproy/al_proy_20m6rl53_1_1
    List of Archived Logs in backup set 5270
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
    1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
    1 58 2174307679 09-MAR-11 2174353241 09-MAR-11
    1 59 2174353241 09-MAR-11 2174384330 10-MAR-11
    1 60 2174384330 10-MAR-11 2174387259 10-MAR-11
    RMAN>
    For example the backups of archivelog from Feb 21st will never be deleted unless I force the delete.
    I'd like to understand why it happens :-)
    Thanks a lot,
    Regards,
    Diego.

  • How to restore cold backup + archived log files

    Hi,
    Suppose I take a cold backup on 18th. After that I have four days of archived log files. if the database crashes on 5th day, I have to restore the 18th cold back + 4 days of archived log files. How do I restore since it is a cold backup and I cant do incomplete recovery.
    can I use
    Recover database ( with 18th cold backup) in mount state and apply archived logs.
    Prabhath

    The details of how you perform forward recovery using a cold backup depends on
    1- rman or manual backup
    2- using current or backup control file
    3- if rman, recovery catalog or no recovery catalog
    4- if full database recovered or only a few files
    Each of these conditions will affect what is known to Oracle and what needs to be done. For example if you restored the entire cold backup including the control file then Oracle would see a consistent database and not need to perform recovery so you would need to startup mount and tell the database to perform recovery using a backup control file. If using rman and no recovery catalog you might need to catalog some of the archived redo logs, etc....
    It is advisable to consult the Backup and Recovery manuals before attempting recovery for any new scenario.
    HTH -- Mark D Powell --

  • How to recover the database when some of the archive log file get deleted.

    I am facing a problem with Oracle database, which is related to archivelogs.
    Our development database is running in archivelog mode, but we don't have backups scheduled and have no recovery catalog.
    When the database was in running condition, disk got full, so some archivelogs were deleted manually.
    After this they restarted the DB, and now DB is not coming up. Errors are as follows:
    SQL> startup
    ORACLE instance started.
    Total System Global Area 1444383504 bytes
    Fixed Size 731920 bytes
    Variable Size 486539264 bytes
    Database Buffers 956301312 bytes
    Redo Buffers 811008 bytes
    Database mounted.
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/export/home/oracle/dev/ADVFRW/ADVFRW.system'
    SQL> recover datafile '/export/home/oracle/dev/ADVFRW/ADVFRW.system'
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    SQL> recover database using backup controlfile;
    ORA-00279: change 215548705 generated at 09/02/2008 17:06:10 needed for thread
    1
    ORA-00289: suggestion :
    /export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC
    ORA-00280: change 215548705 for thread 1 is in sequence #1107
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC
    ORA-00308: cannot open archived log
    '/export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    Media recovery cancelled.
    SQL>
    1. How to recover the database and bring it online
    Any help will be highly appreciated.
    With Regards
    Hemant Joshi
    Edited by: hem_Kec on Sep 7, 2008 9:07 AM

    Hi,
    Archive log files are the copies of redolog files.As redo log files are circularly overwritten,oracle generates archive log file of the corresponding redo logfiles being overwritten.So if you have a backup that dates back to 10 am in the morning and if your database creashed at 3 pm,you cannot use the redo log files alone as they have incomplete information.To completely recover the database upto 3 pm,you need archive log files generated between 10 am to 3 pm. In your case since you are missing one archive log file,you cannot perform complete recovery and hence would suffer data loss.

  • Logical standby | archive log deleted | how to remove gap ???

    hi gurus...
    i have problem on logical standby
    by mistake standby log coming to logical standby has been deleted , now how to fill up the gap ???
    ON STANDBY
    SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# APPLIED
    228 674847 674872 YES
    229 674872 674973 CURRENT
    230 674973 674997 NO
    231 674997 675023 NO
    232 675023 675048 NO
    233 675048 675109 NO
    234 675109 675135 NO
    235 675135 675160 NO
    236 675160 675183 NO
    237 675183 675208 NO
    238 675208 675232 NO
    239 675232 675257 NO
    240 675257 675282 NO
    241 675282 675382 NO
    242 675382 675383 NO
    243 675383 675650 NO
    244 675650 675652 NO
    245 675652 675670 NO
    246 675670 675688 NO
    247 675688 675791 NO
    248 675791 678524 NO
    archive log are shipping to standby location also and getting registered
    ALERT LOG OF STANDBY
    Fri May 7 12:25:36 2010
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[21]: Successfully opened standby log 5: '/u01/app/oracle/oradata/BEST/redo05.log'
    Fri May 7 12:25:37 2010
    RFS LogMiner: Registered logfile [u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_248_1_715617824.dbf] to LogMiner session id [1]
    but i dont have standby log after 229 sequence ...
    ON PRIMARY
    SYS@TEST AS SYSDBA> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /u01/app/oracle/flash_recovery_area/TEST/standlogOldest online log sequence 247
    Next log sequence to archive 249
    Current log sequence 249
    what to do next to apply sequences and bring both in sync.
    please help me ,,,,
    Edited by: user12281508 on May 7, 2010 9:45 AM

    thanks for response.
    no its pure logical standby
    i have tried to ftp the archive logs of primary to standby and applied manually
    SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf';
    alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf'
    ERROR at line 1:
    ORA-01289: cannot add duplicate logfile
    SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf';
    alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf'
    ERROR at line 1:
    ORA-01289: cannot add duplicate logfile
    any other way ????

Maybe you are looking for