1 Reply Latest reply: Sep 9, 2012 11:53 PM by pinrell RSS

Problems Creating Clone in SnapManager Oracle (Not Working)

pinrell
Currently Being Moderated

Hi all

I have a problem and would like to know if anyone has happened at some point.
I have AIX 5.3 with Oracle 11g and Oracle SnapDrive 3.2 and SnapManager 4.2
The problem I have when I try to create a clone of my Backup, the backup is correct and verified.
Apparently the process is done correctly showing the following steps.

 

--[ INFO] SMO-13036: Starting operation Clone Create on host saptest2.mecalux.com

--[ INFO] SMO-13046: Operation GUID 402881ab3990b4e2013990b4ed7c0001 starting on Profile BCKT02

--[ INFO] SMO-04030: Validating uniqueness of new SID "T99".

--[ INFO] SMO-04040: Using ORACLE_HOME of "/oracle/T02/11203" from clonespec for clone.

--[ INFO] SMO-04042: Using Oracle OS account "orat02" from clonespec for clone.

--[ INFO] SMO-04044: Using Oracle OS group "dba" from clonespec for clone.

--[ INFO] SMO-07127: Locked database for SnapManager operations - created lock file "/oracle/T02/11203/dbs/.sm_lock_T99" on host saptest2.mecalux.com.

--[ INFO] SD-00025: Beginning to connect filesystem(s) [/oracle/T02/sapdata1] from snapshot smo_bckt02_t02_f_h_1_402881ab3990a6af013990a6b9640001_0.

--[ INFO] SD-00016: Discovering storage resources for /oracle/T02/sapdata1_T99.

--[ INFO] SD-00017: Finished storage discovery for /oracle/T02/sapdata1_T99.

--[ INFO] SD-00026: Finished connecting filesystem(s) [/oracle/T02/sapdata1] from snapshot smo_bckt02_t02_f_h_1_402881ab3990a6af013990a6b9640001_0.

--[ INFO] ORACLE-00502: Adding entry for database T99 in /etc/oratab.

--[ INFO] SMO-07300: Beginning clone of database "T02" to SID "T99" on host "saptest2.mecalux.com".

--[ INFO] SMO-07302: Generating parameter file for "T99" at "/oracle/T02/11203/dbs/initT99.ora".

--[ INFO] SMO-07303: Generating password file for "T99" at "/oracle/T02/11203/dbs/orapwT99".

--[ INFO] SMO-07304: Starting up database "T99" in NOMOUNT mode.

--[ INFO] SMO-07305: Generating control files for database "T99".

--[ INFO] SMO-07312: Create Control File - Database: T99.

--[ INFO] SMO-07313: Create Control File - Redolog: /oracle/T02/sapdata1_T99/redo_4_1.log.

--[ INFO] SMO-07313: Create Control File - Redolog: /oracle/T02/sapdata1_T99/redo_1_0.log.

--[ INFO] SMO-07313: Create Control File - Redolog: /oracle/T02/sapdata1_T99/redo_2_1.log.

--[ INFO] SMO-07313: Create Control File - Redolog: /oracle/T02/sapdata1_T99/redo_1_1.log.

--[ INFO] SMO-07313: Create Control File - Redolog: /oracle/T02/sapdata1_T99/redo_3_1.log.

--[ INFO] SMO-07313: Create Control File - Redolog: /oracle/T02/sapdata1_T99/redo_2_0.log.

--[ INFO] SMO-07313: Create Control File - Redolog: /oracle/T02/sapdata1_T99/redo_3_0.log.

--[ INFO] SMO-07313: Create Control File - Redolog: /oracle/T02/sapdata1_T99/redo_4_0.log.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01700_1/p01700.data1.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_5/p01.data5.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_12/p01.data12.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_10/p01.data10.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_9/p01.data9.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01700_4/p01700.data4.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01700_3/p01700.data3.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_8/p01.data8.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_4/p01.data4.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01usr_1/p01usr.data1.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_6/p01.data6.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_1/p01.data1.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_2/p01.data2.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_7/p01.data7.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/system_1/system.data1.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_3/p01.data3.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/sysaux_1/sysaux.data1.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/undo_1/undo.data1.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01700_2/p01700.data2.

--[ INFO] SMO-07314: Create Control File - Datafile: /oracle/T02/sapdata1_T99/p01_11/p01.data11.

--[ INFO] SMO-07306: Generating server parameter file for database "T99" at Oracle default location.

--[ INFO] SMO-07337: Recovering database clone "T99" to a consistent point using archived logs from the backup.

--[ INFO] SMO-04082: Recovering cloned database

--[ INFO] SM0-03054: Mounting backup BackupSep2012 on host saptest2.mecalux.com to feed archivelogs.

--[ INFO] SD-00025: Beginning to connect filesystem(s) [/oracle/T02/oraarch] from snapshot smo_bckt02_t02_f_h_2_402881ab3990a6af013990a6b9640001_0.

--[ INFO] SD-00016: Discovering storage resources for /opt/Ontap/smo/mnt/-oracle-T02-oraarch-20120904115654401_0.

--[ INFO] SD-00017: Finished storage discovery for /opt/Ontap/smo/mnt/-oracle-T02-oraarch-20120904115654401_0.

--[ INFO] SD-00026: Finished connecting filesystem(s) [/oracle/T02/oraarch] from snapshot smo_bckt02_t02_f_h_2_402881ab3990a6af013990a6b9640001_0.

--[ INFO] SM0-03061: Perform recovery using backup BackupSep2012

--[ INFO] SM0-03081: Perform recovery using all connected backups BackupSep2012

--[ INFO] ORACLE-30023: Beginning batch recovery process for database T99.

--[ INFO] ORACLE-30008: Beginning recovery process for database T99.

--[ INFO] ORACLE-30010: Database recovery point objective: earliest consistent point

--[ INFO] ORACLE-30017: Recovery point objective of earliest consistent point reached after applying archived/online redo logs [/opt/Ontap/smo/mnt/-oracle-T02-oraarch-20120904115654401_0/T02arch1_4804_779186134.dbf].

--[ INFO] ORACLE-30024: Finished batch recovery process for database T99.

--[ INFO] SM0-03066: Recovery succeeded.

--[ INFO] SM0-03055: Disconnecting backup BackupSep2012.

--[ INFO] SD-00016: Discovering storage resources for saptest02arcv_0.

--[ INFO] SD-00017: Finished storage discovery for saptest02arcv_0.

--[ INFO] SD-00037: Beginning to disconnect volume groups [saptest02arcv_0].

--[ INFO] SD-00038: Finished disconnecting volume groups [saptest02arcv_0].

--[ INFO] SMO-07320: Opening database "T99" with RESETLOGS option.

--[ INFO] SMO-07316: Shutting down database "T99".

--[ INFO] SMO-07321: Starting up database "T99" in MOUNT mode.

--[ INFO] SMO-07307: Generating new Database ID for "T99".


But, not continuous, it is in this way for hours, someone may sound happens.

If a make a "smo operation list -profile XXXX can be seen as the process takes two days.

 

Start Date           Status     Operation ID                     Type               Host
-------------------- ---------- -------------------------------- ------------------ -----------------------------------
2012-09-04 10:45:42  SUCCESS    402881ab399074e901399075001c000a Profile Create     saptest2.mecalux.com
2012-09-04 11:40:03  SUCCESS    402881ab3990a6af013990a6b9640001 Backup             saptest2.mecalux.com
2012-09-04 11:55:34  RUNNING    402881ab3990b4e2013990b4ed7c0001 Clone              saptest2.mecalux.com
2012-09-04 12:49:48  SUCCESS    402881ab3990e688013990e693cd0001 Remove Clone       saptest2.mecalux.com


If a make a “smo operation show –profile xxxx –id 402881ab3990b4e2013990b4ed7c0001”you can see shows no errors

 

Operation Attempted
  Operation ID: 402881ab3990b4e2013990b4ed7c0001
  Type: Clone
  For profile: BCKT02
  With Force: No
  Label: T99
Performed on backup
  Operation ID: 402881ab3990a6af013990a6b9640001
  Label: BackupSep2012
Operation Runtime Information
  Status: RUNNING
  Start date: 2012-09-04 11:55:34 CEST
  End date:
  Client user: JPinell
  Effective user: snapadm
  By schedule: none
Host
  Host Run upon: saptest2.mecalux.com
  Process ID: 7381054
  SnapManager version: 3.2.0
Repository
  Connection: SnapAdmin@smo/localhost:1527
  Repository version: 320
Error messages
  The operation did not generate any error messages.
Resources In Use
  This operation currently does not have any resources in use.

 

That may be happening?

More Like This

  • Retrieving data ...