Home » Server Options » RAC & Failsafe » OFS add standalone database to group error
OFS add standalone database to group error [message #208894] Tue, 12 December 2006 08:06 Go to next message
ezlee
Messages: 1
Registered: December 2006
Junior Member
I was installing OFS 3.3.3 with Oracle 10g R2 on 2 win2k3sp1 servers. The standalone database instance could be startup at each node respectively without any issue.
The standalone database verification ran successfully. (I failover the data files to the second node, and verify that I can start and connect the same database instance, maybe I missed any configuration in registry or somewhere on node2?)



But when I tried to add the resource to the cluster group, I got following error:

Versions: client = 3.3.3 server = 3.3.3 OS =

Operation: Adding resource "OLTP.WORLD" to group "OLTP"
Starting Time: Dec 10, 2006 22:02:09
Elapsed Time: 0 minutes, 25 seconds

1 22:02:09 Starting clusterwide operation
2 22:02:10 FS-10370: Adding the resource OLTP.WORLD to group OLTP
3 22:02:10 FS-10371: ORAFS01 : Performing initialization processing
4 22:02:11 FS-10371: ORAFS02 : Performing initialization processing
5 22:02:14 FS-10372: ORAFS01 : Gathering resource owner information
6 22:02:14 FS-10372: ORAFS02 : Gathering resource owner information
7 22:02:14 FS-10373: ORAFS01 : Determining owner node of resource OLTP.WORLD
8 22:02:14 FS-10374: ORAFS01 : Gathering cluster information needed to perform the specified operation
9 22:02:14 FS-10374: ORAFS02 : Gathering cluster information needed to perform the specified operation
10 22:02:14 FS-10375: ORAFS01 : Analyzing cluster information needed to perform the specified operation
11 22:02:15 >>> FS-10652: ORAFS01 has Oracle Database version 10.2.0 installed in ORADB10G_HOME1
12 22:02:15 >>> FS-10652: ORAFS02 has Oracle Database version 10.2.0 installed in ORADB10G_HOME1
13 22:02:15 FS-10376: ORAFS01 : Starting configuration of resource OLTP.WORLD
14 22:02:15 FS-10378: ORAFS01 : Preparing for configuration of resource OLTP.WORLD
15 22:02:15 FS-10380: ORAFS01 : Configuring virtual server information for resource OLTP.WORLD
16 22:02:15 > FS-10496: Generating the Oracle Net migration plan for OLTP.WORLD
17 22:02:16 > FS-10490: Configuring the Oracle Net listener for OLTP.WORLD
18 22:02:16 >> FS-10600: Oracle Net configuration file updated: D:\ORACLE\PRODUCT\10.2.0\DB_1\NETWORK\ADMIN\LISTENER.ORA
19 22:02:16 >> FS-10606: Listener configuration updated in database parameter file: m:\spfileoltp.ora
20 22:02:20 >> FS-10605: Oracle Net listener Fsloltpd created
21 22:02:21 >> FS-10602: Oracle Net listener LISTENER restarted
22 22:02:21 > FS-10491: Configuring the Oracle Net service name for OLTP.WORLD
23 22:02:21 >> FS-10600: Oracle Net configuration file updated: D:\ORACLE\PRODUCT\10.2.0\DB_1\NETWORK\ADMIN\TNSNAMES.ORA
24 22:02:21 FS-10381: ORAFS01 : Creating the resource information for resource OLTP.WORLD
25 22:02:21 > FS-10424: Checking whether the database OLTP.WORLD is online
26 22:02:31 ** ERROR : ORA-01506: missing or illegal database name
27 22:02:31 ** ERROR : FS-10778: The Oracle Database resource provider failed to configure the cluster resource OLTP.WORLD
28 22:02:31 ** ERROR : FS-10890: Oracle Services for MSCS failed during the add operation
29 22:02:31 ** ERROR : FS-10497: Starting clusterwide rollback of the operation30 22:02:31 FS-10488: ORAFS01 : Starting rollback of operation
31 22:02:31 > FS-10090: Rolling back Oracle Net changes on node ORAFS01
32 22:02:34 FS-10489: ORAFS01 : Completed rollback of operation
33 22:02:34 ** ERROR : FS-10495: Clusterwide rollback of the operation has been completed
34 22:02:34 Please check your Windows Application log using the Event Viewer for any additional errors
35 22:02:34 The clusterwide operation failed !

The DB_NAME is already stated in the spfile, but why still got "ORA-01506: missing or illegal database name" error?

How and where can I find out any other detailed information about the error?

thanks, ezlee
Re: OFS add standalone database to group error [message #235328 is a reply to message #208894] Sat, 05 May 2007 01:22 Go to previous messageGo to next message
j_littlebishop
Messages: 1
Registered: May 2007
Junior Member
DEAR EZLEE HI,
I HAVE AN EXACT PROBLEM WITH A FAILSAFE CONFIGURATION.WHEN I TRY TO ADD THE DATABASE RESOURCE TO THE GROUP I RECIEVE AN ORA-01506 ERROR MESSAGE.DID YOU EVER FIND OUT WHAT WAS WRONG?
THANK YOU IN ADVANCE,
JOHN.
Re: OFS add standalone database to group error [message #252946 is a reply to message #235328] Fri, 20 July 2007 18:59 Go to previous messageGo to next message
clreddy
Messages: 2
Registered: July 2007
Location: California
Junior Member
Did you ever get solution for this problem. I am also having same problem. db_name is set to correct value in SPFILE and PFILE. I am not sure what is the problem. What did you guys do to fix this problem.
Re: OFS add standalone database to group error [message #252983 is a reply to message #252946] Sat, 21 July 2007 02:47 Go to previous messageGo to next message
clreddy
Messages: 2
Registered: July 2007
Location: California
Junior Member
Alright I did fix my problem. There were couple of issues.
I was using spfile for the parameter file for 10g database. You really need to use init.ora file instead. It is also expecting the user to be part of ORA_<SID>_DBA local group. I made the above changes and it worked fine.

Re: OFS add standalone database to group error [message #253330 is a reply to message #252983] Mon, 23 July 2007 09:39 Go to previous message
DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland
Senior Member
Quote:
I was using spfile for the parameter file for 10g database


Why you dont use SPFILE in 10g Rac Enviroment?

You can but it shoud be at SHARED LOCATION.

Quote:
You really need to use init.ora file instead


When you will use PFILE with Rac you should have 2PFILE for 2Nodes,but if you are using SPFILE you should have one SPFILE at shared location.
Previous Topic: 10g RAC i node cluster ON WINDOWS
Next Topic: Move 9i non ASM data to 10.2.0.3 using ASM
Goto Forum:
  


Current Time: Thu Mar 28 13:47:10 CDT 2024