Unable to startup 12c RAC database, can't open spfile in ASM

hello,
I'm testing 12cRAC database on RHEL5 and need your help to troubleshoot and fix the following issue -
DBCA fails at the end of the configuration to create and startup new RAC database with the following errors
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+DATA/TDB1/spfileTDB1.ora'
ORA-17503: ksfdopn:2 Failed to open file +DATA/TDB1/spfileTDB1.ora
ORA-15056: additional error message
ORA-17503: ksfdopn:2 Failed to open file +DATA/TDB1/spfiletdb1.ora
ORA-01017: invalid username/password; logon denied
I also tried executing script (which was created by DBCA) to create the new DB manually and got the same results - it happens during first attempt to start it up using SPFILE after new DB was successfully created (it was started up using pfile)
Clusterware with ASM install was successful, binaries were also installed without issues,
cluster seems healthy, I see correct files within ASM using asmcmd etc ..
got stuck here and need some directions ... very confused by ORA-01017 password error
wonder if anyone had same or similar issues ?
Thank you !

Fixed.
Thank you everyone for suggestions and recommendations -
ASM is accessible using asmcmd and I can see all the DB files incuding spfile, they were created by DBCA, alert log showed same information I posted
After extensive troubleshooting and testing the issue was idedntified and fixed - 'dba' group needs to be the primary group for 'oracle' user, not the secondary one. I suspected that something was not right with 'oracle' user access to asm based on that strange password error. There is more I need to check as the issue and fix with swapping groups seems strange. Secondary group is not enough ti have proper rights ??? my first reaction was - seriously ? wtf ?
Anyway - I need to move one now ...
Thank you again !

Similar Messages

Question: 10gR2 database can not see the 11gR2 ASM diskgroup?

Hi there,
env:
uname -rm
2.6.18-92.1.22.el5xen x86_64
Single server(non-RAC)
note: we don't want to upgrade 10gr2 database into 11gR2 yet. But we created the 11gR2 ASM, then a 11gr2 database on ASM, and plan to migrate datafile in 10gR2 database to 11gR2 ASM
1. oracle 10gR2 installed first version: 10.2.0.3.0
2. then install 11gR2 Grid Infrastructure, and created ASM (version 11gr2)
$ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.1.0 Production on Tue Oct 19 10:30:56 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Automatic Storage Management option
SQL> col name form a15
SQL> col COMPATIBILITY form a15
SQL> col DATABASE_COMPATIBILITY form a15
SQL> l
1* select name , STATE, COMPATIBILITY, DATABASE_COMPATIBILITY from v$asm_diskgroup
SQL> /
NAME STATE COMPATIBILITY DATABASE_COMPAT
ORCL_DATA1 MOUNTED 11.2.0.0.0 10.1.0.0.0
ORA_DATA MOUNTED 10.1.0.0.0 10.1.0.0.0
3. in 10gR2 database
sqlplus /
SQL*Plus: Release 10.2.0.3.0 - Production on Tue Oct 19 12:12:31 2010
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning and Data Mining options
SQL> select * from v$asm_diskgroup;
no rows selected
4. pin the node into css
# /u01/app/product/11.2.0/grid/bin/crsctl pin css -n mynodename
CRS-4000: Command Pin failed, or completed with errors.
Question: 10gR2 database can not see the 11gR2 ASM diskgroup?
please help
Thanks
Scott

What is the output of
olsnodes -t -n
Also, see unix error log and ohasd error log if you find anything in that

How many databases can be opened simultaneously in a single file?

To all:
I don't known how many databases can be opened simultaneously in a single file. After my application open 499 databases in a single file simultaneously, DB->open return error 12.(can not allocate memory ?).
How can i do ? Thanks.

I found it:
Berkeley DB Reference Guide:
Locking Subsystem
PrevRefNext
Configuring locking: sizing the system
The lock system is sized using the following three methods:
DB_ENV->set_lk_max_locks
DB_ENV->set_lk_max_lockers
DB_ENV->set_lk_max_objects
The DB_ENV->set_lk_max_locks, DB_ENV->set_lk_max_lockers, and DB_ENV->set_lk_max_objects methods specify the maximum number of locks, lockers, and locked objects supported by the lock subsystem, respectively. The maximum number of locks is the number of locks that can be simultaneously requested in the system. The maximum number of lockers is the number of lockers that can simultaneously request locks in the system. The maximum number of lock objects is the number of objects that can simultaneously be locked in the system. Selecting appropriate values requires an understanding of your application and its databases. If the values are too small, requests for locks in an application will fail. If the values are too large, the locking subsystem will consume more resources than is necessary. It is better to err in the direction of allocating too many locks, lockers, and objects because increasing the number of locks does not require large amounts of additional resources. The default values are 1000 of each type of object.
When configuring a Berkeley DB Concurrent Data Store application, the number of lock objects needed is two per open database (one for the database lock, and one for the cursor lock when the DB_CDB_ALLDB option is not specified). The number of locks needed is one per open database handle plus one per simultaneous cursor or non-cursor operation.
Configuring a Berkeley DB Transactional Data Store application is more complicated. The recommended algorithm for selecting the maximum number of locks, lockers, and lock objects is to run the application under stressful conditions and then review the lock system's statistics to determine the maximum number of locks, lockers, and lock objects that were used. Then, double these values for safety. However, in some large applications, finer granularity of control is necessary in order to minimize the size of the Lock subsystem.
The maximum number of lockers can be estimated as follows:
* If the database environment is using transactions, the maximum number of lockers can be estimated by adding the number of simultaneously active non-transactional cursors open database handles to the number of simultaneously active transactions and child transactions (where a child transaction is active until it commits or aborts, not until its parent commits or aborts).
* If the database environment is not using transactions, the maximum number of lockers can be estimated by adding the number of simultaneously active non-transactional cursors and open database handles to the number of simultaneous non-cursor operations.
The maximum number of lock objects needed for a single database operation can be estimated as follows:
* For Btree and Recno access methods, you will need one lock object per level of the database tree, at a minimum. (Unless keys are quite large with respect to the page size, neither Recno nor Btree database trees should ever be deeper than five levels.) Then, you will need one lock object for each leaf page of the database tree that will be simultaneously accessed.
* For the Queue access method, you will need one lock object per record that is simultaneously accessed. To this, add one lock object per page that will be simultaneously accessed. (Because the Queue access method uses fixed-length records and the database page size is known, it is possible to calculate the number of pages -- and, therefore, the lock objects -- required.) Deleted records skipped by a DB_NEXT or DB_PREV operation do not require a separate lock object. Further, if your application is using transactions, no database operation will ever use more than three lock objects at any time.
* For the Hash access method, you only need a single lock object.
For all access methods, you should then add an additional lock object per database for the database's metadata page.
Note that transactions accumulate locks over the transaction lifetime, and the lock objects required by a single transaction is the total lock objects required by all of the database operations in the transaction. However, a database page (or record, in the case of the Queue access method), that is accessed multiple times within a transaction only requires a single lock object for the entire transaction.
The maximum number of locks required by an application cannot be easily estimated. It is possible to calculate a maximum number of locks by multiplying the maximum number of lockers, times the maximum number of lock objects, times two (two for the two possible lock modes for each object, read and write). However, this is a pessimal value, and real applications are unlikely to actually need that many locks. Reviewing the Lock subsystem statistics is the best way to determine this value.
I created DB_CONFIG file, and add three lines:
set_lk_max_locks 20000
set_lk_max_lockers 20000
set_lk_max_objects 20000
As the default values are 1000 of each type of object, my applicaton open 499 database(except internal database) simultaneously(CDB modal) . After changed parameters, my application opend above 6000 database.

Time to connect to RAC database

Hi,
I have installed 11gr2 RAC database on windows server 2008 on ASM. I can connect to existing prod db withing a second but it is taking almost 20Seconds for me to connect to the RAC database. Is it because of the SCAN IPs?
Can anyone let me know the reason behind it and the resolution on it?
Thanks...
Edited by: user2995637 on Jul 22, 2011 6:15 AM
Edited by: user2995637 on Jul 22, 2011 6:16 AM

user2995637 wrote:
I have installed 11gr2 RAC database on windows server 2008 on ASM. I can connect to existing prod db withing a second but it is taking almost 20Seconds for me to connect to the RAC database. Is it because of the SCAN IPs?No. Should not be the case, normally.
Yes, some TNS connections can be slower than others. There are a number of factors. The initial connection may result in a redirect to another listener on a different IP address (e.g. load balancing). This will be slower than a direct connection (no redirect).
In such a case for example, where a redirect occurs, the client with receive a redirect to a new hostname. It needs to resolve that to an IP. This can be slow due to DNS issues (either with the DNS itself, or with the resolution scope config of the client).
The connection can request a dedicated sever instead of a shared server. A shared server connection is simply a hand-off of that client to an existing dispatcher process. A dedicated server connection requires the Listener to launch a brand new Oracle server process, for that process to attach itself to the SGA, and then resume the connection/conversation with the client. Thus shared server is by its nature a lot faster to establish a connection with than a dedicated server.
So there are a number of moving parts that can be slow. And you will need to isolate these and test each in turn to determine where the performance knock is.

How can I have a collective AWR report for RAC database in 10gR2 and 11gR1?

Plz correct me here
awrrpt.sql takes the snapshot at the instance level and incase we have 5 instances we have to take 5 awr reports for a particular period.correct???
If above is true ,any wayout to collect a single collective AWR report for RAC database which includes information on all the instances in Oracle 10g R2 or 11gR1 ?
Thanks in advance
Gagan

I have never come across a way for this. though I can n't say it is not there.
But I guess it may not be feasible too becuase as we know the current AWR report contains data which is specific for one instance.
Various hit ratios, top events, instance effeciency reports.... what not ..
It would be really nice to see something is a new format where it lists values from each instance in a single report.. I guess such a thing Does not exiist as of now.

Can not start Rac database

Hi,
Oracle RAC database 10.2.0.3/RedHat4 with 2 nodes.
In the begining we had an error ORA-600[12803] so only sys can connect to database I find the note 1026653.6 this note said that we need to create AUDSES$ sequence but befor that we have to restart the database.
When we stop the datanbase we had another ORA-600 and it's impossible to start it!!
Here is a coppy of our alert file:
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes = 300
sessions = 335
sga_max_size = 524288000
__shared_pool_size = 310378496
__large_pool_size = 4194304
__java_pool_size = 8388608
__streams_pool_size = 8388608
spfile = +DATA/osista/spfileosista.ora
nls_language = FRENCH
nls_territory = FRANCE
nls_length_semantics = CHAR
sga_target = 524288000
control_files = DATA/osista/controlfile/control01.ctl, DATA/osista/controlfile/control02.ctl
db_block_size = 8192
__db_cache_size = 184549376
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=USE_DB_RECOVERY_FILE_DEST
db_file_multiblock_read_count= 16
cluster_database = TRUE
cluster_database_instances= 2
db_create_file_dest = +DATA
db_recovery_file_dest = +FLASH
db_recovery_file_dest_size= 68543315968
thread = 2
instance_number = 2
undo_management = AUTO
undo_tablespace = UNDOTBS2
undo_retention = 29880
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=OSISTAXDB)
local_listener = (address=(protocol=tcp)(port=1521)(host=132.147.160.243))
remote_listener = LISTENERS_OSISTA
job_queue_processes = 10
background_dump_dest = /oracle/product/admin/OSISTA/bdump
user_dump_dest = /oracle/product/admin/OSISTA/udump
core_dump_dest = /oracle/product/admin/OSISTA/cdump
audit_file_dest = /oracle/product/admin/OSISTA/adump
db_name = OSISTA
open_cursors = 300
pga_aggregate_target = 104857600
aq_tm_processes = 1
Cluster communication is configured to use the following interface(s) for this instance
172.16.0.2
Wed Jun 13 11:04:30 2012
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=8560
DIAG started with pid=3, OS id=8562
PSP0 started with pid=4, OS id=8566
LMON started with pid=5, OS id=8570
LMD0 started with pid=6, OS id=8574
LMS0 started with pid=7, OS id=8576
LMS1 started with pid=8, OS id=8580
MMAN started with pid=9, OS id=8584
DBW0 started with pid=10, OS id=8586
LGWR started with pid=11, OS id=8588
CKPT started with pid=12, OS id=8590
SMON started with pid=13, OS id=8592
RECO started with pid=14, OS id=8594
CJQ0 started with pid=15, OS id=8596
MMON started with pid=16, OS id=8598
Wed Jun 13 11:04:31 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=17, OS id=8600
Wed Jun 13 11:04:31 2012
starting up 1 shared server(s) ...
Wed Jun 13 11:04:31 2012
lmon registered with NM - instance id 2 (internal mem no 1)
Wed Jun 13 11:04:31 2012
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
1
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Wed Jun 13 11:04:31 2012
LMS 0: 0 GCS shadows cancelled, 0 closed
Wed Jun 13 11:04:31 2012
LMS 1: 0 GCS shadows cancelled, 0 closed
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Post SMON to start 1st pass IR
Wed Jun 13 11:04:31 2012
LMS 0: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:04:31 2012
LMS 1: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:04:31 2012
Submitted all GCS remote-cache requests
Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=20, OS id=8877
Wed Jun 13 11:04:43 2012
alter database mount
Wed Jun 13 11:04:43 2012
This instance was first to mount
Wed Jun 13 11:04:43 2012
Starting background process ASMB
ASMB started with pid=25, OS id=10068
Starting background process RBAL
RBAL started with pid=26, OS id=10072
Wed Jun 13 11:04:47 2012
SUCCESS: diskgroup DATA was mounted
Wed Jun 13 11:04:51 2012
Setting recovery target incarnation to 1
Wed Jun 13 11:04:52 2012
Successful mount of redo thread 2, with mount id 3005749259
Wed Jun 13 11:04:52 2012
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: alter database mount
Wed Jun 13 11:05:06 2012
alter database open
Wed Jun 13 11:05:06 2012
This instance was first to open
Wed Jun 13 11:05:06 2012
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Wed Jun 13 11:05:07 2012
Started redo scan
Wed Jun 13 11:05:07 2012
Completed redo scan
61 redo blocks read, 4 data blocks need recovery
Wed Jun 13 11:05:07 2012
Started redo application at
Thread 1: logseq 7924, block 3, scn 506098125
Wed Jun 13 11:05:07 2012
Recovery of Online Redo Log: Thread 1 Group 2 Seq 7924 Reading mem 0
Mem# 0: +DATA/osista/onlinelog/group_2.372.742132543
Wed Jun 13 11:05:07 2012
Completed redo application
Wed Jun 13 11:05:07 2012
Completed crash recovery at
Thread 1: logseq 7924, block 64, scn 506118186
4 data blocks read, 4 data blocks written, 61 redo blocks read
Switch log for thread 1 to sequence 7925
Picked broadcast on commit scheme to generate SCNs
db_recovery_file_dest_size of 65368 MB is 0.61% 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.
SUCCESS: diskgroup FLASH was mounted
SUCCESS: diskgroup FLASH was dismounted
Thread 1 advanced to log sequence 7926
SUCCESS: diskgroup FLASH was mounted
SUCCESS: diskgroup FLASH was dismounted
Thread 1 advanced to log sequence 7927
Wed Jun 13 11:05:11 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=31, OS id=12747
Wed Jun 13 11:05:11 2012
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=32, OS id=12749
Wed Jun 13 11:05:12 2012
Thread 2 opened at log sequence 7176
Current log# 4 seq# 7176 mem# 0: +DATA/osista/onlinelog/group_4.289.742134597
Wed Jun 13 11:05:12 2012
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Wed Jun 13 11:05:12 2012
Successful open of redo thread 2
Wed Jun 13 11:05:12 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Jun 13 11:05:12 2012
ARC0: Becoming the heartbeat ARCH
Wed Jun 13 11:05:12 2012
SMON: enabling cache recovery
Wed Jun 13 11:05:15 2012
Successfully onlined Undo Tablespace 20.
Wed Jun 13 11:05:15 2012
SMON: enabling tx recovery
Wed Jun 13 11:05:15 2012
Database Characterset is AL32UTF8
Wed Jun 13 11:05:16 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_9174.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Wed Jun 13 11:05:16 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_9174.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
USER: terminating instance due to error 600
Instance terminated by USER, pid = 9174
ORA-1092 signalled during: alter database open...
Wed Jun 13 11:06:16 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 eth0 172.16.0.0 configured from OCR for use as a cluster interconnect
Interface type 1 bond0 132.147.160.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes = 300
sessions = 335
sga_max_size = 524288000
__shared_pool_size = 314572800
__large_pool_size = 4194304
__java_pool_size = 8388608
__streams_pool_size = 8388608
spfile = +DATA/osista/spfileosista.ora
nls_language = FRENCH
nls_territory = FRANCE
nls_length_semantics = CHAR
sga_target = 524288000
control_files = DATA/osista/controlfile/control01.ctl, DATA/osista/controlfile/control02.ctl
db_block_size = 8192
__db_cache_size = 180355072
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=USE_DB_RECOVERY_FILE_DEST
db_file_multiblock_read_count= 16
cluster_database = TRUE
cluster_database_instances= 2
db_create_file_dest = +DATA
db_recovery_file_dest = +FLASH
db_recovery_file_dest_size= 68543315968
thread = 2
instance_number = 2
undo_management = AUTO
undo_tablespace = UNDOTBS2
undo_retention = 29880
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=OSISTAXDB)
local_listener = (address=(protocol=tcp)(port=1521)(host=132.147.160.243))
remote_listener = LISTENERS_OSISTA
job_queue_processes = 10
background_dump_dest = /oracle/product/admin/OSISTA/bdump
user_dump_dest = /oracle/product/admin/OSISTA/udump
core_dump_dest = /oracle/product/admin/OSISTA/cdump
audit_file_dest = /oracle/product/admin/OSISTA/adump
db_name = OSISTA
open_cursors = 300
pga_aggregate_target = 104857600
aq_tm_processes = 1
Cluster communication is configured to use the following interface(s) for this instance
172.16.0.2
Wed Jun 13 11:06:16 2012
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=18682
DIAG started with pid=3, OS id=18684
PSP0 started with pid=4, OS id=18695
LMON started with pid=5, OS id=18704
LMD0 started with pid=6, OS id=18721
LMS0 started with pid=7, OS id=18735
LMS1 started with pid=8, OS id=18753
MMAN started with pid=9, OS id=18767
DBW0 started with pid=10, OS id=18788
LGWR started with pid=11, OS id=18796
CKPT started with pid=12, OS id=18799
SMON started with pid=13, OS id=18801
RECO started with pid=14, OS id=18803
CJQ0 started with pid=15, OS id=18805
MMON started with pid=16, OS id=18807
Wed Jun 13 11:06:17 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=17, OS id=18809
Wed Jun 13 11:06:17 2012
starting up 1 shared server(s) ...
Wed Jun 13 11:06:17 2012
lmon registered with NM - instance id 2 (internal mem no 1)
Wed Jun 13 11:06:17 2012
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
1
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Wed Jun 13 11:06:18 2012
LMS 0: 0 GCS shadows cancelled, 0 closed
Wed Jun 13 11:06:18 2012
LMS 1: 0 GCS shadows cancelled, 0 closed
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Post SMON to start 1st pass IR
Wed Jun 13 11:06:18 2012
LMS 0: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:06:18 2012
LMS 1: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:06:18 2012
Submitted all GCS remote-cache requests
Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=20, OS id=18816
Wed Jun 13 11:06:18 2012
ALTER DATABASE MOUNT
Wed Jun 13 11:06:18 2012
This instance was first to mount
Wed Jun 13 11:06:18 2012
Reconfiguration started (old inc 2, new inc 4)
List of nodes:
0 1
Wed Jun 13 11:06:18 2012
Starting background process ASMB
Wed Jun 13 11:06:18 2012
Global Resource Directory frozen
Communication channels reestablished
ASMB started with pid=22, OS id=18913
Starting background process RBAL
* domain 0 valid = 0 according to instance 0
Wed Jun 13 11:06:18 2012
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Wed Jun 13 11:06:18 2012
LMS 0: 0 GCS shadows cancelled, 0 closed
Wed Jun 13 11:06:18 2012
LMS 1: 0 GCS shadows cancelled, 0 closed
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Wed Jun 13 11:06:18 2012
LMS 0: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:06:18 2012
LMS 1: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:06:18 2012
Submitted all GCS remote-cache requests
Fix write in gcs resources
RBAL started with pid=23, OS id=18917
Reconfiguration complete
Wed Jun 13 11:06:22 2012
SUCCESS: diskgroup DATA was mounted
Wed Jun 13 11:06:26 2012
Setting recovery target incarnation to 1
Wed Jun 13 11:06:26 2012
Successful mount of redo thread 2, with mount id 3005703530
Wed Jun 13 11:06:26 2012
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: ALTER DATABASE MOUNT
Wed Jun 13 11:06:27 2012
ALTER DATABASE OPEN
This instance was first to open
Wed Jun 13 11:06:27 2012
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Wed Jun 13 11:06:27 2012
Started redo scan
Wed Jun 13 11:06:27 2012
Completed redo scan
61 redo blocks read, 4 data blocks need recovery
Wed Jun 13 11:06:28 2012
Started redo application at
Thread 2: logseq 7176, block 3
Wed Jun 13 11:06:28 2012
Recovery of Online Redo Log: Thread 2 Group 4 Seq 7176 Reading mem 0
Mem# 0: +DATA/osista/onlinelog/group_4.289.742134597
Wed Jun 13 11:06:28 2012
Completed redo application
Wed Jun 13 11:06:28 2012
Completed crash recovery at
Thread 2: logseq 7176, block 64, scn 506138248
4 data blocks read, 4 data blocks written, 61 redo blocks read
Picked broadcast on commit scheme to generate SCNs
Wed Jun 13 11:06:28 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=28, OS id=19692
Wed Jun 13 11:06:28 2012
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=29, OS id=19695
Wed Jun 13 11:06:28 2012
Thread 2 advanced to log sequence 7177
Thread 2 opened at log sequence 7177
Current log# 3 seq# 7177 mem# 0: +DATA/osista/onlinelog/group_3.291.742134597
Successful open of redo thread 2
Wed Jun 13 11:06:28 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Jun 13 11:06:28 2012
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Wed Jun 13 11:06:28 2012
ARC1: Becoming the heartbeat ARCH
Wed Jun 13 11:06:28 2012
SMON: enabling cache recovery
Wed Jun 13 11:06:28 2012
db_recovery_file_dest_size of 65368 MB is 0.61% 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.
SUCCESS: diskgroup FLASH was mounted
SUCCESS: diskgroup FLASH was dismounted
Wed Jun 13 11:06:31 2012
Successfully onlined Undo Tablespace 20.
Wed Jun 13 11:06:31 2012
SMON: enabling tx recovery
Wed Jun 13 11:06:31 2012
Database Characterset is AL32UTF8
Wed Jun 13 11:06:31 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_19596.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Wed Jun 13 11:06:32 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_19596.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
USER: terminating instance due to error 600
Instance terminated by USER, pid = 19596
ORA-1092 signalled during: ALTER DATABASE OPEN...
Wed Jun 13 11:11:35 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Interface type 1 eth0 172.16.0.0 configured from OCR for use as a cluster interconnect
Interface type 1 bond0 132.147.160.0 configured from OCR for use as a public interface
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes = 300
sessions = 335
sga_max_size = 524288000
__shared_pool_size = 318767104
__large_pool_size = 4194304
__java_pool_size = 8388608
__streams_pool_size = 8388608
spfile = +DATA/osista/spfileosista.ora
nls_language = FRENCH
nls_territory = FRANCE
nls_length_semantics = CHAR
sga_target = 524288000
control_files = DATA/osista/controlfile/control01.ctl, DATA/osista/controlfile/control02.ctl
db_block_size = 8192
__db_cache_size = 176160768
compatible = 10.2.0.3.0
log_archive_dest_1 = LOCATION=USE_DB_RECOVERY_FILE_DEST
db_file_multiblock_read_count= 16
cluster_database = TRUE
cluster_database_instances= 2
db_create_file_dest = +DATA
db_recovery_file_dest = +FLASH
db_recovery_file_dest_size= 68543315968
thread = 2
instance_number = 2
undo_management = AUTO
undo_tablespace = UNDOTBS2
undo_retention = 29880
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=OSISTAXDB)
local_listener = (address=(protocol=tcp)(port=1521)(host=132.147.160.243))
remote_listener = LISTENERS_OSISTA
job_queue_processes = 10
background_dump_dest = /oracle/product/admin/OSISTA/bdump
user_dump_dest = /oracle/product/admin/OSISTA/udump
core_dump_dest = /oracle/product/admin/OSISTA/cdump
audit_file_dest = /oracle/product/admin/OSISTA/adump
db_name = OSISTA
open_cursors = 300
pga_aggregate_target = 104857600
aq_tm_processes = 1
Cluster communication is configured to use the following interface(s) for this instance
172.16.0.2
Wed Jun 13 11:11:35 2012
cluster interconnect IPC version:Oracle UDP/IP (generic)
IPC Vendor 1 proto 2
PMON started with pid=2, OS id=16101
DIAG started with pid=3, OS id=16103
PSP0 started with pid=4, OS id=16105
LMON started with pid=5, OS id=16107
LMD0 started with pid=6, OS id=16110
LMS0 started with pid=7, OS id=16112
LMS1 started with pid=8, OS id=16116
MMAN started with pid=9, OS id=16120
DBW0 started with pid=10, OS id=16132
LGWR started with pid=11, OS id=16148
CKPT started with pid=12, OS id=16169
SMON started with pid=13, OS id=16185
RECO started with pid=14, OS id=16203
CJQ0 started with pid=15, OS id=16219
MMON started with pid=16, OS id=16227
Wed Jun 13 11:11:36 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=17, OS id=16229
Wed Jun 13 11:11:36 2012
starting up 1 shared server(s) ...
Wed Jun 13 11:11:36 2012
lmon registered with NM - instance id 2 (internal mem no 1)
Wed Jun 13 11:11:36 2012
Reconfiguration started (old inc 0, new inc 2)
List of nodes:
1
Global Resource Directory frozen
* allocate domain 0, invalid = TRUE
Communication channels reestablished
Master broadcasted resource hash value bitmaps
Non-local Process blocks cleaned out
Wed Jun 13 11:11:36 2012
LMS 0: 0 GCS shadows cancelled, 0 closed
Wed Jun 13 11:11:36 2012
LMS 1: 0 GCS shadows cancelled, 0 closed
Set master node info
Submitted all remote-enqueue requests
Dwn-cvts replayed, VALBLKs dubious
All grantable enqueues granted
Post SMON to start 1st pass IR
Wed Jun 13 11:11:36 2012
LMS 1: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:11:36 2012
LMS 0: 0 GCS shadows traversed, 0 replayed
Wed Jun 13 11:11:36 2012
Submitted all GCS remote-cache requests
Fix write in gcs resources
Reconfiguration complete
LCK0 started with pid=20, OS id=16235
Wed Jun 13 11:11:37 2012
ALTER DATABASE MOUNT
Wed Jun 13 11:11:37 2012
This instance was first to mount
Wed Jun 13 11:11:37 2012
Starting background process ASMB
ASMB started with pid=22, OS id=16343
Starting background process RBAL
RBAL started with pid=23, OS id=16347
Wed Jun 13 11:11:44 2012
SUCCESS: diskgroup DATA was mounted
Wed Jun 13 11:11:49 2012
Setting recovery target incarnation to 1
Wed Jun 13 11:11:49 2012
Successful mount of redo thread 2, with mount id 3005745065
Wed Jun 13 11:11:49 2012
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)
Completed: ALTER DATABASE MOUNT
Wed Jun 13 11:22:25 2012
alter database open
This instance was first to open
Wed Jun 13 11:22:26 2012
Beginning crash recovery of 1 threads
parallel recovery started with 2 processes
Wed Jun 13 11:22:26 2012
Started redo scan
Wed Jun 13 11:22:26 2012
Completed redo scan
61 redo blocks read, 4 data blocks need recovery
Wed Jun 13 11:22:26 2012
Started redo application at
Thread 1: logseq 7927, block 3
Wed Jun 13 11:22:26 2012
Recovery of Online Redo Log: Thread 1 Group 1 Seq 7927 Reading mem 0
Mem# 0: +DATA/osista/onlinelog/group_1.283.742132543
Wed Jun 13 11:22:26 2012
Completed redo application
Wed Jun 13 11:22:26 2012
Completed crash recovery at
Thread 1: logseq 7927, block 64, scn 506178382
4 data blocks read, 4 data blocks written, 61 redo blocks read
Switch log for thread 1 to sequence 7928
Picked broadcast on commit scheme to generate SCNs
Wed Jun 13 11:22:27 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=31, OS id=13010
Wed Jun 13 11:22:27 2012
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=32, OS id=13033
Wed Jun 13 11:22:27 2012
Thread 2 opened at log sequence 7178
Current log# 4 seq# 7178 mem# 0: +DATA/osista/onlinelog/group_4.289.742134597
Successful open of redo thread 2
Wed Jun 13 11:22:27 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Jun 13 11:22:27 2012
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Wed Jun 13 11:22:27 2012
ARC1: Becoming the heartbeat ARCH
Wed Jun 13 11:22:27 2012
SMON: enabling cache recovery
Wed Jun 13 11:22:30 2012
db_recovery_file_dest_size of 65368 MB is 0.61% 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.
SUCCESS: diskgroup FLASH was mounted
SUCCESS: diskgroup FLASH was dismounted
Wed Jun 13 11:22:31 2012
Successfully onlined Undo Tablespace 20.
Wed Jun 13 11:22:31 2012
SMON: enabling tx recovery
Wed Jun 13 11:22:32 2012
Database Characterset is AL32UTF8
Wed Jun 13 11:22:32 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_11751.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Wed Jun 13 11:22:33 2012
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_11751.trc:
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
USER: terminating instance due to error 600
Instance terminated by USER, pid = 11751
ORA-1092 signalled during: alter database open...
regards,

Hi;
Errors in file /oracle/product/admin/OSISTA/udump/osista2_ora_9174.trc:Did you check trc file?
ORA-00600: code d'erreur interne, arguments : [kokiasg1], [], [], [], [], [], [], []You are getting oracle internal error(ORA 600) which mean you could need to work wiht oracle support team. Please see below note, if its not help than i suggest log a sr:
Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool [ID 153788.1]
for your future rac issue please use Forum Home » High Availability » RAC, ASM & Clusterware Installation which is RAC dedicated forum site.
Regard
Helios

Database can not mount in exchange server 2013 due to Unable to mount database. (hr=0x80004005, ec=-543)

Hello All,
Database can not mount. In this Database domain Administrator mailbox have.
Please suggest. It's very important
The error:
[PS] C:\Windows\system32>Mount-Database -Identity MBX-01 -Force
Confirm
At least one committed transaction log file is missing. Mounting this database will result in data loss. If you can
locate the missing log files, don't continue. Are you sure you want to continue?
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): a
Failed to mount database "MBX-01". Error: An Active Manager operation failed. Error: The database action failed.
Error: Operation failed with message: MapiExceptionJetErrorRequiredLogFilesMissing: Unable to mount database.
(hr=0x80004005, ec=-543)
Diagnostic context:
    Lid: 65256
    Lid: 10722   StoreEc: 0xFFFFFDE1
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 45120   dwParam: 0x51FF5F0
    Lid: 57728   dwParam: 0x51FF68C
    Lid: 46144   dwParam: 0x51FF709
    Lid: 34880   dwParam: 0x51FF709
    Lid: 34760   StoreEc: 0xFFFFFDE1
    Lid: 41344   Guid: 1c2c8cab-ae3f-40c8-8024-ffc776b22360
    Lid: 35200   dwParam: 0x2EFC
    Lid: 46144   dwParam: 0x51FFA55
    Lid: 34880   dwParam: 0x51FFA55
    Lid: 56264   StoreEc: 0x1388
    Lid: 46280   StoreEc: 0xFFFFFDE1
    Lid: 1750    ---- Remote Context End ----
    Lid: 1047    StoreEc: 0xFFFFFDE1 [Database: MBX-01, Server: EG-EXCHG-01.ABC.com]
    + CategoryInfo          : InvalidOperation: (MBX-01:ADObjectId) [Mount-Database], InvalidOperationException
    + FullyQualifiedErrorId : [Server=EG-EXCHG-01,RequestId=ca57e784-43c7-4357-9ab6-08881c87bb77,TimeStamp=9/18/2014 5
   :31:08 AM] [FailureCategory=Cmdlet-InvalidOperationException] 51350054,Microsoft.Exchange.Management.SystemConfigu
rationTasks.MountDatabase
    + PSComputerName        : eg-exchg-01.ABC.com

Hi,
This issue indicate corrupted database or corrupted logs. I suggest you to check and repair the database or check and repair the database log.
1. Check the state of database by following command: eseutil /mh "Path of the database"
Ps: Default path of the database is “C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database\Mailbox Database.edb”
Default path of the log files is “C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database\E00”
2. If the state is in clean shutdown, move all the log files from the Transaction logs folder location and then mount the database.
3. If the state is in dirty shutdown, check if the log files that is indicated as Logs required is available or not.
4. You can run Eseutil ml “Path of the log file\e00” to make sure that the log files is required is in a Clean state. This command will help you check the health of all the log files in the location.
5. If the log files are healthy, then try Soft recovery with the command Eseutil /r e00 /l ”Path of log files” /p “Path of the database”
Note:
Make sure you make a backup of the database before attempting any kind of repairs
6. Once the command completes successfully, then mount the database.
7. In case the required log files are not available in a clean state or missing, either restore from a successful back up or perform Hard repair with defragment.
Refer to this file about hard repair:
http://gallery.technet.microsoft.com/Step-by-Step-Exchange-2013-f8bed401
Hope this will be helpful for you

Can we put RAC database in Archivelog mode without shutting down

All,
Can we put RAC database in Archivelog mode without shutting down.
Currently our new production database (2 node RAC) is in no archive log mode, Need to enable archive log in the database...
I believe we need to set the cluster_database=false and then put the DB in archive log mode then we need to bounce the database to take effect...
Just curious to know in 11gR2 ...Can we put the RAC database in archive log mode without any downtime ...?

Even RAC or non-RAC, database should bounced and enable/disable archive log mode from mount status.

Can we run 11g RAC and 12c RAC in the same server?

There is a requirement to run 11g RAC and 12C RAC in the same server for a year or so and then remove 11g RAC?
Current setup:
HP-unix 3 node RAC on 11g R2
4CPU
64 GB RAM
3 TB SAN storage
no ASM
Upgrade setup:
HP-unix 3 node RAC on 12C RAC
8CPU
128 GB RAM
6+ TB SAN storage
ASM
We are asked to use the same server and upgrade Hardware to install and run 12C RAC. What are the implications of running RAC in the same server/nodes?
Thank you for your time!

Hi,
The following table shows you the compatibility between various versions:
Clusterware
ASM
DB
Certified
12.1
12.1
12.1
Y
12.1
12.1
11.2(a)
Y
12.1
12.1
11.1(a)
Y
12.1
12.1
10.2(a)
Y
11.2
11.2(b)
11.2
Y
11.2
11.2(b)
11.1
Y
11.2
11.2(b)
10.2
Y
11.1
11.1
11.1(c)
Y
11.1
11.1
10.2
Y
11.1
11.1
10.1
Y
11.1
10.2
11.1
Y
11.1
10.2
10.2
Y
11.1
10.2
10.1
Y
11.1
10.1(d)
11.1
Y
11.1
10.1(d)
10.2
Y
11.1
10.1
10.1
Y
10.2
10.2
10.2
Y
10.2
10.2
10.1
Y
10.2
10.1(d)
10.2
Y
10.2
10.1
10.1
Y
10.1
10.1
10.1
Y
(a) Pre-12.1 database instances require an ASM instance resident on the same node as the database instance. Pre-12.1 database instances cannot leverage the implicit HA of Flex ASM.
Oracle Clusterware (CRS/GI) - ASM - Database Version Compatibility (Doc ID 337737.1)

Add RAC database as a target for EMC 12c

Hello,
I have installed Enterprise manager 12c on Host 1 Redhat linux 5.5
We have already installed a RAC database 2 nodes on Host 2 and Host 3 ; RAC version 11.2.0.3 on Redhat linux 5.5.
I am planning to add the RAC database to be monitored by Enterprise manager 12c.
I am going to deploy the agent using the following video: http://www.youtube.com/watch?v=dP-8Bw8CVu8
How to add the RAC database to be monitored by the Enterprise manager 12c after the agent deploy on hosts: Host 2 and Host3?
Thank you,
Diego

Pleae find the output;
[oracle@host01 emd]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 02-MAR-2012 02:22:01
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.2.0 - Production
Start Date                17-FEB-2012 04:46:16
Uptime                    13 days 21 hr. 35 min. 44 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /opt/11.2.0/grid/network/admin/listener.ora
Listener Log File         /opt/app/oracle/diag/tnslsnr/host01/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.32.65)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.32.66)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
Service "db.domain.com" has 1 instance(s).
Instance "db1", status READY, has 2 handler(s) for this service...
Service "dbXDB.domain.com" has 1 instance(s).
Instance "db1", status READY, has 1 handler(s) for this service...
Service "db_srvc.domain.com" has 1 instance(s).
Instance "db1", status READY, has 2 handler(s) for this service...
The command completed successfully
[oracle@host01 emd]$

Can a non-RAC database use SCAN ?

I have a 4 node 11gR2 cluster which has all different kinds of versions ( 10g ,11gR1 & 11gR2 ) on both RAC & NON RAC .
I know for sure that I can use SCAN for non 11gR2 databases for RAC databases .
For standalone db's It seems like it is working intermitently but is this supported ? the reason why I ask is there is no documentation on how to configure or troubleshoot for non-RAC using SCAN .
Appreciate your help
Ravi

I was trying to find some information about the issue, but i think SCAN is really designed for RAC databases.
You don't really need to use the SCAN for what you just described:
you can update the client tnanames with the vip addresses of all nodes with FAILOVER = ON
Example:
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=node1-vip)(PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=node2-vip)(PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=node3-vip)(PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=node4-vip)(PORT=1521))
(FAILOVER = ON)
(CONNECT_DATA=(SERVER = DEDICATED)(SERVICE_NAME=DB.WORLD))
However, you can try this (i never tried it, but i think it should work):
- See the document http://download.oracle.com/docs/cd/E11882_01/install.112/e10813/undrstnd.htm#BEICFAIC
+... If you do not set LOCAL_LISTENER, then the Database Agent automatically keeps the database associated with the Grid home's node listener updated...+
So don't set the LOCAL_LISTENER in your db.
- Update the client tnsnames with the SCAN if the version of the database is 11.2.0.1
- Try to see if it works fine
- Move your db to another node and try again

Can I put ALL my applications into one RAC database

Dear all,
Is it possible to share all of my workloads between a single RAC database or would it be better to run more than one RAC database on the the same cluster if they have very different characteristics (e.g. OLTP vs DSS or sensitive vs non-sensitive data). Oracle seem to imply that they have cut down their number of physical databases drastically but have they been able to do that because the workload is very homongenous, i.e all ERP stuff? Should it be possible to accommodate all workloads by having different instance parameters or does that defeat the object of being able to fail over a service from one instance to another?
Views/experiences please.

Hi, generally it is possible to put everything into one RAC database, especially if they share the same data. So you do not have to transport data from one database into the other.
Furthermore the resource allocation can perfectly be addressed with the resource manager of the database together with services. The workload has not to be homogenous.
However it might make sense to connect the DSS users to different nodes in the cluster than the OLTP users (via. services).
On the other hand there might be non technical issues which would make seperate databases more attractive. Like Patching could mean downtime of all applications. Like certifications of software, which would not allow you to upgrade your database, like ERP needs 10.2.0.2 while DSS would be better off with 11g) and so on.
There is really no right or wrong.
Still to get the most of the benefits out of a cluster the fewer databases you have.

Can not open database after restore...

Hi,
I am doing a system copy from a online backup of our production system to our qas system. It is AIX and Oracle 10.2.0.2.0 on both systems.
I have done the restore using the backup log file from the production system. I have run the control.sql script, applied 4 archive log files using "recover database using backup controlfile until cancel;". Last I run "alter database open resetlogs;", but here my problems start....
Here is what happends...
I apply the archive logs:
ORA-00279: change 65129304 generated at 01/22/2008 19:50:35 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8210_632565567.dbf
ORA-00280: change 65129304 for thread 1 is in sequence #8210
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8209_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
From the alert log:
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE start
Database is not in archivelog mode
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE complete
2008-02-23 01:00:23.810
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Have somebody had this problem? Hope you can help me :-).
Best regards Henrik

I entered cancel when the log files had been restored and then I did "alter database open resetlogs;"
Here is what I did:
orasrq> sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.2.0 - Production on Fri Feb 22 13:01:38 2008
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 4714397696 bytes
Fixed Size                  2077560 bytes
Variable Size            2365590664 bytes
Database Buffers         2332033024 bytes
Redo Buffers               14696448 bytes
SQL> @controlSRQ.sql
Control file created.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/SRQ/sapdata1/system_1/system.data1'
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 65088663 generated at 01/22/2008 18:30:19 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8203_632565567.dbf
ORA-00280: change 65088663 for thread 1 is in sequence #8203
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65091816 generated at 01/22/2008 18:35:25 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8204_632565567.dbf
ORA-00280: change 65091816 for thread 1 is in sequence #8204
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8203_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65094835 generated at 01/22/2008 18:39:16 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8205_632565567.dbf
ORA-00280: change 65094835 for thread 1 is in sequence #8205
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8204_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65101797 generated at 01/22/2008 18:56:03 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8206_632565567.dbf
ORA-00280: change 65101797 for thread 1 is in sequence #8206
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8205_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65108888 generated at 01/22/2008 19:05:31 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8207_632565567.dbf
ORA-00280: change 65108888 for thread 1 is in sequence #8207
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8206_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 65108888 generated at 01/22/2008 19:05:31 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8207_632565567.dbf
ORA-00280: change 65108888 for thread 1 is in sequence #8207
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65115833 generated at 01/22/2008 19:20:32 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8208_632565567.dbf
ORA-00280: change 65115833 for thread 1 is in sequence #8208
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8207_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 65115833 generated at 01/22/2008 19:20:32 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8208_632565567.dbf
ORA-00280: change 65115833 for thread 1 is in sequence #8208
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65122618 generated at 01/22/2008 19:35:37 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8209_632565567.dbf
ORA-00280: change 65122618 for thread 1 is in sequence #8209
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8208_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65129304 generated at 01/22/2008 19:50:35 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8210_632565567.dbf
ORA-00280: change 65129304 for thread 1 is in sequence #8210
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8209_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cn
ORA-00308: cannot open archived log 'cn'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection force

Can not open database - 10g

Dear experts,
I have a problem to open my database. ORA-01033: ORACLE initialization or shutdown in progress. I have restarted server many times. I tried several ways but no joy. Please see the steps I did to solve this -
SQL> connect dmadmin /mypwdx89 as sysdba
Connected.
SQL> STARTUP MOUNT
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> ALTER DATABASE OPEN;
ALTER DATABASE OPEN
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: 'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSTEM01.DBF'
SQL> RECOVER DATABASE;
ORA-00279: change 149935494 generated at 06/10/2009 17:05:33 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\ARCHIVELOG\2009_06_23\O1_MF_1_
673_%U_.ARC
ORA-00280: change 149935494 for thread 1 is in sequence #673
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\ARCHIVELOG\2009_06_10\O1_MF_1
_673_530WXF9P_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
SQL> select * from v$controlfile;
STATUS
NAME
IS_
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL01.CTL
NO
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL02.CTL
NO
STATUS
NAME
IS_
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL03.CTL
NO
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145750508 bytes
Database Buffers 25165824 bytes
Redo Buffers 262144 bytes
SQL> select name from v$controlfile;
no rows selected
SQL>
SQL> alter database mount;
Database altered.
SQL> select name from v$controlfile;
NAME
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL01.CTL
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL02.CTL
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL03.CTL
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: 'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSTEM01.DBF'
SQL>
The I tried to recover datafile
SQL> Recover datafile '<datafile-name>';
again error - even can not open data file ...i restarted server .. no use..same error.
Please help to resolve this issue.
Regards,
Ranjith John

Hi All,
Please see the alert log file ..file size is already few GBs now. There are errors in the file.
It says - ORA-19815: WARNING: db_recovery_file_dest_size of 10048576000 bytes is 100.00% used, and has 0 remaining bytes available.
so, i guess the back up was not done .please help to resovle this issue.
ARC1: Error 19809 Creating archive log file to 'C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\ARCHIVELOG\2009_04_14\O1_MF_1_37_U_.ARC'
ARC1: All standby destinations failed; successful archival assumed
ARC1: Failed to archive log 1 thread 1 sequence 37 (19809)
Tue Apr 14 11:46:51 2009
Errors in file c:\oracle\product\10.1.0\admin\zuma\bdump\zuma_arc1_1352.trc:
ORA-16038: log 1 sequence# 37 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: 'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\REDO01.LOG'
Tue Apr 14 11:46:51 2009
ARC0: Evaluating archive log 1 thread 1 sequence 37
Tue Apr 14 11:46:51 2009
Errors in file c:\oracle\product\10.1.0\admin\zuma\bdump\zuma_arc0_3828.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 10048576000 bytes is 100.00% used, and has 0 remaining bytes available.
You have the following choices to free up space from
flash recovery area:
1. Consider changing your RMAN retention policy.
If you are using dataguard, then consider changing your
RMAN archivelog deletion policy.
2. Backup files to tertiary device such as tape using the
RMAN command BACKUP RECOVERY AREA.
3. Add disk space and increase the db_recovery_file_dest_size
parameter to reflect the new space.
4. Delete unncessary files using the RMAN DELETE command.
If an OS command was used to delete files, then use
RMAN CROSSCHECK and DELETE EXPIRED commands.
Tue Apr 14 11:46:51 2009
Errors in file c:\oracle\product\10.1.0\admin\zuma\bdump\zuma_arc0_3828.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 10017792 bytes disk space from 10048576000 limit
ARC0: Error 19809 Creating archive log file to 'C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\ARCHIVELOG\2009_04_14\O1_MF_1_37_U_.ARC'
ARC0: All standby destinations failed; successful archival assumed
ARC0: Failed to archive log 1 thread 1 sequence 37 (19809)
Regards,
Ranjith John

How to install Oracle 11.2.0.4.0 Rac Database on Grid Infrastructure 12.1.0.2.0 (Windows 2012 R2)

Hi all.
This is the scenario:
I have a 2 node cluster Microsoft Windows 2012 R2 x86_64, the nodes are part of domain.
Installed Oracle 12cR1 (12.1.0.2.0) as follows:
Installation done using domain administrator named "installoracle" that has been EXPLICIT promoted to local administrator in both nodes.
One domain user named "oracle12c" with no administrator privileges neither in the domain or nodes.
Installation, after a lot of customization in the OS of the nodes, has gone ok, perfect indeed, not even a warning during runinstaller execution.
All services and resources are up & running, I have rebooted nodes and all comes back ok in place. In windows services I can see some services started with "oracle12c" user, and all windows groups: DBA, SYSKM, etc, has been created.
Now I have to install Oracle RAC database in 11gR2 version (11.2.0.4.0) to accomplish with application requirements.
So, I execute runInstaller (setup.exe) logged as administrator via domain administrator "installoracle" (the one that was able to do the smooth 12c GI installation) and the gui comes with out problems, but at 4th screen the one in which you have to choose what kind of installation you want to do (Single, RAC or RoN) I select RAC option, the gui returns error: crs is not running in the local node...
Finally, in order to deliver some database 11.2.0.4.0 for my customer, I try to do installation of SW for Single Node, I did using "installoracle". The sw has been installed in one of the nodes. Then I have created a database and I have stored datafiles in ASM (this ASM is part of 12c clusterware) and also register the 11gR2 single instance database in the Grid Infrastructure listener
So, whats next??? Why is this behavior??? I did similar installations in Linux/Solaris with no issue (well as everyone can imagine, always there are some issues, but when solved you got GI in 12c and databases in the release that you want 12c, 11g, 10g...)
Any clue?
Thanks in advance!!
Best Regards!!

To go back to old version (without changing compatible parameter), you can perform downgrade.
Instructions are available at
How to Downgrade from Database 11.2 to Previous Release (Includes 11.2.0.4 - 11.2.0.1) (Doc ID 883335.1)
In this case you will having all the data file including the new one.
But remember database may not be in the same status as before (Before upgrade). it may have invalid objects of higher version after downgrade.
Downgrade is applicable only to successfully upgraded databases. In case upgrade faced some issue, do not try downgrade there.
Your second approach it not correct. Note that each datafile header will have db version. We can not open database in normal mode when header version and binary versions are different.

Unable to startup 12c RAC database, can't open spfile in ASM

Similar Messages

Maybe you are looking for