Cold backup recovery - ORA-01092

Hi,
10.2.0.3.0 on AIX
I tried to restore a cold backup, created controlfiles.
When I try to open database, I get error
ORA-01092: ORACLE instance terminated. Disconnection forced
Please suggest me
Thanks
KSG

Hi,
So what you are doing exactly?
I restored a coldbackup from client side.
I recreated the controlfile.
.....21 CHARACTER SET AL32UTF8
22 ;
Control file created.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
Alertlog file
"alert_THRDY02.log" 130 lines, 5608 characters
Thread 1 opened at log sequence 1
Current log# 4 seq# 1 mem# 0: /oracle/oradata10g/THRDY02/redo03b.log
Successful open of redo thread 1
Wed Jun 9 11:08:24 2010
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Jun 9 11:08:24 2010
SMON: enabling cache recovery
Wed Jun 9 11:08:25 2010
Errors in file /glosoft/oracle/oracle10g/product/10.2.0/db_1/admin/THRDY02/udump
/thrdy02_ora_1958330.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Wed Jun 9 11:08:25 2010
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 1958330
ORA-1092 signalled during: alter database open resetlogs...
Trc file
kccsga_update_ckpt: num_1 = 8, num_2 = 0, num_3 = 0, lbn_2 = 0, lbn_3 = 0
Control file created with size 344 blocks
*** 2010-06-09 11:08:21.419
Prior to RESETLOGS processing...
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE start
Database is not in archivelog mode
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE complete
*** 2010-06-09 11:08:21.422
Thread 1: Sequence reset to 1.
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Thanks
KSG
Edited by: KSG on Jun 9, 2010 11:18 AM
Edited by: KSG on Jun 9, 2010 3:37 PM

Similar Messages

Cold Backup ERROR ORA-01113

Hi Friends,
Oracle 10g R2 DB
I have taken a cold backup pf my database.
I shutdown the db, and copy all the datafile,logfile,controlfile to /u01/BACKUP_DB.
Then I tried to test my backup by pointing all the dbfs to /u01/BACKUP_DB.
startup mount
alter database rename file ... to ...;
alter database open;
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1 '/u01/BACKUP_DB/system01.dbf'
Where did I go wrong? :(
I am sure I shutdown the database.
Thanks a lot

Why do I get ORA-01113 for the cold backup?
To get some clue why ora-01113 error comes during backup and recovery review following link.
I recreated controlfile, but recover database failed!
Khurram

Cold Backup / Recovery for OEM Grid

Hi friends,
OEM 10.2.0.5
RHEL 4.6
How do you Clone or Backup OEM Grid (Management server(OMS) , agent, and repository database)?
in case of disaster?
They are all under our server dir /home/oracle. If I have a backup of my /home/oracle on external tape or disk,
and ithappened that my OEM server crashed and it can not be fixed anymore. Then we buy another server
with the same specs and OS. Then copy/download the backup. How can I start it up? Just like the original setup?
Thanks a lot.
Ms K

ytterp2009 wrote:
thanks :)
So, I dont need the local OEM anymore ;)
Yes ..
By the way, does the agent keep backup of its gathered data? Or does it delete them automatically after it is sent
to the OMS server? I am afraid that my agent disk space will get full.
Does agent use oracle tables to keep data? or just text filesAgent gathers data and stores it in form of xml in $AGENT_HOME/sysman/upload and sends these xml to OMS and deletes them automatically.In OMS they are stored at $OMS_HOME/sysman/recv . Then these xmls are processed by loader and get loaded into repository DB and deleted automatically from directory.
By default your agent can store data upto 50 MB and once it is full then your agent will stop working. Check out parameters in $AGENT_HOME/sysman/config/emd.properties file.
please check :
http://racdba.wordpress.com/2009/12/05/oem-agent-common-errors/
How do I know what time/schedule or how frequent does the agent updates our OMS server?
How often does the agent gathers data from the managed database?It depends on the frequency of metric applied for the target.
Please read :
Enterprise Manager Grid Control Agent 10g, Process Control (Start, Stop & Status) Troubleshooting Guide [ID 548928.1]
Understanding the Enterprise Manager 10g Grid Control Management Agent, Directory Structure and Key Configuration Files. [ID 234872.1]
Regards
Rajesh

Database give ORA-600 error after cold backup

HI,
I have oracle 10g install on linux system. i take cold backup of my database using
sql> shutdown immediate
and then copy all files to any other location.
but when i start my database it gives me error like
Errors in file /opt/oracle/fina/bdump/fina_smon_4422.trc:
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4193], [136], [139], [], [], [], [], []
Fri Dec 4 15:23:18 2009
Errors in file /opt/oracle/fina/bdump/fina_smon_4422.trc:
ORA-00600: internal error code, arguments: [4193], [67], [70], [], [], [], [], []
Fri Dec 4 15:23:19 2009
Doing block recovery for file 2 block 1702
Block recovery from logseq 13, block 3531 to scn 758385
Fri Dec 4 15:23:19 2009
Recovery of Online Redo Log: Thread 1 Group 1 Seq 13 Reading mem 0
Mem# 0 errs 0: /opt/oracle/fina/dbs/redo01.log
Block recovery completed at rba 13.3532.16, scn 0.758386
Doing block recovery for file 2 block 153
Block recovery from logseq 13, block 3531 to scn 758436
Fri Dec 4 15:23:19 2009
Recovery of Online Redo Log: Thread 1 Group 1 Seq 13 Reading mem 0
Mem# 0 errs 0: /opt/oracle/fina/dbs/redo01.log
Block recovery completed at rba 13.3612.16, scn 0.758437
Fri Dec 4 15:23:19 2009
Errors in file /opt/oracle/fina/bdump/fina_smon_4422.trc:
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [4193], [67], [70], [], [], [], [], []
Fri Dec 4 15:23:29 2009
Errors in file /opt/oracle/fina/bdump/fina_smon_4422.trc:
ORA-00600: internal error code, arguments: [4193], [136], [139], [], [], [], [], []
Fri Dec 4 15:23:29 2009
Errors in file /opt/oracle/fina/bdump/fina_pmon_4410.trc:
ORA-00474: SMON process terminated with error
Fri Dec 4 15:23:29 2009
PMON: terminating instance due to error 474
Instance terminated by PMON, pid = 4410i have seen this happen sometime after cold backup database give errors. is taking cold backup of database is not safe.
Please suggest.

Umesh,
Since it is case of Ora 600, for which only last solution is oracle support, but i would like to mention that your are getting ORA-00600: internal error code, arguments: [4193].... So, this 4193 is cause to read following links too:
http://www.orafaq.com/forum/t/47048/2/ and. see Metalink note 153788.1 and 39282.1.
Regards
Girish Sharma

How to do media recovery from cold backup?????????/

Hi
i take cold backup of my 9i database ....
in case my database is up .....
how will i recover my database if i lose a single database file and i want to recover it from cold backup......
Thanks in advance
Gagan

Here you go
These are the steps:
1. Restore the lost file from a backup.
2. If the database is down, mount it.
SVRMGR> STARTUP MOUNT PFILE=<location_of_pfile>;
3. Issue the following query:
SVRMGR> SELECT V1.GROUP#, MEMBER, SEQUENCE#,
FIRST_CHANGE#
FROM V$LOG V1, V$LOGFILE V2
WHERE V1.GROUP# = V2.GROUP# ;
This will list all your online redolog files and their respective
sequence and first change numbers.
4. If the database is in NOARCHIVELOG mode, issue the query:
SVRMGR> SELECT FILE#, CHANGE# FROM V$RECOVER_FILE;
If the CHANGE# is GREATER than the minimum FIRST_CHANGE# of your logs,
the datafile can be recovered. Just keep in mind that all the logs to
applied will be online logs, and move on to step 5.
If the CHANGE# is LESS than the minimum FIRST_CHANGE# of your logs, the
file cannot be recovered. Your options at this point would be to restore
the most recent full backup (and thus lose all changes to the database
since) or recreate the tablespace as explained in scenario a.
5. Recover the datafile:
SVRMGR> RECOVER DATAFILE '<full_path_file_name>'
6. Confirm each of the logs that you are prompted for until you receive the
message "Media recovery complete". If you are prompted for a non-existing
archived log, Oracle probably needs one or more of the online logs to
proceed with the recovery. Compare the sequence number referenced in the
ORA-280 message with the sequence numbers of your online logs. Then enter
the full path name of one of the members of the redo group whose sequence
number matches the one you are being asked for. Keep entering online logs
as requested until you receive the message "Media recovery complete"
7. If the database is at mount point, open it.

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,

Need clarification for cold backup and recovery

Hello Everyone ..
I have much confusion on cold backup and recovery topic.
Already i posted a scanario regarding this and i want to know some clarity points to understand.
1. I had cold backup two days before
2. I am creating an object *(EMP)* and inserting some records then issue log switch continiously.
3. Manually i removed all physical files (datafiles , control files , log files , redolog files ...)
4. then i issued STARTUP FORCE MOUNT;
5. here i am getting error identifying control file.
6. cold backup two days before all files restored
6. then i issue recover database using backup controlfile until cancel;
7. i am trying to issue select * from emp; i am getting error
select * from emp
*ERROR at line 1:
ORA-00942: table or view does not existMy QUESTION IS
After cold backup finished , i created emp table ..
when restoring old back " There is no emp table"
*- then , can i recover emp table ? - If so , please explain about this ..*
Note : REF - LINK https://forums.oracle.com/forums/message.jspa?messageID=11056341#11056341
- Above link says what i did ? . In this thread i am asking concept & logic ..
please do NOT consider as "*DUPLICATE*"

When you recover the database using backup controlfile until cancel, you have to apply archived logs. Did you apply all of them?
If the create command was in the online redo, not yet archived, and you lost the online redo, then you won't have it. This is why you want to have redo multiplexed, it is a critical piece.
In some recovery scenarios, if you haven't lost the online redo, you need to specify those files as if they were archives.
It is normally easier to just be sure you have the latest controlfiles and let Oracle figure it out automatically (which is why you want to use online RMAN backups rather than cold backups). But yes, it is important to understand what is going on for different scenarios. I used to have manual standbys, and one of the disaster instruction sets explained to try to get online redo over to the standby to lose as few transactions as possible. That could still be useful for some snapshot hardware type scenarios, assuming the business is too cheap to do proper failovers.

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

Archived log application to a cold backup fails with ora-00328

I am testing backup and recovery scenario as mentioned in Metalink Doc id:69468.1 where a cold backup of one production server is restored on a separate machine. Some activity, say a table creation in some schema and insertion of rows in it is followed by a few log switches. Next I moved just the archived logs ( newly generated) to the test machine and proceed as follow to recover but log application is failing as below,any help would be appreciated!
SQL> startup mount;
ORACLE instance started.
Total System Global Area 205520896 bytes
Fixed Size 1248116 bytes
Variable Size 71304332 bytes
Database Buffers 130023424 bytes
Redo Buffers 2945024 bytes
Database mounted.
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00328: archived log ends at change 581535, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
SQL> recover database until cancel;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
ORA-00328: archived log ends at change 581535, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
SQL> recover database using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
ORA-00328: archived log ends at change 581541, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
Please Help

The error displayed stated you are required to have an specific sequence:
ORA-00280: change 581754 for thread 1 is in sequence #1
Check the contents of the v$recover_file dynamic view and verify if you really have all required archivelog files.
~ Madrid

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

ORA-00314 - Restoring from Cold Backup. ( Redologs on Raw Disk startup)

Greetings,
We're running Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production ( Solaris Sparc )
we've recently switched to redologs on raw disks to improve DB write performance. Have taken a cold backup of db , But db denies to open normally after restoration.
Any ideas what could be wrong? and how to fix this?
TIA,
SQL> startup;
ORACLE instance started.
Total System Global Area 1.0737E+10 bytes
Fixed Size 1996520 bytes
Variable Size 3640658200 bytes
Database Buffers 7063207936 bytes
Redo Buffers 31555584 bytes
Database mounted.
ORA-00314: log 1 of thread 1, expected sequence# doesn't match
ORA-00312: online log 1 thread 1: '/dev/rdsk/c1t4d0s3'
ORA-00312: online log 1 thread 1: '/dev/rdsk/c1t5d0s3'

Try this ..
First i create a backup of control file:
SQL> alter database backup controlfile to trace;
Database altered.
Then i check udump directory. There are some trace files To find out which one contains control file, i simply make a text search :
testdb oracle@aurora:/data06/app/oracle/admin/testdb/udump> grep 'CREATE CONTROLFILE REUSE DATABASE' *.*
testdb_ora_181267.trc:CREATE CONTROLFILE REUSE DATABASE "testdb" NORESETLOGS NOARCHIVELOG
testdb_ora_181267.trc:CREATE CONTROLFILE REUSE DATABASE "testdb" RESETLOGS NOARCHIVELOG
I execute the commands which is included with CREATE CONTROLFILE REUSE DATABASE
SQL> startup nomount
ORACLE instance started.
Total System Global Area 314572800 bytes
Fixed Size 1302944 bytes
Variable Size 106700384 bytes
Database Buffers 205520896 bytes
Redo Buffers 1048576 bytes
SQL> CREATE CONTROLFILE REUSE DATABASE "testdb" RESETLOGS NOARCHIVELOG
2 MAXLOGFILES 4
3 MAXLOGMEMBERS 4
4 MAXDATAFILES 1000
5 MAXINSTANCES 1
6 MAXLOGHISTORY 4544
7 LOGFILE
8 GROUP 1 '/data07/oradata/testdb/redo01.log' SIZE 50M,
9 GROUP 2 '/data07/oradata/testdb/redo02.log' SIZE 50M,
10 GROUP 3 '/data07/oradata/testdb/redo03.log' SIZE 50M
11 DATAFILE
12 '/data07/oradata/testdb/system01.dbf',
13 '/data07/oradata/testdb/undo01.dbf',
14 '/data07/oradata/testdb/sysaux01.dbf',
15 '/data07/oradata/testdb/users01.dbf',
16 '/data07/oradata/testdb/data01.dbf',
17 '/data07/oradata/testdb/work01.dbf',
18 '/data07/oradata/testdb/ascs01.dbf',
19 '/data07/oradata/testdb/uccs_data01.dbf',
20 '/data07/oradata/testdb/uccs_index01.dbf'
21 CHARACTER SET WE8ISO8859P9
22 ;
Control file created.
Then recover db.
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE

ORA-01154: On Open After Cold Backup - No DataGuard

We have one 11.2.0.3 database that will occasionally fail to start with an ORA-01154 after a cold backup. It's a test database, so I usually just manually start it the next morning. I have seen this with standby databases running Data Guard, but never on a standalone database with no Data Guard. Anyone seen this behavior? It started after the database was upgraded from 11.2.0.1 to 11.2.0.3.

Could it be whatever did the shutdown didn't complete? Do you have some automated process doing the shutdown? Why do you have cold backups?

Enterprise Manager Configin a new host after recovery from cold backup

Dear friends ,
we have recovered a DB in new host(windows) from the cold backup.
Listener is configured and EM is also configured .
I am able to login through the EM . In the front page i get an error like
java.lang.exception:unknownhost exception sensding request ::<hostname>.<domain>
Please Note :The hostname from which we have taken backup(operation system) is different from the new host name where have recovered the DB.
Also when i clicked the link for administration page or performance page
i was taken to the login page which was showing as follows
user name:
password:
Connect String : <old host name>.<domain name>
Now i dont know where is parameter of old host details are stored and how it has to be replaced.
Please reply if anyone can have the solution .
Thanks in advance
Madhu

Please Note :The hostname from which we have taken backup(operation system) is different from the new host name where have recovered the DB
This is the call for trouble actually.EM repository stores the info of hostname/ipaddress of the machine where it is configured. So any change in that information will not let you use EM.There are couple of files which are there in which this information is stored and if needed, that information can be be manualy edited.But manual editing is not a good way to deal with repository.So the better option for you is to recreate the repository of your EM
Follow the link for the description of the commands.
You would have to use
$emca -deconfig dbcontrol db -repos drop
$emca -config dbcontrol db -repod createHTH
Aman....

Recovery from cold backup

Hi,
We take Hot backup everyday, but I took a cold backup using the same catalog. If I want to restore the cold backup I took, what is the proceedure. We are running on 10g in HP Unix.
Thanks.

Hi Rock2,
If you want to restore the cold backup you need to know the tag belonging to this backup.
Using the logfile of the coldbackup or <list backup summary;> in rman you should be able to get this info.
The restore would be similar as:
connect catalog rman/pwd@define_rcv;
# check in catalog database for the dbid.
# If so set the appropriate dbid by unhashing the line directly below using the current dbid
# set dbid = define_dbid
connect target /;
STARTUP NOMOUNT;
run {
allocate channel tc1 type 'SBT_TAPE'; # or 'DISK'
allocate channel tc2 type 'SBT_TAPE'; # or 'DISK'
# adjust the TAG in the following lines
restore controlfile from tag TAG0000001;
sql 'alter database mount';
restore database from tag TAG0000001;
sql 'alter database open resetlogs';
release channel tc1;
release channel tc2;
Regards,
Tycho

Recovery in R12 with user managed cold backups

We have R12.1.1 ( db 11.1.0.7 ) on RHEL 5.3 ( ALL SET UP 64 bit ).
we have user managed cold backup scheduled with tar -czvf command.
Archiving is enabled. Production server is 2 nodes ( Apps + DB ) .
Suppose we have backup on hard disk and our Production server ( db is crashed ).
we will prepare new server copy the backup from Hard disk to new server and run adcfgclone.pl scripts.
What else do we need to do on this new server to go live ?
Please reply

Hi;
We have R12.1.1 ( db 11.1.0.7 ) on RHEL 5.3 ( ALL SET UP 64 bit ).
we have user managed cold backup scheduled with tar -czvf command.
Archiving is enabled. Production server is 2 nodes ( Apps + DB ) .
Suppose we have backup on hard disk and our Production server ( db is crashed ).
we will prepare new server copy the backup from Hard disk to new server and run adcfgclone.pl scripts.
What else do we need to do on this new server to go live ?1. If you run preclone sh before take cold backup than you can go wiht clone process
2. If you dont run than you can create same user, same mount point on new server and try to relink oracle binary(I assume you have also ORACLE_HOME backup) and try to make up your system
Regard
Helios

Cold backup recovery - ORA-01092

Similar Messages

Maybe you are looking for