Unsolved
This post is more than 5 years old
14 Posts
0
820
Recovery of Oracle 10g after symclone activate
Hi everyone,
Environment:
DMX-3
IBM p595 / AIX 5.3
Oracle 10g R2
Solutions Enabler 6.3.1.1
We are encountering difficulties with recovery of Oracle instances taken using TimeFinder Clone.
Outline process:
symclone -precopy create
symioctl archive log
symioctl begin backup -checkpoint
symioctl freeze -checkpoint
symclone activate -consistent
symioctl thaw
symioctl end backup
symioctl archive log
This approach works perfectly with Timefinder/Mirror and Oracle 8/9 and has been in production for several years.
Our DBAs are unable to open and recover any cloned database, even though they can access all the components they say they require such as archive logs, latest SCN number, cre_control_file etc.
The errors are always something like:
Thu Sep 20 13:41:00 SUM 2007 - INFORMATION - Running recovery script: "/techsymx/hotlogs/recover_db_change_number.sql"
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/techsymx/db01/system01.dbf'
We believe we have eliminated TimeFinder as the culprit as we get the same error regardless of whether the cloning process is in flight, or has finished ( i.e. the -precopy flag has led to 100% of data being copied to the targets before the clone is activated )
Is anybody using this configuration successfully - if so maybe you could suggest where we need to focus our attention ?
Many thanks,
Nick,
UK
Environment:
DMX-3
IBM p595 / AIX 5.3
Oracle 10g R2
Solutions Enabler 6.3.1.1
We are encountering difficulties with recovery of Oracle instances taken using TimeFinder Clone.
Outline process:
symclone -precopy create
symioctl archive log
symioctl begin backup -checkpoint
symioctl freeze -checkpoint
symclone activate -consistent
symioctl thaw
symioctl end backup
symioctl archive log
This approach works perfectly with Timefinder/Mirror and Oracle 8/9 and has been in production for several years.
Our DBAs are unable to open and recover any cloned database, even though they can access all the components they say they require such as archive logs, latest SCN number, cre_control_file etc.
The errors are always something like:
Thu Sep 20 13:41:00 SUM 2007 - INFORMATION - Running recovery script: "/techsymx/hotlogs/recover_db_change_number.sql"
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/techsymx/db01/system01.dbf'
We believe we have eliminated TimeFinder as the culprit as we get the same error regardless of whether the cloning process is in flight, or has finished ( i.e. the -precopy flag has led to 100% of data being copied to the targets before the clone is activated )
Is anybody using this configuration successfully - if so maybe you could suggest where we need to focus our attention ?
Many thanks,
Nick,
UK
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
September 20th, 2007 06:00
But my first impression is that for some reason the datafile /techsymx/db01/system01.dbf isn't on the clone disks. Maybe it's a symbolic link to something that's not in the clone disks .. Or maybe there is some mountpoint not cloned.
Googling for "ORA-01110" seems to pinpoint the problem .. there are a lot of pages that talks about the ORA-01110 error. Some of them talks about database NOT in archive log mode while some other talks about missing/unknown datafiles ..
Unfortunatly I can't help you further.
Major Goat
14 Posts
0
September 22nd, 2007 03:00
Oracle 10g and TimeFinder clone are both exonerated - it was a scripting error.
Basically a ksh trap was taking tablespaces out of hot backup mode before the clone was activated.