Restore Validate Database vs Backup Validate Database

Hi,
I want to add the following sentence after taking the backup using following command (backup as compressed backupset database plus archivelog;)
restore database validate;
or
backup validate database;
which one is best?

It depends on what you are trying to accomplish, as per documentation:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#sthref141BACKUP .. VALIDATE: Causes RMAN to scan the specified files and verify their contents, testing whether this file can be backed up. RMAN creates no output files. Use this command periodically to check for physical and logical errors in database files.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta051.htm#sthref796
RESTORE... VALIDATE causes RMAN to select existing backups that it would use to perform a RESTORE operation, and scan them all to ensure that they are present and free of corruption.>
Guessing what you're trying to do, I recommend:
backup check logical as compressed backupset database plus archivelog;
restore validate database;
CHECK LOGICAL. Tests data and index blocks that pass physical corruption checks for logical corruption, for example, corruption of a row piece or index entry. If RMAN finds logical corruption, then it logs the block in the alert.log and server session trace file. HTH
Enrique
PS If you have access to Metalink see Note:388422.1 Top 10 Backup and Recovery best practices.
Edited by: Enrique Orbegozo on Dec 17, 2008 4:21 PM

Similar Messages

  • Alter database begin backup; missing keyword error

    Hi all,
    I am trying to put my database in backup mode using the command "alter database begin backup", but it is giving error shown below:
    $ sqlplus '/as sysdba'
    SQL*Plus: Release 9.2.0.5.0 - Production on Wed Nov 25 16:52:58 2009
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Connected to:
    Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.5.0 - Production
    SQL> select name,open_mode from v$database;
    NAME OPEN_MODE
    N05PCS07 READ WRITE
    SQL> alter database begin backup;
    alter database begin backup
    ERROR at line 1:
    ORA-00905: missing keyword
    NE one can tell why the command is failing??
    pls...
    Thanks in advance.
    SHAILESH

    Hello,
    All the former posts are right, alter database begin backup; doesn't exists in 9.2 althought
    you already have in this release the alter database end backup;.
    So as to put all the tablespaces in backup mode in one command I suggest you to create a
    stored procedure as follows:
    CREATE OR REPLACE PROCEDURE begin_backup IS
    TYPE RefCurTyp IS REF CURSOR;
    cv RefCurTyp;
    sql_cv VARCHAR2(400);
    tbs VARCHAR2(128);
    sql_stmt VARCHAR2(200);
    BEGIN
    -- Mise en BEGIN BACKUP des TABLESPACES
    sql_cv := 'SELECT distinct (A.name) FROM sys.v_$tablespace A, sys.v_$datafile B, sys.v_$backup C where A.TS# = B.TS# and B.FILE# = C.FILE# and C.STATUS = ''NOT ACTIVE''';
    OPEN cv FOR sql_cv;
    LOOP
    FETCH cv INTO tbs;
    EXIT WHEN cv%NOTFOUND;
    sql_stmt := 'ALTER TABLESPACE '||tbs||' BEGIN BACKUP';
    EXECUTE IMMEDIATE sql_stmt;
    END LOOP;
    CLOSE cv;
    END;
    Then, I just have to call the Procedure like that:
    execute <schema>.begin_backup; and all the tablespaces are in backup mode.
    This procedure must be created on a User/Schema with the following privileges:
    alter tablespace
    select on sys.v_$tablespace
    select on sys.v_$datafile
    select on sys.v_$backupHope it can help.
    Best regards,
    Jean-Valentin
    Edited by: Lubiez Jean-Valentin on Nov 25, 2009 9:44 PM

  • Backup validate check logical database

    What is exactly the following RMAN command do? I want to know Is it doing a full backup or not?
    rman> backup validate check logical database' . Kindly help me.

    RMAN does not physically backup the database with this command. But it reads all blocks and checks for corruptions.
    If it finds corrupted blocks it will place the information about the corruption into a view:
    v$database_block_corruption;
    Now we can tell RMAN to recover all the blocks which it has found as being corrupt:
    RMAN> blockrecover corruption list; # (all blocks from v$database_block_corruption)
    Use below link for reference.
    http://luhartma.blogspot.com/2006/04/how-to-check-for-and-repair-block.html
    -Bharath

  • What are the commands using in SAP ECC 6.0 ehp on SYBASE Database? Backup and restore commands?

    Hi All,
    What are the commands using in SAP ECC 6.0 ehp on SYBASE Database? Backup and restore commands?

    Hi Jayachander,
    Have a look at these sap notes:
    For taking backup: Schedule from DB13 and get the exact command from Logs
    1841993 - SYB: How to schedule backups in DBA Cockpit
    1887068 - SYB: Using external backup and restore with SAP Sybase ASE
    How to restore DB
    1611715 - SYB: How to restore a Sybase ASE database server (Windows)
    Divyanshu

  • Restore RMAN from different Database Rman backup

    Hi Everybody
    I am practicing Rman so I have one query that how to restore rman backup from another database.
    For Example :
    1. I have Rman backup of DB1 with level 0 and level 1 cumulative database plus archievelog
    2. I need to import or restore Rman backup of DB1 to another database DB2.
    What is the procedure for doing the above queries. Please anyone one help me out.
    I have using oracle 10g r2 running in windows server 2003.
    Thanks in advance.

    These are the steps ; you need to write the appropiate commands for each step: Hope it helps!
    1) Take appropriate RMAN backup of the database db1. Note that you should turn on the CONTROLFILE AUTOBACKUP configuration so that we have the controlfile backed up after the database backup. When we restore the controlfile on new host from this autobackup piece, it will have the information of the latest backup.
    2) Create a PFILE for the destination database db2 using the database db1
    3) Move the backup pieces and the modified INIT.ORA file to the new host. Starting from 10g it is NO longer compulsory to copy the RMAN backup pieces to exactly the same location on the new host as the production location.
    4) Use the pfile created above to STARTUP NOMOUNT the database on the new host
    5) Now invoke RMAN and restore the controlfile specifying the location where the controlfile autobackup piece is restored on this new server. You can mount the database once the controlfile is restored successfully.
    6) You can skip this step if you have restored the RMAN backup pieces to exactly the same location they were backed up on database db1. If this is not the case then you need to catalog the RMAN backup pieces to make RMAN aware of thier new location on the new host. Note that CATALOG BACKUPPIECE command is available only starting from 10g.
    7) Having determined the point up to which media recovery should run, start the restore/recovery using for example:
    RMAN> run {
    2> set until sequence 59 thread 1;
    3> set newname for datafile 1 to '/new_location/system01.dbf';
    4> set newname for datafile 2 to '/new_location/undotbs01.dbf';
    5> set newname for datafile 3 to '/new_location/sysaux01.dbf';
    6> set newname for datafile 4 to '/new_location/users01.dbf';
    7> restore database;
    8> switch datafile all;
    9> recover database;
    10> }

  • How to restore a database from backup taken in standby database

    Its our  environment standard to run backup in standby database.
    Now we have to perform refresh production database to UAT database.
    I have performed normal refresh/duplicate.  Is there any additional procedures need to be followed to perform refresh from standby database backup

    RMAN Restoration to New Server with Different Directory and New Database Name
    In this case, I have an existing production database with RMAN Level 0 backup:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'C:\flash_recovery_area\galaxy\backupsets\autobackup\SAMSUNG-ctl_%F';
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'C:\flash_recovery_area\galaxy\backupsets\level0\level0-%d-%T-%U' MAXPIECESIZE 4G;
    DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE - 7';
    SHOW ALL;
    REPORT SCHEMA;
    LIST BACKUP OF DATABASE;
    REPORT NEED BACKUP;
    REPORT UNRECOVERABLE;
    LIST EXPIRED BACKUP BY FILE;
    LIST ARCHIVELOG ALL;
    REPORT OBSOLETE;
    CROSSCHECK BACKUP DEVICE TYPE DISK;
    CROSSCHECK COPY OF ARCHIVELOG ALL;
    DELETE NOPROMPT EXPIRED BACKUP DEVICE TYPE DISK;
    DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;
    RUN {
    sql 'alter system archive log current';
    BACKUP INCREMENTAL LEVEL 0 DATABASE PLUS ARCHIVELOG DELETE INPUT;
    LIST BACKUP OF DATABASE;
    REPORT NEED BACKUP;
    REPORT UNRECOVERABLE;
    LIST EXPIRED BACKUP BY FILE;
    LIST ARCHIVELOG ALL;
    REPORT OBSOLETE;
    CROSSCHECK BACKUP DEVICE TYPE DISK;
    CROSSCHECK COPY OF ARCHIVELOG ALL;
    DELETE NOPROMPT EXPIRED BACKUP DEVICE TYPE DISK;
    DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;
    The backupsets will be restored into a new server with different file structure. The database will also be different. In the new server, I have created a blank database (SID or CUSTOM database with the name DBGRID). This is easier so I won't have to create any directories, user ORADIM or create new PWFile.
    This document assumes that a blank (starter) database has been created in the new server. The RDBMS version is the same as the source database.
    In this example, the source database name is GALAXY and the target database name is DBGRID.
    Let me know if you have any feedback or comments. All I want is to share these steps with you and make it better so we can help other DBA's as well.
    Steps start here
    -->
    ORIGINAL DATABASE: GALAXY
    DUPLICATE DATABASE: DBGRID
    FROM THE SOURCE DATABASE (GALAXY)
    1. Backup the database using RMAN incremental backups.
    2. Check the RMAN logs generated and look for the result of the command:
    C:\Users\Administrator>set ORACLE_SID=GALAXY
    C:\Users\Administrator>rman target /
    Recovery Manager: Release 11.2.0.1.0 - Production on Wed Aug 1 06:55:08 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: GALAXY (DBID=3578870300)
    RMAN> report schema;
    using target database control file instead of recovery catalog
    Report of database schema for database with db_unique_name GALAXY
    List of Permanent Datafiles
    ===========================
    File Size(MB) Tablespace RB segs Datafile Name
    1    680      SYSTEM *** C:\ORACLE\ORADATA\GALAXY\SYSTEM01.DBF
    2    510      SYSAUX *** C:\ORACLE\ORADATA\GALAXY\SYSAUX01.DBF
    3    140      UNDOTBS1 *** C:\ORACLE\ORADATA\GALAXY\UNDOTBS01.DBF
    4    5        USERS *** C:\ORACLE\ORADATA\GALAXY\USERS01.DBF
    5    106      EXAMPLE *** C:\ORACLE\ORADATA\GALAXY\EXAMPLE01.DBF
    6    2048     ALLINDEX *** C:\ORACLE\ORADATA\GALAXY\ALLINDEX01.DBF
    List of Temporary Files
    =======================
    File Size(MB) Tablespace Maxsize(MB) Tempfile Name
    1    29       TEMP 32767 C:\ORACLE\ORADATA\GALAXY\TEMP01.DBF
    This command shows all the physical database files that will be backed-up by the current RMAN job.
    List the online redolog files:
    SQL> select * from v$logfile;
    GROUP# STATUS  TYPE    MEMBER IS_
    3         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO03A.LOG     NO
    3         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO03B.LOG     NO
    2         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO02A.LOG     NO
    2         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO02B.LOG     NO
    1         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO01A.LOG     NO
    1         ONLINE C:\ORACLE\ORADATA\GALAXY\REDO01B.LOG     NO
    6 rows selected.
    3. Since the target server has different structure, it is easier to use a pfile to startup the database rather than restoring the spfile from backup.
    C:\Users\Administrator>set ORACLE_SID=GALAXY
    C:\Users\Administrator>sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 1 06:56:14 2012
    Copyright (c) 1982, 2010, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> create pfile='C:\TEMP\initGALAXYrman.ora' from spfile;
    File created.
    4. Edit the pfile to have the following parameters:
    (These parameters has been edited to fit the target database requirements)
    galaxy entries has been changed to dbgrid. Directories has been corrected as well.
    dbgrid.__db_cache_size=192937984
    dbgrid.__java_pool_size=4194304
    dbgrid.__large_pool_size=4194304
    dbgrid.__oracle_base='D:\app\Administrator'#ORACLE_BASE set from environment
    dbgrid.__pga_aggregate_target=281018368
    dbgrid.__sga_target=524288000
    dbgrid.__shared_io_pool_size=0
    dbgrid.__shared_pool_size=301989888
    dbgrid.__streams_pool_size=4194304
    *.audit_file_dest='D:\app\Administrator\admin\DBGRID\adump'
    *.audit_trail='db'
    *.compatible='11.2.0.0.0'
    *.control_files='D:\oradata\DBGRID\control01.ctl','D:\oradata\DBGRID\control02.ctl'
    *.db_block_size=8192
    *.db_domain=''
    Leave as it is for now --> *.db_name='GALAXY'
    *.db_recovery_file_dest='D:\fra\backupsets\duplicate'
    *.DB_RECOVERY_FILE_DEST_SIZE=4G
    *.diagnostic_dest='D:\app\Administrator'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=DBGRIDXDB)'
    *.job_queue_processes=1000
    *.log_archive_dest_1='location=D:\fra\backupsets\archs'
    *.log_buffer=10485760
    *.memory_target=805306368
    *.open_cursors=300
    *.processes=800
    *.remote_login_passwordfile='EXCLUSIVE'
    *.session_cached_cursors=300
    *.sessions=885
    *.undo_tablespace='UNDOTBS1'
    Make sure that all the directory values in this edited pfile are existing in the target server.
    5. Copy all the RMAN backup pieces generated in the source database. Transfer the edited pfile as well. Make sure that all directories presented in the pfile exists in the target server.
    In this example, RMAN backupsets are located at:
    Backupsets:
    Level0 and Level1 = D:\fra\backupsets\duplicate\level0 , D:\fra\backupsets\duplicate\level1
    Controlfile and Spfile Autobackup = D:\fra\backupsets\duplicate\autobackup
    Edited pfile initGALAXYrman= C:\TEMP\initDBGRIDnew.ora
    FROM THE TARGET DATABASE (DBGRID)
    6. Connect to RMAN and perform database duplication using RMAN backup restoration
    C:\Users\Administrator>rman target /
    Recovery Manager: Release 11.2.0.1.0 - Production on Wed Aug 1 07:26:45 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database (not started)
    RMAN> set dbid = 3578870300; --> THIS IS THE DBID OF THE SOURCE DATABASE!
    executing command: SET DBID
    RMAN> startup nomount pfile='C:\TEMP\initDBGRIDnew.ora'; -->restore the edited pfile
    Oracle instance started
    Total System Global Area     535662592 bytes
    Fixed Size 1375792 bytes
    Variable Size 327156176 bytes
    Database Buffers 192937984 bytes
    Redo Buffers 14192640 bytes
    RMAN> restore controlfile from 'D:\fra\backupsets\duplicate\autobackup\SAMSUNG-CTL_C-3578870300-20120801-00'; -->restore the correct controlfile
    Starting restore at 01-AUG-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=19 device type=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
    output file name=D:\ORADATA\DBGRID\CONTROL01.CTL
    output file name=D:\ORADATA\DBGRID\CONTROL02.CTL
    Finished restore at 01-AUG-12
    RMAN> alter database mount; -->mount the database
    database mounted
    released channel: ORA_DISK_1
    RMAN> catalog start with "D:\fra\backupsets\duplicate";
    --> catalog the location of the backup pieces to make it known to the control file
    Starting implicit crosscheck backup at 01-AUG-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=19 device type=DISK
    Crosschecked 3 objects
    Finished implicit crosscheck backup at 01-AUG-12
    Starting implicit crosscheck copy at 01-AUG-12
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 01-AUG-12
    searching for all files in the recovery area
    cataloging files...
    no files cataloged
    searching for all files that match the pattern D:\fra\backupsets\duplicate
    List of Files Unknown to the Database
    =====================================
    File Name: D:\FRA\BACKUPSETS\duplicate\autobackup\SAMSUNG-CTL_C-3578870300-20120801-00
    File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-01NHGTGV_1_1
    File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1
    File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-03NHGTMT_1_1
    Do you really want to catalog the above files (enter YES or NO)? YES
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: D:\FRA\BACKUPSETS\duplicate\autobackup\SAMSUNG-CTL_C-3578870300-20120801-00
    File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-01NHGTGV_1_1
    File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1
    File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-03NHGTMT_1_1
    RMAN> list backup summary; -->check your backup they are now known
    List of Backups
    ===============
    Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
    1 B  A  A DISK 01-AUG-12       1       2 NO         TAG20120801T011054
    2 B  0  A DISK 01-AUG-12       1       2 NO         TAG20120801T011137
    3 B  A  A DISK 01-AUG-12       1       2 NO         TAG20120801T011405
    RMAN> list archivelog all; -->list you archivelog for point in time recovery
    List of Archived Log Copies for database with db_unique_name GALAXY
    =====================================================================
    Key Thrd Seq     S Low Time
    26 1    29      A 01-AUG-12
    Name: D:\FRA\BACKUPSETS\ARCHS\ARC0000000029_0785167457.0001
    Perform database restoration and recovery. The sequence number is Seq+1 for complete recovery, so that will be 29 + 1 = 30. You can also do recovery via SCN or time based recovery.
    Remember in the previous step: RMAN> REPORT SCHEMA;
    Each datafile has a corresponding datafile number.
    Follow the format to convert them into their respective new restoration directory in the target server.
    SET NEWNAME has the format:
    SET NEWNAME FOR DATAFILE [FILE NUMBER IN THE REPORT SCHEMA COMMAND] TO
    ‘[NEW LOCATION AND FILENAME OF THE DATAFILES]’;
    RMAN> run {
    2> SET UNTIL SEQUENCE 30 THREAD 1;
    3> set newname for datafile 1 to 'D:\oradbgrid\oradata\SYSTEM01.DBF';
    4> set newname for datafile 2 to 'D:\oradbgrid\oradata\SYSAUX01.DBF';
    5> set newname for datafile 3 to 'D:\oradbgrid\oradata\UNDOTBS01.DBF';
    6> set newname for datafile 4 to 'D:\oradbgrid\oradata\USERS01.DBF';
    7> set newname for datafile 5 to 'D:\oradbgrid\oradata\EXAMPLE01.DBF';
    8> set newname for datafile 6 to 'D:\oradbgrid\oradata\ALLINDEX01.DBF';
    9> restore database;
    10> switch datafile all;
    11> recover database;
    12> }
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 01-AUG-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=19 device type=DISK
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to D:\oradbgrid\oradata\SYSTEM01.DBF
    channel ORA_DISK_1: restoring datafile 00002 to D:\oradbgrid\oradata\SYSAUX01.DBF
    channel ORA_DISK_1: restoring datafile 00003 to D:\oradbgrid\oradata\UNDOTBS01.DBF
    channel ORA_DISK_1: restoring datafile 00004 to D:\oradbgrid\oradata\USERS01.DBF
    channel ORA_DISK_1: restoring datafile 00005 to D:\oradbgrid\oradata\EXAMPLE01.DBF
    channel ORA_DISK_1: restoring datafile 00006 to D:\oradbgrid\oradata\ALLINDEX01.DBF
    channel ORA_DISK_1: reading from backup piece D:\FRA\BACKUPSETS\DUPLICATE\LEVEL0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1
    channel ORA_DISK_1: piece handle=D:\FRA\BACKUPSETS\DUPLICATE\LEVEL0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1 tag=TAG20120801T011137
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:02:06
    Finished restore at 01-AUG-12
    Starting recover at 01-AUG-12
    using channel ORA_DISK_1
    starting media recovery
    archived log for thread 1 with sequence 29 is already on disk as file D:\FRA\BACKUPSETS\ARCHS\ARC0000000029_0785167457.0001
    archived log file name=D:\FRA\BACKUPSETS\ARCHS\ARC0000000029_0785167457.0001 thread=1 sequence=29
    media recovery complete, elapsed time: 00:00:01
    Finished recover at 01-AUG-12
    Log in to SQL*Plus to recreate the redolog files.
    Format:
    ALTER DATABASE RENAME FILE ‘[OLD REDOLOG LOCATION]’ TO ‘[NEW REDOLOG LOCATION]’;
    C:\Users\Administrator>sqlplus "/ as sysdba"
    SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 1 08:54:27 2012
    Copyright (c) 1982, 2010, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select instance_name, status from v$instance;
    INSTANCE_NAME STATUS
    dbgrid MOUNTED
    SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO03A.LOG' TO 'C:\oracle\oradata\dbgrid\REDO03A.LOG';
    Database altered.
    SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO03B.LOG' TO 'C:\oracle\oradata\dbgrid\REDO03B.LOG';
    Database altered.
    SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO02A.LOG' TO 'C:\oracle\oradata\dbgrid\REDO02A.LOG';
    Database altered.
    SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO02B.LOG' TO 'C:\oracle\oradata\dbgrid\REDO02B.LOG';
    Database altered.
    SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO01A.LOG' TO 'C:\oracle\oradata\dbgrid\REDO01A.LOG';
    Database altered.
    SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO01B.LOG' TO 'C:\oracle\oradata\dbgrid\REDO01B.LOG';
    Database altered.
    Open the database in resetlogs option. Create spfile from the edited pfile then bounce the database.
    RMAN> alter database open resetlogs;
    database opened
    SQL> create spfile from pfile='C:\TEMP\initDBGRIDnew.ora';
    File created.
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup
    ORACLE instance started.
    Total System Global Area  535662592 bytes
    Fixed Size 1375792 bytes
    Variable Size 327156176 bytes
    Database Buffers 192937984 bytes
    Redo Buffers 14192640 bytes
    Database mounted.
    Database opened.
    SQL> select instance_name, status from v$instance;
    INSTANCE_NAME STATUS
    dbgrid OPEN
    Create a new TEMP tablespace, make this as the new default temporary tablespace. Drop the old TEMP tablespace. Restart the database.
    SQL> CREATE TEMPORARY TABLESPACE TEMP01 TEMPFILE 'D:\oradbgrid\oradata\TEMP0101.dbf' SIZE 200M;
    Tablespace created.
    SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP01;
    Database altered.
    SQL> drop tablespace TEMP including contents and datafiles;
    Tablespace dropped.
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount;
    ORACLE instance sta

  • Restoring a Rman Tablespace backup to noarchilog mode database

    Hi All,
    Is it possible to take a backup of a tablespace through rman from archivelog mode database and restore the same to noarchivelog mode database through rman ? Please suggest if it is not possible why it is not possible.
    We have a testing database from which a tablespace has been dropped. Can it be restored from the Prod database ?
    Please help. The database version is 9.2.0.8..

    Fabricio_Jorge wrote:
    I think it's possible to backup/restore a single tablespace:
    BACKUP TABLESPACE nome_tablespace [FORMAT 'path/bkp_file'];
    Being able to backup a single tablespace is NOT the same as grafting that TS into a different database.
    First, you are not really backing up a 'tablespace'. You are backing up files. In this case, just the files that implement the named TS, but files, nevertheless. And files belong to a database. Header info in each file defines, among other things, the dbid of the database the file belongs to. And the current scn. That will be a severe mis-match if you tried to 'restore' it to some other db.

  • Database restore with just one backup set

    Hallo experts,
    I got a big problem with restoring my XE database. I have a newly created full backup from my XE. While saving the flashback_area I got a hard crash on my system but I saved the last backup set file on a server. Unfortunately I was not able to save other backup sets and I think, there was a special backup of my control files. The restore on another system does not work because of invalid piece.
    The data of this database is necessary for my work. Is there anybody out there who can help to restore the data with the existing backup set.
    I did not change the entire structure of my original XE database. I only created to schemas with data in. is there any solution to restore the data.
    Thanks for any help.
    Holger

    Hi you all,
    I think that somebody will be interested in the solution of my problem,so I post it here and in german on my website (www.datacubus.de).
    My XEdatabase is successfully restored and I walked through some undocumented and not supported features of ORACLE to win the challenge.
    The first fact is, that ORACLE XE has a very static structure if you use it as is. The datafiles are predefined and so a manual restore with a foreign backup piece seems to be possible.
    Here is my way:
    Create a backup of your controlfile
    ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
    Shutdown your database
    shutdown immediate
    Start the database in nomount mode
    [holger@MSA04071]$ rman nocatalog target /
    RMAN> startup force nomount;
    RMAN> quit
    Restore the datafiles
    I used the following script to restore the datafiles from the backup piece without any check:
    declare
    devtype varchar2(256);
    v_file varchar2(255);
    done boolean;
    begin
    v_file:='/usr/lib/oracle/xe/app/oracle/flash_recovery_area/XE/backupset/o1_mf_nnndf_TAG20070420T234848_32lfb0w9_.bkp';
    devtype:= dbms_backup_restore.DeviceAllocate(type => '',ident => 'D1');
    dbms_backup_restore.RestoreSetDatafile;
    dbms_backup_restore.RestoreDatafileTo(dfnumber => 1,toname=>'/usr/lib/oracle/xe/oradata/XE/system.dbf');
    dbms_backup_restore.RestoreDatafileTo(dfnumber => 2,toname=>'/usr/lib/oracle/xe/oradata/XE/undo.dbf');
    dbms_backup_restore.RestoreDatafileTo(dfnumber => 3,toname=>'/usr/lib/oracle/xe/oradata/XE/sysaux.dbf');
    dbms_backup_restore.RestoreDatafileTo(dfnumber => 4,toname=>'/usr/lib/oracle/xe/oradata/XE/users.dbf');
    dbms_backup_restore.RestoreBackupPiece(done => done,handle => v_file,params => null);
    dbms_backup_restore.DeviceDeallocate;
    end;
    Start this script as sysdba. But by carefull. This only works if no entire change of datafiles had taken place!
    Reset DBID
    Because of the saved DBID within the datafile, the database can't be opened. But there is a little trick for resetting the DBID.
    shutdown;
    startup mount;
    execute dbms_backup_restore.zeroDbid(0);
    shutdown normal;
    Delete or rename existing Controlfile
    Edit trace file
    You have to modify your controlfile script as follows:
    1. Only use the CREATE CONTROLFILE... block
    2. Delete RECOVER DATABASE block
    3. Replace REUSE with SET
    4. Replace NORESETLOGS with RESETLOGS
    Create new control file
    Use the CREATE CONTROLFILE block for creation of a new control file.
    Open Database
    alter database open resetlogs;
    Much work but all my data is back and now I will backup the whole flashback_area to avoid further nightmares.
    Bye
    Holger

  • What databases to backup to restore Search Enterprise configuration and search pages?

    Hello,
    If I needed to restore the Enterprise Search configuration and search pages, what SharePoint pages do I need to backup?
    SharePoint config and/or SharePoint admin databases?
    Thanks.
    Paul

    Hi Paul,
    SharePoint Enterprise Search site is stored in SharePoint Content database associated with the web application which hosts enterprise search site, if you want to resoter the search configuration and search pages(may have customized the search web part
    page), you can try to firstly test the restore of particular content database and search administrator database.
    https://technet.microsoft.com/en-us/library/jj219738.aspx#AdminDB
    Thanks
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Can CDC enabled database DIFF backups be RESTORED while maintaining the CDC integrity?

    We tried restoring FULL + subsequent DIFF backups of a CDC enabled database to a different SQL server and found that the CDC integrity is not being maintained. We did RESTORE the databases with the KEEP_CDC option.
    Can someone please guide us on how to successfully restore the CDC enabled database backups(FULL + DIFF) while maintaining the CDC integrity?
    Note: SQL Server Version: SQL Server 2012 SP1 CU2

    Hi YoungBreeze,
    Based on your description, I make a test on my computer.
    Firstly, I create a database named ‘sqldbpool’ , then enable the
    Change Data Capture (CDC) feature and take full+ differential backups of the database. Below are the scripts I used.
    -- Create database sqldbpool
    CREATE DATABASE [sqldbpool] ON PRIMARY
    ( NAME = N'SQLDBPool', FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\SQLDBPool.mdf' , SIZE = 5120KB ,
    MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB )
    LOG ON
    ( NAME = N'SQLDBPool_log', FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\SQLDBPool_log.LDF' , SIZE = 3840KB ,
    MAXSIZE = 2048GB , FILEGROWTH = 10%)
    GO
    use sqldbpool;
    go
    -- creating table
    create table Customer
    custID int constraint PK_Employee primary key Identity(1,1)
    ,custName varchar(20)
    --Enabling CDC on SQLDBPool database
    USE SQLDBPool
    GO
    EXEC sys.sp_cdc_enable_db
    --Enabling CDC on Customer table
    USE SQLDBPool
    GO
    EXEC sys.sp_cdc_enable_table
    @source_schema = N'dbo',
    @source_name = N'Customer',
    @role_name = NULL
    GO
    --Inserting values in customer table
    insert into Customer values('jugal'),('shah')
    -- Querying CDC table to get the changes
    select * from cdc.dbo_customer_CT
    --Taking full database backup
    backup database sqldbpool to disk = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\sqldbpool.bak'
    insert into Customer values('111'),('222')
    -- Querying CDC table to get the changes
    select * from cdc.dbo_customer_CT
    --Taking differential database backup
    BACKUP DATABASE sqldbpool TO DISK = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\sqldbpooldif.bak' WITH DIFFERENTIAL
    GO
    Secondly, I restore the ‘sqldbpool’ database  in a different SQL Server instance with the following scripts. After the restoration, everything works as expected and the database maintains the CDC integrity.
    Use master
    Go
    --restore full database backup
    restore database sqldbpool from disk = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\sqldbpool.bak' with keep_cdc
    Restore Database sqldbpool From Disk = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\sqldbpool.bak'
    With Move 'SQLDBPool' To 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\SQLDBPool.mdf',
    Move 'SQLDBPool_log' To 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\SQLDBPool_log.LDF',
    Replace,
    NoRecovery;
    Go
    --restore differential database backup
    restore database sqldbpool from disk = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\sqldbpooldif.bak' with keep_cdc
    --add the Capture and Cleanup jobs
    Use sqldbpool
    exec sys.sp_cdc_add_job 'capture'
    GO
    exec sys.sp_cdc_add_job 'cleanup'
    GO
    insert into Customer values('TEST'),('TEST1')
    -- Querying CDC table to get the changes
    select * from cdc.dbo_customer_CT
    When we restore a CDC enabled database, we need to note that the CDC feature is available only on the Enterprise, Developer, and Evaluation editions of SQL Server. And we need to add the Capture and Cleanup agent jobs after restoring the database.
    For more details about restoring a CDC enabled database in SQL Server, you can review the following similar articles.
    Restoring a SQL Server database that uses Change Data Capture:
    http://www.mssqltips.com/sqlservertip/2421/restoring-a-sql-server-database-that-uses-change-data-capture/
    CDC Interoperability with Mirroring and Recovery:
    http://www.sqlsoldier.com/wp/sqlserver/cdcinteroperabilitywithmirroringandrecovery
    Thanks,
    Lydia Zhang

  • 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

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

  • RMAN Parallel Backup Validate

    Hi,
    OS= Solaris 10
    Database = 10gR2
    I am using following script to validate the physical and logical corruption in the database through RMAN:
    rman target /
    RMAN> RUN {
    CONFIGURE DEVICE TYPE DISK PARALLELISM 8;
    ALLOCATE CHANNEL d1 DEVICE TYPE DISK;
    ALLOCATE CHANNEL d2 DEVICE TYPE DISK;
    ALLOCATE CHANNEL d3 DEVICE TYPE DISK;
    ALLOCATE CHANNEL d4 DEVICE TYPE DISK;
    BACKUP VALIDATE DATABASE;
    RELEASE CHANNEL;
    My machine has 4 CPUs.
    I just want to verify that will the above RMAN script open up 4 channels in parallel and validate the database?
    regards

    Hi Fahd,
    Can you please study the below link also from the forum.
    Backup Time
    Best regards,
    Rafi.
    http://rafioracledba.blogspot.com/

  • BACKUP VALIDATE vs VALIDATE in checking logical/physical corruption

    Hello all,
    I am checking if our 10gR2 database has any physical or logical corruption. I have read in some places where they state that VALIDATE command is enough to check database for physical corruption. Our database was never backed up by RMAN specifically before. Are any configuration settings needed for running BACKUP VALIDATE command? The reason I am asking is because just the VALIDATE command returns an error and BACKUP VALIDATE command runs without error but it is not showing the
    "File Status Marked Corrupt Empty Blocks Blocks Examined High SCN" lines.
    I used the command in two different formats and both do not show individual data file statuses:
    RMAN> run {
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE DEVICE TYPE DISK PARALLELISM 10 BACKUP TYPE TO BACKUPSET;
    BACKUP VALIDATE CHECK LOGICAL DATABASE FILESPERSET=10;
    RMAN> BACKUP VALIDATE CHECK LOGICAL DATABASE
    RMAN> VALIDATE DATABASE;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "database": expecting one of: "backupset"
    RMAN-01007: at line 1 column 10 file: standard input
    However on a different database already being backed up by RMAN daily, BACKUP VALIDATE output shows list of datafiles and STATUS = OK as below:
    List of Datafiles
    =================
    File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
    How can we check every individual datafile status. Appreciate your responses. Thanks.

    Hi,
    After you have run:
    BACKUP VALIDATE CHECK LOGICAL DATABASE You can use sqlplus and run:
    select * from v$database_block_corruption.The output will tell you which block in which datafile is corrupt.
    Regards,
    Tycho
    Edited by: tychos on 8-sep-2011 18:34

  • Backup validate :Error

    Hi Expert,
    while executing backup validate database archivelog all in one of the server i received this
    RMAN> backup validate database archivelog all;
    Starting backup at 04-JUL-07
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=18 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 07/04/2007 06:21:34
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specificati
    on does not match any archive log in the recovery catalog
    What this means and is it any major concern?
    Thanks
    Shaan

    this means you didn't have any archives and rman is unable to validate them.
    RMAN does not actually produce backup sets, but rather reads the specified files in their entirety, to determine whether they can be backed up and are not corrupted.
    found at:
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmbackp008.htm#sthref672

Maybe you are looking for

  • IMPORT to memory id with field exit

    hi everyone, i need your help, i'm import to memory/export with field exit, I must capture a data of ik11, from table IMRG... this is the code: FUNCTION FIELD_EXIT_IMRC_MDOCM.    DATA: V_MDOC LIKE IMRG-MDOCM. EXPORT V_MDOC TO MEMORY ID 'DOC'. ENDFUNC

  • Drag and Drop with Capture feature

    I would like to set up a drag and drop interaction. The user will drag several icons and place them on a map. They do not have to use all the icons provided to them. The map is a rectangle and I need to capture the icons placed on the map and there l

  • HT4528 I can't get siri to start when holding down home button?

    I can't get siri to start when holding down the home button?

  • How to view web pages off line

    how do you save web pages so they can be viewed on line?

  • Adding custom jspx to the contentDB application

    HI, I want to use my two my own custom jspx to the contentDB. As the contentDB is built in ADF, i have also created the jspx in adf, but along with this some xml files and backing beans also got created and some data control also got created. But i s