ORA-16005 : database requires recovery

Following error occurred while trying to open oracle datababse in read only mode
$ sqlplus /nolog
SQL> connect /as sysdba
connected
SQL>
SQL> startup nomount
ORACLE instance started
Total System Global Area 612368384 bytes
Fixed Size 1281504 bytes
Variable Size 163578400 bytes
Database Buffers 415236096 bytes
Redo Buffes 32272348 bytes
SQL>
SQL> alter database mount ;
Database altered
SQL> alter database open ready only ;
alter database open ready only
ERROR at line 1:
ORA-16005: database requires recovery
SQL>
Since database is in No Archive mode why it is giving ORA-16005 error while starting a databse in ready only mode ????

ORA-16005 database requires recovery
Cause: The database requires recovery, and therefore cannot be opened for read-only access by this instance.
Action: Perform the necessary recovery and re-open for read-only access.
Oracle says as above. Please perform the recovery and then open the database in read only mode. We are unaware about what happened before.

Similar Messages

ORA-10458: standby database requires recovery

hi
kindly help me... i got error when standby open in read only mode
SQL*Plus: Release 11.2.0.3.0 Production on Sat Jan 19 14:37:46 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Total System Global Area 5344731136 bytes
Fixed Size 2237776 bytes
Variable Size 1275071152 bytes
Database Buffers 4060086272 bytes
Redo Buffers 7335936 bytes
Database mounted.
SQL> Alter Database Recover Managed Standby Database Disconnect;
Database altered.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Database altered.
SQL> ALTER DATABASE OPEN READ ONLY;
ALTER DATABASE OPEN READ ONLY
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01152: file 22 was not restored from a sufficiently old backup
ORA-01110: data file 22: '/archive/data/undo01.dbf'

hi CKPT
I executed the action plan as you recommend and got below information;
SQL> recover standby database;
ORA-00279: change 5983485554580 generated at 01/01/2013 19:27:17 needed for
thread 1
ORA-00289: suggestion : /archive/PROD_1_750568044_45027.ARC
ORA-00280: change 5983485554580 for thread 1 is in sequence #45027
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
'/archive/PROD_1_750568044_45400.ARC'
ORA-00310: archived log contains sequence 45400; sequence 45027 required
ORA-00334: archived log: '/archive/PROD_1_750568044_45400.ARC'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 22 was not restored from a sufficiently old backup
ORA-01110: data file 22: '/archive/data/undo01.dbf'
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01666: control file is for a standby database
SQL> alter system switch logfile;
alter system switch logfile
ERROR at line 1:
ORA-01109: database not open
---------------------------------- and some other activity but still not found any solution-------------
RMAN> recover database until sequence
2> 45026;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:42:47
RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484595990
RMAN> recover database until sequence 45027;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:42:59
RMAN-06556: datafile 22 must be restored from backup older than SCN 5983485554580
RMAN> recover database until sequence 45025;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:43:09
RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484160276
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 01/23/2013 16:43:25
ORA-01666: control file is for a standby database

Backup database required recovery

Hello all,
I am trying to perform hot backup and recovery, the bckup was taken and then im getting this error.
iam using oracle 11.2.0.1.0 and on windows environment.
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database required recovery
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'C:\APP\USER\ORADATA\PROD3\SYSTEM01.DBF'

SQL> startup
ORACLE instance started.
Total System Global Area 2555445248 bytes
Fixed Size 2178456 bytes
Variable Size 1577058920 bytes
Database Buffers 956301312 bytes
Redo Buffers 19906560 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database required recovery
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'C:\APP\USER\ORADATA\PROD3\SYSTEM01.DBF'
SQL> select hxfil FILENUMBER,fhsta STATUS,fhscn SCN,fhrba_Seq SEQUENCE from x$kc
vfh;
FILENUMBER STATUS SCN SEQUENCE
1 8193 20030487 15
2 1 20030487 15
3 1 20030487 15
4 1 20030487 15
5 1 20030487 15
6 4 20032393 19
7 4 20032393 19
7 rows selected.

DBXML database requires recovery often

I am running a dbxml database (2.4.13, DB: 4.7.25) with transactions. There are not many calls to the database daily (<200 on average), however it keeps exiting with an exception requesting that recovery be run:
Db Error: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
almost daily, and interfering with the full system operation since it requires the database. I am not sure why this is happening so often. Any suggestions?
Doug

There is a strict requirement that write operations are done one at a time. You can get by without it if things are kinda slow but not consistenly. You can manage it with your own coding locks. Also, I experienced lots of issues with recovery when I had my database on a san mount. When I switched it to local machine, things got lots better.
http://www.oracle.com/technology/documentation/berkeley-db/xml/gsg_xml_txn/cxx/index.html

ORA-16136: Managed Standby Recovery not active

Hi
I am trying implement the dataguard in the windows platform. And this is my first time. Right now iam trying on physical standby. i have done everything as per the document. But iam getting some error. After giving the
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
SQL> ALTER SYSTEM SWITCH LOGFILE;
SQL> recover managed standby database cancel;
// I am getting error
ORA-16136: Managed Standby Recovery not active
When just like that i tried to open the standby database in read only mode, i am getting error
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\DB1\SYSTEM01.DBF'
When i checked the alert log file of Primary Database, it shows:
PING[ARCo]: Heartbeat failed to connect to standby 'db2sby'. Error is 1031.
Wed Sep 01 14:10:27 2010
Thread 1 advanced to log sequence 337 (LGWR switch)
Current log# 2 seq# 337 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\DB1\REDO02.LOG
Wed Sep 01 14:10:28 2010
Deleted Oracle managed file C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\DB1\ARCHIVELOG\2010_02_25\O1_MF_1_224_5RD10Z5V_.ARC
Wed Sep 01 14:14:53 2010
Error 1031 received logging on to the standby
Wed Sep 01 14:14:53 2010
Errors in file c:\oracle\product\10.2.0\admin\db1\bdump\db1_arco_2156.trc:
ORA-01031: insufficient privileges
PING[ARCo]: Heartbeat failed to connect to standby 'db2sby'. Error is 1031.
Wed Sep 01 14:19:53 2010
Error 1031 received logging on to the standby
Wed Sep 01 14:19:53 2010
Errors in file c:\oracle\product\10.2.0\admin\db1\bdump\db1_arco_2156.trc:
ORA-01031: insufficient privileges
And when i checked alert log file of stand by database:
Wed Sep 01 14:13:19 2010
Errors in file c:\oracle\product\10.2.0\standbyy\admin\db2\bdump\db2sby_dbw0_3060.trc:
ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: 'C:\TSUNDO12.DBF'
ORA-27086: unable to lock file - already in use
OSD-00001: additional error information
O/S-Error: (OS 101) The exclusive semaphore is owned by another process
--> The above error of Standby was coming for each datafile such as system, users etc.
Kindly Help me.
Shiyas M

here is the pfile of Primary Database:
db1.__db_cache_size=188743680
db1.__java_pool_size=4194304
db1.__large_pool_size=4194304
db1.__shared_pool_size=83886080
db1.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0/admin/db1/adump'
*.background_dump_dest='C:\oracle\product\10.2.0/admin/db1/bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\db1\control01.ctl','C:\oracle\product\10.2.0\oradata\db1\control02.ctl','C:\oracle\product\10.2.0\oradata\db1\control03.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0/admin/db1/cdump'
*.db_16k_cache_size=4194304
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='db1'
*.DB_UNIQUE_NAME='db1prim'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(db1,db2sby)'
*.LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle\product\10.2.0\ARCHIVELOG VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=db1prim'
*.LOG_ARCHIVE_DEST_2='SERVICE=db2sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=db2sby'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE
*.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
*.LOG_ARCHIVE_MAX_PROCESSES=30
*.FAL_SERVER=db2sby
*.FAL_CLIENT=db1
*.DB_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
*.LOG_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
*.STANDBY_FILE_MANAGEMENT=AUTO
*.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=db1XDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=95420416
*.processes=150
*.recyclebin='OFF'
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=287309824
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0/admin/db1/udump'
*.utl_file_dir='OCM_CONFIG_HOME/state'
Here is the Pfile of standby database:
db1.__db_cache_size=188743680
db1.__java_pool_size=4194304
db1.__large_pool_size=4194304
db1.__shared_pool_size=83886080
db1.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\Standbyy\oradata\db2\control001.ctl','C:\oracle\product\10.2.0\Standbyy\oradata\db2\control002.ctl','C:\oracle\product\10.2.0\Standbyy\oradata\db2\control003.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2'
*.db_16k_cache_size=4194304
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='db1'
*.DB_UNIQUE_NAME='db2sby'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(db1,db2sby)'
*.LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle\product\10.2.0\ARCHIVELOG VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=db2sby'
*.LOG_ARCHIVE_DEST_2='SERVICE=db1 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=db1'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE
*.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
*.LOG_ARCHIVE_MAX_PROCESSES=30
*.FAL_SERVER=db1
*.FAL_CLIENT=db2sby
*.DB_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
*.LOG_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
*.STANDBY_FILE_MANAGEMENT=AUTO
*.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area\DB2SBY'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=db1XDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=95420416
*.processes=150
*.recyclebin='OFF'
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=287309824
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\udump'
*.utl_file_dir='OCM_CONFIG_HOME/state'

ORA-279 signalled during recovery of standby database

Hi All,
I am preparing standby database after taking hot backup and copying those datafiles to standby,
taken controlfile standby controlfile backup from primary
mounted the standby database using standby controlfile using
startup nomount pfile='/u01/stand.ora'
alter database mount standby database;
Now I have started applying archives on standby database after copying all archives from primary to standby box the archives generated during backup using..
recover standby database;
But I am getting the below warning on the recovery screen...
ORA-00279: change 51667629050 generated at 07/02/2009 00:59:43 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55118_652209172.arc
ORA-00280: change 51667629050 for thread 1 is in sequence #55118
ORA-00278: log file '/nodal-archive/archive/1_55117_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667703096 generated at 07/02/2009 01:06:04 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55119_652209172.arc
ORA-00280: change 51667703096 for thread 1 is in sequence #55119
ORA-00278: log file '/nodal-archive/archive/1_55118_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667767649 generated at 07/02/2009 01:12:28 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55120_652209172.arc
ORA-00280: change 51667767649 for thread 1 is in sequence #55120
ORA-00278: log file '/nodal-archive/archive/1_55119_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc
ORA-00280: change 51667831821 for thread 1 is in sequence #55121
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer
needed for this recovery
and I am getting the below warning on the alert log..........
Sun Jul 5 18:37:36 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:37:36 2009
Media Recovery Log /nodal-archive/archive/1_55256_652209172.arc
Sun Jul 5 18:40:31 2009
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Sun Jul 5 18:40:31 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:40:31 2009
Media Recovery Log /nodal-archive/archive/1_55257_652209172.arc
Please suggest what to do now.............
Thanks in Advance,
Sukanta Paul.

Hi Sukanta,
I didn't really understand what the problem is...
Let me explain, hope it will be clear.
You created a standby control file, and backed up the database (it doesn't matter in which order). Now, you have a standby database that is ready to apply logs. It will be able to apply log forever, until we will stop it.
The messages you see say the following:
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for thread 1 {color:blue} - this says that the recovery process is now at scn 51667831821 {color}
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc {color:blue} - the information needed for the recover is in this file (this is only the default name, you can choose other name if the file is called differently) {color}
ORA-00280: change 51667831821 for thread 1 is in sequence #55121 {color:blue} - same here, the needed archive is sequence 55121 {color}
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer needed for this recovery {color:blue} - this message is after Oracle has applied the log, and it means that this log is no longer needed {color}
Now it will wait for the next log. Again, this process is endless, this is how it is made to allow the standby database to be always synched with the primary.
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

Database Datafiles Recovery. ORA-01219: database not open:

Hi,
I have a 10g database running on SuSE Linux server. I mistakenly deleted one of my file system's files that contain some of the database datafiles. I can connect to the database but I am failing to run queries:
SQL> select * from global_name;
select * from global_name
ERROR at line 1:
ORA-01219: database not open: queries allowed on fixed tables/views only
I do weekly cold backups of the server. My database is in NOARCHIVE log mode. What is the best way to recover my data; Is it possible that I restore only the file system or I should should do a complete restore of all file systems??
Regards
Kevin
Edited by: Kevin Honde on Jul 28, 2010 2:55 PM

I mistakenly deleted one of my file system's files that contain some of the database datafiles.Ok
I do weekly cold backups of the server.Great !!
My database is in NOARCHIVE log mode. That's the mistake in my opinion
What is the best way to recover my data; Restore it from the latest available cold backup.
There will be a data loss post weekly consistent cold backup. Which you have to accept because you do not have your database running in Archive Log mode.

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

ORA-01504: database name 'DEV1' does not match parameter db_name 'PROD1'

Hi, All -
This is my first time cloning a database. The recovery finished but gave me the following error message. All the parameters in the pfile are set to "DEV1". I believe that the parameter db_name 'PROD1' exists in the control file and causing this error. The control file is under ASM.
How can I change the parameter in the control file and bring the 'DEV1' cloned database up? Also, how can I avoid this issue next time I do a clone?
Thanks in advance!
Oracle 10g Release 2 on RHEL5
Database cloning using RMAN Duplicate > ORA-01504: database name 'DEV1' does not match parameter db_name 'PROD1'
ASMCMD> ls
control01.ctl
current.275.729098001
archive log filename=/u001/dbsvr/dev1/1_131706_653848580.dbf recid=59 stamp=741953991
media recovery complete, elapsed time: 00:09:31
*Finished recover at 01-FEB-11*
contents of Memory Script:
   shutdown clone;
   startup clone nomount ;
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area     725614592 bytes
Fixed Size                     2075592 bytes
Variable Size                448791608 bytes
Database Buffers             268435456 bytes
Redo Buffers                   6311936 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DEV1" RESETLOGS ARCHIVELOG
MAXLOGFILES     50
MAXLOGMEMBERS      5
MAXDATAFILES      100
MAXINSTANCES     1
MAXLOGHISTORY     5445
LOGFILE
GROUP 1 '+DATA3/dev1/datafile/redo01.log' SIZE 100 M ,
GROUP 2 '+DATA3/dev1/datafile/redo02.log' SIZE 100 M ,
GROUP 3 '+DATA3/dev1/datafile/redo03.log' SIZE 100 M
DATAFILE
'+DATA3/dev1/datafile/system01.dbf'
CHARACTER SET WE8ISO8859P1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 02/01/2011 10:30:17
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01504: database name 'DEV1' does not match parameter db_name 'PROD1'
RMAN>
RMAN> **end-of-file**
RMAN>

Respected, Sybrand Bakker -
Thanks for constructive feedback!
Here are the command that I ran.
RMAN> connect target sys/<password>@PROD1
connected to target database: PROD1 (DBID=556212836)
RMAN> connect auxiliary sys/<password>
connected to auxiliary database: DEV1 (not mounted)
RMAN> @rman_dup.sql
rman_dup.sql contains
run {
    allocate auxiliary channel d1 type disk;
set newname for datafile 1 to '+DATA3/dev/datafile/system01.dbf';
set newname for datafile 2 to '+DATA3/dev/datafile/undotbs01.dbf';
set newname for datafile 3 to '+DATA3/dev/datafile/cwmlite01.dbf';
set newname for datafile 4 to '+DATA3/dev/datafile/drsys01.dbf';
set newname for datafile 5 to '+DATA3/dev/datafile/example01.dbf';
set newname for datafile 6 to '+DATA3/dev/datafile/indx01.dbf';
set newname for datafile 7 to '+DATA3/dev/datafile/odm01.dbf';
set newname for datafile 8 to '+DATA3/dev/datafile/tools01.dbf';
set newname for datafile 9 to '+DATA3/dev/datafile/users01.dbf';
set newname for datafile 10 to '+DATA3/dev/datafile/xdb01.dbf';
set newname for datafile 11 to '+DATA3/dev/datafile/cons01.dbf';
set newname for datafile 12 to '+DATA3/dev/datafile/survey01.dbf';
set newname for datafile 13 to '+DATA3/dev/datafile/mem201.dbf';
set newname for datafile 14 to '+DATA3/dev/datafile/cons02.dbf';
set newname for datafile 15 to '+DATA3/dev/datafile/mem202.dbf';
set newname for datafile 16 to '+DATA3/dev/datafile/cater01.dbf';
set newname for datafile 17 to '+DATA3/dev/datafile/users02.dbf';
set newname for datafile 18 to '+DATA3/dev/datafile/mar_data01.dbf';
set newname for datafile 19 to '+DATA3/dev/datafile/sysaux01.dbf';
set newname for datafile 20 to '+DATA3/dev/datafile/streams_tbs_01.dbf';
set newname for datafile 21 to '+DATA3/dev/datafile/users03.dbf';
set newname for tempfile 1 to '+DATA3/dev1/tempfile/temp01.dbf';
duplicate target database to dev1
until scn 48712532746
logfile
   '+DATA3/dev1/datafile/redo01.log' size 100M,
   '+DATA3/dev1/datafile/redo02.log' size 100M,
   '+DATA3/dev1/datafile/redo03.log' size 100M;
}Edited by: CipherDBA on Feb 3, 2011 10:50 AM

ORA-01103: database name 'ORDB' in control file is not 'ORCL'

hey there !!
11.2.0
win 7 pro
let me tell u whole scenario for how i reach to this error - ORA-01103: database name 'ORDB' in control file is not 'ORCL'
-installed new 11g ( test/ practice environment )
-by default database created 'ORCL' while installation
-created another instance 'ORDB' ( my aim was to create auxiliary database/duplicate database )
-done well according to oracle documents and SUCESSFULLY created a duplicated database
-i thot of sycnronization to auxiliary to target db , so i read docs and learn that you can issue
DUPLICATE TARGET DATABASE TO dupdb ( its an oracle Doc's exmple so i put my db name and path accordingly )
SKIP TABLESPACE tools
LOGFILE
GROUP 1 ('/duplogs/redo01a.log',
'/duplogs/redo01b.log') SIZE 200K REUSE,
GROUP 2 ('/duplogs/redo02a.log',
'/duplogs/redo02b.log') SIZE 200K REUSE;NOW, process was Failed , above command didn work bcos of some syntax error .
BUT what happned is - now whenever i connect both target and auxiliary database from RMAN it shows this -
C:\Users\Administrator>rman target /@orcl auxiliary /@ordb
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Apr 5 10:54:04 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1339650140)
connected to auxiliary database: ORCL (not mounted)
RMAN>and also whenever i connect Target ( main , not auxiliary db ) from SQL it shows the error that i described in title .
I feel like something BUG because this happned to me 5th time , in that 5 times 4 times i got this error while i was duplicating a database . and also after sucessfully duplicated DB ( that was 5th time )
Thanks
Regards

Hi ,
check the db_name parameter in init parameter file.
Edited by: Jamsher on Apr 4, 2013 10:33 PM

Help for: ORA-01103: database name PRIMARY in control file is not STANDBY

Hello all, this will be my first post to the support forum. I'm an associate dba with just 6 months on the job, so if I've forgotten something or not given some infromation that is needed please let me know.
I've also combed the forums/internet, and some of the answers haven't helped. The Oracle Document ORA-1103 While Mounting the Database Using PFILE [ID 237073.1] says my init.ora file is corrupted, but creating a new init.ora file from the spfile does not help. Neither does just starting from the spfile. I have older copies of the init.ora file and the spfiles that the database was running on previously, so I believe they are good.
This standby NIRNASD1 has existed previously, I had to refresh the primary NIKNASD2, and then re-instantiate NIRNASD1 after the refresh is complete.
My env is set correctly, and my ORACLE_SID has been exported to NIRNASD1
NIKNASD2 = Primary Database
NIRNASD1 = Secondary/Standby Database
Goal: Creation of Logical Standby NIRNASD1 after creating Physical Standby from NIKNASD2
My database versions are 10.2.0.4.0, and the databases are on a Unix server. Both databases are located on separate servers.
Steps that I have taken:
I used RMAN to backup our primary database to the staging area:
$ rman target /
run {
backup database
format '/datatransa/dg_stage/%U'
include current controlfile for standby;
sql "alter system archive log current";
backup archivelog all format '/datatransa/dg_stage/%U';
I used RMAN to Create Secondary Database utilizing RMAN DUPLICATE command.
RMAN> run {
2> allocate auxiliary channel auxdisk device type disk;
3> duplicate target database for standby NOFILENAMECHECK;
4> }
On Secondary database I started Managed Recovery mode
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
(I used pfile here, thinking that I needed to mount the database to the pfile so that the database would see the change in the dataguard parameters in the init.ora file, the change from logical to physical- I commeneted out the logical and uncommented the physical line)
# Dataguard Parameters
For logical standby, change db_name to name of standby database.
db_name=NIKNASD2 ### for physical, db_name is same as primary
#db_name=NIRNASD1 ### for logical, db_name is same as unique_name
SQL> STARTUP MOUNT PFILE = /oraa/app/oracle/product/1020/admin/NIRNASD1/pfile/initNIRNASD1.ora;
ORACLE instance started.
Total System Global Area 1577058304 bytes
Fixed Size 2084368 bytes
Variable Size 385876464 bytes
Database Buffers 1174405120 bytes
Redo Buffers 14692352 bytes
Database mounted.
SQL> ALTER DATABASE recover managed standby database using current logfile disconnect;
I then verified the Data Guard Configuration by using “alter system archive log current;” on the primary database and watching the sequence number change in the secondary database.
I made sure that:
•     The primary database was in MAXIMUM PERFORMANCE MODE
•     Stopped managed recover on the standby database: alter database recover managed standby database cancel;
•     Built a logical standby data dictionary on the primary database
•     The db_name in init.ora was changed (this is in our document at my job)
•     I changed my database name (from physical to logical) in my init.ora pfile (reverse of what I did above)
# Dataguard Parameters
For logical standby, change db_name to name of standby database.
#db_name=NIKNASD2 ### for physical, db_name is same as primary
db_name=NIRNASD1 ### for logical, db_name is same as unique_name
I then went to shutdown my standby database and re-start it in a mount exclusive state, which is where I get the ORA-01103 Error (Again I used the pfile, thinking that I needed to tell the database it is now a logical standby):
SQL> shutdown immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP EXCLUSIVE MOUNT PFILE = /oraa/app/oracle/product/1020/admin/NIRNASD1/pfile/initNIRNASD1.ora;
ORACLE instance started.
Total System Global Area 1577058304 bytes
Fixed Size 2084368 bytes
Variable Size 385876464 bytes
Database Buffers 1174405120 bytes
Redo Buffers 14692352 bytes
ORA-01103: database name 'NIKNASD2' in control file is not 'NIRNASD1'
From what I understand of the process, the name in the control file is correct, I want it to be NIRNASD1. But the database for some reason thinks it should be NIKNASD2. The following are the parts of my init.ora file that include the dataguard parameters:
# Database Identification
db_domain=""
#db_name=NIRNASD1
#db_unique_name=NIRNASD1
# File Configuration
control_files=("/oradba2/oradata/NIRNASD1/control01.ctl", "/oradba3/oradata/NIRNASD1/control02.ctl", "/oradba4/oradata/NIRNASD1/control03.ctl")
# Instance Identification
instance_name=NIRNASD1
# Dataguard Parameters
#db_name=NIKNASD2 ### for physical, db_name is same as prmary
db_name=NIRNASD1 ### for logical, db_name is same as unique_name
db_unique_name=NIRNASD1
dg_broker_start=TRUE
db_file_name_convert='NIKNASD2','NIRNASD1'
log_file_name_convert='NIKNASD2','NIRNASD1'
log_archive_config='dg_config=(NIRNASD1,NIKNASD2)'
log_archive_dest_1='LOCATION="/oraarcha/NIRNASD1/" valid_for=(ONLINE_LOGFILES,all_roles) db_unique_name=NIRNASD1'
#log_archive_dest_2='LOCATION="/oraarcha/NIKNASD2/" valid_for=(standby_logfiles,standby_roles) db_unique_name=NIRNASD1'
log_archive_dest_2='LOCATION="/oraarcha/NIKNASD2/" valid_for=(standby_logfile,standby_role) db_unique_name=NIRNASD1'
STANDBY_ARCHIVE_DEST='LOCATION=/oraarcha/NIKNASD2/'
# Parameters are not needed since this server will NOT become primary
#log_archive_dest_2='service=NIKNASD2
# valid_for=(online_logfiles,primary_role)
# db_unique_name=NIKNASD2'
fal_server='NIKNASD2'
fal_client='NIRNASD1'
I would appreciate any help, or pointing me in the right direction. I'm just missing something. I am reviewing the documents for building a physical and logical standby from oracle. Just not sure where to go from here.
Thank you
Edited by: 977917 on Dec 19, 2012 5:49 PM

First of all, thank you both for answering my post. I've pulled up Mr. Hesse's page and will make it a go-to staple.
We're in the process of upgrading our databases, but we have 130+ databases and only six Oracle dba's, and I'm one of them. It's a large corporation, and things move at a "slow and tested" pace.
The pfile parameters listed above are from my secondary/standby database. And I do want to create a logical standby.
I forgot to mention that we do use DataGuard Broker, but I did not think that would be the cause of why the database was starting up incorrectly, so I did not mention it. My apologies there.
As far as the db_name, here's my question on that. It's my understanding the the db_name should be the name of the primary database when you are working with a physical standby, but as soon as you convert it to logical, you should change the db_name to the secondary/standby database? Am I correct on that?
Leading from that, during the process of creating the physical standby and converting the physical standby to the logical standby, should I change the db_name in the secondary/standby database in the spfile and never use the pfile at all? For instance, when I create the physical standby I have to change the db_name in the standby to the PRIMARY database, so that makes me think I should change db_name in the spfile? (If you see above, I changed db_name in the pfile and did a startup pfile)
This morning I was able to reach out to a fellow DBA (they are were asleep when I posted this last night), and they tried a few things. We had a redirect in the standby directory /oraa/app/oracle/product/1020/dbs folder that looked like this: spfileNIRNASD1.ora -> /oraa/app/oracle/product/1020/admin/NIRNASD1/pfile/spfileNIRNASD1.ora
She removed the redirect and the startup mount exclusive then worked without the error.
Thank you again for your help Mr.Quluzade and Mr. Hesse, I appreciate you all taking the time to teach someone new to the craft. I will definitely read up on the link that you sent me.
Chris Cranford

RMAN-06067: RECOVER DATABASE required with a backup or created controlfile

Hi,
DB:9.2.0.8
OS: AIX 5.3
I am restoring DB with until time(12/06/2012) for needed tablespaces.
I restored the 12th date controlfile ,which is backed up with archivedlogs. I also have one more controlfile which backed up with full DB..
Restore of tablespaces are completed..
When recovery is going , failed with following error..
allocated channel: c7
channel c7: sid=22 devtype=SBT_TAPE
channel c7: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
allocated channel: c8
channel c8: sid=21 devtype=SBT_TAPE
channel c8: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
executing command: SET until clause
Starting recover at 23-06-2012 02:00:15
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: c5
released channel: c6
released channel: c7
released channel: c8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/23/2012 03:36:57
RMAN-06067: RECOVER DATABASE required with a backup or created controlfile
RMAN>
Restore Script:
connect target /
connect catalog rmanc/recom@lgn_rmanc
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
allocate channel c9 type 'SBT_TAPE';
allocate channel c10 type 'SBT_TAPE';
allocate channel c11 type 'SBT_TAPE';
allocate channel c12 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
release channel c9;
release channel c10;
release channel c11;
release channel c12;
Recover Script:
connect catalog rmanc/recom@lgn_rmanc
connect target /
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
recover tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
Any suggestion in this is helpful to me..
Thanks in advance,

Hello;
I read your post and here's the thoughts that came to mind : ( my largest concern is you might restore something that damages your current system )
1. So you want to restore the whole DB back to 12/06/2012 to get some tablespaces from then right?
2. Are you restoring to a different system?
3. How did you start the database ( NOMOUNT, MOUNT )
4. If you are restoring the whole DB back to 12/06/2012 how did you restore the control file?
5. Your command shows :
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
COMMENT : Generally I use recover tablespace for point in time recovery and use an auxilary destination.
Meaning I don't use restore at all, in fact using restore may cause an issue.
SUMMARY : I don't see how this will work as is.
It seems you want data from five tablespaces from about six months ago including the SYSTEM tablespace.
This is an Incomplete Recovery. I believe I would rethink this completely.
Give the time that has past I would consider restoring the whole database to a different server where cannot damage anything.
Once this is done I would decide how to get the data I need.
Or I would check for a daily export file and recover the tablespace data that way.
So you have some good details on your question but it seems the plan is either missing something or you need to add a few more details.
Example
I'm recovering old tablespaces into a test system.
Here's how I'm not damaging my current production system.
I don't have an export from that date.
So take a step back and either rethink or give a few more details on how this is safe.
Best Regards
mseberg

Ora-01219 database not open; only queries on fixed tables and views.

Hi everyone
There is another post stating this error, but since the source is different, I think is okay to make a different post as well.
Our database was working fine until the other day, when suddenly power went off, UPS was damaged and didn't hold, and when we restarted the database this is what happens:
Using Enterprise Manager Console, we can make a succesful connection in the same machine, but if we choose Schema, the following error appears:
ora-01219 database not open; only queries on fixed tables and views.
When accesing from a different machine:
ORA-01033: ORACLE initialization or shutdown in progress
Thanks in advance

Here is the last entries of alert log
Fatal NI connect error 12638, connecting to:
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 11.1.0.7.0 - Production
Time: 20-JUL-2010 15:48:31
Tracing not turned on.
Tns error struct:
ns main err code: 12638
TNS-12638: Fallo de recuperación de credenciales
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Tue Jul 20 15:50:50 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in server-side spfile E:\ORACLE\CRIMINALISTICA\PRODUCT\11.1.0\DB_1\DATABASE\SPFILECRIM.ORA
System parameters with non-default values:
processes = 150
memory_target = 816M
control_files = "E:\ORACLE\ORADATA\CRIM\CONTROL01.CTL"
control_files = "E:\ORACLE\ORADATA\CRIM\CONTROL02.CTL"
control_files = "E:\ORACLE\ORADATA\CRIM\CONTROL03.CTL"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "E:\Oracle\flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=CRIMXDB)"
audit_file_dest = "E:\ORACLE\ADMIN\CRIM\ADUMP"
audit_trail = "DB"
db_name = "CRIM"
open_cursors = 300
diagnostic_dest = "E:\ORACLE"
Tue Jul 20 15:50:55 2010
PMON started with pid=2, OS id=1688
Tue Jul 20 15:50:55 2010
VKTM started with pid=3, OS id=2236 at elevated priority
Tue Jul 20 15:50:55 2010
DIAG started with pid=4, OS id=2332
Tue Jul 20 15:50:55 2010
DBRM started with pid=5, OS id=2328
Tue Jul 20 15:50:55 2010
PSP0 started with pid=6, OS id=2432
VKTM running at (20)ms precision
Tue Jul 20 15:50:55 2010
DIA0 started with pid=7, OS id=2160
Tue Jul 20 15:50:55 2010
MMAN started with pid=8, OS id=2156
Tue Jul 20 15:50:55 2010
DBW0 started with pid=9, OS id=2064
Tue Jul 20 15:50:55 2010
LGWR started with pid=10, OS id=3176
Tue Jul 20 15:50:55 2010
CKPT started with pid=11, OS id=3180
Tue Jul 20 15:50:55 2010
SMON started with pid=12, OS id=3184
Tue Jul 20 15:50:55 2010
RECO started with pid=13, OS id=3188
Tue Jul 20 15:50:55 2010
MMON started with pid=14, OS id=3192
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = E:\Oracle
Tue Jul 20 15:50:55 2010
MMNL started with pid=15, OS id=3196
Tue Jul 20 15:50:56 2010
alter database mount exclusive
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 1304879008
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Errors in file e:\oracle\diag\rdbms\crim\crim\trace\crim_dbw0_2064.trc:
ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: 'E:\ORACLE\ORADATA\STOPCRIM5\STOPCRIM5TABLESPACE.ORA'
ORA-27047: unable to read the header block of file
OSD-04006: fallo de ReadFile(); no se ha podido leer del archivo
O/S-Error: (OS 38) Se ha alcanzado el final del archivo.
Errors in file e:\oracle\diag\rdbms\crim\crim\trace\crim_dbw0_2064.trc:
ORA-01157: cannot identify/lock data file 16 - see DBWR trace file
ORA-01110: data file 16: 'E:\ORACLE\ORADATA\PRUEBACARLOS\PRUEBACARLOSTABLESPACE.ORA'
ORA-27047: unable to read the header block of file
OSD-04006: fallo de ReadFile(); no se ha podido leer del archivo
O/S-Error: (OS 38) Se ha alcanzado el final del archivo.
Errors in file e:\oracle\diag\rdbms\crim\crim\trace\crim_dbw0_2064.trc:
ORA-01157: cannot identify/lock data file 17 - see DBWR trace file
ORA-01110: data file 17: 'E:\ORACLE\ORADATA\PRUEBACARLOS\PRUEBACARLOSINDEX.ORA'
ORA-27047: unable to read the header block of file
OSD-04006: fallo de ReadFile(); no se ha podido leer del archivo
O/S-Error: (OS 38) Se ha alcanzado el final del archivo.
ORA-1157 signalled during: alter database open...
Tue Jul 20 16:04:39 2010
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.

ORA-39700: database must be opened with UPGRADE option

Dear buddies,
I just opened my database : startup upgrade and it started up.
But couldn't perform a backup.
Should I be running pupbld?
Could this problem be due to some opatch?
Here is a part of my alert log:
Thread 1 opened at log sequence 1050
Current log# 3 seq# 1050 mem# 0: D:\ORACLE\DATA\MIG\LOG_03.DBF
Successful open of redo thread 1
Wed Aug 11 13:35:15 2010
MTTR advisory is disabled because either FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is set
Wed Aug 11 13:35:15 2010
SMON: enabling cache recovery
Wed Aug 11 13:35:16 2010
Errors in file d:\oracle\admin\mig\udump\mig_ora_1564.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Wed Aug 11 13:35:16 2010
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Wed Aug 11 13:35:16 2010
Errors in file d:\oracle\admin\mig\bdump\mig_pmon_3088.trc:
ORA-00704: bootstrap process failure
Wed Aug 11 13:35:16 2010
Errors in file d:\oracle\admin\mig\bdump\mig_reco_1868.trc:
ORA-00704: bootstrap process failure
Wed Aug 11 13:35:16 2010
Errors in file d:\oracle\admin\mig\bdump\mig_psp0_2624.trc:
ORA-00704: bootstrap process failure
Wed Aug 11 13:35:16 2010
Errors in file d:\oracle\admin\mig\bdump\mig_mman_3312.trc:
ORA-00704: bootstrap process failure
Wed Aug 11 13:35:16 2010
Errors in file d:\oracle\admin\mig\bdump\mig_dbw0_2304.trc:
ORA-00704: bootstrap process failure
Wed Aug 11 13:35:16 2010
Errors in file d:\oracle\admin\mig\bdump\mig_lgwr_552.trc:
ORA-00704: bootstrap process failure
Wed Aug 11 13:35:16 2010
Errors in file d:\oracle\admin\mig\bdump\mig_ckpt_2300.trc:
ORA-00704: bootstrap process failure
Wed Aug 11 13:35:17 2010
Errors in file d:\oracle\admin\mig\bdump\mig_smon_2136.trc:
ORA-00704: bootstrap process failure
Instance terminated by USER, pid = 1564
ORA-1092 signalled during: ALTER DATABASE OPEN...
Please comment.
Thanks.
Nith

I just opened my database : startup upgrade and it started up.
But couldn't perform a backup.As you said you have started the DB in upgrade mode and trying to take the backup of database. I think you can't take the backup of DB in upgrade mode.Please shut it down first and start up it in normal mode and do the backup.
Which backup strategy you are following?
What you exactly want to do upgrade the database or trying to take a bcakup?

ORA-16795: database resource guard detects that database re-creation is req

Hi, I have Data Guard with data broker (Oracle 10.2.0.4) set up with RMAN and RMAN catalog. I was recovering my primary from a corrupted datafile, when automatic failover took place. After I did the recovery, I tried to re-instate my primary, but ran into the followign error:
Error: ORA-16795: database resource guard detects that database re-creation is requiredIn order to recreate the old primary (new standby), can I just delete all of the dbf files on old primary and then follow the steps to create a standby using backups from new primary? What about RMAN catalog? Do I have to unregister anything from there? Do I need to delete the configuration? If anyone has steps on how to RE-CREATE standby, that would be very helpful. Thank you!

I followed the above Metalink note, but when I try to restore standby controlfie I get:
RMAN> restore standby controlfile from '/data/backup/081409/';
Starting restore at 14-AUG-09
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/14/2009 08:53:23
RMAN-06172: no autobackup found or specified handle is not a valid copy or pieceMy directory structure is the same on both machines for primary and standby. I did not have autobackup set when I took primary's backup. I backed up primary in the following way:
backup database plus archivelog;
backup current controlfile for standby;Any ideas?

ORA-16005 : database requires recovery

Similar Messages

Maybe you are looking for