No clarity on location of archive logs in Oracle 11g database

I have this query which I am not able to resolve. There is one location of archive log mentioned as /oraarch/app/oracle/oradata/snlprod/archive_logs/ in the parameter log_archive_dest_1. But the archive logs are showing in another location /orabackup/rman/snlprod/archive_logs. I am wondering how the archive logs are showing in this location, /orabackup/rman/snlprod/archive_logs.
I guess there is only one way in which location can be given which is seen from Availability->Recovery Settings->Media Recovery.
I hope, my question is clear.
Please revert with the reply to my query.
Regards

Must be
show parameter db_recovery_file_dest
If you want archived redo log send to /oraarch/app/oracle/oradata/snlprod/archive_logs
then you must set  log_archive_dest_1 ='LOCATION= /oraarch/app/oracle/oradata/snlprod/archive_logs'
log_archive_dest_1 is same before then it means your all  archvied redo log file will create in this directory
Regards
Mahir M. Quluzade

Similar Messages

  • Oracle recommended location for archive logs in  oracle 10g rac

    Hello All,
    We would like to know the oracle recommended location for the archive logs in oracle10g RAC .we are using ASM.
    Thanks...

    user4487322 wrote:
    thanks. Is it the recommended setting ,if we go for a DR setup?I mean archive logs in ASM.If you can use dataguard, the archivelog copy to the standby system would be handled by Oracle and it supports ASM.
    Just remember, what ever your strategy, the archivelogs must be in a SHARED location (where all nodes can read/write to this location.)

  • Locating user tables in an Oracle 11g database

    Excuse my ignorance on this subject
    But our company has an Oracle 11g database that drives one of our business applications. I am not an oracle admin and there is very little documentation on the application itself, however the application seems to have its own set of explicit login (username and password) credentials so I am guessing they are hashed somewhere in the database tables.
    My question would be – are there any default oracle tables where user credentials would typically be? or tips on tracking down where the password hashes may be? Or can this differ from application to application? Any tips welcome. Apologies for the naivity of the question. My goal is to identify which database accounts can query the table the hashes are in, as we have some users who can access the database for data analysis purposes - but I dont want them to have access to the table.

    user599292 wrote:
    EdStevens wrote:
    user599292 wrote:
    Excuse my ignorance on this subject
    But our company has an Oracle 11g database that drives one of our business applications. I am not an oracle admin and there is very little documentation on the application itself, however the application seems to have its own set of explicit login (username and password) credentials so I am guessing they are hashed somewhere in the database tables.
    My question would be – are there any default oracle tables where user credentials would typically be? or tips on tracking down where the password hashes may be? Or can this differ from application to application? Any tips welcome. Apologies for the naivity of the question. My goal is to identify which database accounts can query the table the hashes are in, as we have some users who can access the database for data analysis purposes - but I dont want them to have access to the table.The information relative to the user accounts is revealed in the view DBA_USERS, which normal users should not have a need to see. However, the passwords are stored in a true hash. It cannot be used directly, and cannot be reversed. So being able to see the hashed password does not in itself constitute a security risk.
    When a user is being authenticated, the procedure that oracle uses is NOT to 'decrypt' the stored password to see if it matches the password presented by the user. Rather, the password presented by the user is hashed, and that hash value is compared against the stored value.My concern was if they could extract those password hash values, there are many free password crackers where if they run dictionary values against those hash values and if any match they then have some passwords to gain perhaps elevated access in the application.Such a method would have to assume a password, know how oracle 'salts' the password, hash the result, then compare to the hashed values from the table. If you employ even a modicum of password complexity enforcement, I doubt that your developers are going to have access to the kind of computing capacity that would be required to get a positive result within your lifetime.
    You need to do three things
    First and foremost, adhere to the principle of 'least privilege'. Do not grant a user account any privileges that are not required for that account to complete it's business task. That includes access to any tables or views. Be wary of any "--ANY---" privileges.
    Second, use the password complexity function to enforce a reasonable level of password complexity.
    Third, Set the user's profile to expire the pasword after 'x' number of days and prevent the reuse of a password until after 'y' iterations.

  • 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;

  • User change password after first logging in Oracle 11g

    Hi
    Can you help someone in connection with this problem:
    user can not change password after first logging in Oracle 11g
    All the best
    Ragip Avdijaj

    Sounds like they are not getting logged in at all, so they are never getting to the point where they can change the password, but we need to see more detail to give a better answer (an example or copy-paste of a sqlplus session might help)

  • Specifying separate location for Archived logs in Persistent settings

    DB version:11gR1
    I am new to RMAN
    Currently my RMAN bkp script looks like
    run {
    recover copy of database with tag "INCR_BKP";
         backup check logical incremental level 1 format '/data_DISK1/bkp_dir/nhprod31/data/INCR_%d_%u'
              for recover of copy with tag "INCR_BKP" database;
         backup (archivelog all  format='/data_DISK2/bkp_dir/nhprod31/arch_logs/ARCH_%d_%T_%u_s%s_p%p' DELETE ALL INPUT TAG "arch_logs");
         backup format '/data_DISK1/bkp_dir/nhprod31/ctrl_file/RMAN_CTL_%s:%t:%p.bkp' current controlfile;
    }I want Datafiles and Archived logs to be stored in different locations like above.
    But i want to remove those lengthy path locations in the script and just use
    backup database plus archivelog;For this, i need to set
    configure channel device type disk format ='/u01/backup/ora_%U.bak';Question1.
    Is it possible to specify a separate archive log location using CONFIGURE command?
    Question2.
    If it is not possible, all the backup files will have the same naming convention
    ora_%U.bakhow will you identify the type of backup file. Say, i need the archive log files to be named with Log sequence number in it (like ARCH_%d_%T_%u_s%s_p%p). Shouldn't Oracle be including a provision for this?
    I am not even sure that each archive log file will backed up as a single backup file. Oracle may consolidate all the archive logs in to one backup piece. Please forgive my ignorance.

    783999 wrote:
    Try this for datafile backup:
    RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '<PATH>/rbkp/databkp/DATA_L0_QA_%d_%s_%p';
    RMAN> show all;
    This worked for me.
    Regards,
    BikramThis won't work. Re-read the question carefully.

  • Change the location of Archive Logs on standby Server

    Can somebody tell me the process how to change the archive logs location for the standby by server. e.g. Its going now to location C:\stby\archives and I want to send it to E:\stby\archives
    Thx

    Hi,
    Change the STANDBY SPFILE/PFILE Value of <b>standby_archive_dest=E:\stby\archives</b>
    see this
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/init_params.htm#84366
    HTH
    Regards!

  • Archived log missed in standby database

    Hi,
    OS; Windows 2003 server
    Oracle: 10.2.0.4
    Data Guard: Max Performance
    Dataguard missed some of the archivelog files and but latest log files are applying. standby database is not in sync with primary.
    SELECT LOCAL.THREAD#, LOCAL.SEQUENCE# FROM (SELECT THREAD#, SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=1) LOCAL WHERE LOCAL.SEQUENCE# NOT IN (SELECT SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=2 AND THREAD# = LOCAL.THREAD#);
    I queried above command and I found some files are missed in standby.
    select status, type, database_mode, recovery_mode,protection_mode, srl, synchronization_status,synchronized from V$ARCHIVE_DEST_STATUS where dest_id=2;
    STATUS TYPE DATABASE_MODE RECOVERY_MODE PROTECTION_MODE SRL SYNCHRONIZATION_STATUS SYN
    VALID PHYSICAL MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE NO CHECK CONFIGURATION NO
    Anyone can tell me how to apply those missed archive log files.
    Thanks in advacne

    Deccan Charger wrote:
    I got below error.
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
    ERROR at line 1:
    ORA-01153: an incompatible media recovery is activeYou need to essentially do the following.
    1) Stop managed recovery on the standby.
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;2) Resolve the archive log gap - if you have configured FAL_SERVER and FAL_CLIENT Oracle should do this when you follow step 3 below, as you've manually copied the missed logs you should be OK
    3) restart managed recovery using the command shown above.
    You can monitor archive log catchup using the alert.log or your original query.
    Niall Litchfield
    http://www.orawin.info/
    Edited by: Niall Litchfield on May 4, 2010 2:29 PM
    missed tag

  • Managing ARCHIVE Logs in Oracle 10.2.0.3

    I am working with a customer who seems to think there is a way of controling the database other than a custom JOB, script or RMAN in how it creates, manages and deletes its archive logs while running in archivelog mode. He wants the database to automatically delete obsolete archive logs. He also wants to control the duration in time between each time an archive log is written in order to stop the growth of archive logs and filling up disk space.
    I am saying this is not possible. You either configure RMAN to delete the obsolete or expired archive logs based on your retention policy or do it manually in the Enterprise Manager or Grid Control Console by deletenig obsolete or expired logs.
    Am I correct or am I off base here?

    4.1.3 Sizing Redo Log Files
    The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance. Undersized log files increase checkpoint activity and reduce performance.
    Although the size of the redo log files does not affect LGWR performance, it can affect DBWR and checkpoint behavior. Checkpoint frequency is affected by several factors, including log file size and the setting of the FAST_START_MTTR_TARGET initialization parameter. If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files. The optimal size can be obtained by querying the OPTIMAL_LOGFILE_SIZE column from the V$INSTANCE_RECOVERY view. You can also obtain sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control.
    It may not always be possible to provide a specific size recommendation for redo log files, but redo log files in the range of a hundred megabytes to a few gigabytes are considered reasonable. Size your online redo log files according to the amount of redo your system generates. A rough guide is to switch logs at most once every twenty minutes.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/build_db.htm#sthref237
    If you are talking about data guard then:
    4.1.3 Sizing Redo Log Files
    The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance. Undersized log files increase checkpoint activity and reduce performance.
    Although the size of the redo log files does not affect LGWR performance, it can affect DBWR and checkpoint behavior. Checkpoint frequency is affected by several factors, including log file size and the setting of the FAST_START_MTTR_TARGET initialization parameter. If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files. The optimal size can be obtained by querying the OPTIMAL_LOGFILE_SIZE column from the V$INSTANCE_RECOVERY view. You can also obtain sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control.
    It may not always be possible to provide a specific size recommendation for redo log files, but redo log files in the range of a hundred megabytes to a few gigabytes are considered reasonable. Size your online redo log files according to the amount of redo your system generates. A rough guide is to switch logs at most once every twenty minutes.
    Automatic Deletion of Applied Archive Logs
    Archived logs, once they are applied on the logical standby database, will be automatically deleted by SQL Apply.
    This feature reduces storage consumption on the logical standby database and improves Data Guard manageability.
    See also:
    Oracle Data Guard Concepts and Administration for details
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14214/chapter1.htm#sthref269

  • How to delete archive logs on the standby database....in 9i

    Hello,
    We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
    The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
    Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.
    thanks,
    C.

    We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
    The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
    Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.From 10g there is option to purge on deletion policy when archives were applied. Check this note.
    *Configure RMAN to purge archivelogs after applied on standby [ID 728053.1]*
    Still it is on 9i, So you need to schedule RMAN job or Shell script file to delete archives.
    Before deleting archives
    1) you need to check is all the archives are applied or not
    2) then you can remove all the archives completed before 'sysdate-2';
    RMAN> delete archvielog all completed before 'sysdate-2';
    As per your requirement.

  • Manually Apply Archived log to stand by database

    Hi all,
    I'm using Oracle 10g. So, we need to apply the archived logs of Primary database to stand by database, but this process must be manually.
    A "robot" copy the archived logs to destination. I need to get these archived logs from destination and manually apply to stand by database.
    How can I do this?
    thank you very much!!!!

    How can I do this?First stop current recover process as
    alter database recover managed standby database cancel;Then transfer all need archive logs from primary to standby side and apply these manually using below command.
    recover standby database until cancel
    /*this command will ask full path of archive logs
    and give these then finally enter "CANCEL" word*/Finally you can continue normal/automatic state using
    alter database recover managed standby database ;

  • Tidying the list of archive logs in Oracle

    We have been using Archive Logging for a while but manually handle the purging of them. Since we restart our 9.2 Oracle DBs daily and perform backups (cold) daily, the archive logs are currently suitable for a day.
    However, in Oracle Enterprise Manager > Storage > Archive Logs, we see the entire list (history) of archive logs.
    Can this be tidied and how?
    Thanks

    my mistake
    Problem Description:
    ====================
    When querying "v$loghist," the number of rows displayed is less than the total
    number of Redo Logs created by the database.
    Solution Description:
    =====================
    The quantity of Log History is driven by the internal parameter "maxloghistory".
    When creating a database you have the option to specify the "maxloghistory"
    parameter. The default value is OS dependent.
    In order to alter this parameter you need to re-create the controlfile and
    specify the "maxloghistory" parameter.
    Explanation:
    ============
    The setting for log history in the control file is set very low.
    The Log history is stored in the controlfile. When a database is created we
    specify how much Log history to store. Often, this setting is ignored or made
    small so the controlfile is not too large.
    References:
    ===========
    Oracle Server SQL Reference
    Note: there are some bugs about maxloghistory being ignored if you try to recreate your database.

  • Logging to Oracle 11g

    Hello,
    I am a new user for Oracle 11g. After the successful installation when I tried to Logging to SQL Plus Command Prompt with username and Password .Its throws the following set of errors
    Error Message
    Enter user-name: myOracle
    Enter password:
    ERROR:
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    Process ID: 0
    Session ID: 0 Serial number: 0
    I again tried to login through SYS as SYSDBA but its saying Log Files are full and show the following set of message
    Error Message Through CMD
    C:\Documents and Settings\Bhaskar Anand>sqlplus /nolog
    SQL*Plus: Release 11.2.0.1.0 Production on Thu Aug 25 14:37:22 2011
    Copyright (c) 1982, 2010, Oracle. All rights reserved.
    SQL> connect sys as sysdba
    Enter password:
    ERROR:
    ORA-28056: Writing audit records to Windows Event Log failed
    OSD-2266672: Message 2266672 not found; product=RDBMS; facility=SOSD
    O/S-Error: (OS 1502) The event log file is full.
    ORA-28056: Writing audit records to Windows Event Log failed
    OSD-2266672: Message 2266672 not found; product=RDBMS; facility=SOSD
    O/S-Error: (OS 1502) The event log file is full.
    Do Help me with the situation

    refer the link:-ORA-28056: while connect to the database

  • DB13: Execute Redo log backup of remote Oracle 11g database fails

    Dear Experts,
    First of all I have to state I am not very experienced in administrating (Oracle) databases, but I would like to ask you all the following:
    We run two SAP Systems with each their own database on the same host:
    1. SAP SRM ABAP system on Oracle 11g
    2. SAP NetWeaver WebAS Java (Portal) on Oracle 11g
    We would like to schedule backups of the Java database in transaction code DB13 on the SRM ABAP system.
    Actions already taken:
    - We have maintained the proper database connection to the Java database and have set file system permissions correctly (according SAP Note 102570). Connection in transaction DB02 is fine and stats are showing for both databases.
    - We have maintained enviroment settings for <SID>_ORACLE_HOME and <SID>_SAPDATA_HOME and for the shell (csh).
    - Destination SAPXPG_DBDEST_<host> is maintained in SM59.
    When we schedule a Redo log backup of Java System in DB13 and execute immediately, we receive the following error:
    Process died due to signal 11
    SXPG_COMMAND_EXECUTE mislukt voor BRARCHIVE - oorzaak: unknown
    Any tips?
    Thanks in advance & Best regards,
    Jan Laros

    Hi Eduardo,
    Thank you for your reply.. Today I am at another customer, so I can not check it. But is seems to me that the BRTOOLS are up-to-date as we installed the system fresh and imported the Support Package and kernel updates right afterwards.
    I will check which BRTOOLS are used tonight, anyway.
    Best regards,
    Jan

  • How to backup flashback data archive enabled tables -oracle 11g?

    1) Whether the flashback data archive can be backed up using the following options in oracle? Any pointer from the documentation would be much appreciated.
         RMAN
         Data pump
    2) How to move the flashback data archive table from one database to another? The reason why I am asking this question is that the history data for flashback data archive table is managed by undo tablespace. In this case, if I simply export the flashback data archive enabled tables to another database, will I able to view the history information?
    Regards,
    Richard

    Hi Morgan,
    Thanks for your response. Our intention is that to configure the total recall feature in the reporting instance for historical data view. Let's say , we are mining the changed data from the OLTP instance to reporting instance via logical standby. In this case, the history data will be maintained in the reporting instance?
    Regards,
    Richard

Maybe you are looking for