Check corruption using RMAN

Hi,
We take cold database backup daily using tivoli. It's just like OS copy of database files when database is down. Can we check this backup for logical and physical corruption using RMAN?
Database Version: 10.2.0.2 on AIX 5.3
Thanks in advance,
Edited by: santi on May 1, 2010 6:14 AM

dbv -help
DBVERIFY: Release 10.2.0.1.0 - Production on Sat May 1 07:48:41 2010
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
Keyword     Description                    (Default)
FILE        File to Verify                 (NONE)
START       Start Block                    (First Block of File)
END         End Block                      (Last Block of File)
BLOCKSIZE   Logical Block Size             (8192)
LOGFILE     Output Log                     (NONE)
FEEDBACK    Display Progress               (0)
PARFILE     Parameter File                 (NONE)
USERID      Username/Password              (NONE)
SEGMENT_ID  Segment ID (tsn.relfile.block) (NONE)
HIGH_SCN    Highest Block SCN To Verify    (NONE)
            (scn_wrap.scn_base OR scn)           dbv can be run against datafiles while DB is up & online or while DB is down

Similar Messages

  • How to overcome Block corruption using RMAN

    Hi All,
    How to overcome bolck corruption using RMAN. What is the procedure to do so.
    Thanks & Regards
    J.Venugopal

    Hi all,
    I´ve performed the following command on RMAN:
    RMAN> BACKUP VALIDATE CHECK LOGICAL DATABASE ARCHIVELOG ALL;After, I query the V$DATABASE_BLOCK_CORRUPTION table, and the below records
    was returned:
         FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
            67       4670          1         1202832866 LOGICAL
            68     154131        338         1175601952 LOGICAL
            68     155329         60         1174783128 LOGICAL
            68     155409         60         1174783132 LOGICAL
            68     155471         78         1174783135 LOGICAL
            68     155551         78         1174783139 LOGICAL
            68     155631         18         1174783143 LOGICAL
            68     155651         18         1174783144 LOGICAL
            68     155671         18         1174783145 LOGICAL
            68     155691         18         1174783146 LOGICAL
            68     155711         18         1174783147 LOGICAL
            68     155731         18         1174783148 LOGICAL
            68     155751         18         1174783149 LOGICAL
            68     155771         78         1174783150 LOGICAL
            68     155851         78         1174783154 LOGICAL
            68     155931         49         1174783158 LOGICAL
            73     165758          1         1180191676 LOGICALSo, when I try to recover these blocks by using blockrecover command, I got the error:
    RMAN> blockrecover corruption list;
    Starting blockrecover at 27-SEP-07
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of blockrecover command at 09/27/2007 10:22:10
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 73 found to restore
    RMAN-06023: no backup or copy of datafile 68 found to restore
    RMAN-06023: no backup or copy of datafile 67 found to restoreWhat can I do in this case?
    Thank U very much!
    []´s

  • Error in Database backup using RMAN.

    Hi
    While taking full online backup using RMAN i got the following error.
    ORA-19566: exceeded limit of 0 corrupt blocks for file /oracle/DEV/sapdata2/dev640_6/dev640.data6
    Please help me how to resolve this issue.

    Hi,
    Please perform DBverify Job and Also analyze the alert<SID>.log file for your Database to get more information about such logical or physical corruption.  You may require Block level recovery for the complained DB Files. Please refer this useful document " [Early Detection and Correction of Data Block Corruptions Using RMAN |http://www.ioug.org/client_files/members/select_pdf/04q4/RMAN.pdf]" and share the same with your Oracle DBA.
    You can execute the following commands to get information about corrupted block(s), if its there.
    select * from v$backup_corruption;
    select * from v$database_block_corruption;
    Regads,
    Bhavik G. Shroff

  • Recover Block level corruption without using Rman

    Dear All,
    OS - OEL
    DB - Oracle 10G
    ORA-01578: ORACLE data block corrupted (file # 11, block # 16325)
    ORA-01110: data file 11: '/oracle/PROD/fin_dev/data/fin08.dbf'
    How we will recover it without using Rman?

    If you are not using RMAN, you are using scripted backups.  You take the datafile (or tablespace) offline, restore the backup of the datafile and recover the datafile using the SQLPlus commands.
    Hemant K Chitale

  • Database restore  from a particular backup set using rman

    Hi all,
    My OS: UNIX
    DB : 10.2.0.1
    As i checked the database it will indicate datafile 5 is header corruption.
    yesterday i take complete online backup of the database using RMAN but now when i run restore database command it will show as
    ORA-19870: error reading backup piece /cms/BACKUP/ora_BSCS_set149_piece1_20111206_4lmth1qj_1_1
    ORA-19573: cannot obtain exclusive enqueue for datafile 6
    Database is open and datafile is physically present there
    So can anyone tell what to do next
    Edited by: Vikas Kohli on Dec 9, 2011 9:58 AM

    here are the result for the same:
    Starting restore at 09-DEC-11
    using channel ORA_DISK_1
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    147 Incr 0 1.10G DISK 00:14:10 06-DEC-11
    BP Key: 147 Status: AVAILABLE Compressed: YES Tag: TAG20111206T085858
    Piece Name: /cms/BACKUP/ora_BSCS_set149_piece1_20111206_4lmth1qj_1_1
    List of Datafiles in backup set 147
    File LV Type Ckp SCN Ckp Time Name
    1 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/system01.dbf
    2 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/undotbs01.dbf
    3 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/sysaux01.dbf
    4 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/users01.dbf
    5 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/DATA.dbf
    6 0 Incr 9068988016235 06-DEC-11 /u01/app/oracle/oradata/BSCS/users02.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    149 Incr 1 11.49M DISK 00:00:07 07-DEC-11
    BP Key: 149 Status: AVAILABLE Compressed: YES Tag: TAG20111207T082737
    Piece Name: /cms/BACKUP/ora_BSCS_set151_piece1_20111207_4nmtjkbr_1_1
    List of Datafiles in backup set 149
    File LV Type Ckp SCN Ckp Time Name
    1 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/system01.dbf
    2 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/undotbs01.dbf
    3 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/sysaux01.dbf
    4 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/users01.dbf
    5 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/DATA.dbf
    6 1 Incr 9068988069143 07-DEC-11 /u01/app/oracle/oradata/BSCS/users02.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    151 Incr 1 115.07M DISK 00:01:24 08-DEC-11
    BP Key: 151 Status: AVAILABLE Compressed: YES Tag: TAG20111208T075327
    Piece Name: /cms/BACKUP/ora_BSCS_set153_piece1_20111208_4pmtm6nn_1_1
    List of Datafiles in backup set 151
    File LV Type Ckp SCN Ckp Time Name
    1 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/system01.dbf
    2 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/undotbs01.dbf
    3 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/sysaux01.dbf
    4 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/users01.dbf
    5 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/DATA.dbf
    6 1 Incr 9068988123314 08-DEC-11 /u01/app/oracle/oradata/BSCS/users02.dbf
    no backup of log thread 1 seq 411 lowscn 9068988025356 found to restore
    no backup of log thread 1 seq 412 lowscn 9068988167985 found to restore
    no backup of log thread 1 seq 413 lowscn 9068988203392 found to restore
    List of Archived Log Copies
    Key Thrd Seq S Low Time Name
    263 1 3 A 05-DEC-11 /u01/app/oracle/admin/BSCS/arch/BSCS/1_3_769127125.dbf
    273 1 13 A 07-DEC-11 /u01/app/oracle/admin/BSCS/arch/BSCS/1_13_769127125.dbf
    Media recovery start SCN is 9068988123314
    Recovery must be done beyond SCN 9068988123314 to clear data files fuzziness
    Finished restore at 09-DEC-11

  • PERFORMING A TEST BACKUP (VALIDATE BACKUP) USING RMAN

    제품 : RMAN
    작성날짜 : 2002-05-30
    PERFORMING A TEST BACKUP (VALIDATE BACKUP) USING RMAN
    =====================================================
    PURPOSE
    RMAN을 이용하여 Test Backup을 수행하기 위한 정보를 제공한다.
    EXPLANATION
    8.1.7 부터 RMAN에서 BACKUP command에 VALIDATE keyword를 사용할 수 있게 되었다
    이 명령의 수행은 다음과 같은 작업을 수행한다.
    - Datafile의 physical and logical corruption을 check한다.
    - 모든 database file들이 존재하는지, 그리고 올바른 위치에 있는지를 검증한다.
    RMAN은 실제적으로 backupset을 생성하지 않는다 그러나 그것들이 backup될 수
    있는지 없는지를 결정하기 위해서 기술된 file들을 scan한다.
    BACKUP VALIDATE 는 backup job을 수행시 수행되는 것을 제외하고는
    RESTORE VALIDATE와 거의 비슷하다.
    EXAMPLE
    아래와 같은 command들을 수행하여 backup하고자 하는 database file과 archived redo
    log들이 실제로 backup될 수 있는지를 검증할 수 있다.
    RUN {
    ALLOCATE CHANNEL ch1 TYPE 'sbt_tape';
    BACKUP VALIDATE
    DATABASE
    ARCHIVELOG ALL;
    Note: MAXCORRUPT or PROXY parameter는 VALIDATE option과 함께 사용할 수 없다.
    REFERENCE DOCUMENTS
    NOTE:121109.1

    Clint,
    I ran the command lines you wrote me after i placed the database in Startup MOUNT state, RMAN gave error messages that the database needs to be open:
    RMAN> SQL 'ALTER TABLESPACE USERTB2 OFFLINE IMMEDIATE';
    sql statement: ALTER TABLESPACE USERTB2 OFFLINE IMMEDIATE
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 11/04/2005 15:31:33
    RMAN-11003: failure during parse/execution of SQL statement: ALTER TABLESPACE US
    ERTB2 OFFLINE IMMEDIATE
    ORA-01109: database not open
    Then I ran the same command lines after I opened the database, RMAN gave error messages that "offline immediate disallowed unless media recovery enabled":
    RMAN> SQL 'ALTER TABLESPACE USERTBS2 OFFLINE IMMEDIATE';
    sql statement: ALTER TABLESPACE USERTBS2 OFFLINE IMMEDIATE
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 11/04/2005 15:48:17
    RMAN-11003: failure during parse/execution of SQL statement: ALTER TABLESPACE US
    ERTBS2 OFFLINE IMMEDIATE
    ORA-01145: offline immediate disallowed unless media recovery enabled
    I am stuck again and need your help!
    Thank you,
    Mitra

  • Updating standby database from primary using rman

    I have created a standby database using rman on my oracle linux server, now i want to update the standby from my primary database, but i didn't remember the scn which i used for creating the standby. How can i find out the scn from where i should perform the incremental backup on the primary, so that i can update my standby database with the latest information.

    You simply need to find out which logs on the Primary have yet to be applied to your Standby. Have a look at this (or any Oracle Data Guard docs.): http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/manage_ps.htm#1024046
    As long as the logs are available on the Primary server, then they should be sent across to the Standby server. Use the views described in the above link to check for any gaps, etc.

  • Creation of Logical Standby Database Using RMAN ACTIVE DATABASE COMMAND

    Hi All,
    I am in confusion how to create logical standby database from primary database using rman active database command.
    What i did:-
    Create primary database on machine 1 on RHEL 5 with Oracle 11gR2
    Create standby database on machine 2 on RHEL 5 With Oracle 11gR2 from primary using RMAN active database command
    Trying to create logical standby database on machine 3 on RHEL 5 with Oracle 11gR2 using RMAN active database command from primary.
    The point which confuse me is to start the logical standby in nomount mode on machine 3 with which pfile like i create the pfile for standby database do i need to create the pfile for logical standby db.
    I done the creation of logical standby database by converting physical standby to logical standby database
    I am following the below mentioned doc for the same:
    Creating a physical and a logical standby database in a DR environment | Chen Guang&amp;#039;s Blog
    Kindly guide me how to work over the same or please provide me the steps of the same.
    Thanks in advance.

    Thanks for your reply
    I already started the logical standby database with pfile in nomount mode. And successfully completed the duplication of database. by mentioning the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameter.
    But i am not able to receive the logs on the above mentioned blog i run the sql command to check the logs but getting "no rows selected"
    My primary database pfile is:
    pc01prmy.__db_cache_size=83886080
    pc01prmy.__java_pool_size=12582912
    pc01prmy.__large_pool_size=4194304
    pc01prmy.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    pc01prmy.__pga_aggregate_target=79691776
    pc01prmy.__sga_target=239075328
    pc01prmy.__shared_io_pool_size=0
    pc01prmy.__shared_pool_size=134217728
    pc01prmy.__streams_pool_size=0
    *.audit_file_dest='/u01/app/oracle/admin/pc01prmy/adump'
    *.audit_trail='db'
    *.compatible='11.1.0.0.0'
    *.control_files='/u01/app/oracle/oradata/PC01PRMY/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01PRMY/controlfile/o1_mf_91g3mf6v_.ctl'
    *.db_block_size=8192
    *.db_create_file_dest='/u01/app/oracle/oradata'
    *.db_domain=''
    *.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
    *.db_name='pc01prmy'
    *.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.diagnostic_dest='/u01/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
    *.fal_client='PC01PRMY'
    *.fal_server='PC01SBY'
    *.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
    *.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
    *.log_archive_dest_2='SERVICE=pc01sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pc01sby'
    *.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='DEFER'
    *.log_archive_dest_state_3='DEFER'
    *.log_archive_max_processes=30
    *.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
    *.open_cursors=300
    *.pga_aggregate_target=78643200
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=236978176
    *.undo_tablespace='UNDOTBS1'
    My logical standby pfile is:-
    pc01ls.__db_cache_size=92274688
    pc01ls.__java_pool_size=12582912
    pc01ls.__large_pool_size=4194304
    pc01ls.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    pc01ls.__pga_aggregate_target=79691776
    pc01ls.__sga_target=239075328
    pc01ls.__shared_io_pool_size=0
    pc01ls.__shared_pool_size=125829120
    pc01ls.__streams_pool_size=0
    *.audit_file_dest='/u01/app/oracle/admin/pc01ls/adump'
    *.audit_trail='db'
    *.compatible='11.1.0.0.0'
    *.control_files='/u01/app/oracle/oradata/PC01LS/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01LS/controlfile/o1_mf_91g3mf6v_.ctl'
    *.db_block_size=8192
    *.db_create_file_dest='/u01/app/oracle/oradata'
    *.db_domain=''
    *.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
    *.db_name='pc01prmy'
    *.db_unique_name='pc01ls'
    *.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.diagnostic_dest='/u01/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
    *.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
    *.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
    *.log_archive_dest_2='LOCATION=/u01/app/oracle/flash_recovery_area/PC01LS/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=pc01ls'
    *.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
    *.open_cursors=300
    *.pga_aggregate_target=78643200
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=236978176
    *.undo_tablespace='UNDOTBS1'
    Kindly advice over the same

  • Oracle 9i TEMP tablespace backup problem using RMAN!

    Oracle8/8i whole backup is ok for our backup software(using RMAN without RC database), but for Oracle 9i, I get following error messages when backing up temp tablespace.
    1. RMAN-20202: tablespace not found in the recovery catalog
    2. RMAN-06019: could not translate tablespace name "TEMP"
    I check some views of Oracle9i, and know some changes happen for temp tablespace in 9i, but how to deal with this problem. Any idea, please!

    In 9i RMAN does not restore temporary datafiles. Instead, you should create them after your restore. I believe that Oracle is going to make a change to this in the next release of 9i and have RMAN create the temporary files. You can view the temporary datafiles @ v$tempfile.
    I believe RMAN doesn't restore temporary files because they are locally managed and not in the control files. RMAN reads the controlfile of the target database to obtain info about backups, datafiles, etc.
    Hope this helps.

  • Cold backup downtime using RMAN

    Over the weekend I performed a cold RMAN backup on a 3.6 TB
    database. Because a lot of the database was backed up with
    transportable tablespaces, the net amount being backed up was
    approximately 365 Gb. I took down the database at 11:00 and the
    script finished at 4am, but in reviewing the logs, the database
    actually appears to have been opened at 2am.
    I assumed that the database would be down the entirety of the
    backup. Can anyone help me understand why the database was
    opened so long before the RMAN command completed? Was the
    backup adversely affected in any way by a user obtaining access
    prior to the RMAN process completing.
    Any information greatly appreciated.

    unfortunately i think you misunderstood the original question. i took the database down to do the cold backup. in order to use rman, you have to startup nomount the instance.
    the script run was:
    #!/usr/bin/ksh
    rman msglog '/data2/oracle2/local/log/rman_lvl0.log' <<EOF
    @connect.rman
    run {
    backup incremental level 0 tag full_bkup0 database diskratio=0;
    alter database open;
    exit;
    EOF
    exit
    the "alter database open" tells RMAN to open the database once the backup is completed. i had a process running that checked each 10 seconds to see if the PID for the RMAN process was still running. The process itself appears to have run for an additional 2 hours after the database was opened.
    there is nothing on the system to suggest that the database was opened by anything other than RMAN. was the database opened prematurely? was the additional time spent in the RMAN script doing the sync in the database? did the usage by the user prior to RMAN completing invalidate the backup? (so far the cloning is still running without error).

  • Create new database using rman cold backup

    It oracle 10g database version 10.2.0.4
    I took the cold backup of the database using rman ( Database name TEST)
    1.RMAN> startup mount;
    2.RMAN> backup database include current controlfile;
    3.RMAN> alter database open;
    I aim to create the new database called DEMO using this backup
    Please let know the setps for creating new database
    Edited by: prajeevan on Jan 19, 2011 9:09 PM

    I took the cold backup of the database using rman ( Database name TEST)
    1.RMAN> startup mount;
    2.RMAN> backup database include current controlfile;
    3.RMAN> alter database open;
    I aim to create the new database called DEMO using this backup
    Please let know the setps for creating new databaseIf it is in archivelog mode you can use duplicate to refresh database DEMO from TEST..
    or after cold backup, go to mount ,
    create trace file of controlfile becuase you are chaning database name
    recreate the controlfile
    open database in resetlogs;
    check also http://blogs.oracle.com/AlejandroVargas/gems/RMANDUPDBPRACTICE.pdf

  • Script for cold backup using RMAN

    Dear all,
    db_version:-10.2.0.4
    os_version:- Windows 2003 server
    I wish to schedule a script that will take cold backup of my database using RMAN.
    Any help is appreciated ..
    Edited by: user12000301 on May 18, 2011 5:02 AM

    Dear All,
    Thanks a lot for your valuable time :
    However i have managed to do it as follows :
    1. First i have configure the parameter of RMAN ( Since it is my UAT in Noarchive log mode), I have never tried RMAN cold backup on the same.
    Following is the out put of SHOW ALL;
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'D:\DB\RMAN_BKP\BACKUPS%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\DB\RMAN_BKP\BACKUPS\DB_%U.%r';
    CONFIGURE MAXSETSIZE TO UNLIMITED;
    CONFIGURE ENCRYPTION FOR DATABASE OFF;
    CONFIGURE ENCRYPTION ALGORITHM 'AES128';
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\DB\RMAN_BKP\BACKUPS\SNCFDB.ORA';
    2. I have created a rman_cold_bkp.bat file which has following entry :
    cd c:\oracle10g\bin
    set oracle_sid=DB
    rman target system/*** @D:\DB\RMAN_BKP\SCRIPT\rman_cold_bkp.rcv log=D:\DB\RMAN_BKP\SCRIPT\rman_cold_bkp.log
    exit
    3. Whereas rman_cold_bkp.rcv file contains following contents:
    run
    allocate channel C1 device type disk;
    shutdown immediate;
    startup mount;
    backup database;
    alter database open;
    release channel C1;
    exit
    I did checked it and it;s working fine for me :-)
    Regards,
    Girish

  • How to backup Oracle Database Single Instance using RMAN

    Folks,
    Hello. I am using Oracle Database Server 11gR1 with Operating System Oracle Linux 5.10.
    I understand how to backup database instance in SQL Server with Windows. But don't really understand how to backup database instance in Oracle with Linux.
    I have done Cold backup and Hot backup for the database instance HRCS90 but both get the same error message.
    Cold backup is below:
    SQL> startup
    ORACLE instance started.
    Total System Global Area  538677248 bytes
    Fixed Size                  2146024 bytes
    Variable Size             528482584 bytes
    Database Buffers            4194304 bytes
    Redo Buffers                3854336 bytes
    Database mounted.
    Database opened.
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    RMAN> backup database;
    Starting backup at 25-NOV-13
    using target database control file instead of recovery catalog
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 11/25/2013 14:26:52
    RMAN-06171: not connected to target database
    RMAN> backup HRCS90
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "identifier": expecting one of: "archivelog, auxiliary, as, backup, backupset, blocks, channel, check, copy, copies, controlfilecopy, cumulative, current, database, datafile, datafilecopy, device, diskratio, db_recovery_file_dest, db_file_name_convert, duration, filesperset, for, format, from, full, force, file, incremental, keep, (, maxsetsize, nochecksum, noexclude, nokeep, not, proxy, pool, reuse, recovery, section, skip, spfile, skip readonly, setsize, tablespace, tag, to, validate"
    RMAN-01008: the bad identifier was: HRCS90
    RMAN-01007: at line 1 column 8 file: standard input
    RMAN> backup database HRCS90
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "identifier": expecting one of: "archivelog, auxiliary, backup, backupset, channel, copy, controlfilecopy, current, database, datafile, datafilecopy, delete, diskratio, db_recovery_file_dest, filesperset, format, from, force, file, include, keep, (, maxsetsize, noexclude, nokeep, not, pool, plus, reuse, recovery, section, ;, skip, spfile, skip readonly, setsize, tablespace, tag, to"
    RMAN-01008: the bad identifier was: HRCS90
    RMAN-01007: at line 1 column 17 file: standard input
    While the database instance HRCS90 is startup, I do hot backup using the same commands and get the same error message with above cold backup.
    My question is:
    Can any folk tell me the specific steps (command by command) to backup a single database instance in Oracle using RMAN ?
    Thanks.

    Folks,
    Hello. Thanks a lot for replying. My database instance named HRCS90 is going to be backed up. My backup directory is /backup_Database_Instance_HRCS90.
    If database in open state, we must back up in archive log. If database in mount state but not open, we can back up in noarchive log.
    I have tried to back up HRCS90 in archive and noarchive log when database in mount state but not open as below:
    SQL>startup mount;
    SQL>exit
    [user@linux bin]$./rman
    RMAN>connect target;
    RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup_Database_Instance_HRCS90/full_%u_%s_%p';
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backup_Database_Instance_HRCS90/full_%u_%s_%p';
    new RMAN configuration parameters are successfully stored
    released channel: ORA_DISK_1
    RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 360 DAYS;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 360 DAYS;
    new RMAN configuration parameters are successfully stored
    RMAN> backup as backupset database plus archivelog;
    Starting backup at 01-DEC-13
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=44 device type=DISK
    specification does not match any archived log in the recovery catalog
    backup cancelled because all files were skipped
    Finished backup at 01-DEC-13
    Starting backup at 01-DEC-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/oradata/HRCS90/system01.dbf
    input datafile file number=00090 name=/u01/oradata/HRCS90/psimage.dbf
    input datafile file number=00060 name=/u01/oradata/HRCS90/gpapp.dbf
    input datafile file number=00119 name=/u01/oradata/HRCS90/tlwork.dbf
    input datafile file number=00102 name=/u01/oradata/HRCS90/pttlrg.dbf
    input datafile file number=00054 name=/u01/oradata/HRCS90/faapp.dbf
    input datafile file number=00110 name=/u01/oradata/HRCS90/saapp.dbf
    input datafile file number=00101 name=/u01/oradata/HRCS90/pttbl.dbf
    input datafile file number=00002 name=/u01/oradata/HRCS90/sysaux01.dbf
    input datafile file number=00106 name=/u01/oradata/HRCS90/py0lrg.dbf
    input datafile file number=00004 name=/u01/oradata/HRCS90/psdefault.dbf
    input datafile file number=00117 name=/u01/oradata/HRCS90/tlapp.dbf
    input datafile file number=00007 name=/u01/oradata/HRCS90/adapp.dbf
    input datafile file number=00082 name=/u01/oradata/HRCS90/paapp.dbf
    input datafile file number=00074 name=/u01/oradata/HRCS90/hrsapp.dbf
    input datafile file number=00092 name=/u01/oradata/HRCS90/ptamsg.dbf
    input datafile file number=00056 name=/u01/oradata/HRCS90/fgapp.dbf
    input datafile file number=00114 name=/u01/oradata/HRCS90/stapp.dbf
    input datafile file number=00005 name=/u01/oradata/HRCS90/aaapp.dbf
    input datafile file number=00118 name=/u01/oradata/HRCS90/tllarge.dbf
    input datafile file number=00009 name=/u01/oradata/HRCS90/avapp.dbf
    input datafile file number=00065 name=/u01/oradata/HRCS90/hrapp2.dbf
    input datafile file number=00078 name=/u01/oradata/HRCS90/hrwork.dbf
    input datafile file number=00116 name=/u01/oradata/HRCS90/stwork.dbf
    input datafile file number=00077 name=/u01/oradata/HRCS90/hrswork.dbf
    input datafile file number=00115 name=/u01/oradata/HRCS90/stlarge.dbf
    input datafile file number=00049 name=/u01/oradata/HRCS90/epapp.dbf
    input datafile file number=00098 name=/u01/oradata/HRCS90/ptprc.dbf
    input datafile file number=00037 name=/u01/oradata/HRCS90/eoewapp.dbf
    input datafile file number=00032 name=/u01/oradata/HRCS90/eoecapp.dbf
    input datafile file number=00086 name=/u01/oradata/HRCS90/piapp.dbf
    input datafile file number=00099 name=/u01/oradata/HRCS90/ptprjwk.dbf
    input datafile file number=00019 name=/u01/oradata/HRCS90/cularge.dbf
    input datafile file number=00035 name=/u01/oradata/HRCS90/eoeiapp.dbf
    input datafile file number=00045 name=/u01/oradata/HRCS90/eoppapp.dbf
    input datafile file number=00076 name=/u01/oradata/HRCS90/hrslarge.dbf
    input datafile file number=00044 name=/u01/oradata/HRCS90/eoltapp.dbf
    input datafile file number=00094 name=/u01/oradata/HRCS90/ptappe.dbf
    input datafile file number=00050 name=/u01/oradata/HRCS90/eplarge.dbf
    input datafile file number=00084 name=/u01/oradata/HRCS90/pcapp.dbf
    input datafile file number=00111 name=/u01/oradata/HRCS90/sacapp.dbf
    input datafile file number=00100 name=/u01/oradata/HRCS90/ptrpts.dbf
    input datafile file number=00023 name=/u01/oradata/HRCS90/eobfapp.dbf
    input datafile file number=00096 name=/u01/oradata/HRCS90/ptcmstar.dbf
    input datafile file number=00108 name=/u01/oradata/HRCS90/pylarge.dbf
    input datafile file number=00016 name=/u01/oradata/HRCS90/cularg1.dbf
    input datafile file number=00018 name=/u01/oradata/HRCS90/cularg3.dbf
    input datafile file number=00025 name=/u01/oradata/HRCS90/eocmapp.dbf
    input datafile file number=00027 name=/u01/oradata/HRCS90/eocmwrk.dbf
    input datafile file number=00029 name=/u01/oradata/HRCS90/eoculrg.dbf
    input datafile file number=00033 name=/u01/oradata/HRCS90/eoeclrg.dbf
    input datafile file number=00036 name=/u01/oradata/HRCS90/eoeilrg.dbf
    input datafile file number=00039 name=/u01/oradata/HRCS90/eoewwrk.dbf
    input datafile file number=00041 name=/u01/oradata/HRCS90/eoiulrg.dbf
    input datafile file number=00046 name=/u01/oradata/HRCS90/eopplrg.dbf
    input datafile file number=00048 name=/u01/oradata/HRCS90/eotplrg.dbf
    input datafile file number=00053 name=/u01/oradata/HRCS90/erwork.dbf
    input datafile file number=00061 name=/u01/oradata/HRCS90/gpdeapp.dbf
    input datafile file number=00072 name=/u01/oradata/HRCS90/hrlarg1.dbf
    input datafile file number=00079 name=/u01/oradata/HRCS90/htapp.dbf
    input datafile file number=00087 name=/u01/oradata/HRCS90/pilarge.dbf
    input datafile file number=00120 name=/u01/oradata/HRCS90/waapp.dbf
    channel ORA_DISK_1: starting piece 1 at 01-DEC-13
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup plus archivelog command at 12/01/2013 17:52:45
    ORA-19504: failed to create file "/backup_Database_Instance_HRCS90/full_0boqei2c_11_1"
    ORA-27040: file create error, unable to create file
    Linux-x86_64 Error: 13: Permission denied
    RMAN>
    RMAN>
    RMAN>
    RMAN>
    RMAN> backup as backupset database;
    Starting backup at 01-DEC-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/oradata/HRCS90/system01.dbf
    input datafile file number=00090 name=/u01/oradata/HRCS90/psimage.dbf
    input datafile file number=00060 name=/u01/oradata/HRCS90/gpapp.dbf
    input datafile file number=00119 name=/u01/oradata/HRCS90/tlwork.dbf
    input datafile file number=00102 name=/u01/oradata/HRCS90/pttlrg.dbf
    input datafile file number=00054 name=/u01/oradata/HRCS90/faapp.dbf
    input datafile file number=00110 name=/u01/oradata/HRCS90/saapp.dbf
    input datafile file number=00101 name=/u01/oradata/HRCS90/pttbl.dbf
    input datafile file number=00002 name=/u01/oradata/HRCS90/sysaux01.dbf
    input datafile file number=00106 name=/u01/oradata/HRCS90/py0lrg.dbf
    input datafile file number=00004 name=/u01/oradata/HRCS90/psdefault.dbf
    input datafile file number=00117 name=/u01/oradata/HRCS90/tlapp.dbf
    input datafile file number=00007 name=/u01/oradata/HRCS90/adapp.dbf
    input datafile file number=00082 name=/u01/oradata/HRCS90/paapp.dbf
    input datafile file number=00074 name=/u01/oradata/HRCS90/hrsapp.dbf
    input datafile file number=00092 name=/u01/oradata/HRCS90/ptamsg.dbf
    input datafile file number=00056 name=/u01/oradata/HRCS90/fgapp.dbf
    input datafile file number=00114 name=/u01/oradata/HRCS90/stapp.dbf
    input datafile file number=00005 name=/u01/oradata/HRCS90/aaapp.dbf
    input datafile file number=00118 name=/u01/oradata/HRCS90/tllarge.dbf
    input datafile file number=00009 name=/u01/oradata/HRCS90/avapp.dbf
    input datafile file number=00065 name=/u01/oradata/HRCS90/hrapp2.dbf
    input datafile file number=00078 name=/u01/oradata/HRCS90/hrwork.dbf
    input datafile file number=00116 name=/u01/oradata/HRCS90/stwork.dbf
    input datafile file number=00077 name=/u01/oradata/HRCS90/hrswork.dbf
    input datafile file number=00115 name=/u01/oradata/HRCS90/stlarge.dbf
    input datafile file number=00049 name=/u01/oradata/HRCS90/epapp.dbf
    input datafile file number=00098 name=/u01/oradata/HRCS90/ptprc.dbf
    input datafile file number=00037 name=/u01/oradata/HRCS90/eoewapp.dbf
    input datafile file number=00032 name=/u01/oradata/HRCS90/eoecapp.dbf
    input datafile file number=00086 name=/u01/oradata/HRCS90/piapp.dbf
    input datafile file number=00099 name=/u01/oradata/HRCS90/ptprjwk.dbf
    input datafile file number=00019 name=/u01/oradata/HRCS90/cularge.dbf
    input datafile file number=00035 name=/u01/oradata/HRCS90/eoeiapp.dbf
    input datafile file number=00045 name=/u01/oradata/HRCS90/eoppapp.dbf
    input datafile file number=00076 name=/u01/oradata/HRCS90/hrslarge.dbf
    input datafile file number=00044 name=/u01/oradata/HRCS90/eoltapp.dbf
    input datafile file number=00094 name=/u01/oradata/HRCS90/ptappe.dbf
    input datafile file number=00050 name=/u01/oradata/HRCS90/eplarge.dbf
    input datafile file number=00084 name=/u01/oradata/HRCS90/pcapp.dbf
    input datafile file number=00111 name=/u01/oradata/HRCS90/sacapp.dbf
    input datafile file number=00100 name=/u01/oradata/HRCS90/ptrpts.dbf
    input datafile file number=00023 name=/u01/oradata/HRCS90/eobfapp.dbf
    input datafile file number=00096 name=/u01/oradata/HRCS90/ptcmstar.dbf
    input datafile file number=00108 name=/u01/oradata/HRCS90/pylarge.dbf
    input datafile file number=00016 name=/u01/oradata/HRCS90/cularg1.dbf
    input datafile file number=00018 name=/u01/oradata/HRCS90/cularg3.dbf
    input datafile file number=00025 name=/u01/oradata/HRCS90/eocmapp.dbf
    input datafile file number=00027 name=/u01/oradata/HRCS90/eocmwrk.dbf
    input datafile file number=00029 name=/u01/oradata/HRCS90/eoculrg.dbf
    input datafile file number=00033 name=/u01/oradata/HRCS90/eoeclrg.dbf
    input datafile file number=00036 name=/u01/oradata/HRCS90/eoeilrg.dbf
    input datafile file number=00039 name=/u01/oradata/HRCS90/eoewwrk.dbf
    input datafile file number=00041 name=/u01/oradata/HRCS90/eoiulrg.dbf
    input datafile file number=00046 name=/u01/oradata/HRCS90/eopplrg.dbf
    input datafile file number=00048 name=/u01/oradata/HRCS90/eotplrg.dbf
    input datafile file number=00053 name=/u01/oradata/HRCS90/erwork.dbf
    input datafile file number=00061 name=/u01/oradata/HRCS90/gpdeapp.dbf
    input datafile file number=00072 name=/u01/oradata/HRCS90/hrlarg1.dbf
    input datafile file number=00079 name=/u01/oradata/HRCS90/htapp.dbf
    input datafile file number=00087 name=/u01/oradata/HRCS90/pilarge.dbf
    input datafile file number=00120 name=/u01/oradata/HRCS90/waapp.dbf
    channel ORA_DISK_1: starting piece 1 at 01-DEC-13
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/01/2013 17:56:51
    ORA-19504: failed to create file "/backup_Database_Instance_HRCS90/full_0coqeia5_12_1"
    ORA-27040: file create error, unable to create file
    Linux-x86_64 Error: 13: Permission denied
    As we see the above last 2 commands, either archive or noarchive, I get the same error:
    Archive: ORA-19504: "failed to create file /backup_Database_Instance_HRCS90/full_0boqei2c_11_1"
    Noarchive: ORA-19504: "failed to create file /backup_Database_Instance_HRCS90/full_0coqeia5_12_1" 
    My question is:
    What is the file "full_0boqei2c_11_1" or "full_0coqeia5_12_1" ?  How to solve the above error ?
    Thanks.

  • Can I use RMAN transportable database cross platform from 10g to 11g?

    Hi,
    I'm working on the migration plan, the source db server is solaris with 10g database while the destination server is AIX with 11g database.
    Can I use RMAN transportable database for this purpose?
    Coz I have read the restrictions on Cross-Platform Transportable Database, but it does not mention whether it can work for different version of database.
    please help.

    Hi,
    Do you have metalink account? If yes please check : Cross-Platform Migration on Destination Host Using Rman Convert Database [ID 414878.1]*
    RMAN Cross-Platform Transportable Databases and Tablespaces
    Thank you

  • Backup archive logs problem using RMAN

    Hi guys
    I got failure when using RMAN to backup archive log files:
    Starting backup at 20-APR-06
    current log archived
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 04/20/2006 21:53:57
    RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
    ORA-19625: error identifying file /opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_17/o1_mf_1_1_21p5c251_.arc
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    RMAN> **end-of-file**
    My archive log files location:
    SQL> show parameter log_archive_dest
    NAME TYPE VALUE
    log_archive_dest_1 string LOCATION=/opt/oracle/oradata/DB10G/arch/
    Current archive log files:
    $ ls /opt/oracle/oradata/DB10G/arch
    1_17_586191737.dbf 1_21_586191737.dbf 1_25_586191737.dbf 1_29_586191737.dbf 1_33_586191737.dbf
    1_18_586191737.dbf 1_22_586191737.dbf 1_26_586191737.dbf 1_30_586191737.dbf 1_34_586191737.dbf
    1_19_586191737.dbf 1_23_586191737.dbf 1_27_586191737.dbf 1_31_586191737.dbf 1_35_586191737.dbf
    1_20_586191737.dbf 1_24_586191737.dbf 1_28_586191737.dbf 1_32_586191737.dbf afiedt.buf
    $
    But when I check v$archived_log:
    SQL> select name,status,deleted from v$archived_log;
    NAME S DEL
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    D YES
    /opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_17/ A NO
    /opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_18/ A NO
    /opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_19/ A NO
    /opt/oracle/oradata/DB10G/redo01.log A NO
    /opt/oracle/oradata/DB10G/redo02.log A NO
    /opt/oracle/oradata/DB10G/redo03.log A NO
    /opt/oracle/oradata/DB10G/arch/1_5_585926175.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_6_585926175.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_7_585926175.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_1_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_2_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_3_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_4_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_5_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_6_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_7_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_8_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_9_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_10_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_11_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_12_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_13_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_14_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_15_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_16_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_17_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_18_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_19_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_20_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_21_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_22_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_23_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_24_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_25_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_26_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_27_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_28_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_29_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_30_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_31_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_32_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_33_586191737.dbf A NO
    /opt/oracle/oradata/DB10G/arch/1_34_586191737.dbf A NO
    More records than actual archived logs. How could it happen? How to solve?
    THanks in advance.
    Sharon

    Hi,
    Use
    RMAN>crosscheck archivelog all; cmd

Maybe you are looking for

  • Team Foundation Server 2013 Refresh button not refreshing Custom Control values in TFS Templates

    Hi all, We have recently migrated from Team Foundation Server 2010 to Team Foundation Server 2013 Update 2. In TFS 2013 template design we found the refresh form control (inbuilt control of TFS) which is unable to refresh the custom control values th

  • Print Check box in smartform standard output

    Hi All, My requirement is to print a checkbox in the smartform output page. Somehow i came to know that in Web properties of the text node , we can choose a checkbox. But i am not able to figure out how it is to be implemented or what are the steps t

  • I'm "rebuilding" my raid -- do I need to "erase" my raid's hard drives

    As some of you know I've been having a weird problem with my raid. One of my drives is failing but for whatever reason I am unable to replace it and create a "hot spare" and then expanding it to re-create my raid.  There's some I am finishing my curr

  • VIDEO_TDR_FAILURE on GT60-OND , please help

    This started 4 days ago .Have formatted 3 times sense and used so many different drivers. Many drivers will fail to install . I am using 327.02 drivers right now after a fresh format and still BSOD .Any ideas out there or maybe this lappy is ready fo

  • TS3694 error 1645

    Hi im having trouble with the WIFI it will no longer connect to my wireless network at home which is working fine an another iPhone 4S and also an Ipad i just tried to restore to the factory settings and even tried restarting the phone nuimerous time