Problem in database recovery thru RMAN

I am completely new to RMAN.
I took full backup thru RMAN and as per suggested by some document, I deleted controlfile, datafile and SPfile in order to learn recovery thru RMAN.
now, when I try to connect to RMAN catalog I'm getting the following error "
RMAN> connect catalog rman/rman@test9i
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-04004: error from recovery catalog database: ORA-01033: ORACLE initializat
on or shutdown in progress"
can anybody help me in connecting and recovering the database.

I thinnk there may be user connected while performing a shutdown.Disconnect the user and stop the listner then you perform the recovery
correct me if i am wrong

Similar Messages

  • Problem in performing multiple Point-In-Time Database Recovery using RMAN

    Hello Experts,
    I am getting an error while performing database point in time recovery multiple times using RMAN. Details are as follows :-
    Environment:
    Oracle 11g, ASM,
    Database DiskGroups : DG_DATA (Data files), DG_ARCH(Archive logs), DG_REDO(Redo logs Control file).
    Snapshot DiskGroups :
    Snapshot1 (taken at 9 am): SNAP1_DATA, SNAP1_ARCH, +SNAP1_REDO
    Snapshot2 (taken at 10 am): SNAP2_DATA, SNAP2_ARCH, +SNAP2_REDO
    Steps performed for point in time recovery:
    1. Restore control file from snapshot 2.
         RMAN> RESTORE CONTROLFILE from '+SNAP2_REDO/orcl/CONTROLFILE/Current.256.777398261';
    2. For 2nd recovery, reset incarnation of database to snapshot 2 incarnation (Say 2).
    3. Catalog data files from snapshot 1.
    4. Catalog archive logs from snapshot 2.
    5. Perform point in time recovery till given time.
         STARTUP MOUNT;
         RUN {
              SQL "ALTER SESSION SET NLS_DATE_FORMAT = ''dd-mon-yyyy hh24:mi:ss''";
              SET UNTIL TIME "06-mar-2013 09:30:00";
              RESTORE DATABASE;
              RECOVER DATABASE;
              ALTER DATABASE OPEN RESETLOGS;
    Results:
    Recovery 1: At 10.30 am, I performed first point in time recovery till 9:30 am, it was successful. Database incarnation was raised from *2* to *3*.
    Recovery 2: At 11:10 am, I performed another point in time recovery till 9:45 am, while doing it I reset the incarnation of DB to *2*, it failed with following error :-
    Starting recover at 28-FEB-13
    using channel ORA_DISK_1
    starting media recovery
    media recovery failed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 03/06/2013 11:10:57
    ORA-00283: recovery session canceled due to errors
    RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
    start until time 'MAR 06 2013 09:45:00'
    ORA-00283: recovery session canceled due to errors
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '+DG_REDO/orcl/onlinelog/group_1.257.807150859'
    ORA-17503: ksfdopn:2 Failed to open file +DG_REDO/orcl/onlinelog/group_1.257.807150859
    ORA-15012: ASM file '+DG_REDO/orcl/onlinelog/group_1.257.807150859' does not exist
    Doubts:
    1. Why did recovery failed 2nd time, but not 1st time and why is RMAN looking for online redo log group_1.257.807150859 in 2nd recovery ?
    3. I tried restoring control file from AutoBackup, in that case both 1st and 2nd recovery succeeded.
    However for this to work, I always need to keep the AutoBackup feature enabled.
    How reliable is control file AutoBackup ? Is there any alternative to using AutoBackup, can I restore control file from snapshot backup only ?
    4. If I restore control file from AutoBackup, then from what point of time/SCN does RMAN restores the control file ?
    Please help me out in this issue.
    Thanks.

    992748 wrote:
    Hello experts,
    I'm little newbie to RMAN recovery. Please help me in these doubts:
    1. If I have datafiles, archive logs & control files backup, but current online REDO logs are lost, then can I perform incomplete database recovery ?yes, if you have backups of everything else
    2. Till what maximum time/scn can incomplete database recovery be performed ??Assuming the only thing lost is the redo logs, you can recover to the last scn in the last archivelog.
    3. What is role of online REDO logs in incomplete database recovery ? They provide the final redo changes - the ones that have not been written to archivelogs
    Are they required for incomplete recovery ?It depends on how much incomplete recovery you need to do.
    Think of all of your changes as a constant stream of redo information. As a redolog fills, it is copied to archive, then (eventually) reused. over time, your redo stream is in archivelog_1, continuing into archvivelog_2, then to 3, and eventually, when you get to the last archivelog, into the online redo. A recovery will start with the oldest necessary point in the redo stream and continue forward. Whether or not you need the online redo for a PIT recovery depends on how far forward you need to recover.
    But you should take every precaution to prevent loss of online redo logs .. starting with having multiple members in each redo group ... and keeping those multiple members on physically separate disks.

  • Problem in Database Recovery..

    I m working at Test Environment, My database is running in ArchiveLogMode. I have current backup and old backup (one month old),
    For practice of Backup & Recovery, I deleted the control files, online redo logs and data files and restored from old backup(one month old).
    Note: I want to let you know that I have all the ArchivedRedoLog files and I have also created one tablespace (tablespace: abamco_test)that is not available in old backup.
    Is it possible to recover that tablespace with only ArchivedRedoLog files (No datafile backup)??????????
    =========================================================================
    SQL> select name from v$database;
    NAME
    ROCK
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    <><> deleted all the datafiles, redologs, and control files.
    <><> copied & pasted all the redologs, and control files from one month old backup
    SQL> startup
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247876 bytes
    Variable Size 83887484 bytes
    Database Buffers 75497472 bytes
    Redo Buffers 7139328 bytes
    ORA-00205: error in identifying control file, check alert log for more info
    SQL> shutdown immediate
    ORA-01507: database not mounted
    ORACLE instance shut down.
    <><> COpied One month old control file and pasted in OraData folder.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247876 bytes
    Variable Size 83887484 bytes
    Database Buffers 75497472 bytes
    Redo Buffers 7139328 bytes
    Database mounted.
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
    SQL> shutdown immediate
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    <><> Copied all the datafiles, oneline redo log files from one month Old backup.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247876 bytes
    Variable Size 83887484 bytes
    Database Buffers 75497472 bytes
    Redo Buffers 7139328 bytes
    Database mounted.
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-01110: data file 6: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\ABAMCO_TEST01.DBF'
    ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
    ORA-01110: data file 6: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\ABAMCO_TEST01.DBF'
    SQL> shutdown immediate
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247876 bytes
    Variable Size 83887484 bytes
    Database Buffers 75497472 bytes
    Redo Buffers 7139328 bytes
    Database mounted.
    ORA-01122: database file 1 failed verification check
    ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
    ORA-01207: file is more recent than control file - old control file
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-01122: database file 1 failed verification check
    ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
    ORA-01207: file is more recent than control file - old control file
    SQL> shutdown immediate;
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup nomount;
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247876 bytes
    Variable Size 83887484 bytes
    Database Buffers 75497472 bytes
    Redo Buffers 7139328 bytes
    SQL> alter database backup controlfile to trace;
    alter database backup controlfile to trace
    ERROR at line 1:
    ORA-01507: database not mounted
    SQL> alter database mount;
    Database altered.
    SQL> alter database backup controlfile to trace;
    Database altered.
    SQL> shutdown immediate;
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    <><> copied the (contents) from generated file and saved in controlfile_recover.sql script.
    STARTUP NOMOUNT
    CREATE CONTROLFILE REUSE DATABASE "ROCK" NORESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
    LOGFILE
    GROUP 1 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\REDO01.LOG' SIZE 50M,
    GROUP 2 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\REDO02.LOG' SIZE 50M,
    GROUP 3 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\REDO03.LOG' SIZE 50M
    -- STANDBY LOGFILE
    DATAFILE
    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF',
    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\UNDOTBS01.DBF',
    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSAUX01.DBF',
    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\USERS01.DBF',
    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM03.DBF',
    'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\ABAMCO_TEST01.DBF'
    CHARACTER SET WE8MSWIN1252
    SQL> @D:\controlfile_recover.sql
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247876 bytes
    Variable Size 83887484 bytes
    Database Buffers 75497472 bytes
    Redo Buffers 7139328 bytes
    CREATE CONTROLFILE REUSE DATABASE "ROCK" RESETLOGS ARCHIVELOG
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01565: error in identifying file 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\ABAMCO_TEST01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    ORA-01507: database not mounted
    ALTER DATABASE OPEN RESETLOGS
    ERROR at line 1:
    ORA-01507: database not mounted
    ALTER TABLESPACE TEMP ADD TEMPFILE 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\TEMP01.DBF' REUSE
    ERROR at line 1:
    ORA-01109: database not open
    SQL> alter tablespace ABAMCO_TEST offline;
    alter tablespace ABAMCO_TEST offline
    ERROR at line 1:
    ORA-01109: database not open
    SQL>
    SQL>
    SQL> shutdown immediate;
    ORA-01507: database not mounted
    ORACLE instance shut down.
    <><> I removed one line 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\ABAMCO_TEST01.DBF' from controlfile_recover.sql
    SQL> @D:\controlfile_recover.sql
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247876 bytes
    Variable Size 83887484 bytes
    Database Buffers 75497472 bytes
    Redo Buffers 7139328 bytes
    CREATE CONTROLFILE REUSE DATABASE "ROCK" RESETLOGS ARCHIVELOG
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01163: SIZE clause indicates 12800 (blocks), but should match header 1536
    ORA-01110: data file 5: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM03.DBF'
    ORA-01507: database not mounted
    ALTER DATABASE OPEN RESETLOGS
    ERROR at line 1:
    ORA-01507: database not mounted
    ALTER TABLESPACE TEMP ADD TEMPFILE 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\TEMP01.DBF' REUSE
    ERROR at line 1:
    ORA-01109: database not open
    SQL> SHUTDOWN IMMEDIATE;
    ORA-01507: database not mounted
    ORACLE instance shut down.
    SQL> @D:\controlfile_recover.sql
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247876 bytes
    Variable Size 83887484 bytes
    Database Buffers 75497472 bytes
    Redo Buffers 7139328 bytes
    CREATE CONTROLFILE REUSE DATABASE "ROCK" RESETLOGS ARCHIVELOG
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01163: SIZE clause indicates 16384 (blocks), but should match header 1536
    ORA-01110: data file 5: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM03.DBF'
    ORA-01507: database not mounted
    ALTER DATABASE OPEN RESETLOGS
    ERROR at line 1:
    ORA-01507: database not mounted
    ALTER TABLESPACE TEMP ADD TEMPFILE 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\TEMP01.DBF' REUSE
    ERROR at line 1:
    ORA-01109: database not open
    SQL> shutdown immediate;
    ORA-01507: database not mounted
    ORACLE instance shut down.
    SQL> @D:\controlfile_recover.sql
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247876 bytes
    Variable Size 83887484 bytes
    Database Buffers 75497472 bytes
    Redo Buffers 7139328 bytes
    CREATE CONTROLFILE REUSE DATABASE "ROCK" RESETLOGS ARCHIVELOG
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01163: SIZE clause indicates 32768 (blocks), but should match header 1536
    ORA-01110: data file 5: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM03.DBF'
    ORA-01507: database not mounted
    ALTER DATABASE OPEN RESETLOGS
    ERROR at line 1:
    ORA-01507: database not mounted
    ALTER TABLESPACE TEMP ADD TEMPFILE 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\TEMP01.DBF' REUSE
    ERROR at line 1:
    ORA-01109: database not open
    SQL> shutdown immediate;
    ORA-01507: database not mounted
    ORACLE instance shut down.
    SQL> @D:\controlfile_recover.sql
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1247876 bytes
    Variable Size 83887484 bytes
    Database Buffers 75497472 bytes
    Redo Buffers 7139328 bytes
    CREATE CONTROLFILE REUSE DATABASE "ROCK" RESETLOGS ARCHIVELOG
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01163: SIZE clause indicates 65536 (blocks), but should match header 1536
    ORA-01110: data file 5: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM03.DBF'
    ORA-01507: database not mounted
    ALTER DATABASE OPEN RESETLOGS
    ERROR at line 1:
    ORA-01507: database not mounted
    ALTER TABLESPACE TEMP ADD TEMPFILE 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\TEMP01.DBF' REUSE
    ERROR at line 1:
    ORA-01109: database not open
    SQL>
    Any suggestions? what should I do now?

    Here's what I found on Metalink :
    Subject: ORA-1163 creating a controlfile
    Doc ID: Note:377933.1 Type: PROBLEM
    Last Revision Date: 24-JUL-2006 Status: REVIEWED
    Problem Description:
    ====================
    You are attempting to recreate your controlfile after a clean shutdown ( shutdown normal or immediate)
    Upon running the create controlfile script you receive:
    CREATE CONTROLFILE REUSE DATABASE "PRODAB" NORESETLOGS ARCHIVELOG
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01163: SIZE clause indicates 12800 (blocks), but should match header 240160
    ORA-01110: data file X: '<full path of datafile>'
    Problem Explanation:
    ====================
    Sample controlfile.sql
    CREATE CONTROLFILE REUSE DATABASE "PRODAB" NORESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 454
    LOGFILE
    GROUP 1 '/oradata/PROD/redo01.log' SIZE 10M,
    GROUP 2 '/oradata/PROD/redo02.log' SIZE 10M,
    GROUP 3 '/oradata/PROD/redo03.log' SIZE 10M
    -- STANDBY LOGFILE
    DATAFILE
    '/oradata/PROD/system01.dbf',
    '/oradata/PROD/undotbs01.dbf',
    '/oradata/PROD/sysaux01.dbf',
    '/oradata/PROD/users01.dbf', <----------------Notice the extra comma after thelast datafile.
    CHARACTER SET WE8ISO8859P1
    Search Words:
    =============
    create controlfile ORA-1503 ORA-1163 ORA-1110
    Solution Description:
    =====================
    This extra comma is causing the create controlfile to raise this unexpected error as seen above.
    Solution Explanation:
    =====================
    This is a syntax error and by removing the trailing comma the create control should bypass this error.
    Wow ! Oracle made a syntax error ! why am i not surprised ? :)
    Thanks Khurram for your help !

  • Recovery problem thru RMAN

    for the first time, I decided to use RMAN, took fullbackup thru rman twice then I deleted my controlfile, datafiles and SPfile, now I don't know how to recover them because I am not even able to connect to catalog database.
    can somebody tell me how to recover the database in this situtation, I have the backup intact.

    What version of RMAN are you using? What version is the target database? What command are you using to connect to the RMAN catalog?
    You can still connect: "rman target / nocatalog" - this will use the current controlfile for the database and not the recovery catalog. From then it should be possible to run something like "RESTORE CONTROLFILE FROM AUTOBACKUP".
    We'd need more info to help!
    Regards
    Dale

  • Doubt about database point in time recovery using rman

    Hi Everyone,
    I have been practising various rman restore and recovery scenarios . I have a doubt regarding database point in time recovery using rman. Imagine i have a full database backup including controlfile scheduled to run at 10 PM everyday. today is 20th dec 2013. imagine i want to restore the database to a prior point in time ( say 18th dec till 8 AM). so i would restore all the datafiles  from 17th night's backup and apply archives till 8 AM of 18th dec . in this scenario should i restore the controlfile too from 17th dec bkp ( i am assuming yes we should ) or can we use the current controlfile ( assuming it is intact). i found the below from oracle docs.
    Performing Point-in-Time Recovery with a Current Control File
    The database must be closed to perform database point-in-time recovery. If you are recovering to a time, then you should set the time format environment variables before invoking RMAN. The following are sample Globalization Support settings:
    NLS_LANG = american_america.us7ascii
    NLS_DATE_FORMAT="Mon DD YYYY HH24:MI:SS"
    To recover the database until a specified time, SCN, or log sequence number:
    After connecting to the target database and, optionally, the recovery catalog database, ensure that the database is mounted. If the database is open, shut it down and then mount it:
    2.  SHUTDOWN IMMEDIATE;
    3.  STARTUP MOUNT;
    4. 
    Determine the time, SCN, or log sequence that should end recovery. For example, if you discover that a user accidentally dropped a tablespace at 9:02 a.m., then you can recover to 9 a.m.--just before the drop occurred. You will lose all changes to the database made after that time.
    You can also examine the alert.log to find the SCN of an event and recover to a prior SCN. Alternatively, you can determine the log sequence number that contains the recovery termination SCN, and then recover through that log. For example, query V$LOG_HISTORY to view the logs that you have archived. 
    RECID      STAMP      THREAD#    SEQUENCE#  FIRST_CHAN FIRST_TIM NEXT_CHANG
             1  344890611          1          1      20037 24-SEP-02      20043
             2  344890615          1          2      20043 24-SEP-02      20045
             3  344890618          1          3      20045 24-SEP-02      20046
    Perform the following operations within a RUN command:
    Set the end recovery time, SCN, or log sequence. If specifying a time, then use the date format specified in the NLS_LANG and NLS_DATE_FORMAT environment variables.
    If automatic channels are not configured, then manually allocate one or more channels.
    Restore and recover the database.
      The following example performs an incomplete recovery until November 15 at 9 a.m. 
    RUN
      SET UNTIL TIME 'Nov 15 2002 09:00:00';
      # SET UNTIL SCN 1000;       # alternatively, specify SCN
      # SET UNTIL SEQUENCE 9923;  # alternatively, specify log sequence number
      RESTORE DATABASE;
      RECOVER DATABASE;
    If recovery was successful, then open the database and reset the online logs:
    5.  ALTER DATABASE OPEN RESETLOGS;
    I did not quiet understand why the above scenario is using current controlfile as the checkpoint scn in the current controlfile and the checkpoint scn in the datafile headers do not match after the restore and recovery. Thanks in Advance for your help.
    Thanks
    satya

    Thanks for the reply ... but what about the checkpoint scn in the controlfile . my understanding is that unless the checkpoint scn in the controlfile and datafiles do not match the database will not open. so assuming the checkpoint scn in my current controlfile is 1500 and i want to recover my database till scn 1200. so the scn in the datafiles (which is 1200) is not not matching with the scn in the controlfile(1500). so will the database open in such cases.
    Thanks
    Satya

  • Problems doing an active Database duplication through RMAN

    Hi,
    I'm trying to do active Database duplication through RMAN (http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmdupdb.htm#).
    My OS is Sun Solaris 5
    Oracle version: 11gR1 Database on a 11gR2 Grid.
    I'm receiving the error
    RMAN> connect auxiliary sys/sys@rac402
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-04006: error from auxiliary database: ORA-12528: TNS:listener: all appropriate instances are blocking new connections
    I'm seeing the listeners are in blocked state as mt auxiliary Database is in nomount state.
    Service "rac40" has 1 instance(s).
    Instance "rac402", status BLOCKED, has 1 handler(s) for this service...
    Service "rac40_XPT" has 1 instance(s).
    Instance "rac402", status BLOCKED, has 1 handler(s) for this service...
    If I connect directly, I'm able to connect ("connect auxiliary / " after setting ORACLE_SID)
    But active RMAN is saying
    RMAN-03002: failure of Duplicate Db command at 06/18/2012 01:37:14
    RMAN-06217: not connected to auxiliary database with a net service name (I don't know why Oracle is so specific in connecting through net service name only!!!)
    So, how could I move forward?? any help is greatly appreciated!!!
    Thanks in advance.
    Regards,
    CSM

    Hi ,
    I have issue to active Database duplication issue and getting below error. Can someone suggest something on this error ?
    RMAN> duplicate target database to 'ub305' from active database;
    Starting Duplicate Db at 07-AUG-2012 13:33:22
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=2 device type=DISK
    contents of Memory Script:
    sql clone "create spfile from memory";
    executing Memory Script
    sql statement: create spfile from memory
    contents of Memory Script:
    shutdown clone immediate;
    startup clone nomount;
    executing Memory Script
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area 21512572928 bytes
    Fixed Size 2235984 bytes
    Variable Size 11005854128 bytes
    Database Buffers 10468982784 bytes
    Redo Buffers 35500032 bytes
    contents of Memory Script:
    sql clone "alter system set control_files =
    ''+DG_075_DATA01/ub305/controlfile/current.345.790692287'', ''+DG_075_FRA01/ub305/controlfile/current.292.790692289'' comment=
    ''Set by RMAN'' scope=spfile";
    sql clone "alter system set db_name =
    ''UA305'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
    sql clone "alter system set db_unique_name =
    ''UB305'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
    shutdown clone immediate;
    startup clone force nomount
    backup as copy current controlfile auxiliary format '+DG_075_DATA01/ub305/controlfile/current.345.790692287';
    restore clone controlfile to '+DG_075_FRA01/ub305/controlfile/current.292.790692289' from
    '+DG_075_DATA01/ub305/controlfile/current.345.790692287';
    sql clone "alter system set control_files =
    ''+DG_075_DATA01/ub305/controlfile/current.345.790692287'', ''+DG_075_FRA01/ub305/controlfile/current.292.790692289'' comment=
    ''Set by RMAN'' scope=spfile";
    shutdown clone immediate;
    startup clone nomount;
    alter clone database mount;
    executing Memory Script
    sql statement: alter system set control_files = ''+DG_075_DATA01/ub305/controlfile/current.345.790692287'', ''+DG_075_FRA01/ub305/controlfile/current.292.790692289'' comment= ''Set by RMAN'' scope=spfile
    sql statement: alter system set db_name = ''UA305'' comment= ''Modified by RMAN duplicate'' scope=spfile
    sql statement: alter system set db_unique_name = ''UB305'' comment= ''Modified by RMAN duplicate'' scope=spfile
    Oracle instance shut down
    Oracle instance started
    Total System Global Area 21512572928 bytes
    Fixed Size 2235984 bytes
    Variable Size 11005854128 bytes
    Database Buffers 10468982784 bytes
    Redo Buffers 35500032 bytes
    Starting backup at 07-AUG-2012 13:34:11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=1333 instance=ua3051 device type=DISK
    channel ORA_DISK_1: starting datafile copy
    copying current control file
    output file name=/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ua3051.f tag=TAG20120807T133412 RECID=17 STAMP=790695252
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
    Finished backup at 07-AUG-2012 13:34:15
    Starting restore at 07-AUG-2012 13:34:15
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=2 device type=DISK
    channel ORA_AUX_DISK_1: copied control file copy
    Finished restore at 07-AUG-2012 13:34:16
    sql statement: alter system set control_files = ''+DG_075_DATA01/ub305/controlfile/current.345.790692287'', ''+DG_075_FRA01/ub305/controlfile/current.292.790692289'' comment= ''Set by RMAN'' scope=spfile
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area 21512572928 bytes
    Fixed Size 2235984 bytes
    Variable Size 11005854128 bytes
    Database Buffers 10468982784 bytes
    Redo Buffers 35500032 bytes
    database mounted
    RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
    contents of Memory Script:
    set newname for datafile 1 to
    "+dg_075_data01";
    set newname for datafile 2 to
    "+dg_075_data01";
    set newname for datafile 3 to
    "+dg_075_data01";
    set newname for datafile 4 to
    "+dg_075_data01";
    set newname for datafile 5 to
    "+dg_075_data01";
    set newname for datafile 6 to
    "+dg_075_data01";
    set newname for datafile 7 to
    "+dg_075_data01";
    set newname for datafile 8 to
    "+DG_075_DATA01/ub305/datafile/ts001_rsa.ora";
    backup as copy reuse
    datafile 1 auxiliary format
    "+dg_075_data01" datafile
    2 auxiliary format
    "+dg_075_data01" datafile
    3 auxiliary format
    "+dg_075_data01" datafile
    4 auxiliary format
    "+dg_075_data01" datafile
    5 auxiliary format
    "+dg_075_data01" datafile
    6 auxiliary format
    "+dg_075_data01" datafile
    7 auxiliary format
    "+dg_075_data01" datafile
    8 auxiliary format
    "+DG_075_DATA01/ub305/datafile/ts001_rsa.ora" ;
    sql 'alter system archive log current';
    executing Memory Script
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    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 backup at 07-AUG-2012 13:34:46
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00008 name=+DG_305_DATA01/ua305/datafile/ts001_rsa.ora
    output file name=+DG_075_DATA01/ub305/datafile/ts001_rsa.ora tag=TAG20120807T133447
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:05
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00001 name=+DG_305_DATA01/ua305/datafile/system.256.788357663
    output file name=+DG_075_DATA01/ub305/datafile/system.322.790695353 tag=TAG20120807T133447
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:07
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00002 name=+DG_305_DATA01/ua305/datafile/sysaux.257.788357663
    output file name=+DG_075_DATA01/ub305/datafile/sysaux.321.790695359 tag=TAG20120807T133447
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:07
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00007 name=+DG_305_DATA01/ua305/datafile/ata_apm.271.788369355
    output file name=+DG_075_DATA01/ub305/datafile/ata_apm.320.790695367 tag=TAG20120807T133447
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:07
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00003 name=+DG_305_DATA01/ua305/datafile/undotbs1.258.788357663
    output file name=+DG_075_DATA01/ub305/datafile/undotbs1.319.790695373 tag=TAG20120807T133447
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00004 name=+DG_305_DATA01/ua305/datafile/users.259.788357663
    output file name=+DG_075_DATA01/ub305/datafile/users.316.790695377 tag=TAG20120807T133447
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00005 name=+DG_305_DATA01/ua305/datafile/undotbs2.264.788357815
    output file name=+DG_075_DATA01/ub305/datafile/undotbs2.315.790695381 tag=TAG20120807T133447
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00006 name=+DG_305_DATA01/ua305/datafile/ata_mds.270.788369353
    output file name=+DG_075_DATA01/ub305/datafile/ata_mds.314.790695383 tag=TAG20120807T133447
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:01
    Finished backup at 07-AUG-2012 13:36:24
    sql statement: alter system archive log current
    contents of Memory Script:
    backup as copy reuse
    archivelog like "+DG_305_FRA01/ua305/archivelog/2012_08_07/thread_1_seq_223.572.790694523" auxiliary format
    "+DG_075_FRA01" archivelog like
    "+DG_305_FRA01/ua305/archivelog/2012_08_07/thread_1_seq_224.573.790695385" auxiliary format
    "+DG_075_FRA01" archivelog like
    "+DG_305_FRA01/ua305/archivelog/2012_08_07/thread_2_seq_91.574.790695387" auxiliary format
    "+DG_075_FRA01" ;
    catalog clone recovery area;
    switch clone datafile all;
    executing Memory Script
    Starting backup at 07-AUG-2012 13:36:30
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archived log copy
    input archived log thread=1 sequence=223 RECID=311 STAMP=790694522
    output file name=+DG_075_FRA01/ub305/archivelog/2012_08_07/thread_1_seq_223.299.790695391 RECID=0 STAMP=0
    channel ORA_DISK_1: archived log copy complete, elapsed time: 00:00:01
    channel ORA_DISK_1: starting archived log copy
    input archived log thread=1 sequence=224 RECID=312 STAMP=790695384
    output file name=+DG_075_FRA01/ub305/archivelog/2012_08_07/thread_1_seq_224.267.790695393 RECID=0 STAMP=0
    channel ORA_DISK_1: archived log copy complete, elapsed time: 00:00:01
    channel ORA_DISK_1: starting archived log copy
    input archived log thread=2 sequence=91 RECID=313 STAMP=790695386
    output file name=+DG_075_FRA01/ub305/archivelog/2012_08_07/thread_2_seq_91.283.790695393 RECID=0 STAMP=0
    channel ORA_DISK_1: archived log copy complete, elapsed time: 00:00:01
    Finished backup at 07-AUG-2012 13:36:34
    searching for all files in the recovery area
    List of Files Unknown to the Database
    =====================================
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_220.279.790692475
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_221.312.790692477
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_222.311.790692479
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_2_seq_89.310.790692479
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_2_seq_89.309.790694525
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_2_seq_90.261.790694527
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_223.262.790694527
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_223.299.790695391
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_224.267.790695393
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_2_seq_91.283.790695393
    File Name: +dg_075_fra01/UB305/CONTROLFILE/Current.289.790692289
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_220.279.790692475
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_221.312.790692477
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_222.311.790692479
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_2_seq_89.310.790692479
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_2_seq_89.309.790694525
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_2_seq_90.261.790694527
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_223.262.790694527
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_223.299.790695391
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_1_seq_224.267.790695393
    File Name: +dg_075_fra01/UB305/ARCHIVELOG/2012_08_07/thread_2_seq_91.283.790695393
    List of Files Which Where Not Cataloged
    =======================================
    File Name: +dg_075_fra01/UB305/CONTROLFILE/Current.289.790692289
    RMAN-07517: Reason: The file header is corrupted
    datafile 1 switched to datafile copy
    input datafile copy RECID=17 STAMP=790695395 file name=+DG_075_DATA01/ub305/datafile/system.322.790695353
    datafile 2 switched to datafile copy
    input datafile copy RECID=18 STAMP=790695395 file name=+DG_075_DATA01/ub305/datafile/sysaux.321.790695359
    datafile 3 switched to datafile copy
    input datafile copy RECID=19 STAMP=790695395 file name=+DG_075_DATA01/ub305/datafile/undotbs1.319.790695373
    datafile 4 switched to datafile copy
    input datafile copy RECID=20 STAMP=790695395 file name=+DG_075_DATA01/ub305/datafile/users.316.790695377
    datafile 5 switched to datafile copy
    input datafile copy RECID=21 STAMP=790695395 file name=+DG_075_DATA01/ub305/datafile/undotbs2.315.790695381
    datafile 6 switched to datafile copy
    input datafile copy RECID=22 STAMP=790695395 file name=+DG_075_DATA01/ub305/datafile/ata_mds.314.790695383
    datafile 7 switched to datafile copy
    input datafile copy RECID=23 STAMP=790695395 file name=+DG_075_DATA01/ub305/datafile/ata_apm.320.790695367
    datafile 8 switched to datafile copy
    input datafile copy RECID=24 STAMP=790695395 file name=+DG_075_DATA01/ub305/datafile/ts001_rsa.ora
    contents of Memory Script:
    set until scn 8950952;
    recover
    clone database
    delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 07-AUG-2012 13:36:35
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=191 device type=DISK
    starting media recovery
    archived log for thread 1 with sequence 224 is already on disk as file +DG_075_FRA01/ub305/archivelog/2012_08_07/thread_1_seq_224.267.790695393
    archived log for thread 2 with sequence 91 is already on disk as file +DG_075_FRA01/ub305/archivelog/2012_08_07/thread_2_seq_91.283.790695393
    archived log file name=+DG_075_FRA01/ub305/archivelog/2012_08_07/thread_1_seq_224.267.790695393 thread=1 sequence=224
    archived log file name=+DG_075_FRA01/ub305/archivelog/2012_08_07/thread_2_seq_91.283.790695393 thread=2 sequence=91
    media recovery complete, elapsed time: 00:00:01
    Finished recover at 07-AUG-2012 13:36:38
    Oracle instance started
    Total System Global Area 21512572928 bytes
    Fixed Size 2235984 bytes
    Variable Size 11005854128 bytes
    Database Buffers 10468982784 bytes
    Redo Buffers 35500032 bytes
    contents of Memory Script:
    sql clone "alter system set db_name =
    ''UB305'' comment=
    ''Reset to original value by RMAN'' scope=spfile";
    sql clone "alter system reset db_unique_name scope=spfile";
    shutdown clone immediate;
    startup clone nomount;
    executing Memory Script
    sql statement: alter system set db_name = ''UB305'' comment= ''Reset to original value by RMAN'' scope=spfile
    sql statement: alter system reset db_unique_name scope=spfile
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area 21512572928 bytes
    Fixed Size 2235984 bytes
    Variable Size 11005854128 bytes
    Database Buffers 10468982784 bytes
    Redo Buffers 35500032 bytes
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "UB305" RESETLOGS ARCHIVELOG
    MAXLOGFILES 192
    MAXLOGMEMBERS 3
    MAXDATAFILES 1024
    MAXINSTANCES 32
    MAXLOGHISTORY 292
    LOGFILE
    GROUP 1 ( '+dg_075_fra01', '+dg_305_data01' ) SIZE 100 M REUSE,
    GROUP 2 ( '+dg_075_fra01', '+dg_305_data01' ) SIZE 100 M REUSE
    DATAFILE
    '+DG_075_DATA01/ub305/datafile/system.322.790695353'
    CHARACTER SET AL32UTF8
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 08/07/2012 13:37:18
    RMAN-05501: aborting duplication of target database
    RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
    ORA-00349: failure obtaining block size for '+dg_305_data01'
    ORA-15001: diskgroup "DG_305_DATA01" does not exist or is not mounted

  • Problem about tdp for sap rman error

    I installed tdp for sap and scheduled a online backup , after the backup finished, I checked the log.
    all data files were backuped successfully. but there is an error about rman. I do not know how to do about that? Could you help me? I think the backup could be successful without rman, why in the backup log, it shows a rman error .
    I checked the initDEV.sap and initDEV.utl, there is no entry about rman, I do not use rman_util.
    BR0530I Cataloging backups of all database files...
    BR0278E Command output of 'SHELL=/bin/sh /oracle/DEV/102_64/bin/rman nocatalog':
    Recovery Manager: Release 10.2.0.4.0 - Production on Sun Mar 8 13:34:21 2009
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    RMAN>
    RMAN> connect target *
    connected to target database: DEV (DBID=3672496816)
    using target database control file instead of recovery catalog
    RMAN> *end-of-file*
    RMAN>
    host command complete
    RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32>
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of catalog command on default channel at 03/08/2009 13:34:23
    ORA-19564: error occurred writing 8192 bytes at block number 1
    ORA-27091: unable to queue I/O
    ORA-27041: unable to open file
    IBM AIX RISC System/6000 Error: 13: Permission denied
    Additional information: 3
    RMAN>
    Recovery Manager complete.
    BR0280I BRBACKUP time stamp: 2009-03-08 13.34.23
    BR0279E Return code from 'SHELL=/bin/sh /oracle/DEV/102_64/bin/rman nocatalog': 1
    BR0536E RMAN call for database instance DEV failed
    BR0280I BRBACKUP time stamp: 2009-03-08 13.34.23
    BR0532E Cataloging backups of all database files failed

    Hello Victor,
    we need the RMAN commands that were executed and at which step this error occurs.
    Maybe it is a problem with the snap controlfile for the AUTOBACKUP or many other scenarios are possible.
    We are also using the TDP for mySAP, but without RMAN support.
    If you want to use just RMAN (like we do for non-SAP systems / no BR*Tools) you can save a lot of license/service costs, if you are using TDP for Oracle, but keep in mind that you are losing the support for that by SAP. You can directly open a call by oracle for these situations.
    If you want this scenario as described we need more detailed information. Maybe a "LIST BACKUP" would also be nice.
    Regards
    Stefan

  • BACKUP AND RECOVERY USING RMAN

    제품 : ORACLE SERVER
    작성날짜 : 2003-08-04
    BACKUP AND RECOVERY USING RMAN
    ==============================
    1. Backup Method
    1.1 backing up in noarchivelog mode
    SVRMGR> shutdown;
    SVRMGR> startup mount
    rman을 가동시킨 후 다음을 수행
    run {
    # backup the database to disk
    allocate channel dev1 type disk;
    backup (database format '/oracle/backups/bp_%s_%p'); }
    1.2 Backing up databases and tablespaces in archivelog mode >
    - database 단위 backup script
    run {
    allocate channel dev1 type 'sbt_tape';
    backup skip offline (database format '/oracle/backups/%d_%u');
    release channel dev1;
    - tablespace 단위 backup script
    run {
    allocate channel dev1 type disk;
    backup
    (tablespace system,tbs_1,tbs_2,tbs_3,tbs_4,tbs_5
    format '/oracle/backups/bp_%s_%p');
    - datafile 단위 backup script
    run { 
    allocate channel dev1 type disk;
    backup
    (datafile '?/dbs/t_dbs1.f'
    format '/oracle/backups/%d_%u');
    - control file backup script
    control file은 system datafile의 첫번째 화일을 백업받을 때 백업되며 다음과
    같은 방법으로도 백업받을 수 있다.
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (tablespace tbs_5 include current controlfile
    format '%d_%u');
    - archived logs backup script
    NLS_LANG=american
    NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (archivelog from time 'Nov 13 1996 20:57:13'
    until time 'Nov 13 1996 21:06:05'
    all
    format '%d_%u');
    run {
    allocate channel dev1 type 'sbt_tape';
    backup
    (archivelog low logseq 288 high logseq 301 thread 1
    all delete input
    format '%d_%u');
    - copying datafiles
    run {
    allocate channel dev1 type disk;
    copy datafile '?/dbs/tbs_01.f/dbs/tbs_01.f' to '?/copy/temp3.f';
    - incremental backups
    새로운 데이타화일이 추가되거나 테이블스페이스가 추가된다면 level 0의 backup을
    반드시 수행한다.
    run {
    allocate channel dev1 type 'sbt_tape';
    backup incremental level 0
    (database
    format '%d_%u');
    run {
    allocate channel dev1 type 'sbt_tape';
    backup incremental level 1
    (database
    format '&d_%u');
    2. Recovery Method
    - tablespace recovery
    run { 
    allocate channel dev1 type disk;
    allocate channel dev2 type 'sbt_tape';
    sql "alter tablespace tbs_1 offline immediate" ;
    set newname for datafile 'disk7/oracle/tbs11.f'
    to 'disk9/oracle/tbs11.f' ;
    restore (tablespace tbs_1) ;
    switch datafile all ;
    recover tablespace tbs_1 ;
    sql "alter tablespace tbs_1 online" ;
    release channel dev1;
    release channel dev2;
    - point-in-time recovery
    TBS_1 테이블스페이스는 두 개의 데이타 화일 소유. TEMP1은 백업이 없으나 user
    data는 없는 temporary segemnt만 가지고 있음.
    NLS_LANG=american
    NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
    SVRMGR> shutdown abort;
    SVRMGR> startup nomount;
    run { 
    # recover database until 3pm after restoring tbs_1 to a new location
    allocate channel dev1 type disk;
    allocate channel dev2 type 'sbt_tape';
    set until time 'Nov 15 1996 15:00:00'
    set newname for datafile '/vobs/oracle/dbs/tbs_11.f'
    to '?/dbs/temp1.f' ;
    set newname for datafile '?/dbs/tbs_12.f'
    to '?/dbs/temp2.f' ;
    restore controlfile to '/vobs/oracle/dbs/cf1.f' ;
    replicate controlfile from '/vobs/oracle/dbs/cf1.f';
    sql "alter database mount" ;
    restore database skip tablespace temp1;
    switch datafile all;
    recover database skip tablespace temp1;
    sql "alter database open resetlogs";
    sql "drop tablespace temp1";
    sql "create tablespace temp1 datafile '/vobs/oracle/dbs/temp1.f' size 10M";
    release channel dev1;
    release channel dev2;
    - 전체 데이타베이스를 복구하려 할때
    current redologfile이 존재할때 다음과 같은 작업으로 전체 데이타베이스를 복구할
    수 있다.
    replace script restore_recover_db_cf {
    execute script restore_cf;
    sql 'alter database mount';
    execute script restore_db;
    execute script recover_db;
    sql 'alter database open resetlogs';
    replace script alloc_1_disk {
    allocate channel d1 type disk;
    setlimit channel d1 kbytes 2097150 maxopenfiles 32 readrate 200;
    replace script rel_1_disk {
    release channel d1;
    replace script restore_cf {
    execute script alloc_1_disk;
    restore
    controlfile to '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
    replicate
    controlfile from '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
    execute script rel_1_disk;
    replace script restore_db {
    execute script alloc_1_disk;
    restore
    (database);
    execute script rel_1_disk;
    replace script recover_db {
    execute script alloc_1_disk;
    recover
    database;
    execute script rel_1_disk;
    Reference Documents
    <Note:104796.1>

    Hi Alok,
    why there is a need for standby here? you mean to say standby db?
    what i exactly need is , whether i will be making use of archivelogs which are all archived during that backup period (in mount stage) after some days, if i face any problem with the PRODUCTION Database..

  • Problem in Backup/Recovery 10g

    Hi
    I am Trying to Take Backup in Oracle 10g ........
    RMAN > Configure retention policy to recovery window of 4 days
    RMAN > configure controlfile autobackup on;
    RMAN > Configure device type disk backup type to compressed backupset;
    RMAN> backup as backupset database spfile;
    Starting backup at 14-MAR-07
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/14/2007 10:20:
    49
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    continuing other job steps, job failed will not be re-run
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current controlfile in backupset
    including current SPFILE in backupset
    channel ORA_DISK_1: starting piece 1 at 14-MAR-07
    channel ORA_DISK_1: finished piece 1 at 14-MAR-07
    piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2007_03
    _14\O1_MF_NCSNF_TAG20070314T102048_2ZGY13BK_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current SPFILE in backupset
    channel ORA_DISK_1: starting piece 1 at 14-MAR-07
    channel ORA_DISK_1: finished piece 1 at 14-MAR-07
    piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2007_03
    _14\O1_MF_NNSNF_TAG20070314T102048_2ZGY15PK_.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/14/2007 10:20:
    49
    I can identefy the Problem .

    Your database is running in NOARCHIVELOG mode. You cannot make an online backup.
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

  • ORACLE8: RECOVERY MANAGER 사용 방법(RMAN)

    제품 : ORACLE SERVER
    작성날짜 : 1997-11-17
    Oracle 8 NEW : Recovery manager 란 ?
    ====================================
    - 소개
    Oracle 8 은 새로운 backup와 recovery 방법인 Recovery manager 를 제공한다.
    Recovery manager(이하 RMAN) 는 backup,restore,recover process를 관리하는
    tool 이다. Oracle Enterprise Manager 를 통해 GUI mode 로 가능하고,
    rman 이라는 command line interface 를 함께 제공한다.
    특히, OS device control 기능이 보완 되었기 때문에, 현재 backup catalog 를
    유지하고, 이 정보를 이용해 OS level 에서 file 을 auto-restore 해 주기
    때문에, database recovery 전에 file 을 manual 하게 restore 할 필요가
    없어졌다.
    Incremental backup 을 제공하고, backup 이나 restore 중에 current block
    detection 을 해 주며(v$backup_corruption, v$copy_corruption 또는 alert
    log 에 report), Rman 작업시에 parallelization 을 제공하며, open database
    backup 동안 특별한 redo 를 발생하지 않는다.
    - 구조
    Recovery               
    manager in OEM(oracle          
              enterprise      ---> Database
              manager) <---     (catalog)          
    or RMAN
         /| |
         | |/
    DATABASE     ---> OS
    (target to backup) <--- Device
    - 구성 요소 설명
    1) recovery manager
    Command 를 해석하고, backup, restore, recover 를 실행하기 위해 target
    database 로 command 를 전달한다. recovery catalog 를 update 한다. 실행
    과정을 조정, 모니터링 한다.
    2) Target database
    backup,restore,recovery action 이 수행될 데이타베이스
    3) Recovery Catalog
    Information 저장장소. 즉, target database 의 물리적 스키마, datafile 과
    archivelog 의 backup sets 과 pieces, backup script 등을 포함하고 있음.
    rman 작업시 recovery catalog 정보를 이용한다.
    4) channel
    allocation channel 은 target database 의 backup,restore,recover 에 대한
    server process 초기화를 한다. 즉, 이 channel 은 disk 를 포함 기타 OS
    device 를 지정하게 되며, 이 갯수에 따라 parallelization 의 degree 가 결정
    된다.
    - recovery catalog 를 사용할 것인지를 결정하기
    catalog 없이 RMAN 을 사용할 때의 단점은 recovery catalog 의 overhead 가
    없는 대신, Point-In-Time recovery 를 쉽게 할 수 없다. 또한, control file
    손상시에 recovery 할 수 없고, stored script 를 사용할 수 없다.
    (datafile 이 20개 이상일 경우에는 recovery catalog 사용을 권장한다.)
    - Setup
    가. Recovery catalog 생성
    1. Backup(target) db 외의 별도의 db 생성 (8.0.3 이상)
    2. catalog DB 에 분리된 tablespace 생성
    create tablespace rcvcat datafile '/oracle/rcvcat/rcvcat01.dbf'
    size 20 M;
    3. catalog 의 owner 생성과 권한부여
         create user rman identified by rman
         temporary tablespace temp
         default tablespace rcvcat;
         grant dba,connect,resource,recovery_catalog_owner to rman;
    4. catalog 저장에 필요한 object 생성
         cd $ORACLE_HOME/rdbms/admin
         sqlplus rman/rman
         @catrman
    나. Recovery manager 기동
    1. recovery catalog DB 를 사용하는 경우
    rman target \"system/manager\" rcvcat \"rman/rman@orabeta1\"
    (orabeta1 은 catalog DB 로 접속하는 tnsname 입니다.
    즉, sqlplus rman/rman@orabeta1 하면, catalog db 와 접속되어야 합니다.)
    2. recovery catalog DB 를 사용하지 않는 경우
    rman target system/manager@target nocatalog
    위 경우 모두, target database 를 catalog 에 등록해야 한다.
    RMAN> register database;
    다. Backup 시작
    - Backup 은 database 가 open 또는 close(close 후에는 반드시 mount
    상태이어야 한다)
    - Backup 의 단위
         full database
         tablespace
         datafile
         control file
         archived logs
    - Backup 의 예
    --full database
    run { 
    allocate channel dev1 type disk;
    allocate channel dev2 type disk;
    backup full filesperset 2
    (database format '/user7/ora8/backup.%n_%p') ;
    release channel dev1;
    release channel dev2;
    -- tablespace
    run {
    allocate channel dev_1 type disk ;
    backup incremental level 0
    filesperset 1
    (tablespace system channel dev_1 format '/vol312/net8%d_%u');
    release channel dev_1;
    -- datafile
    run{ 
    allocate channel dev1 type disk;
    copy datafile "/vo3/orabeta6/backup/copy_tools.dbf"
    to "/vo3/orabeta6/oradata/orabeta6/tools01.dbf"
    tag "org_tools";
    release channel dev1;
    -- archived logs
    create script beta_arch_full { 
    allocate channel dev1 type disk;
    allocate channel dev2 type disk;
    backup full filesperset 10
    (archivelog all delete input
    format '/vo3/orabeta6/backup/beta_arch.%s_%p') ;
    release channel dev1;
    release channel dev2;
    -- backup to tape
    run {
    allocate channel t1 type 'sbt_tape';
    backup
    format 'dbfull_sunday_s%s_t%t'
    tag 'Sunday full backup'
    (database);
    라. Restore
    - Backup 으로 부터 원래 위치로 복원
    - Archive log file 은 manual 하게 restore 할 수도 있고, 필요하다면
    recovery 시 자동으로 restore 된다.
    restore (archivelog all| like <filename | <archivelog range>);
    - restore 명령
    database : restore (database);
    tablespace : restore (tablespace <name>,...,<name>);
    datafile : restore (datafile <name>,...,<name>);
    control file : restore control file to location;
    - recovery 시에 database 는 어떤 상태에 있어야 하는가 ?
    1) control file restore - not mount
         SVRMGRL> startup nomount
    2) whole database, or system tablespace - not open
         SVRMGRL> startup mount
    3) tablespace or datafile - open but tablespace or datafile offline
         SVRMGRL> alter tablespace user_data offline temporary;
         SVRMGRL> alter database datafile '/oracle/file/user_data1.dbf'           offline;
    마, Recovery
    - Recoervy 는 file restore 후의 과정이다.
    1) Archive log mode : complete recovery, incomplete recovery 가 가능하다     
    2) No archive log mode : consistent whole database backup 으로 부터
    restore 하는 것이 유일한 option 이다.
    - whole database recovery 의 예
    svrmgrl
    connect internal
    shutdown abort
    startup mount
    rman target \"system/manager\" rcvcat \"rman/rman@orabeta1\"
    run {
    allocate channel dev1 type disk;
    allocate channel dev2 type disk;
    restore database;
    recover database;
    release channel dev1;
    release channel dev2;
    or
    run {
    allocate channel dev1 type disk;
    allocate channel dev2 type disk;
    restore tablespace 'SYSTEM';
    restore tablespace 'USERS';
    recover tablespace 'SYSTEM';
    recover tablespace 'USERS';
    sql "alter database open ";
    release channel dev1;
    release channel dev2;
    - datafile 하나가 사용할 수 없을 경우의 recovery
    가정) full backup set 이 있을 경우
    ORA-01157: cannot identify data file 3 - file not found
    ORA-01110: data file 3: '/user7/ora8/oradata/ORA8/temp01.dbf'
    SVRMGR> startup mount
    rman target \"system/manager\" rcvcat \"rman/rman@orabeta1\"
    RMAN> run {
    allocate channel dev1 type disk;
    restore database;
    recover database;
    release channel dev1;
    };

    Check the TSM logs for errors, the error stack here doesn't show any useful information (only informational messages and an undefined exit code). This is an 8i problem, later releases transfer much better messages from the media management software.

  • Database recovery - Thiry party tool

    Please let me know if there are any third party applications available that can be used in data recovery process in Oracle ?
    Thanks
    Matt.

    Matt wrote:
    @Aman...
    Your reply does not help me .
    I know about RMAN.
    Edited by: Matt on May 21, 2011 5:00 AMAnd rman is all you need to know about oracle backup.
    But if you insist on discovering other tools, google is your friend. But I would caution you, these tools fall into one of two catagories
    The first are tools that are really just providing a menu or gui front-end to calling rman, providing a bit friendlier interface to rman. These are expensive solutions in search of a problem.
    The second discard rman completely, thinking they are smarter than oracle about how to back up an oracle database. If you use these products, you'd better be very, VERY good at oracle recovery, because when the excrement hits the ventilation system, Oracle Support will not provide much, if any, help.
    But of course, since you are, by your own admission, just a student, you won't be able to afford any of these tools anyway.

  • Database Recovery Urgent

    Dear All
    I have take (Oracle 10.2.0) complete backup using RMAN, Now i lost media (HardDisk) and cannot recover existing database.
    Please guide me how i can register and recover database on new server using two days old full RMAN backup.
    Backup on DVD is doing this script.
    RMAN> RUN { ALLOCATE CHANNEL C1 TYPE DISK;
    BACKUP DATABASE FORMAT 'F:\RMAN\SID_%d_%T_%s';
    Thanks
    Edited by: Naeem Sheeraz on Dec 20, 2008 3:04 PM

    You have to install the same version of oralce with same directory structure and with same instance name on other machine.
    You may create the old instance by OS laterz after installing the oracle.
    C:\>oradim -new -sid orcl
    Instance created.
    after instance creation ,create password file by using orapwd utility
    C:\>orapwd file=C:\oracle\product\10.1.0\Db_2\database\PWDorcl.ora password=sys
    put alls backup files from FRA which is in tape cartridge to its respected location.
    Connect to RMAN
    C:\>rman
    Recovery Manager: Release 10.1.0.2.0 - Production
    Copyright (c) 1995, 2004, Oracle.  All rights reserved.
    RMAN> connect target sys/sys
    connected to target database (not started)
    RMAN>
    RMAN> startup force nomount
    startup failed: ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file 'C:\ORACLE\PRODUCT\10.1.0\DB_2\DATABASE
    \INITORCL.ORA'
    trying to start the Oracle instance without parameter files ...
    Oracle instance started
    Total System Global Area     113246208 bytes
    Fixed Size                      787708 bytes
    Variable Size                 61602564 bytes
    Database Buffers              50331648 bytes
    Redo Buffers                    524288 bytesput the previous backup within the same location as it was an old machine
    If you have autobackup on configuration then
    RMAN> restore spfile from 'yoursspfilebackup'
    2> ;
    Starting restore at 09-APR-08
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=29 devtype=DISK
    channel ORA_DISK_1: autobackup found: C:\oracle\product\10.1.0\flash_recovery_ar
    ea\ORCL\AUTOBACKUP\2008_04_09\O1_MF_S_651605789_3ZSG2GHX_.BKP
    channel ORA_DISK_1: SPFILE restore from autobackup complete
    Finished restore at 09-APR-08
    RMAN> shutdown immediate
    Oracle instance shut down
    C:\>rman
    Recovery Manager: Release 10.1.0.2.0 - Production
    Copyright (c) 1995, 2004, Oracle.  All rights reserved.
    RMAN> connect target sys/sys
    connected to target database (not started)
    RMAN> startup
    Oracle instance started
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of startup command at 04/09/2008 18:17:41
    ORA-00205: error in identifying controlfile, check alert log for more info
    RMAN> restore controlfile from autobackup
    2> ;
    Starting restore at 09-APR-08
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=160 devtype=DISK
    recovery area destination: C:\oracle\product\10.1.0\flash_recovery_area
    database name (or lock name space) used for search: ORCL
    channel ORA_DISK_1: autobackup found in the recovery area
    channel ORA_DISK_1: autobackup found: C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AR
    EA\ORCL\AUTOBACKUP\2008_04_09\O1_MF_S_651605800_3ZSG2SLS_.BKP
    channel ORA_DISK_1: controlfile restore from autobackup complete
    output filename=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\CONTROL01.CTL
    output filename=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\CONTROL02.CTL
    output filename=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\CONTROL03.CTL
    Finished restore at 09-APR-08
    RMAN> startup mount
    database is already started
    database mounted
    RMAN> restore database;
    RMAN> recover database;Khurram

  • Create a database from 8i RMAN backup

    Hi,
    I am in need to recover some historic data from a historic database's RMAN backup.
    The situation is ... I have one old RMAN backup of a 8i database which includes datafiles, archivellog files and control files. Init.ora file is also available.
    I have installed the 8i software in a host and created the oracle service through ORADIM and pwd file through ORAPWD utility. Then copied the init.ora file under 'C:\Oracle\ADMIN\ORCL\PFILE' and the RMAN backup files under 'C:\Oracle\Ora81\DATABASE' folder.
    Now I can start the instance with the init.ora file but can not mount as control files are not there. when I try to restore the control files through RMAN as...
    RMAN> run
    2> {
    3> restore controlfile;
    4> }
    RMAN-03022: compiling command: restore
    RMAN-03022: compiling command: IRESTORE
    RMAN-03026: error recovery releasing channel resources
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: restore
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: IRESTORE
    RMAN-06172: not connected to recovery catalog database
    RMAN>
    Now without the catalog database how can I restore the control files and the database from the RMAN backup?
    I think the old RMAN metadata was stored in catalog database.
    Any suggestion please?
    regards

    Sorry I wrongly said that I do not have the DBID, I have DBID but I have controlfile backup as RMAN backupset, not in Binary. So even if I set DBID, RMAN asks for the catalog database, which is not available.
    As I worked...
    C:\>rman
    Recovery Manager: Release 8.1.5.0.0 - Production
    RMAN> SET DBID=1208994555
    RMAN-03022: compiling command: CSET
    RMAN> connect target sys/*****
    RMAN-06193: connected to target database (not started)
    RMAN> startup nomount
    RMAN-06196: Oracle instance started
    Total System Global Area 552011724 bytes
    Fixed Size 65484 bytes
    Variable Size 69357568 bytes
    Database Buffers 482514944 bytes
    Redo Buffers 73728 bytes
    RMAN> run
    2> {
    3> allocate channel ch1 type disk;
    4> restore controlfile;
    5> alter database mount;
    6> }
    RMAN-03022: compiling command: allocate
    RMAN-03026: error recovery releasing channel resources
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: allocate
    RMAN-06172: not connected to recovery catalog database
    RMAN> shutdown
    RMAN-06402: Oracle instance shut down
    RMAN> set dbid 1208994555
    RMAN-03022: compiling command: CSET
    RMAN> connect target sys/*** nocatalog
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01005: syntax error: found "nocatalog": expecting one of: "newline, ;"
    RMAN-01007: at line 1 column 27 file: standard input
    RMAN> connect target sys/**** nocatalog;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01005: syntax error: found "nocatalog": expecting one of: "newline, ;"
    RMAN-01007: at line 1 column 27 file: standard input
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01005: syntax error: found ";": expecting one of: "allocate, alter, beginli
    ne, catalog, change, connect, create, crosscheck, debug, delete, drop, exit, end
    inline, host, {, library, list, mount, open, print, register, release, replace,
    report, reset, resync, rman, rpctest, run, set, sql, "
    RMAN-01007: at line 1 column 36 file: standard input
    RMAN> exit
    Recovery Manager complete.
    C:\>rman target sys/**** nocatalog
    Recovery Manager: Release 8.1.5.0.0 - Production
    RMAN-06193: connected to target database (not started)
    RMAN> run{
    2> allocate channel ch1 type disk;
    3> restore controlfile;
    4> alter database mount;
    5> }
    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: ch1
    RMAN-08500: channel ch1: sid=12 devtype=DISK
    RMAN-03022: compiling command: restore
    RMAN-03022: compiling command: IRESTORE
    RMAN-03026: error recovery releasing channel resources
    RMAN-08031: released channel: ch1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: restore
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: IRESTORE
    RMAN-06003: ORACLE error from target database: ORA-01507: database not mounted
    ORA-06512: at "SYS.X$DBMS_RCVMAN", line 923
    ORA-06512: at line 1
    RMAN-06097: text of failing SQL statement: begin dbms_rcvman . setDatabase ( upp
    er ( :dbname:dbname_i ) , :rlscn , :rltime , :fhdbi:fhdbi_i ) ; end ;
    RMAN>

  • Physical Standby Database Creation with RMAN

    Hi,
    I'm in 10g on Linux. I want to create a standby database on another Linux server. I did not find a clear procedure to create it in Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02
    and niether in Oracle® Data Guard Concepts and Administration 10g Release 2 (10.2) B14239-04
    In the last one chapter 3 sends you to F appendix and F appendix says do nothing before having than all in chapter 3 :
    In F.1.1 page F-2 it is said :
    See Chapter 3 for a complete discussion of physical standby database preparation,including initialization parameter settings. You must perform all necessary preparation tasks described in these chapters before RMAN can successfully create the standby database files and mount the standby database.
    Any way I'm looking for a procedure or clear article to create it.
    Many thanks before.

    Physical Standby Database Creation with RMAN
    Use the DUPLICATE command.
    Check out this metalink doc: Note:374069.1 and Note:118409.1
    Message was edited by:
    STW
    Message was edited by:
    STW

  • Failure during database recovery on Homogeneous System Copy

    Dear all,
    i am trying to do system copy, and it fails after the execution step:  database recovery
    MaxDB: 7.6.5.15
    SAP Netweaver 7 Ehp 1
    apparantly this is something to do with LOAD_SYSTAB.
    I could run load_systab [-u <sysdba_user>,<sysdba_user_password>] manually, but the Log file of SAPinst shows the following:
    WARNING[E] 2009-09-28 17:17:57.328
               CJSlibModule::writeError_impl()
    The dbmcli call for action LOAD_SYSTAB failed. SOLUTION: Check the logfile XCMDOUT.LOG.
    TRACE      2009-09-28 17:17:57.546 [iaxxejsbas.hpp:408]
               handleException<ESAPinstJSError>()
    Converting exception into JS Exception EJSException.
    TRACE      2009-09-28 17:17:57.562
    Function setMessageIdOfExceptionMessage: dbmodada.actorext.dbmcliCallFailed
    WARNING[E] 2009-09-28 17:17:57.562
               CJSlibModule::writeError_impl()
    The dbmcli call for action LOAD_SYSTAB failed. SOLUTION: Check the logfile XCMDOUT.LOG.
    TRACE      2009-09-28 17:17:57.562 [iaxxejsbas.hpp:483]
               EJS_Base::dispatchFunctionCall()
    JS Callback has thrown unknown exception. Rethrowing.
    ERROR      2009-09-28 17:17:57.781 [sixxcstepexecute.cpp:950]
    FCO-00011  The step sdb_instance_load_systables with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|ind|4|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|sdb_instance_load_systables was executed with status ERROR .
    TRACE      2009-09-28 17:17:58.93 [iaxxgenimp.cpp:752]
                CGuiEngineImp::showMessageBox
    <html> <head> </head> <body> <p> An error occurred while processing option SAP NetWeaver 7.0 including Enhancement Package 1 Support Release 1 > Software Life-Cycle Options > System Copy > MaxDB > Target System Installation > Central System > Based on AS ABAP > Central System. You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/NW701/LM/COPY/ADA/SYSTEM/CENTRAL/AS-ABAP/. </p> </body></html>
    TRACE      2009-09-28 17:17:58.109 [iaxxgenimp.cpp:1255]
               CGuiEngineImp::acceptAnswerForBlockingRequest
    Waiting for an answer from GUI
    XCMDOUT.LOG shows only the SAP users data from the source system, and not for the target system which is having the error.
    Could somebody please advise me what to do?
    Thank you,
    Mariana

    Dear Christian,
    yes, I solved this LOAD_SYSTAB problem.
    This is what I did:
    1. check XCMDOUT.LOG
    2. However in my case, I did not see any clue there, so I read this link about LOAD_SYSTAB http://maxdb.sap.com/doc/7_7/45/11cbd6459d7201e10000000a155369/content.htm
    I tried it manually, and it worked: dbmcli u2013d <DB_ID> u2013u DBMUser,password1 load_systab u2013u superdba,password2
    From there, I know that I entered the wrong SYSADM User (superdba) password, this password was in my case the same one a SAPinst Master Password.
    According to https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=25591
    a new installation of MaxDB database, by default, the credential for SYSADM is: "superdba,admin"
    So, accordingly, the solution is:
    change the SYSADM for the <DB_ID> in DBMGUI: D7D - Configuration - Database User area, exactly as the SAPinst Master Passwort.
    Hope this helps.
    Regards,
    Mariana

Maybe you are looking for

  • WLC 5508 and Cisco Aironet 1242 LWAPP AIR-LAP1242AG-A-K9

    i have deployed wlc 5508 ( image 7.0.98.0 ) with 1262N AP and all 45 AP's are working fine, at the same site i had AP1242 which i have converted to LWAPP (8 of them), these accesspoint are registerd perfectly with 5508 but non of the radio's are up.

  • I CAN'T DOWNLOAD YAHOO MESSENGER ON MY NEW MAC AIR BOOK

    I CAN'T OPEN THE YAHOO APPLICATION ON MY NEW MAC AIR BOOK WITH OS X SEVER .

  • Integration of Fiori with SMP

    Hello Fiori und SMP experts, cann somebody answer mir the following questions please Since which version of SMP is the integration of Fiori possible? Is it possible to integrate a Fiori-App with SMP directly without SAP Fiori Client? Thanks a lot in

  • Error in ATP checking

    Hi All, Could you please check the below screen and help me clear the doubts in ATP process. For one item, the existing stock is 1,304,480 PCE and the Production orders (the product end date is tomorrow ). The question is even though the ready stock

  • How to fixs unknown error 1611

    how to fixs unknown error 1611