cancel
Showing results for 
Search instead for 
Did you mean: 

VCS For Oracle,Can't startup automatic after failover to backup hosts

ligh
Level 0
Partner

Hi:

 

I have two server node SFHA 5.1 For Windows,and installed the oracle 10g database.

I have a question that when Server A failover to  Server B,the Server B can't startup oracle automatic(even failback to Server A),but I can enter "startup" in sqlplus command line,then the database is OK?

 

I want to know how should i do?

 

 

 

include "types.cf"

cluster Primary (
 UserNames = { admin = fMMgMKlTMoMU }
 Administrators = { admin }
 )

system SF1 (
 )

system SF2 (
 )

group Primary_Oracle (
 SystemList = { SF1 = 0, SF2 = 1 }
 AutoStartList = { SF1, SF2 }
 )

 IP Ora_IP (
  Address = "192.168.2.103"
  SubNetMask = "255.255.255.0"
  MACAddress @SF1 = 00-50-56-BE-35-92
  MACAddress @SF2 = 00-50-56-BE-18-42
  )

 MountV Ora_MountV (
  MountPath = "E:\\"
  VolumeName = Oradata
  VMDGResName = Ora_VMDg
  )

 NIC Ora_NIC (
  MACAddress @SF1 = 00-50-56-BE-35-92
  MACAddress @SF2 = 00-50-56-BE-18-42
  )

 Netlsnr Ora_Netlsnr (
  ServiceName = OracleOraDb10g_home1TNSListener
  )

 Oracle Ora_Oracle (
  ServiceName = OracleServiceDEMO
  Domain = SFDEMO
  SID = demo
  UserName = administrator
  EncryptedPasswd = hvhTwtTvqVkvLtwVj
  )

 VMDg Ora_VMDg (
  DiskGroupName = Oracle_DG
  )

 Ora_IP requires Ora_NIC
 Ora_MountV requires Ora_VMDg
 Ora_Netlsnr requires Ora_Oracle
 Ora_Oracle requires Ora_IP
 Ora_Oracle requires Ora_MountV


 // resource dependency tree
 //
 // group Primary_Oracle
 // {
 // Netlsnr Ora_Netlsnr
 //     {
 //     Oracle Ora_Oracle
 //         {
 //         IP Ora_IP
 //             {
 //             NIC Ora_NIC
 //             }
 //         MountV Ora_MountV
 //             {
 //             VMDg Ora_VMDg
 //             }
 //         }
 //     }
 // }


 

1 ACCEPTED SOLUTION

Accepted Solutions

Wally_Heim
Level 6
Employee

Hi Ligh,

Assuming that the probem is with starting the Oracle resource on server B, then you should test failover to server B and then check the Oracle_A.txt log to see what problems it encountered when trying to online oracle on server B.

The log is located in %vcs_home%\log\ folder.

You might need to increase logging of the Oracle resource to get more details.  If there is nothing in the logs with default levels then setting LogDBG for the Oracle resource to DBG_1, DBG_2, DBG_20 and DBG_21.  Then repeat the failover test and check the logs again.

Another good place to look is in the Application and System event logs to see if Oracle is reporting why it is not startnig there.

Thanks,

Wally

View solution in original post

2 REPLIES 2

Wally_Heim
Level 6
Employee

Hi Ligh,

Assuming that the probem is with starting the Oracle resource on server B, then you should test failover to server B and then check the Oracle_A.txt log to see what problems it encountered when trying to online oracle on server B.

The log is located in %vcs_home%\log\ folder.

You might need to increase logging of the Oracle resource to get more details.  If there is nothing in the logs with default levels then setting LogDBG for the Oracle resource to DBG_1, DBG_2, DBG_20 and DBG_21.  Then repeat the failover test and check the logs again.

Another good place to look is in the Application and System event logs to see if Oracle is reporting why it is not startnig there.

Thanks,

Wally

joseph_dangelo
Level 6
Employee Accredited

Ligh,

You may want to test the following:

Offline the Oracle service group on system A.   Bring each of the IP and Storage Resources online individually on System B.  At this point, please try and manually start Oracle using the Oracle Instance Management GUI or the Service Control Manager.  If you can not start Oracle in this fashion then I suspect you have something misconfigured within the instance itself on System B.  If you are able to bring the Oracle instance online, then I would check to make sure have the SID and username/password configured identically on both systems.

Good Luck.

Joe D