Cold backup restore on fail safe environment.

Hi,
The setup:
Windows 2008 with 2 node MSCS cluster in active/passive configuration.
Oracle Database 11.1.0.6 .
Oracle Failsafe 3.4.2
Database :test database; 2 in no. ,both Single instance. Both database are created with cold backup from production.
The Requirement:
To refresh both the test database with cold backup from the same production database as before. And then with the same cold backup create a physical standby database of the newly recreated testing database.
The Plan:
1.take all dbfile,controlfile,redologfiles,standbyredologfiles,tempfiles backup from production.
2.after taking the testing database offline from failsafe and normaly starting on node1; restore dbfile,controlfiles,redologs,srl,tempfiles to testing server. spfile should be properly pointing the new controlfile.
3.startup mount.
4.directory structure for control,redo,srl,dbfiles,tempfiles are diffrent.so,rename file for all dbfiles,redologs,srl,tempfiles.
5.creating a standby controlfile for creating physical standby db of this testing database.
6.open the database.
7.shutdown immediate.
8.start with failsafe.
The doubt:
1. is this plan ok for refresh of the test databases?
2. with the backup taken at step1 and standby ctl file created at step 5 can i create a physical standby database of the testing db?
Please note, the production database is only in picture while taking backup.
Please guys help me for clearing the said doubts.
regards.
g

The doubt:
1. is this plan ok for refresh of the test databases?
2. with the backup taken at step1 and standby ctl file created at step 5 can i create a physical standby database of the testing db?
Please note, the production database is only in picture while taking backup. You are taking cold backup, So the mentioned procedure you can follow. But ensure all the services/background processes related to database are not running.
Once you prepare Primary database, even from that database you can create standby control file, so that it will be used for standby database.
But i'm not aware of how fail safe it works, As per the core database part whatever the steps you mentioned, it looks fine.
Thank You.

Similar Messages

OCS on a cluster with Load balancing and fail safe environment

Dear all,
i want to ask is there any documat or hints on how to do an OCS R2 installaiotn on 3 server with RAC option (clustered Fail Safe), how can i install OCS on a cluster with Load balancing and fail safe environment.
plz i need ur help
thanking u
[email protected]

Dear all,
i want to ask is there any documat or hints on how to do an OCS R2 installaiotn on 3 server with RAC option (clustered Fail Safe), how can i install OCS on a cluster with Load balancing and fail safe environment.
plz i need ur help
thanking u
[email protected]

Cold backup restore to a different bit level

Hi all. I am planning for a coldback restore between two databases. The source db is 10.2.0.3 on 32-bit server Windows 2003 and the destination db is 10.2.0.4 on windows 64-bit. Is it possible to perform this restore? Also is RMAN restore possible? Thanks for any responses.

Hi, I performed a restore of cold backup from 10.2.0.3 database to 10.2.0.4 database on another server. I am receiving this error:
ORA-01503: CREATE CONTROLFILE failed
ORA-01159: file is not from same database as previous files - wrong database id
I am restoring only the schema specific datafiles from the old database and not system, sysaux files .. I understand that there is a mismatch here because the source datafiles are not compatible with the new system files. Any idea what can be done here to get around this error? I am trying to perform a clone of the database into another server. The database name is same.

Cold backup Restoration

Hi,
OS: IBM AIX
Oracle 10g.
My database is running in Archivelog mode.
I have to take coldbakup and restore in the new location.
I will use the following steps.
1. Shutdown immediate
2. tar (.dbf, ctr, redolog and archivelog)
Here I have doubt while restoring the database.
Is that necessary to apply archivelog while restoring the backup ( I hope it is not required)
Please suggest me.
Please provide me steps for backup and restore and recovery using coldbackup.
Thanks in advance
KSG

Hi, it is not necessary to restore archived redo logs if you only want to restore to the point of backup, otherwise it is necessary. Why are you using this method anyway and not using RMAN which would be far simpler ?
regards,
graham

Dsconf backup/restore in a replication environment

Hi,
using Sun JS Directory Server 6.3.1. Two servers in a multi-master topology. When making a backup of the directory (on both systems) using dsconf backup, my question is: how should the restore be done, given the fact that there's a replication agreement between the two servers. Should both servers be restored (from the same backup date/time) and when after the restore will the replication start again? Is it possible that replication from host A already starts while host B is still restoring? And if so, how to prevent this situation?
/rolf

One other way to do it is with "dsconf export" and "dsconf import" (2 ways) -
1. When you use dsconf export, without -Q switch, then it automatically import the replication information. You will then have to import both suffixes and enable the "repl-accept-client-update-enabled" attribute to "on" for master instance to start accepting updates from clients.
Eg.
# dsconf set-suffix-prop –e –p <port>“<suffix>” repl-accept-client-update-enabled:on
2. If you export the backup with -Q switch, then you will anyhow import one of the instances and initialize the other from first instance as "dsconf import -Q" does not import the replication information.

Cold backup restore error

Hi,
i tried to restore coldbackup on solaris.while starting instance i got this error.
LRM-00109: could not open parameter file '/oracle/app/oracle/product/9.2.0.8/dbs/initcdmsd1.ora'
ORA-01078: failure in processing system parameters
now in this path init file is there.
$ cd /oracle/app/oracle/product/9.2.0.8/dbs
$ ls
c-2448946487-20090420-00 init.ora initcdmsv1.ora lkCDMSP1 snapcf_cdmsp1.f spfilecdmsv1.ora
c-2448946487-20090421-00 initcdmsp1.ora initcdmsv1_bkup.ora lkCDMSV1 snapcf_cdmsv1.f
c-2448946487-20090422-00 initcdmsp1_bkup.ora initdw.ora orapwcdmsv1 spfilecdmsp1.ora
$
even tried with giving init path
SQL> startup pfile='/oracle/app/oracle/product/9.2.0.8/dbs/initcdmsd1.ora';
LRM-00109: could not open parameter file '/oracle/app/oracle/product/9.2.0.8/dbs/initcdmsd1.ora'
ORA-01078: failure in processing system parameters
SQL> exit
but error is still there.on this server one db is there.for which it giving same error.
pls help me early as possible
Nareshs

s they are there
root@CDM-PRDR-OCLD-1 # cd cdmsp1
root@CDM-PRDR-OCLD-1 # ls
arch dcm.dbf ocl_dcmq.dbf ocl_li.dbf portal.dbf tms_clob1.dbf
attrs1_oid.dbf discopltc1.dbf ocl_dcmq_idx.dbf ocl_li_idx.dbf ptldoc.dbf tms_data1.dbf
b2b_dt.dbf discopltm1.dbf ocl_def.dbf ocl_lr.dbf ptlidx.dbf tms_idx1.dbf
b2b_idx.dbf drsys01.dbf ocl_def_idx.dbf ocl_lr_idx.dbf ptllog.dbf tools01.dbf
b2b_lob.dbf gcats1_oid.dbf ocl_des.dbf ocl_resp.dbf redo01_a.log uddisys01.dbf
b2b_rt.dbf gdefault1_oid.dbf ocl_des_idx.dbf ocl_resp_idx.dbf redo01_b.log undotbs01.dbf
bam.dbf ias_meta01.dbf ocl_disc.dbf ocl_temp1.dbf redo02_a.log users01.dbf
battrs1_oid.dbf indx01.dbf ocl_disc_idx.dbf ocl_test_data.dbf redo02_b.log wcrsys01.dbf
bc4j_internal_data.dbf oca.dbf ocl_disc_rep_data.dbf ocl_test_index.dbf redo03_a.log xdb01.dbf
control01.ctl ocl_app.dbf ocl_dx_index_data.dbf ocl_vrv.dbf redo03_b.log xdb02.dbf
control02.ctl ocl_app_idx.dbf ocl_dx_table_data.dbf ocl_vrv_idx.dbf svrmg1_oid.dbf
control03.ctl ocl_dcd.dbf ocl_glib.dbf orabpel.dbf system01.dbf
cwmlite01.dbf ocl_dcd_idx.dbf ocl_glib_idx.dbf oss_sys01.dbf temp01.dbf

Upgrade a database from 10.2.0.1 to 10.2.0.4 in a fail safe cluster

Hi,
I need to upgrade from oracle 10.2.0.1 (base) to 10.4.0.4 in a fail-safe cluster.
Questions:
1.If I upgrade each node as a alone server, ¿fail-safe cluster can run with 2 nodes in diferent versions? (for example one week,for rollback )
2. I have read how to upgrade a fail-safe cluster metalink document. Please, can somebody tell me the best form (or logical) to upgrade from 10.2.0.1 to 10.2.0.4 in this cluster?
for example:
1. Backup database
2. Upgrade node 1 to 10.2.0.1 to 10.2.0.4 (following metalink document)
3. Test database and applications
4. One week later the same in node 2 (only if it is possibly run oracle in different versions in failsafe, if not, install node 2 after node 1 works fine)
It´s my first failsafe environment, and i´m not sure how to do it.
Thanks a lot for your help!!!

Welcome to the forums !
Pl see if MOS Doc 223709.1 (How to upgrade or apply a patch to the RDBMS in an Oracle Fail Safe environment) can help. I have no personal experience with Fail Safe.
HTH
Srini

Backup & Restore loses "Groups" in "Contacts" - request for fix

Hi,
I am a new Blackberry user and have found that the Blackberry Link backup/restore functions fail to keep track of my Groups within my Contacts list. When I carry out a Restore all my Contacts are restored but all my Groups within Contacts disapperar (although the contacts within my Groups are still retained in my Contacts list).
Does anyone have a fix for this issue please?
I am using Link v 1.2.1 (build18) and BB release 10.2.1.2977 on my Z10.
I do not want to Sync my phone contacts with my Address Book on my Mac since I use them independently.
Thank you for your advice!!

Yeah, for some reason Groups are not restored. Syncing wouldn't work anyway since groups are not sync'd either.
I would suggest updating to the latest version of LInk which is 1.2.3.48. I haven't tested for the backup/restore of groups, though.
1. Please thank those who help you by clicking the "Like" button at the bottom of the post that helped you.
2. If your issue has been solved, please resolve it by marking the post "Solution?" which solved it for you!

COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.

제품 : ORACLE SERVER
작성날짜 : 2002-04-09
COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.
======================================================================
PURPOSE
COLD BACKUP을 받은 후 ARCHIVE LOG MODE로 변환하여 사용한 경우의 RECOVERY
과정을 TEST로 확인하여 본다.
Examples
No Archive log mode.
SQL> select * from tab ;
TNAME TABTYPE CLUSTERID
EMP TABLE
EMP1 TABLE
EMP2 TABLE
EMP3 TABLE
EMP4 TABLE
10 rows selected.
SQL> select count(*) from emp3 ;
COUNT(*)
0
SQL> select count(*) from emp4 ;
COUNT(*)
0
Cold backup을 받은후 Archive log mode 변경한 경우
SVRMGR> startup mount
SVRMGR> archive log list
Database log mode No Archive Mode
Automatic archival Enabled
Archive destination D:\Oracle\oradata\SNAP\archive
Oldest online log sequence 26
Current log sequence 28
SVRMGR> alter database archivelog ;
SVRMGR> alter database open ; => archive log mode 변경.
SQL> select * from tab ;
TNAME TABTYPE CLUSTERID
EMP TABLE
EMP1 TABLE
EMP2 TABLE
EMP3 TABLE
EMP4 TABLE
10 rows selected.
SQL> insert into emp3 select * from emp ;
14 rows created.
SQL> commit ;
Commit complete.
SQL> insert into emp4 select * from emp1 ;
71680 rows created.
SQL> commit ;
Commit complete.
SQL> select count(*) from emp3 ;
COUNT(*)
14
SQL> select count(*) from emp4 ;
COUNT(*)
71680
## log switch 발생.
SVRMGR> alter system switch logfile ;
SQL> insert into emp3 select * from emp ; -- current log에 반영.
14 rows created.
SQL> commit ;
SQL> select count(*) from emp3 ;
COUNT(*)
28
SQL> select count(*) from emp4 ;
COUNT(*)
71680
# ALL DATABASE CRASH #
# recover 과정... #
1. Restore Cold-backup
2. modify initSID.ora
log_archive_start = true
log_archive_dest_1 = "location=D:\Oracle\oradata\SNAP\archive"
log_archive_format = %%ORACLE_SID%%T%TS%S.ARC
3. svrmgrl
Statement processed.
SVRMGR> startup mount
ORACLE instance started.
Total System Global Area 40703244 bytes
Fixed Size 70924 bytes
Variable Size 23777280 bytes
Database Buffers 16777216 bytes
Redo Buffers 77824 bytes
Database mounted.
SVRMGR> archive log list
Database log mode No Archive Mode
Automatic archival Enabled
Archive destination D:\Oracle\oradata\SNAP\archive
Oldest online log sequence 26
Current log sequence 28
SVRMGR> alter database archivelog ;
Statement processed.
SVRMGR> recover database using backup controlfile until cancel ;
ORA-00279: change 340421 generated at 04/29/2001 23:42:20 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC
ORA-00280: change 340421 for thread 1 is in sequence #28
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340561 generated at 04/29/2001 23:47:29 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC
ORA-00280: change 340561 for thread 1 is in sequence #29
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340642 generated at 04/29/2001 23:47:35 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC
ORA-00280: change 340642 for thread 1 is in sequence #30
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340723 generated at 04/29/2001 23:47:40 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC
ORA-00280: change 340723 for thread 1 is in sequence #31
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340797 generated at 04/29/2001 23:48:01 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00032.ARC
ORA-00280: change 340797 for thread 1 is in sequence #32
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SVRMGR> alter database open resetlogs ;
Statement processed.
SVRMGR>
SQL> connect scott/tiger
SQL> select count(*) from emp3 ;
COUNT(*)
14
SQL> select count(*) from emp4 ;
COUNT(*)
71680
# 결론...... #
따라서 current log file에 기록된 14 row에 대한 부분은 recover가 될수
없지만 archive log file에 적용된 log에 대한 data는 정상적으로 복구가
가능하다.
# 주의 사항 #
cold backup을 restore한 후 database open후 shutdown 한 다음 archive
log mode로 변경하여 recover를 진행하는 경우 SCN number가 변경되기
때문에 ora-600 error가 발생하며 media recovery를 필요로 하기 때문에
주의하여야 한다.
SVRMGR> startup
ORACLE instance started.
Total System Global Area 40703244 bytes
Fixed Size 70924 bytes
Variable Size 23777280 bytes
Database Buffers 16777216 bytes
Redo Buffers 77824 bytes
Database mounted.
Database opened.
SVRMGR> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.
SVRMGR> startup mount
ORACLE instance started.
Total System Global Area 40703244 bytes
Fixed Size 70924 bytes
Variable Size 23777280 bytes
Database Buffers 16777216 bytes
Redo Buffers 77824 bytes
Database mounted.
SVRMGR> alter database archivelog ;
Statement processed.
SVRMGR> recover database using backup controlfile until cancel ;
ORA-00279: change 339542 generated at 04/29/2001 23:30:57 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00003.ARC
ORA-00280: change 339542 for thread 1 is in sequence #3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [8390146], [1], [3], [143], [
240], [], []
SVRMGR> exit
Server Manager complete.
Rederence Documents
---------------------

Upgrade Oracle Database in Oracle Fail Safe configuration.

Dear All,
I usually upgrade Oracle Database (10g, 10g r2, 11g, 11g r2) in stand alone configuration without problems.
Now, I will must upgrade one database from 11g to 11g r2 in Fail Safe configuration.
Please, is there some link to read before this operation ?
Many thx.

Pl see if MOS Doc 223709.1 (How to upgrade or apply a patch to the RDBMS in an Oracle Fail Safe environment) can help
HTH
Srini

ORA-00313: open failed for members during restore from COLD backup

Hi all,
I took a cold backup of an 11.1 database using RMAN (database in mount state).
I used the following command to restore it:
restored the controlfile and then
RESTORE DATABASE FROM TAG 'TAGxxxxxxxxxx';
Now I'm restoring it and it's taking too much time. When checking alert log it says:
ORA-51106: check failed to complete due to an error. See error below
ORA-48318: ADR Relation [HM_FINDING] of version=3 cannot be supported
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/oracle1/oradata/******/redo1_02.log'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
RMAN is still in progress, why does it complain about redo?
I'm not doing recovery since it was a cold backup.
Thanks in advance.

Hi Michael,
Yes, it's the correct one because it says "full restore complete":
ORA-00312: online log 1 thread 1: '/oracle1/oradata/******/redo1_01.log'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
Tue Apr 30 14:38:14 2013
Full restore complete of datafile 32 /oracle1/oradata/******/apr_sesm_index_01.dbf. Elapsed time: 1:25:42
checkpoint is 12652187135448
last deallocation scn is 12651877642745
Tue Apr 30 15:38:04 2013
Full restore complete of datafile 34 /oracle1/oradata/******/apr_stage_data_01.dbf. Elapsed time: 6:42:52
checkpoint is 12652187135448
last deallocation scn is 12651877637877
thanks,

RMAN Automatic backup/recovery with oracle fail safe, windows cluster

Hello,
I have question,
1) Whether it is possible to do "RMAN Automatic Backup and recovery" in environment as ?
Environment: -
a. Windows clustering with windows server 2003 Enterprise Edition R2 (Two Node Clustering)
b. Shared disk ( RAID )
c. Oracle 10g standard edition one
d. Oracle fail safe v3.3.3 (for redundancy)
Here we have single oracle instance operating on single database whose files are located on shared disk.
2) If answer to above question is yes please specify if there is some good documentation to it.
Any help regarding this will be greatly appreciated.
Thanks in advance,
Rahul

You just need to make sure that the RMAN scripts are always able to connect to the target database instance whether instance runs on cluster node 1 or cluster node 2
here, If oracle services(resources) will shift from Node1 to Node2 (due to media or any failure) during RMAN Backup then there will be break in connection, will it destroy my backup or will it get started automatically without any harm?
and also I want to know,
Do we need to setup another server which will have RMAN backup script running?

Database Restore from COLD Backup

Dear all,
I .m trying to restore a production database from a COLD backup. Before the COLD BAckup, we have take a HOT backup as usual and then shutdown the database to perform the Cold Backup.
After restirong all the oracle files and arch redo log, i have tried to restart the datbase but it failed with the followgin error message:
SVRMGR> connect internal
Connected.
SVRMGR> startup
ORACLE instance started.
Total System Global Area 625729520 bytes
Fixed Size 69616 bytes
Variable Size 133795840 bytes
Database Buffers 491520000 bytes
Redo Buffers 344064 bytes
Database mounted.
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/usr/oracle/8.1.6/disk1/IF1/system01.dbf'
SVRMGR> exit
Server Manager complete.
root@dbserver#su - oracle
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
Then i have recovered but it seems that the Oracle process do not started and here is what i have found in alert log file:
Errors in file /usr/oracle/8.1.6/admin/IF1/bdump/if1_smon_609.trc:
ORA-00600: internal error code, arguments: [4194], [52], [52], [], [], [], [], []
Mon Mar 8 11:42:46 2004
Recovery of Online Redo Log: Thread 1 Group 1 Seq 29954 Reading mem 0
Mem# 0 errs 0: /usr/oracle/8.1.6/disk2/IF1/redo1a.rdo
SMON: terminating instance due to error 600
Instance terminated by SMON, pid = 609
WARNING! Recovering data file 1 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 2 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 3 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 4 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 5 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 7 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 8 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 9 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 26 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 27 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 29 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 31 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 34 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 36 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 40 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 43 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 49 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 53 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 54 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 55 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
WARNING! Recovering data file 58 from a fuzzy backup. It might be an online
backup taken without entering the begin backup command.
Media Recovery Log
Could someone explain to me what i did wrong?
Thank you
ORA-01113
ORA-01110
ORA-00600: internal error code, arguments: [4194], [52], [52], [], [], [], [], []

Please do not confuse between the backup copies you have. Ensure that you have the latest copy whether cold or hot. If you have COLD copy then simply replace all the data files, redo log files, and the control files and start the database it should start. I do not understand your back up strategy because if you have a Hot backup then why do you need a cold backup. Please let me know in what mode your database is running?
Regards,
DJ

ORA-12560 in database restore cold backup

Hi guys,
I'm trying to restore a cold backup (WINDOWS NT) and I did the following:
1. Restore the datafiles in a specific location, according to the directory that the files were before.
2. Create the service:
C:\>oradim -new -sid ORCL -startmode auto -pfile C:\oracle\admin\ORCL\pfile\initORCL.ora
3. startup the listener with the instance.
4. When I try to connect as follows, I receive the following error:
C:\>connect "/as sysdba"
'connect' is not recognized as an internal or external command,
operable program or batch file.
C:\>sqlplus "/as sysdba"
SQL*Plus: Release 9.2.0.3.0 - Production on MiΘ Ago 13 17:20:32 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
ERROR:
ORA-12560: TNS:protocol adapter error
Enter user-name:
C:\>
What am I missing???
TIA.

You may be hitting bug 4598734. See Metalink Note:359428.1 - Windows: Starting the instance service fails to start the database in Server rel. 10g

Restoring inconsistent cold backup

Hello all.
Here's the scenario: I have a 9.2.0.1 database, in noarchivelog mode, running on Windoze XP. While the database is running, I took a backup of all the datafiles, control files and online logs using copy and paste on windoze. After the copy was done, I have shut down the database. I copied back into the original location the backup of the datafiles I made earlier.
My question is: How I go about to restore this database ? I dont care wether it is consistent or not, I just want to open it to make an export out of it
Things I have tried so far unsuccessfully:
allowresetlogs_corruption
allowreadonly_corruption
If you could shed some light on it on the steps I would need to make, that would be appreciated.
Thanks

What have you tried to far (specifics please, not general statements)?
I have done something close to what you want do a couple of years ago for an Oracle 9.2.0.4 DB on Linux and am looking for my notes. One key thing I found was to not try to change anything but just get a DB up and running that would let me get the data out. That means don't try to use different file paths or anything other changes.
It involved creating a new minimal database from scratch by hand that has the same name, paths, block size as the old one. In my case this minimal DB only had the system_01.dbf, undotbs_01.dbf and users_01.dbf data files even though I ultimately needed access to about 40 others.
The idea is to get a template DB in place that refers to the same paths, then shut it down and replace the minimal system_01.dbf file with the one from your backup. It turned out for me that Oracle could open, load and use my old system tablespace even though it referred to tablespaces that didn't exist yet in the new minimal system; obviously I couldn't use them yet but they didn't cause Oracle to fail to start.
1. You can toss the redo logs since there is nothing in them you need or can use and you will never be able to read them anyway.
2. You will need to create the instance and DB using the same version of Oracle that you had. There were key differences between the early Oracle 9 versions and I wasn't able to get around them.
3. Create an instance for the correct DB version if you don't have one. The easiest way to create a new one is to do a default installation from the original set up files but DO NOT create a database. When given choices use the same values (character set, paths, etc) as your old DB.
4. You will need a text version of the init.ora file in the same location (name and path) where it was before - the character set and block size have to match what you had before. If you have a copy of this file you can try it first. If you don't then create a minimal file; that is, no entries that are not necessary. Oracle comes with a sample with a lot entries commented out.
    a. use the same db_name= parameter in the init.ora file
    b. use a db_files= parameter that is large enough for all of the data files that you will later need access to
    c. use a compatible- parameter that is 9.2.0 and no later
5. You won't be able to use your old, copied, control files since they are binary files and the content won't match the new database; trying to use them will not get you anywhere.
6. Once you can bring up this new DB the first thing you should do is shut it down and take a cold backup.
7. Replace the new system_01.dbf and users_01_dbf files with the ones you copied from the old DB. The new control file can mount and open the old tablespace file and users file since the control file (old Oracle systems only, mind you) have NAME and PATH information but do not care about actual content (how many users, etc).
8. Make sure you can now open and access the DB with your swapped system and user tablespaces. You won't be able to access objects from the system tables that refer to data files that aren't known to the control file so don't even try to yet.
9. You can add your other data files to the DB by doing a CREATE CONTROLFILE command, when unmounted, that adds the other data files that you will want access to. Obviously don't add them all at once; add one and then test to make sure that things are ok. You won't be
It turns out that the control file has the list of datafiles including their names and paths but does not have the sizes; the system tables have the size info and physical info. So you can add a datafile to the control file by path and name without needing to know how big it was supposed to be; that size info will still be in your old system tablespace.I may have missed something and if I fiind my notes will repost with anything else I think of.

Cold backup restore on fail safe environment.

Similar Messages

Maybe you are looking for