Archive purge logs

Similar Questions

• How to archive the log Purge ODI

  Dear gurus,

  I have two concerns: -.

  1. What is the difference (and how to find them) b2in session and scenario of reports.

  2. how to archive purged ODI journal.

  Could you please help me on this.

  Thank you

  Sébastien

  Hello

  1 session: when you run any object in ODI, deriving from the execution logs that are created by exploiting are calling the session.

  The script reports: this is a summary that appears under the node for the execution of each scenario

  For example. I have a TEST Version 001 scenario. When I run this, a session for execution will be created in the operator, and a summary will be created under the node for execution.

  Session: Details of the steps executed.

  

  Scenario report: this is the summary of execution

  

  If you click on it, it will give you the overview of execution:

  

  When you purge the logs, there is an option to also purge scenario reports. If you uncheck this option, the script reports will be retained, while session logs will be purged.

  

  For more details, please see this link: 23 monitoring integration processes (12 c (12.1.2))

  2 archives ODI Purge logs: you can take either an export of logs manually the operator before the purge.

  Or you can use the Odi OdiPurgeLog tool which includes options for archive purge logs. For more information about the tool refer to this link To Oracle Data Integrator reference (12 c (12.1.2)) tools and search for "OdiPurgeLog."

  

  Concerning

  Christian love

• Purge logs archiving on things primary and Standby and for Data Guard RMAN

  
  Hi, I saw a couple of orders in regard to the purge archive records in a Data Guard configuration.

  Set UP the STRATEGY of SUPPRESSION of ARCHIVE to SHIPPED to All RELIEF;

  Set UP the STRATEGY of ARCHIVELOG DELETION to APPLIED on All RELIEF;

  Q1. The above only removes logs archiving to the primary or primary and Standby?

  Q2. If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  I also saw

  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVED;

  Q3. That what precedes, and once again it is something that you re primary side?

  I saw the following advice in the manual of Concepts of data protection & Admin

  Configure the DB_UNIQUE_NAME in RMAN for each database (primary and Standby) so RMAN can connect remotely to him

  Q4. Why would I want my primary ro connect to the RMAN Repository (I use the local control file) of the standby? (is this for me to say define RMAN configuration settings in the Standby) manual

  Q5. Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Q6. If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Q7. Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Q8. What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  Any idea greatly appreciated,

  Jim

  The above only removes logs archiving to the primary or primary and Standby?

  When CONFIGURE you a deletion policy, the configuration applies to all destinations archive

  including the flash recovery area. BACKUP - ENTRY DELETE and DELETE - ARCHIVELOG obey this configuration, like the flash recovery area.

  You can also CONFIGURE an archived redo log political suppression that newspapers are eligible for deletion only after being applied to or transferred to database backup destinations.

  If deletions above archive logs on the primary, is it really remove them (immediately) or does the FRA to delete if space is needed?

  Its a configuration, it will not erase by itself.

  If you want to use FRA for the automatic removal of the archivelogs on a database of physical before you do this:

  1. make sure that DB_RECOVERY_FILE_DEST is set to FRA - view parameter DB_RECOVERY_FILE_DEST - and - setting DB_RECOVERY_FILE_DEST_SIZE

  2. do you have political RMAN primary and Standby set - CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON ALL STANDBY;

  If you want to keep archives more you can control how long keep logs by adjusting the size of the FRA

  Great example:

  http://emrebaransel.blogspot.com/2009/03/delete-applied-archivelogs-on-standby.html

  All Oracle is worth a peek here:

  http://emrebaransel.blogspot.com/

  That what precedes, and once again it is something that you re primary side?

  I would never use it. I always had it put it this way:

  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

  I would use only 'BACKED UP' for the data protection system. Usually it tell oracle how many times to back up before removing.

  Why would I want my primary ro connect to the RMAN Repository?

  Because if you break down, you want to be able to backup there, too.

  Also if it remains idle for awhile you want.

  Should I only work with the RMAN Repository on the primary or should I be also in things in the deposits of RMAN (i.e. control files) of the standby?

  Always use a database of catalog RMAN with Data Guard.

  If I am (usually mounted but not open) Physics, of standby I able to connect to its own local repository for RMAN (i.e. control based on files) while sleep mode is just mounted?

  Same answer as 5, use a catalog database.

  Similiarly if I have an old lofgical (i.e. effectively read-only), to even connect to the local RMAN Repository of Eve?

  Same answer as 5, use a catalog database.

  What is the most common way to schedule a RMAN backup to such an environment? example cron, planner of the OEM, DBMS_SCHEDULER? MY instinct is cron script as Planner OEM requires running the OEM service and DBMS_SCHEDULER requires the data runs?

  I think cron is still, but they all work. I like cron because the database has a problem at work always reports its results.

  Best regards

  mseberg

  Summary

  Always use a database with RMAN catalog.

  Always use CRF with RMAN.

  Always set the deletion «To APPLY ON ALL STANDBY» policy

  DB_RECOVERY_FILE_DEST_SIZE determines how long to keep the archives with this configuration.

  Post edited by: mseberg

• I want to move or archive all logs of all the computers in my domain name in one place

  Original title: more details

  Thanks for the reply, but it did not entirely of my concern. I want a way to automatically archive all the event logs of all computers in the domain to a place or location so that everytime I want to view logs from any computer I have to go to the centralized location and view it instead of going on this computer
  Hope I made my concern more clearly now.
  Hope to hear from you soon
  The sub steps might help you better understand my point of view
  1. I want to move or archive all logs of all the computers in my domain name in one place
  2. I want to be able to access any newspaper of the events from any computer by simply contacting this central location
  Thank you

  Hello

  Given that the problem is related to the domain network, I suggest you post this question in the TechNet forum.
  http://social.technet.Microsoft.com/forums/en-us/categories/

• The EM console has the feature archive / move logs area/application on a recurring basis as a cron job?

  Our client has determined they want the server to backup/archive/move logs regularly and need to know if the EM console has built-in features to the app itself archive/move/backup of these files on a regular basis as would a cron job.  If so, what are the steps in the console 'EM to do?

  Any comments would be greatly appreciated.

  Thank you!

  Hello

  There are several ways to reach these

  (1) If you already have a script as a cron Job, which can be automated by practice below.

  OEM--> business--> Job--> library--> create OS command ' use of the library-->

  In parameter--> choose the command type as script--> and use your script. (If you change the interpreter for usage on the host instead of the default, it is recommended to provide the full path (example: % perlbin %/perl))))

  (2) for backup Archives, as--> above, you can create job of the RMAN SCript library

  Or

  backup archives page 2) go to the database ==> "Availability", "Backup and recovery", "Backup settings" (in the location of backup of configuration etc.) and 'Recovery catalog settings' (to register for production DB in the catalog DB).

  Then you can customize the following scheduled backup:

  Go to 'Schedule backups', 'tailor-made backup', follow the full hot backup schedule screen.

  Please follow the link for more information below

  http://docs.Oracle.com/CD/E24628_01/doc.121/e24473/jobs.htm#EMADM9238

  11.3 creating jobs

  Your first task in creating a job from the job activity page is to choose a job type, resulting in the following section, Select a Type of job. The more typical kinds of work are the OS command jobs, script and multitasking works, which are explained in the following sections:

  • Creation of a post of OS command
  • Creating a SQL Script task
  • Creating a multi task - load

  Concerning

  Krishnan

• Questions about the parameters of database using a fast recovery area and the writing of two copies of archived redo logs.

  My databases are 11.2.0.3.7 Enterprise Edition. My OS is AIX 7.1.

  I am to convert databases to use individual zones of rapid recovery and have two questions about what values to assign to database settings related to archived redo logs. This example refers to a database.

  I read that if I specify

  Log_archive_dest_1 =' LOCATION = USE_DB_RECOVERY_FILE_DEST'

  the names of newspapers archived redo written in the default quick recovery area is '% t_%S_%r.dbf '.

  In the past my archived redo logs have been appointed based on the parameter

  log_archive_format='GPAIDT_archive_log_%t_%s_%r.arc'

  I think log_archive_format will be ignored for logs archived redo written in the fast recovery area.

  I am planning to write a second copy of the archived redo logs based on the parameter

  ALTER system set log_archive_dest_2 = ' LOCATION = / t07/admin/GPAIDT/arch.

  If I do this, the copy of logs placed in /t07 will be called '% t_%S_%r.dbf' or 'GPAIDT_archive_log_%t_%s_%r.arc '?

  Before my use of a fast recovery area, I used the OEM 12 c Console to specify settings of backup of database that has been deleted and archived redo logs after 1 backup. Oracle manuals say rather specify a deletion of "none" policy and allow Oracle delete newspapers in the area of fast recovery if necessary. Since I got to keep a second copy of these log files in /t07 should I keep the policy that says to delete logs after 1 backup? If I don't do that, how will they removed from /t07?

  Thank you

  Bill

  If I do this, the copy of logs placed in /t07 will be called '% t_%S_%r.dbf' or 'GPAIDT_archive_log_%t_%s_%r.arc '?

  They will be "GPAIDT_archive_log_%t_%s_%r.arc". LOG_ARCHIVE_FORMAT is only ignored for directories under OMF.

  Since I got to keep a second copy of these log files in /t07 should I keep the policy that says to delete logs after 1 backup? If I don't do that, how will they removed from /t07?

  You can hold the deletion policy as it is. Oracle documentation, defining the STRATEGY of the ARCHIVELOG DELETION: "the deletion of archived newspaper policy applies to logs archive destinations, including the area of fast recovery."

• Best location for the archived redo logs

  Hello

  I am OOF instructions and I want to make life for the DBA, that looks like my job easier.

  So, as the title says what is the location of the "standard/Best Practice' for archived redo logs? particularly the dest_1 which is usually local on the same server

  Thank you.

  Hello

  For you, I recommend the use of the Flash/fast recovery area.

  Configuration of the archived of Redo Log locations

  Oracle recommends that you use fast area recovery to an archive location, because the archived logs are managed automatically by the database. The file names generated for the newspapers archived in the fast recovery area correspond to Oracle managed files and are not determined by the parameter LOG_ARCHIVE_FORMAT . Whatever archiving scheme you choose, it is always advisable to create multiple copies of archived redo logs.

  Ref 1:

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#CHDEHHDH

  Ref 2:

  http://docs.Oracle.com/CD/E11882_01/server.112/e17157/unplanned.htm#BABEEEFH

  REF 3:

  http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV89418

  Kind regards

  Juan M

• A PL/SQL to add the archived redo log for logminer files - please help debug

  Hello
  
  I have a PL/SQL to add recovery logs a day archived files to logminer utility in order to catch all LMD, which happened for a paticular at a particular time scheme
  
  as below,
  
  -logmnr.sql
  
  Set serveroutput on
  
  declare
  
  v_redo_dictionary_file VARCHAR2 (100);
  v_archived_log_file VARCHAR2 (100);
  
  -catch all them archived redo logs today, put in a cursor
  
  CURSOR logfile_cur IS
  SELECT name from v$ archived_log WHERE the to_char (COMPLETION_TIME, 'dd_MM_yyyy') > '18_01_2010' and not in sequence # (select sequence # v$ archived_log WHERE DICTIONARY_BEGIN = 'YES' AND dictionary_end = 'YES');
  
  
  Start
  
  -Create the DICTIONARY file on the files of the SOURCE database redo
  
  sys. DBMS_LOGMNR_D.build (OPTIONS = > sys.) DBMS_LOGMNR_D.store_in_redo_logs);
  
  
  Select name from v_redo_dictionary_file from v$ archived_log where DICTIONARY_BEGIN = 'YES' AND dictionary_end = 'YES', and sequence # = (select MAX(sequence#) from v$ archived_log WHERE DICTIONARY_BEGIN = 'YES' AND dictionary_end = 'YES');
  
  -Add newspapers of dictionary files
  sys.dbms_logmnr.add_logfile (nom_fichier_journal = > v_redo_dictionary_file,)
  Options = > sys.dbms_logmnr.new);
  
  -Add the log files
  
  Open logfile_cur;
  
  LOOP
  
  SEEK logfile_cur INTO v_archived_log_file;
  EXIT WHEN logfile_cur % NOTFOUND;
  sys.dbms_logmnr.add_logfile (nom_fichier_journal = > v_archived_log_file);
  
  
  END LOOP;
  
  CLOSE Logfile_cur;
  
  -Start LogMiner, also enable the ddl
  
  sys.dbms_logmnr.START_LOGMNR (options = > dbms_logmnr.dict_from_redo_logs + dbms_logmnr.ddl_dict_tracking);
  
  EXCEPTION
  WHILE OTHERS
  THEN
  DBMS_OUTPUT. PUT_LINE (SQLERRM);
  
  END;
  /
  
  
  ###############
  SQL > @logmnr.sql
  ORA-01291: missing logfile
  
  PL/SQL procedure successfully completed.
  
  What I did wrong?
  
  Thank you very much
  Roy

  [Double wire | http://forums.oracle.com/forums/message.jspa?messageID=4035521#4035521]

• Two questions relating to the archive redo logs with RMAN backup

  DB version: 11g
  
  I am new to RMAN.
  
  My database is in ARCHIVELOG mode. I intend to make a weekly backup for my db (02:00 every Monday). There will be all the incremental backups between these windows(Monday-to-Monday) of backup that I have would function for retrieving archived redo logs.
  
  
  Question1.
  I want to save the archived logs every day (for example at 23:00). How can I configure that?
  
  These are the configuration setting, that I intend to implement. I don't know how to set up the archive log backup
  

  configure default device type to disk;
  configure retention policy to redundancy;
  configure device type disk parallelism 1;
  configure channel 1 device type disk clear;
  configure channel 2 device type disk clear;
  configure channel 1 device type disk format '/u05/rman1/datafiles/rmnabackup1_%U';
  configure channel 2 device type disk format '/u05/rman2/datafiles/rmnabackup2_%U';
  configure controlfile autobackup on;
  configure controlfile autobackup format for device type disk to '/u05/rman1/control_files/rmnabackup1_%U';

  Question2.
  After that a new full backup is taken at 02:00 on Mondays, the archived redo logs accumulated since the last 7 days become unnecessary. How can I automate the removal of the archive redo logs with RMAN?

  Archive the log delete them all input command will take the destination of the log archiving log backup archive and delete this destination.

  In the log archive destination he has archived log in the sequence 1 to 100 then will he take the backup and delete any of the destination (Monday 23:00).

  In the log archive destination he has archived sequence journal 101 to 150 then will he take the backup and remove those in the destination (Tuesday 23:00).

  In the log archive destination he has archived log in the sequence from 151 to 180 so will he take the backup and delete any of the destination (Wednesday 10:00).

  It will continue like that.

  Concerning
  Asif Kabir

  -If you help brand the response as correct/useful.

• Archived Skipping log file

  
  

  Hi all;

  
  

  Jump the archived log file. How can I stop this? Can anyone help me?
  

  
  

  RMAN > show all.

  Db_unique_name HRMS RMAN database configuration settings are:

  CONFIGURE REDUNDANCY 3 RETENTION STRATEGY;

  CONFIGURE BACKUP OPTIMIZATION

  SET UP DEFAULT DISK DEVICE TYPE;

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

  SET UP THE DEVICE TYPE DISK PARALLELISM 3 TYPE OF BACKUP BACKUPSET.

  CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default

  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default

  CONFIGURE MAXSETSIZE TO 1000 M;

  CONFIGURE ENCRYPTION OF DATABASE # by default

  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default

  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default

  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u02/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_hrms.f'; # by default

  
  

  RMAN > backup the database archivelog;

  From January 13, 15 backup

  Current archived log

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 44 type device = DISK

  allocated channel: ORA_DISK_2

  channel ORA_DISK_2: SID = 33 type of device = DISK

  allocated channel: ORA_DISK_3

  channel ORA_DISK_3: SID = 39 type device = DISK

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_6_bcb7xyy5_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_7_bcb9h6ys_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_8_bcb9sz55_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_9_bcb9v06m_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_10_bcb9v2r6_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_11_bcbbdw3v_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_12_bcbblfso_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_13_bcbbmb2b_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_14_bcbbmz55_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_15_bcbbom9k_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_16_bcbbrn6m_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_17_bcbbsn7c_.arc. already saved 1 time

  jump archived log file /u02/app/oracle/flash_recovery_area/HRMS/archivelog/2015_01_13/o1_mf_1_18_bcbbvcgx_.arc. already saved 1 time

  ...

  ....

  TRIMMED OF
  

  Citing this message:

  RMAN > jump archive log file already saved 1 time

  in RMAN, you have activated OPTIMAZTION as WE

  RMAN > SET UP OPTIMIZATION BACKUP;

  When you enable the backup optimization setting, all backup commands ignore backups of all files (any file dbf, arhcived log file or a "backup set" RMAN) if they have not changed and they have already been completed on the allocated device type.

• PURGE LOG: Dependencies before the purge

  Hello
  
  I want to purge all my log files, can anyone tell me the dependencies before I have make the scheme? Thank you

  based on my experience of application server contain history of CSC and server logs Essbase-essbase activity as from app, from db on essbase. When Essbase server connect long and reach a maximum size would not be commissioning db essbase. I think that PURGE this log is acceptable as long as you the slaughter of your essbase services

• Archived redo logs in ASM or OS file system?

  DB version: 10.2.0.4
  Version of the operating system: Sun Solaris SPARC 5.10
  
  
  We are on a node two CARS.
  Currently, we store logs archived in BONE cross mounted file systems. This is the recommended method?
  What we will have if we keep newspapers archived in ASM?

  Ideally, the location of the log archive must be on a shared volume. In solaris, you can use ASM as the shared diskgroup.
  When using the common diskgroup say + ARCH / (you can choose your own name diskgroup, but for the ease I posted like this) for archiving logs, two instances can write to the same location.
  Need a recovery and restore operation, you can simply restore the archivelogs ASM and run recovery.

  Well, there are some other well explained by the experts here. I just did a unique advantage.

  Kind regards
  Mahesh.

• PL/SQL to add archived redo log files to logminer

  Hello
  I'm doing a program to automatically add files of newspapers to logminer utility, all archived redo as below,
  
  -logmnr.sql
  Set serveroutput on
  
  declare
  
  v_redo_dictionary_file VARCHAR2 (100);
  v_arihived_log_file VARCHAR2 (100);
  
  CURSOR logfile_cur IS
  SELECT name from v$ archived_log WHERE the to_char (COMPLETION_TIME, 'dd_MM_yyyy') > '18_01_2010' and not in sequence # (select sequence # v$ archived_log WHERE DICTIONARY_BEGIN = 'YES' AND dictionary_end = 'YES');
  
  
  Start
  
  -Create the DICTIONARY file on the files of the SOURCE database redo
  sys. DBMS_LOGMNR_D.build (OPTIONS = > sys.) DBMS_LOGMNR_D.store_in_redo_logs);
  
  Select name from v_redo_dictionary_file from v$ archived_log where DICTIONARY_BEGIN = 'YES' AND dictionary_end = 'YES', and sequence # = (select MAX(sequence#) from v$ archived_log WHERE DICTIONARY_BEGIN = 'YES' AND dictionary_end = 'YES');
  
  -Add newspapers of dictionary files
  
  sys.dbms_logmnr.add_logfile (nom_fichier_journal = > v_redo_dictionary_file,)
  Options = > sys.dbms_logmnr.new);
  -Add the log files
  
  Open logfile_cur;
  
  LOOP
  
  SEEK logfile_cur INTO v_arihived_log_file;
  
  sys.dbms_logmnr.add_logfile (nom_fichier_journal = > v_arihived_log_file);
  
  EXIT WHEN logfile_cur % NOTFOUND;
  
  END LOOP;
  
  CLOSE Logfile_cur;
  
  -Start LogMiner, also enable the ddl
  
  sys.dbms_logmnr.START_LOGMNR (options = > sys.dbms_logmnr.dict_from_redo_logs + sys.dbms_logmnr.ddl_dict_tracking);
  
  
  EXCEPTION
  WHILE OTHERS
  THEN
  DBMS_OUTPUT. PUT_LINE (SQLERRM);
  
  END;
  /
  
  
  ##
  SQL > @logmnr.sql
  ORA-01013: user has requested the cancellation of the current operation
  ORA-01289: cannot add logfile in double /usr/tmp/arch/1_4026_573231463.dbf
  
  ##
  SQL > select name from v$ archived_log WHERE the to_char (COMPLETION_TIME, 'dd_MM_yyyy') > '18_01_2010' and not in sequence # (select sequence # v$ archived_log WHERE DICTIONARY_BEGIN = 'YES' AND dictionary_end = 'YES');
  
  NAME
  --------------------------------------------------------------------------------
  /usr/tmp/arch/1_3973_573231463.dbf
  /usr/tmp/arch/1_3974_573231463.dbf
  /usr/tmp/arch/1_3975_573231463.dbf
  /usr/tmp/arch/1_3977_573231463.dbf
  /usr/tmp/arch/1_3978_573231463.dbf
  /usr/tmp/arch/1_3979_573231463.dbf
  /usr/tmp/arch/1_3981_573231463.dbf
  /usr/tmp/arch/1_3982_573231463.dbf
  /usr/tmp/arch/1_3983_573231463.dbf
  /usr/tmp/arch/1_3984_573231463.dbf
  /usr/tmp/arch/1_3986_573231463.dbf
  
  NAME
  --------------------------------------------------------------------------------
  /usr/tmp/arch/1_3987_573231463.dbf
  /usr/tmp/arch/1_3988_573231463.dbf
  /usr/tmp/arch/1_3989_573231463.dbf
  /usr/tmp/arch/1_3990_573231463.dbf
  /usr/tmp/arch/1_3991_573231463.dbf
  /usr/tmp/arch/1_3992_573231463.dbf
  /usr/tmp/arch/1_3994_573231463.dbf
  /usr/tmp/arch/1_3995_573231463.dbf
  /usr/tmp/arch/1_3996_573231463.dbf
  /usr/tmp/arch/1_3997_573231463.dbf
  /usr/tmp/arch/1_3999_573231463.dbf
  
  NAME
  --------------------------------------------------------------------------------
  /usr/tmp/arch/1_4001_573231463.dbf
  /usr/tmp/arch/1_4003_573231463.dbf
  /usr/tmp/arch/1_4004_573231463.dbf
  /usr/tmp/arch/1_4005_573231463.dbf
  /usr/tmp/arch/1_4006_573231463.dbf
  /usr/tmp/arch/1_4007_573231463.dbf
  /usr/tmp/arch/1_4009_573231463.dbf
  /usr/tmp/arch/1_4010_573231463.dbf
  /usr/tmp/arch/1_4011_573231463.dbf
  /usr/tmp/arch/1_4012_573231463.dbf
  /usr/tmp/arch/1_4013_573231463.dbf
  
  NAME
  --------------------------------------------------------------------------------
  /usr/tmp/arch/1_4015_573231463.dbf
  /usr/tmp/arch/1_4017_573231463.dbf
  /usr/tmp/arch/1_4018_573231463.dbf
  /usr/tmp/arch/1_4019_573231463.dbf
  /usr/tmp/arch/1_4020_573231463.dbf
  /usr/tmp/arch/1_4022_573231463.dbf
  /usr/tmp/arch/1_4023_573231463.dbf
  /usr/tmp/arch/1_4025_573231463.dbf
  /usr/tmp/arch/1_4026_573231463.dbf
  
  
  Why do I get error ' ORA-01289: cannot add duplicates logfile usr/tmp/arch/1_4026_573231463.dbf'
  
  Please suggest,
  
  Thank you
  Roy

  sys.dbms_logmnr.add_logfile (nom_fichier_journal-online v_arihived_log_file);
  EXIT WHEN logfile_cur % NOTFOUND;

  not above but below
  EXIT WHEN logfile_cur % NOTFOUND;
  sys.dbms_logmnr.add_logfile (nom_fichier_journal-online v_arihived_log_file);

  reverse the order of the 2 lines

• Diff between switch logfile and archive current log

  Hello
  I see that the effect for the two statements are the same
  ALTER SYSTEM switch logfile;
  =
  ALTER SYSTEM archive log current;
  
  
  is that there is no difference between them?
  Thank you

  Hello..

  ALTER SYSTEM switch logfile;

  =
  ALTER SYSTEM log current ;> archives

  alter system switch logfile--> switches to the following log file, regardless of the mode that the database is in ARCHIVELOG or NOARCHIVELOG mode. If the archivelog mode change system swicth logfile will generate the Archives of the redolog which was changed.

  change the current archiving--> oracle here log system passes current related to records and archives as well as all other newspapers not archived. It can be fired only the database that is in ARCHIVELOG mode.

  [http://download.oracle.com/docs/cd/B10501_01/server.920/a96519/backup.htm]

  HTH
  Anand

• 10g RAC archive current log

  How the command 'Alter system archive log current' work with 10g RAC. It will apply to all instances of the cars or just the connected instance.

  Because your connection is "RAC_DBA" I think you should be able to test this and answer your question?