Archiving the Logs

Hi, I'm trying to delete a file and check it in a separate folder using a windows command in a data load Maxl script. I have a script windows in place, but it will just overwrite the file to archive. . How can I check in files without overwriting the old file written? Suggestions and comments? Thank you!!

As already explained above by Glenn, "ren" is the right syntax, it is not only recognized as a command shell in your example, because you have not preceded with "shell".

If you are strongly opposed to the creation of a separate .bat file for some reason, just make sure you use the "shell" before each individual order of BACK in the MaxL script.

Tags: Business Intelligence

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

  • Archive the log files are not register with oracle 10g are

    Hello

    I have oracle 10.2.0 Linux redhat 4. my database is archivelog since that sequence mode no 30

    but when I backup all the files in the archives to help newspapers.

    rman> backup archivelog all delete input.
    
    it backups up from sequence 67 
    
    because.
    
    SQL> select sequence# from v$archived_log;
    
     SEQUENCE#
    ----------
            67
            68
            69
            70
            71
            72
            73
            74
            75
            76
            77
    
     SEQUENCE#
    ----------
            78
            79
            80
            81
            82
            83
            84
            85
            86
            87
            88
    
     SEQUENCE#
    ----------
            89
            90
            91
            92
            93
            94
            95
            96
            97
            98
            99
    
     SEQUENCE#
    ----------
           100
           101
           102
           103
           104
           105
           106
           107
           108
           109
           110
    
     SEQUENCE#
    ----------
           111
           112
           113
           114
           115
           116
           117
           118
           119
           120
           121
    
     SEQUENCE#
    ----------
           122
    
    56 rows selected.
    
    while i left with
    
    [oracle@Oracledatabas ArchiveDest]$ ls
    1_30_694492901.dbf  1_40_694492901.dbf  1_50_694492901.dbf  1_60_694492901.dbf
    1_31_694492901.dbf  1_41_694492901.dbf  1_51_694492901.dbf  1_61_694492901.dbf
    1_32_694492901.dbf  1_42_694492901.dbf  1_52_694492901.dbf  1_62_694492901.dbf
    1_33_694492901.dbf  1_43_694492901.dbf  1_53_694492901.dbf  1_63_694492901.dbf
    1_34_694492901.dbf  1_44_694492901.dbf  1_54_694492901.dbf  1_64_694492901.dbf
    1_35_694492901.dbf  1_45_694492901.dbf  1_55_694492901.dbf  1_65_694492901.dbf
    1_36_694492901.dbf  1_46_694492901.dbf  1_56_694492901.dbf  1_66_694492901.dbf
    1_37_694492901.dbf  1_47_694492901.dbf  1_57_694492901.dbf
    1_38_694492901.dbf  1_48_694492901.dbf  1_58_694492901.dbf
    1_39_694492901.dbf  1_49_694492901.dbf  1_59_694492901.dbf
    [oracle@Oracledatabas ArchiveDest]$
    
    i have backup of archive log as 
    
    RMAN> list backup of archivelog all;
    
    
    List of Backup Sets
    ===================
    
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    3       136.49M    DISK        00:00:08     27-AUG-09
            BP Key: 3   Status: AVAILABLE  Compressed: NO  Tag: TAG20090827T061019
            Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_27/o1_mf_annnn_TAG20090827T061019_59dpwfkb_.bkp
    
      List of Archived Logs in backup set 3
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    37      1530188    18-AUG-09 1549890    19-AUG-09
      1    38      1549890    19-AUG-09 1584124    19-AUG-09
      1    39      1584124    19-AUG-09 1628757    19-AUG-09
    
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    7       181.96M    DISK        00:00:12     27-AUG-09
            BP Key: 7   Status: AVAILABLE  Compressed: NO  Tag: TAG20090827T222915
            Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_27/o1_mf_annnn_TAG20090827T222915_59gj7x0o_.bkp
    
      List of Archived Logs in backup set 7
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    63      2413676    26-AUG-09 2435738    26-AUG-09
      1    64      2435738    26-AUG-09 2472234    27-AUG-09
      1    65      2472234    27-AUG-09 2515317    27-AUG-09
      1    66      2515317    27-AUG-09 2546805    27-AUG-09
    
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    9       15.94M     DISK        00:00:02     28-AUG-09
            BP Key: 9   Status: AVAILABLE  Compressed: NO  Tag: TAG20090828T001745
            Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_28/o1_mf_annnn_TAG20090828T001745_59gpmc0s_.bkp
    
      List of Archived Logs in backup set 9
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    30      1328116    17-AUG-09 1330698    17-AUG-09
      1    31      1330698    17-AUG-09 1343639    17-AUG-09
    
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    11      104.87M    DISK        00:00:07     28-AUG-09
            BP Key: 11   Status: AVAILABLE  Compressed: NO  Tag: TAG20090828T012913
            Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_08_28/o1_mf_annnn_TAG20090828T012913_59gtsbdk_.bkp
    
      List of Archived Logs in backup set 11
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    31      1330698    17-AUG-09 1343639    17-AUG-09
      1    32      1343639    17-AUG-09 1386340    17-AUG-09
      1    33      1386340    17-AUG-09 1418708    17-AUG-09
    
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    18      2.44G      DISK        00:03:18     17-SEP-09
            BP Key: 18   Status: AVAILABLE  Compressed: NO  Tag: TAG20090917T002120
            Piece Name: /home/oracle/product/10.2.0/flash_recovery_area/NEO/backupset/2009_09_17/o1_mf_annnn_TAG20090917T002120_5c3gb2m2_.bkp
    
      List of Archived Logs in backup set 18
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    67      2546805    27-AUG-09 2571963    28-AUG-09
      1    68      2571963    28-AUG-09 2610800    28-AUG-09
      1    69      2610800    28-AUG-09 2647832    28-AUG-09
      1    70      2647832    28-AUG-09 2668839    28-AUG-09
      1    71      2668839    28-AUG-09 2705408    29-AUG-09
      1    72      2705408    29-AUG-09 2749633    29-AUG-09
      1    73      2749633    29-AUG-09 2783675    30-AUG-09
      1    74      2783675    30-AUG-09 2826464    30-AUG-09
      1    75      2826464    30-AUG-09 2860499    30-AUG-09
      1    76      2860499    30-AUG-09 2903504    31-AUG-09
      1    77      2903504    31-AUG-09 2943108    31-AUG-09
      1    78      2943108    31-AUG-09 2977859    31-AUG-09
      1    79      2977859    31-AUG-09 2998785    01-SEP-09
      1    80      2998785    01-SEP-09 3042779    01-SEP-09
      1    81      3042779    01-SEP-09 3086898    01-SEP-09
      1    82      3086898    01-SEP-09 3103245    02-SEP-09
      1    83      3103245    02-SEP-09 3147628    02-SEP-09
      1    84      3147628    02-SEP-09 3192216    02-SEP-09
      1    85      3192216    02-SEP-09 3208480    02-SEP-09
      1    86      3208480    02-SEP-09 3248106    03-SEP-09
      1    87      3248106    03-SEP-09 3294064    03-SEP-09
      1    88      3294064    03-SEP-09 3323611    03-SEP-09
      1    89      3323611    03-SEP-09 3352060    04-SEP-09
      1    90      3352060    04-SEP-09 3399516    04-SEP-09
      1    91      3399516    04-SEP-09 3440740    04-SEP-09
      1    92      3440740    04-SEP-09 3457884    05-SEP-09
      1    93      3457884    05-SEP-09 3485157    05-SEP-09
      1    94      3485157    05-SEP-09 3523208    05-SEP-09
      1    95      3523208    05-SEP-09 3558325    05-SEP-09
      1    96      3558325    05-SEP-09 3600414    06-SEP-09
      1    97      3600414    06-SEP-09 3642729    06-SEP-09
      1    98      3642729    06-SEP-09 3678479    07-SEP-09
      1    99      3678479    07-SEP-09 3720642    07-SEP-09
      1    100     3720642    07-SEP-09 3748794    07-SEP-09
      1    101     3748794    07-SEP-09 3777963    08-SEP-09
      1    102     3777963    08-SEP-09 3823393    08-SEP-09
      1    103     3823393    08-SEP-09 3865230    08-SEP-09
      1    104     3865230    08-SEP-09 3880510    09-SEP-09
      1    105     3880510    09-SEP-09 3906888    09-SEP-09
      1    106     3906888    09-SEP-09 3961086    09-SEP-09
      1    107     3961086    09-SEP-09 3982103    10-SEP-09
      1    108     3982103    10-SEP-09 4034528    10-SEP-09
      1    109     4034528    10-SEP-09 4055556    11-SEP-09
      1    110     4055556    11-SEP-09 4115268    11-SEP-09
      1    111     4115268    11-SEP-09 4128557    12-SEP-09
      1    112     4128557    12-SEP-09 4165104    12-SEP-09
      1    113     4165104    12-SEP-09 4202850    12-SEP-09
      1    114     4202850    12-SEP-09 4258353    13-SEP-09
      1    115     4258353    13-SEP-09 4298900    14-SEP-09
      1    116     4298900    14-SEP-09 4341046    14-SEP-09
      1    117     4341046    14-SEP-09 4365180    15-SEP-09
      1    118     4365180    15-SEP-09 4424992    15-SEP-09
      1    119     4424992    15-SEP-09 4439538    15-SEP-09
      1    120     4439538    15-SEP-09 4489259    16-SEP-09
      1    121     4489259    16-SEP-09 4532807    16-SEP-09
      1    122     4532807    16-SEP-09 4548893    17-SEP-09
    
    
    
    and when i try
    
    RMAN> backup archivelog from sequence 30 until sequence 66;
    
    Starting backup at 17-SEP-09
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 09/17/2009 04:01:25
    RMAN-20242: specification does not match any archive log in the recovery catalog
    
    
    when i try to restore database on testing server it ask me for
    
    
    
    MAN> recover database until sequence 121;
    
    Starting recover at 17-SEP-09
    using channel ORA_DISK_1
    
    starting media recovery
    
    channel ORA_DISK_1: starting archive log restore to default destination
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=37
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=38
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=39
    channel ORA_DISK_1: reading from backup piece /home/oracle/o1_mf_annnn_TAG20090827T061019_59dpwfkb_.bkp
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/home/oracle/o1_mf_annnn_TAG20090827T061019_59dpwfkb_.bkp tag=TAG20090827T061019
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:17
    channel ORA_DISK_1: starting archive log restore to default destination
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=63
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=64
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=65
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=66
    channel ORA_DISK_1: reading from backup piece /home/oracle/o1_mf_annnn_TAG20090827T222915_59gj7x0o_.bkp
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/home/oracle/o1_mf_annnn_TAG20090827T222915_59gj7x0o_.bkp tag=TAG20090827T222915
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
    channel ORA_DISK_1: starting archive log restore to default destination
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=31
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=32
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=33
    channel ORA_DISK_1: reading from backup piece /home/oracle/o1_mf_annnn_TAG20090828T012913_59gtsbdk_.bkp
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/home/oracle/o1_mf_annnn_TAG20090828T012913_59gtsbdk_.bkp tag=TAG20090828T012913
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
    archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_31_694492901.dbf thread=1 sequence=31
    archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_32_694492901.dbf thread=1 sequence=32
    archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_33_694492901.dbf thread=1 sequence=33
    archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf thread=1 sequence=34
    archive log filename=/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf thread=1 sequence=35
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 09/17/2009 03:01:31
    RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf'
    ORA-00310: archived log contains sequence 34; sequence 35 required
    ORA-00334: archived log: '/home/oracle/DataBaseBackups/ArchiveDest/1_34_694492901.dbf'
    My question is why my 30 to 66 sequence archivelog file are not saved with the database in v$ archived_log and how to solve this problem.

    Thank you
    Umesh

    You may need to increase the CONTROL_FILE_RECORD_KEEP_TIME value.

    If the archivelogs are still on the disk, you can try to catalog them with:

    RMAN> catalog start with '/home/oracle/DataBaseBackups/ArchiveDest/;
    

    or if you don't need the file you can simply remove the o/s and run the following:

    RMAN> crosscheck archivelog all;
    RMAN> delete expired archivelog all;
    
  • 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.

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

    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

  • RMAN-06820: WARNING: unable to archive the current log on the primary database

    I got the following exception when I try to backup the data files and the archivelogs on the physical by uisng RMAN standby database.

    RMAN-06820: WARNING: unable to archive the current log on the primary database

    Target ORACLE database error:

    ORA-17629: unable to connect to the remote database server

    ORA-17627: ORA-00942: table or view does not exist

    It's the backup script

    "

    connection target sys/oracle

    Configure controlfile autobackup on;

    Run {}

    nocfau together;

    allocate channel ch01 device type disc format ' / test/%U';

    allocate channel ch02 device type disc format ' / test/%U';

    backup database copy archivelog;

    backup copy current controlfile;

    }

    "

    And there is no error ora in the primary alert log.

    I was able to tnsping two server (primary/secondary) properly and could also primary of the remote login on standby db server and switch logfile. I read there is a very similar thread, but it has failed so I post again and hope I could get a few clues. Thank you.

    Hello again;

    Try to change this:

    connection target sys/oracle

    to something like this:

    RMAN target sys/password@PRIMARY auxiliary.

    Complete example:

    http://www.Visi.com/~mseberg/data_guard/duprman2.html

    Best regards

    mseberg

  • Removal of the log archiving using RMAN Target in Oracle 10 g

    Hi all
    Recently, I noticed that archive logs have been 102 GBs out of the car and I need to free up space. When I tried to connect using the RMAN catalog
    connect catalog user@db
    I got error message like
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used
    But I could get through the use
    connect target user@db
    My query is that I can use
    RMAN> delete noprompt expired archivelog all;
    as shown in [how to remove the log file archive | https://forums.oracle.com/forums/thread.jspa?threadID=2321257 & start = 0 & tstart = 0]
    Or I'll take another approach to remove obsolete archive logs?

    Kind regards
    * 009 *.

    Hello;

    Recently, I noticed that archive logs have been 102 GBs out of the car and I need to free up space. When I tried to connect using the RMAN catalog

    connect catalog user@db
    

    I got error message like

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used
    

    But I could get through the use

    connect target user@db
    

    Are you trying to connect through Grid control? If you connect via a script, then please post its content.
    Make sure that you are not connected to the database target using "nocatalog.

    rman target sys/@ catalog /@
    

    My query is that I can use

    RMAN> delete noprompt expired archivelog all;
    

    as shown in [how to remove the log file archive | https://forums.Oracle.com/forums/thread.jspa?threadID=2321257&Start=0&tstart=0]
    Or I'll take another approach to remove obsolete archive logs?

    Kind regards
    * 009 *.

    These archives are saved? The command above does not update the RMAN Repository if in case, the archives have been manually delete at the OS level.
    I recommend you save these records and then remove them.

    RMAN>backup archivelog all not backedup 1 times delete input;
    

    If these archives are already saved and were not deleted from the disk, then you can use the below command

    RMAN>delete force noprompt archivelog all completed before 'SYSDATE-n';
    

    where "n" is the number of days of delay on the current date. Be sure to check if these archives have been saved before deleting.

    Kind regards
    Shivananda

  • delete the log file archive

    Hello
    I use oracle 10g on linux, I want to delete archive log file automatically, there is no way to do this.or can someone tell me scripts to do this.ur help on this is very appreciated

    Respect, s
    Umair Iqbal

    Hello

    Can you please let us know why you want to delete the log file archive?

    BTW, you can use RMAN to achieve by archiving log backup and delete the original file using the following command:

    Backup archivelog all delete input;
    

    Concerning

  • Size of the log file Archive

    Redlogfile size is 16 MB and generating the archivelog file size is approximately 10 Mb. what could be the reason?

    Oracle Version: 10.2.0.4

    OS: Windows

    Published by: Deccan charger 19 April 2010 23:31

    First of all:

    a redo log contains a lot of things necessary for instance etc. recovery an archived log is used only for the restorations - he didn't need all the stuff that is in a redo log, so when written CRA the archiving log that he does not write all knowledge, all that is required for restores

    Second:

    Archive logs is created with dimensions smaller, irregular, as the original redo logs. Why? [388627.1 ID]

    --------------------------------------------------------------------------------

    Last updated 2 June 2007 Type status MODERATE HOWTO

    In this Document
    Goal
    Solution
    References

    --------------------------------------------------------------------------------

    This document is available to you through process of rapid visibility (RaV) of the Oracle's Support and therefore was not subject to an independent technical review.

    Applies to:
    Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 11.1
    Information in this document applies to any platform.

    Goal
    Archive logs is created with dimensions smaller, irregular, as the original redo logs.
    Commands like:
    ALTER SYSTEM SWITCH LOGFILE
    or
    ALTER SYSTEM ARCHIVE LOG...
    are not used to generate archives or change the log file. Thus, there is no parameter ARCHIVE_LAG_TARGET set.
    What else could cause this behaviour?
    Solution
    From:
    Bug: 5450861: NEWSPAPERS ARCHIVE IS GENERATED with one SIZE SMALLER THAN THE REDO LOG FILES
    the explanation of this situation has 2 main reasons:
    1 archiving logs do not have to be in the same size. This was decided very long ago, when blank padding archiving logs stopped for a very good reason - in order to save disk space.

    2. the log command does not exist when a redo log file is 100% full. There is an internal algorithm that determines when to switch journal. It also has a very good reason - do the command of newspaper at the last moment may incur performance problems (for various reasons, outside the scope of this note).
    So, after that newspaper ordering occurs the archivers are only copying the information from the redo log files. As recovery logs are not 100% full after the command to log and archive logs are empty not filled after the copy operation is complete, this results in unequal files smaller than the original of redo log files.
    This is very apparent for very low (less than 10 MB) log files; as a result, produced 2.5 MB archive logs of 5 MB recovery logs are very visible.
    Just note that currently, the default log files are 100 MB in size. If the archives log files would be between 98 and 100 MB person would notice.
    The main concern that one must have for newspapers of archives files is a possible corruption. This can be easily verified by attempting a resumption of testing. When it's ok, the size of the log archive uneven should be of no interest, as is expected.

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

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

    I am facing a problem with the Oracle database, which is linked to archivelogs.
    Our development database is running in archivelog mode, but we don't have safeguards and have no recovery catalog.
    When the database was in running, disk got full, so some archivelogs were deleted manually.
    After that they have restarted the DB, and DB now not come. The errors are as follows:

    -------------------------------------------------------------------------------------------------------------


    SQL > startup
    ORACLE instance started.

    Total System Global Area 1444383504 bytes
    Bytes of size 731920 fixed
    486539264 variable size bytes
    956301312 of database buffers bytes
    Redo buffers 811008 bytes
    Mounted database.
    ORA-01589: must use RESETLOGS or NORESETLOGS option of database open


    SQL > alter database open resetlogs;
    ALTER database open resetlogs
    *
    ERROR on 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: cool cancelled due to errors
    ORA-01610: recovery using BACKUP CONTROLFILE option must be


    SQL > restore database using backup controlfile;
    ORA-00279: change 215548705 generated at 2008-09-02 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 thread 1 is in sequence #1107


    Specify the 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 get file status
    SVR4 error: 2: no such file or directory
    Additional information: 3


    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
    Cancel
    Cancelled media recovery.
    SQL >

    -------------------------------------------------------------------------------------------------------------


    1 how to recover the database and put online

    Any help will be much appreciated.

    Regarding
    Hemant Joshi

    Published by: hem_Kec on 7 Sep 2008 09:07

    Hello

    It is actually quite easy.
    We knew that Oracle was looking for logsequence 1107. There is no archived log, it was deleted, or it has never generated. As you delete files, the 1st solution would be possible, BUT as there was only an instance crash so more old archived logs is not required for crash recovery. There is a need during the restoration of the old backup files, which is not our case.

    Thus, the missing log sequence has not been archived = > it is a redo log.
    To identify the required online redo log, we just to log query v$ as I suggest.

    Once the log identified file, we can recover it by specifying the redo log when you ask logsequence 1107.

    And it is on. We win! :)

  • oracle.as.install.engine.exception.LogInitializeException: not enough space to create the log files in the location specified in the inventory. Create a space under the null specified inventory or to point to a different directory

    Hello

    I have installed:

    -(Oracle Linux) OL 6.6

    121 GB HD

    5.0 GB RAM

    -JDK-7u80-EA-bin-b05-Linux-x64-20_jan_2015.tar.gz (Java)

    -Fmw_12.1.3.0.0_infrastructure.jar (infrastructure)

    -Fmw_12.1.3.0.0_ohs_linux64.bin (SST)

    I try to install OBIEE, I unzip these files:

    -bi_linux_x86_111170_64_disk1_1of2.zip

    -bi_linux_x86_111170_64_disk1_2of2.zip

    -bi_linux_x86_111170_64_disk2_1of2.zip

    -bi_linux_x86_111170_64_disk2_2of2.zip

    -bi_linux_x86_111170_64_disk3.zip

    I run/home/oracle/OBIEE/Disk1/runInslaller and open the screen to select the oraInventory directory, when I click OK, the error message appears (see image below):

    Error_Screen.png

    [oracle@localhost Disk1] $. / runInstaller

    Iniciando Universal Oracle install...

    Espaço Verificando Temp: deve ser superior a 1536 MB.   Passado Reais 36602 MB

    Verificando swap Espaço: deve ser superior a 500 MB.   Passado Reais 2553 MB

    Verificando monitor: deve ser configurado para exibir pelo menos 256 cores.    Reais 16777216 Passado

    2nd para iniciar o Oracle Universal Installer from/tmp/OraInstall2015-09-13_08-13-50 h Aguarde... [oracle@localhost Disk1] $ 13/09 / 2015 20:13:53 oracle.as.install.bi.util.ConsumerUIProperties getCustomPropertiesFilename

    INFO: Using a custom UI properties of the oracle/as/install/bi/config/consumer-ui.properties file

    [ERROR]: error initializing log values

    oracle.as.install.engine.exception.LogInitializeException: Espaço insuficiente para criar os log archives na Localização address para o inventario. Espaço shouts ob o inventario especificado/home/oracle/oraInventory UO aponte para outro inventario

    to oracle.as.install.engine.logging.EngineLogHelper. < init > (EngineLogHelper.java:65)

    at oracle.as.install.engine.logging.EngineLogHelper.initialize(EngineLogHelper.java:192)

    to oracle.as.install.engine.InstallEngine. < init > (InstallEngine.java:135)

    to oracle.as.install.engine.InstallEngine. < clinit > (InstallEngine.java:130)

    at oracle.sysman.oio.oioc.OiocOneClickInstaller.main(OiocOneClickInstaller.java:603)

    In English:

    oracle.as.install.engine.exception.LogInitializeException: not enough space to create the log files in the location specified in the inventory. Create a space under the null specified inventory or to point to a different directory

    What can be?

    Well, you very probably not a lot of space on the left under/Home.

    You can move to another location that is located on/home/oracle/orInventory the / partitioning of the partition where you probably have more space left if you used the default value.

    For example, as a root user:

    mkdir/U01

    MV/home/oracle/oraInventory/U01

    Update /etc/oraInst.loc and replace

    inventory_loc = / home/oracle/oraInventory

    with

    inventory_loc = / u01/oraInventory

Maybe you are looking for