Fe_rpc_command: cmd_type(enum) on Sun cluster

Hi
No matter what I do I seem to run into this problem.
I designed three HA agents and one is really simple and all went ok until I tried to bring the resource group online:
scswitch -Z -g Ingres_rg
scstat -g show:
-- Resource Groups and Resources --
Group Name Resources
Resources: Ingres_rg nodec Ingres_rs
-- Resource Groups --
Group Name Node Name State Suspended
Group: Ingres_rg node2 Online faulted No
Group: Ingres_rg node1 Offline No
-- Resources --
Resource Name Node Name State Status Message
Resource: nodec node2 Online Online - LogicalHostname online.
Resource: nodec node1 Offline Offline
Resource: Ingres_rs node2 Online Faulted - Unable to Failover to other node.
Resource: Ingres_rs node1 Offline Offline
And then in /var/adm/messages:
Mar 25 17:54:58 node2 Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource Ingres_rs status msg on node node2 change to <Starting>
Mar 25 17:54:58 node2 Cluster.RGM.rgmd: [ID 224900 daemon.notice] launching method <IngresHB_svc_start.ksh> for resource <Ingres_rs>, resource group <Ingres_rg>, node <node2>, timeout <300> seconds
Mar 25 17:54:58 node2 Cluster.RGM.rgmd: [ID 268902 daemon.notice] 45 fe_rpc_command: cmd_type(enum):<1>:cmd=</opt/pirar01IngresHB/bin/IngresHB_svc_start.ksh>:tag=<Ingres_rg.Ingres_rs.0>: Calling security_clnt_connect(..., host=<node2>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Mar 25 17:54:59 node2 Cluster.PMF.pmfd: [ID 887656 daemon.notice] Process: tag="Ingres_rg,Ingres_rs,0.svc", cmd="/global/disk2s0/ing_nc_1/ingres/utility/ingstart", Failed to stay up.
Mar 25 17:54:59 node2 Cluster.RGM.rgmd: [ID 494478 daemon.notice] resource Ingres_rs in resource group Ingres_rg has requested restart of the resource on node2.
Mar 25 17:54:59 node2 Cluster.RGM.rgmd: [ID 515159 daemon.notice] method <IngresHB_svc_start.ksh> completed successfully for resource <Ingres_rs>, resource group <Ingres_rg>, node <node2>, time used: 0% of timeout <300 seconds>
Mar 25 17:54:59 node2 Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource Ingres_rs state on node node2 change to R_JUST_STARTED
Mar 25 17:54:59 node2 Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource Ingres_rs state on node node2 change to R_ONLINE_UNMON
Mar 25 17:54:59 node2 Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource Ingres_rs state on node node2 change to R_STOPPING
Mar 25 17:54:59 node2 Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource Ingres_rs status msg on node node2 change to <Stopping>
Mar 25 17:54:59 node2 Cluster.RGM.rgmd: [ID 224900 daemon.notice] launching method <IngresHB_svc_stop.ksh> for resource <Ingres_rs>, resource group <Ingres_rg>, node <node2>, timeout <300> seconds
Mar 25 17:54:59 node2 Cluster.RGM.rgmd: [ID 268902 daemon.notice] 45 fe_rpc_command: cmd_type(enum):<1>:cmd=</opt/pirar01IngresHB/bin/IngresHB_svc_stop.ksh>:tag=<Ingres_rg.Ingres_rs.1>: Calling security_clnt_connect(..., host=<node2>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Mar 25 17:55:00 node2 pirar01.IngresHB:1.0,Ingres_rg,Ingres_rs: [ID 970707 daemon.error] Failed to stop IngresHB using the custom stop command; trying SIGKILL now.
Mar 25 17:55:00 node2 Cluster.RGM.rgmd: [ID 515159 daemon.notice] method <IngresHB_svc_stop.ksh> completed successfully for resource <Ingres_rs>, resource group <Ingres_rg>, node <node2>, time used: 0% of timeout <300 seconds>
Mar 25 17:55:00 node2 Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource Ingres_rs state on node node2 change to R_OFFLINE
Mar 25 17:55:00 node2 Cluster.RGM.rgmd: [ID 784560 daemon.notice] resource Ingres_rs status on node node2 change to R_FM_OFFLINE
Mar 25 17:55:00 node2 Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource Ingres_rs status msg on node node2 change to <>
Mar 25 17:55:00 node2 Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource Ingres_rs state on node node2 change to R_STARTING
Mar 25 17:55:00 node2 Cluster.RGM.rgmd: [ID 784560 daemon.notice] resource Ingres_rs status on node node2 change to R_FM_UNKNOWN
Mar 25 17:55:00 node2 Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource Ingres_rs status msg on node node2 change to <Starting>
Mar 25 17:55:00 node2 Cluster.RGM.rgmd: [ID 224900 daemon.notice] launching method <IngresHB_svc_start.ksh> for resource <Ingres_rs>, resource group <Ingres_rg>, node <node2>, timeout <300> seconds
Mar 25 17:55:00 node2 Cluster.RGM.rgmd: [ID 268902 daemon.notice] 45 fe_rpc_command: cmd_type(enum):<1>:cmd=</opt/pirar01IngresHB/bin/IngresHB_svc_start.ksh>:tag=<Ingres_rg.Ingres_rs.0>: Calling security_clnt_connect(..., host=<node2>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Mar 25 17:55:00 node2 Cluster.PMF.pmfd: [ID 887656 daemon.notice] Process: tag="Ingres_rg,Ingres_rs,0.svc", cmd="/global/disk2s0/ing_nc_1/ingres/utility/ingstart", Failed to stay up.
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 515159 daemon.notice] method <IngresHB_svc_start.ksh> completed successfully for resource <Ingres_rs>, resource group <Ingres_rg>, node <node2>, time used: 0% of timeout <300 seconds>
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource Ingres_rs state on node node2 change to R_JUST_STARTED
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource Ingres_rs state on node node2 change to R_ONLINE_UNMON
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 784560 daemon.notice] resource Ingres_rs status on node node2 change to R_FM_ONLINE
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource Ingres_rs status msg on node node2 change to <>
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource Ingres_rs state on node node2 change to R_MON_STARTING
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 224900 daemon.notice] launching method <IngresHB_mon_start.ksh> for resource <Ingres_rs>, resource group <Ingres_rg>, node <node2>, timeout <300> seconds
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 268902 daemon.notice] 45 fe_rpc_command: cmd_type(enum):<1>:cmd=</opt/pirar01IngresHB/bin/IngresHB_mon_start.ksh>:tag=<Ingres_rg.Ingres_rs.7>: Calling security_clnt_connect(..., host=<node2>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 494478 daemon.notice] resource Ingres_rs in resource group Ingres_rg has requested failover of the resource group on node2.
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 784560 daemon.notice] resource Ingres_rs status on node node2 change to R_FM_FAULTED
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource Ingres_rs status msg on node node2 change to <Unable to Failover to other node.>
Mar 25 17:55:01 node2 [pirar01.IngresHB:1.0,Ingres_rs,Ingres_rg]: [ID 115617 daemon.error] Error in failing over the resource group:Ingres_rg
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 515159 daemon.notice] method <IngresHB_mon_start.ksh> completed successfully for resource <Ingres_rs>, resource group <Ingres_rg>, node <node2>, time used: 0% of timeout <300 seconds>
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource Ingres_rs state on node node2 change to R_ONLINE
Mar 25 17:55:01 node2 Cluster.RGM.rgmd: [ID 529407 daemon.notice] resource group Ingres_rg state on node node2 change to RG_ONLINE
What am I missing here ?
Could it be related to :
Mar 25 17:55:00 node2 Cluster.RGM.rgmd: [ID 268902 daemon.notice] 45 fe_rpc_command: cmd_type(enum):<1>:cmd=</opt/pirar01IngresHB/bin/IngresHB_svc_start.ksh>:tag=<Ingres_rg.Ingres_rs.0>: Calling security_clnt_connect(..., host=<node2>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
Any workaround ?
Thanks in advance for help.
Armand

Hi Thorsten
Yes you are right, I used scdsbuilder in this case.
Thank you for the directions pointed out.
I am not sure I fully understand what you are saying, but to clarify a little bit things as to what I am trying to do here.
ingstart when it runs it simply starts the DBMS installation in a specific manner, that is name server (iigcn), recovery (dmfrcp), archiver (dmfacp) , dbms server (iidbms) , net server (iigcc) . After that ingstart simply goes away.
So I can see that from this standpoint, the enumerated processes can be considered children of ingstart. But from a pid correlation, ingstart is not considered a parent for any of those processes.
The same if true for ingstop.
On the other hand, in a pure failover scenario, all I want to do is to failover to node2 from node1, when node1 goes down, either hardware problem or OS problem. Which means that along with the host failover (logical hostname pointing to node2 from node1), all I need is to run an ingstop (there are reasons to do that) followed by an ingstart. As to probing, it is not required for me in this case at all. I can see the value of probing, but in an active/active cluster, i.e. scalable resources et all, not in a failover one.
So, maybe you could clarify a little bit if possible how I should make use of Child_mon_level in this case and any other resources I may need to consult.
Much appreciated the help.
Thanks
Armand

Similar Messages

Sun cluster 3.2 - resource hasstorageplus taking too much time to start

I have a disk resource called "data" that takes too much time to startup when performing a switchover. Any idea what may control this ?
Jan 28 20:28:01 hnmdb02 Cluster.Framework: [ID 801593 daemon.notice] stdout: becoming primary for data
Jan 28 20:28:02 hnmdb02 Cluster.RGM.rgmd: [ID 350207 daemon.notice] 24 fe_rpc_command: cmd_type(enum):<3>:cmd=<null>:tag=<hnmdb.data.10>: Calling security_clnt_connect(..., host=<hnmdb02>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<0>, ...)
Jan 28 20:28:02 hnmdb02 Cluster.RGM.rgmd: [ID 316625 daemon.notice] Timeout monitoring on method tag <hnmdb.data.10> has been resumed.
Jan 28 20:34:57 hnmdb02 Cluster.RGM.rgmd: [ID 515159 daemon.notice] method <hastorageplus_prenet_start> completed successfully for resource <data>, resource group <hnmdb>, node <hnmdb02>, time used: 23% of timeout <1800 seconds>

heldermo wrote:
I have a disk resource called "data" that takes too much time to startup when performing a switchover. Any idea what may control this ?I'm not sure how this is supposed to be related to Messaging Server. I suggest you ask your question in the Cluster forum:
http://forums.sun.com/forum.jspa?forumID=842
Regards,
Shane.

Does sun Cluster 3.0/3.1 HA Oracle agent support to use Oracle spfile?

When defining the resource, the 'parameter_file' properties is usually sets to the Oracle pfile. Is it possible to use Oracle spfile?
It is said if leaving 'parameter_file' NULL, it will be default to Oracle default. Suppose leaving it NULL and with Oracle spfile created in default location, will it use the spfile?

You did not specify which Sun Cluster version and Oracle version you are running.
Within SC 3.1 my understanding is that beginning with Oracle 9i it is possible to use the spfile.
If you leave the "parameter_file" property empty (NULL) then the default behaviour for 9i should work:
search under $ORACLE_HOME/dbs in the order:
1. spfile$(ORACLE_SID}.ora
2. spfile.ora
3. init${ORACLE_SID}.ora
Greets
Thorsten

Encountered ora-29701 during Sun Cluster for Oracle RAC 9.2.0.7 startup (UR

Hi all,
Need some help from all out there
In our Sun Cluster 3.1 Data Service for Oracle RAC 9.2.0.7 (Solaris 9) configuration, my team had encountered
ora-29701 *Unable to connect to Cluster Manager*
during the startup of the Oracle RAC database instances on the Oracle RAC Server resources.
We tried the attached workaround by Oracle. This workaround works well for the 1^st time but it doesnt work anymore when the server is rebooted.
Kindly help me to check whether anyone encounter the same problem as the above and able to resolve. Thanks.
Bug No. 4262155
Filed 25-MAR-2005 Updated 11-APR-2005
Product Oracle Server - Enterprise Edition Product Version 9.2.0.6.0
Platform Linux x86
Platform Version 2.4.21-9.0.1
Database Version 9.2.0.6.0
Affects Platforms Port-Specific
Severity Severe Loss of Service
Status Not a Bug. To Filer
Base Bug N/A
Fixed in Product Version No Data
Problem statement:
ORA-29701 DURING DATABASE CREATION AFTER APPLYING 9.2.0.6 PATCHSET
*** 03/25/05 07:32 am ***
TAR:
PROBLEM:
Customer applied 9.2.0.6 patchset over 9.2.0.4 patchset.
While creating the database, customer receives following error:
ORA-29701: unable to connect to Cluster Manager
However, if customer goes from 9.2.0.4 -> 9.2.0.5 -> 9.2.0.6, the problem does not occur.
DIAGNOSTIC ANALYSIS:
It seems that the problem is with libskgxn9.so shared library.
For 9.2.0.4 -> 9.2.0.5 -> 9.2.0.6, the install log shows the following:
installActions2005-03-22_03-44-42PM.log:,
[libskgxn9.so->%ORACLE_HOME%/lib/libskgxn9.so 7933 plats=1=>[46]langs=1=> en,fr,ar,bn,pt_BR,bg,fr_CA,ca,hr,cs,da,nl,ar_EG,en_GB,et,fi,de,el,iw,hu,is,in, it,ja,ko,es,lv,lt,ms,es_MX,no,pl,pt,ro,ru,zh_CN,sk,sl,es_ES,sv,th,zh_TW, tr,uk,vi]]
installActions2005-03-22_04-13-03PM.log:, [libcmdll.so ->%ORACLE_HOME%/lib/libskgxn9.so 64274 plats=1=>[46] langs=-554696704=>[en]]
For 9.2.0.4 -> 9.2.0.6, install log shows:
installActions2005-03-22_04-13-03PM.log:, [libcmdll.so ->%ORACLE_HOME%/lib/libskgxn9.so 64274 plats=1=>[46] langs=-554696704=>[en]] does not exist.
This means that while patching from 9.2.0.4 -> 9.2.0.5, Installer copies the libcmdll.so library into libskgxn9.so, while patching from 9.2.0.4 -> 9.2.0.6 does not.
ORACM is located in /app/oracle/ORACM which is different than ORACLE_HOME in customer's environment.
WORKAROUND:
Customer is using the following workaround:
cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk rac_on ioracle ipc_udp
RELATED BUGS:
Bug 4169291

Check if following MOS note helps.
Series of ORA-7445 Errors After Applying 9.2.0.7.0 Patchset to 9.2.0.6.0 Database (Doc ID 373375.1)

SAP 7.0 on SUN Cluster 3.2 (Solaris 10 / SPARC)

Dear All;
i'm installing a two nodes cluster (SUN Cluster 3.2 / Solaris 10 / SPARC), for a HA SAP 7.0 / Oracle 10g DataBase
SAP and Oracle softwares were successfully installed and i could successfully cluster the Oracle DB and it is tested and working fine.
for the SAP i did the following configurations
# clresource create -g sap-ci-res-grp -t SUNW.sap_ci_v2 -p SAPSID=PRD -p Ci_instance_id=01 -p Ci_services_string=SCS -p Ci_startup_script=startsap_01 -p Ci_shutdown_script=stopsap_01 -p resource_dependencies=sap-hastp-rs,ora-db-res sap-ci-scs-res
# clresource create -g sap-ci-res-grp -t SUNW.sap_ci_v2 -p SAPSID=PRD -p Ci_instance_id=00 -p Ci_services_string=ASCS -p Ci_startup_script=startsap_00 -p Ci_shutdown_script=stopsap_00 -p resource_dependencies=sap-hastp-rs,or-db-res sap-ci-Ascs-res
and when trying to bring the sap-ci-res-grp online # clresourcegroup online -M sap-ci-res-grp
it executes the startsap scripts successfully as following
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
stty: : No such device or address
stty: : No such device or address
Starting SAP-Collector Daemon
11:04:57 04.06.2008 LOG: Effective User Id is root
Starting SAP-Collector Daemon
11:04:57 04.06.2008 LOG: Effective User Id is root
* This is Saposcol Version COLL 20.94 700 - V3.72 64Bit
* Usage: saposcol -l: Start OS Collector
* saposcol -k: Stop OS Collector
* saposcol -d: OS Collector Dialog Mode
* saposcol -s: OS Collector Status
* Starting collector (create new process)
* This is Saposcol Version COLL 20.94 700 - V3.72 64Bit
* Usage: saposcol -l: Start OS Collector
* saposcol -k: Stop OS Collector
* saposcol -d: OS Collector Dialog Mode
* saposcol -s: OS Collector Status
* Starting collector (create new process)
saposcol on host eccprd01 started
Starting SAP Instance ASCS00
Startup-Log is written to /export/home/prdadm/startsap_ASCS00.log
saposcol on host eccprd01 started
Running /usr/sap/PRD/SYS/exe/run/startj2eedb
Trying to start PRD database ...
Log file: /export/home/prdadm/startdb.log
Instance Service on host eccprd01 started
Jun 4 11:05:01 eccprd01 SAPPRD_00[26054]: Unable to open trace file sapstartsrv.log. (Error 11 Resource temporarily unavailable) [ntservsserver.cpp 1863]
/usr/sap/PRD/SYS/exe/run/startj2eedb completed successfully
Starting SAP Instance SCS01
Startup-Log is written to /export/home/prdadm/startsap_SCS01.log
Instance Service on host eccprd01 started
Jun 4 11:05:02 eccprd01 SAPPRD_01[26111]: Unable to open trace file sapstartsrv.log. (Error 11 Resource temporarily unavailable) [ntservsserver.cpp 1863]
Instance on host eccprd01 started
Instance on host eccprd01 started
and the it repeats the following warnings on the /var/adm/messages till it fails to the other node
Jun 4 12:26:22 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:25 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:25 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:28 eccprd01 last message repeated 1 time
Jun 4 12:26:28 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:31 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:31 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:34 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:34 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:37 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:37 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:40 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:40 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:43 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:43 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:46 eccprd01 last message repeated 1 time
Jun 4 12:26:46 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:49 eccprd01 last message repeated 1 time
Jun 4 12:26:49 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:52 eccprd01 last message repeated 1 time
Jun 4 12:26:52 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:55 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:55 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:26:58 eccprd01 last message repeated 1 time
Jun 4 12:26:58 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:01 eccprd01 last message repeated 1 time
Jun 4 12:27:01 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:04 eccprd01 last message repeated 1 time
Jun 4 12:27:04 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:07 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:07 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:10 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:10 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:13 eccprd01 last message repeated 1 time
Jun 4 12:27:13 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:16 eccprd01 last message repeated 1 time
Jun 4 12:27:16 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:19 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:19 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:22 eccprd01 last message repeated 1 time
Jun 4 12:27:22 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:25 eccprd01 last message repeated 1 time
Jun 4 12:27:25 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:28 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:28 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:31 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:31 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:34 eccprd01 last message repeated 1 time
Jun 4 12:27:34 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:37 eccprd01 last message repeated 1 time
Jun 4 12:27:37 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:40 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:40 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:43 eccprd01 last message repeated 1 time
Jun 4 12:27:43 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-scs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dispatcher to come up.
Jun 4 12:27:46 eccprd01 last message repeated 1 time
Jun 4 12:27:46 eccprd01 SC[SUNW.sap_ci_v2,sap-ci-res-grp,sap-ci-Ascs-res,sap_ci_svc_start]: [ID 183934 daemon.notice] Waiting for SAP Central Instance main dis
can anyone one help me if there is any error on configurations or what is the cause of this problem.....thanks in advance
ARSSES

Hi all.
I am having a similar issue with a Sun Cluster 3.2 and SAP 7.0
Scenrio:
Central Instance (not incluster) : Started on one node
Dialog Instance (not in cluster): Started on the other node
When I create the resource for SUNW.sap_as like
clrs create --g sap-rg -t SUNW.sap_as .....etc etc
in the /var/adm/messages I got lots of WAITING FOR DISPACHER TO COME UP....
Then after timeout it gives up.
Any clue? What does is try to connect or waiting for? I hve notest that it's something before the startup script....
TIA

Creating Logical hostname in sun cluster

Can someone tell me, what exactly logical hostname in sun cluster mean?
For registering logical hostname resource in failoover group, what exactly i need to specify
for example, i have two nodes in sun cluster , How to create or configure a logical hostanme and it should point to which IP Address ( Whether it should point to IP addresses of nodes in sun cluster). Can i get clarification on this?

Thanks Thorsten for ur continue help...
The output of clrs status abc_lg
=== Cluster Resources ===
Resource Name Node Name State Status Message
abc_lg node1 Offline Offline
node2 Offline Offline
The status is offline...
the output of clresourcegroup status
=== Cluster Resource Groups ===
Group Name Node Name Suspended Status
abc_rg node1 No Unmanaged
node2 No Unmanaged
You say that the resource should de enabled after creating the resource.. I am using GDS and i am just following the steps he provided to acheive high availabilty (in developers guide...)
I have 1) Logical hostname resorce.
2) Application resource in my failover resource group
When i bring online the failover resource group , what should my failover resource group status and the status of resource in my resource group

File System Sharing using Sun Cluster 3.1

Hi,
I need help on how to setup and configure the system to share a remote file system that is created on a SAN disk (SAN LUN ) between two Sun Solaris 10 servers.
The files in the remote system should be read/writabe from both the solaris servers concurrently.
As a security policy NFS mount is not allowed. Some one suggested it can be done by using Sun Cluster 3.1 agents on both servers. Any details on how I can do this using Sun Cluster 3.1 is really appreciated.
thanks
Suresh

You could do this by installing Sun Cluster on both systems and then creating a global file system on the shared LUN. However, if there was significant write activity on both nodes, then the performance will not necessarily what you need.
What is wrong with the security of NFS? If it is set up properly I don't think this should be a problem.
The other option would be to use shared QFS, but without Sun Cluster.
Regards,
Tim
---

Connected to an idle instance in sun cluster nodes.

i have two sun cluster node sharing common storage.
Two schema's:
test1 for nodeA
test2 for nodeB.
My requirement is as below:
Login into b node.
export ORACLE_SID=test1.
sqlplus / as sysdba.
But i am getting as
"connected to an idle instance"
Is there any way to connect to node A schema from Node B.

I found the answer..
sqlplus <sysdbauser>/<password>@test1 as sysdba

RAC 10g on Sun Cluster 3.1 U3 and Interconnect

Hello,
I have the following Interconnects on my Sun Cluster:
ce5: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 6
     inet 1.1.1.1 netmask ffffff80 broadcast 1.1.1.127
     ether 0:3:ba:95:fa:23
ce5: flags=2008841<UP,RUNNING,MULTICAST,PRIVATE,IPv6> mtu 1500 index 6
     ether 0:3:ba:95:fa:23
     inet6 fe80::203:baff:fe95:fa23/10
ce0: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 index 7
     inet 1.1.0.129 netmask ffffff80 broadcast 1.1.0.255
     ether 0:3:ba:95:f9:97
ce0: flags=2008841<UP,RUNNING,MULTICAST,PRIVATE,IPv6> mtu 1500 index 7
     ether 0:3:ba:95:f9:97
     inet6 fe80::203:baff:fe95:f997/10
clprivnet0: flags=1009843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,PRIVATE,IPv4> mtu 1500 index 8
     inet 1.1.193.1 netmask ffffff00 broadcast 1.1.193.255
     ether 0:0:0:0:0:1
In the Installation of RAC the routine will ask me which Interface I will use for RAC Interconnect and I do not know if it does not matter which Interface I choose, because I nevertheless in any case I have an SPOF.
Can anybody help??
Thank you very much

Sorry for the late reply, but the interface to pick is the clprivnet0. This load-balances over the available private interconnects under the covers and so does not represent a single point of failure.
Tim
---

11g r2 non rac using asm for sun cluster os (two node but non-rac)

I am going to install grid installation for non-rac using asm for two node sun cluster environment..
How to create candidate disk in solaris cluster (sparc os) to install grid home in asm.. please provide me the steps if anyone knows

Please refer the thread Re: 11GR2 ASM in non-rac node not starting... failing with error ORA-29701
and this doc http://docs.oracle.com/cd/E11882_01/install.112/e24616/presolar.htm#CHDHAAHE

Sun Cluster with Netapps - iSCSI quorum and network port

I am proposing Sun cluster with Netapps 3020C.
May I know
1) OS is Solaris 9. The SUN OSP says that we need to obtain an iSCSI license from Netapps. Is this the iSCSI initiator software for Solaris 9 to talk to the NAS quorum? Or do I need to purchased a 3rd party iSCSI initiator ?
2) We provide 2 network ports for the Netapps private NAS LAN. Is it a must to cater another dedicated network port for the iSCSI communication with the quorum?
3) If we need purchase a 3rd party iSCSI initiator, where can we get this? I have checked Qlogic and Cisco, they are both not suitable for my solution.
Appreciate your help

Hi,
1) OS is Solaris 9. The SUN OSP says that we need to
obtain an iSCSI license from Netapps. Is this the
iSCSI initiator software for Solaris 9 to talk to the
NAS quorum? Or do I need to purchased a 3rd party
iSCSI initiator ?Have a look at http://docs.sun.com/app/docs/doc/817-7957/6mn8834r2?a=view
I read the "Requirements When Configuring NAS Devices as Quorum Devices"
section as this is the license for the iSCSI inititator software.
So you need to enable iSCSI on the netapps box and need to install a package from netapps (NTAPclnas) on the cluster nodes.
2) We provide 2 network ports for the Netapps
private NAS LAN. Is it a must to cater another
dedicated network port for the iSCSI communication
with the quorum?Have a look at http://docs.sun.com/app/docs/doc/819-0580/6n30eahcc?a=view#ch4_quorum-9
I don't read such a requirement there.
3) If we need purchase a 3rd party iSCSI initiator,
where can we get this? I have checked Qlogic and
Cisco, they are both not suitable for my solution.
Appreciate your helpI don't thibk you need such a 3rd party iSCSI initiator, unless this is stated in the above docs.
Greets
Thorsten

Content Server on Sun Cluster

Hello.
Does anybody know, is Contenr Server can work on Sun Cluster?
I did not find any information in notes or PAM. Technically, Sun Cluster support both Apache and MaxDB.

HI,
It is supported on sun cluster. You can use Apache 2.052 and MaxDB 7.6
Anirudh,

Rename Sun Cluster Resource Group

Hi All,
We have a 2 node Sun Cluster 3.0 running on 2 x V440 servers. We want to change the resource group.
Can I use "scrgadm -c -g RG_NAME -h nodelist -y property" command to change the resource group name. Can I do this online while the clusters are running or do I need to bring the cluster to mainenance mode? Any help would be appreciated.
Thanks.

You cannot rename a resource group in that way in Sun Cluster.
You have two options:
-Recreate the resource group with the new name
-Use an unsupported procedure to change the name in the CCR. This requires downtime of both nodes and as it is unsupported I am not going to describe it here. If that is what you want to do, please log a call with Sun.
If you think renaming resource groups is a useful feature may I also ask you to contact your Sun Service representative so that they can take proper action to log an RFE for the feature.

Sun Cluster.. Why?

What are the advantages of installing RAC 10.2.0.3 on a Sun Cluster.? Are there any benefits?

Oracle 10g onward, there is no such burning requirement for Sun Cluster (or any third party cluster) as far as you are using all Oracle technologies for your Oracle RAC database. You should Oracle RAC with ASM for shared storage and that would not require any third party cluster. Bear inmind that
You may need to install Sun Cluster in the following scenarios:
1) If there is applicaiton running with in the cluster along with Oracle RAC database that you want to configure for HA and Sun Cluster provide the cluster resourced (easy to use) to manage and monitor the application. THIS can be achieved with Oracle Clusterware but you will have to write your own cluster resource for that.
2) If you want to install cluster file system such as QFS then you will need to install the Sun Cluster. If this cluster is only running the Oracle RAC database then you can rely on Oracle technologies such as ASM, raw devices without installing Sun Cluster.
3) Any certification conflicts.
Any correction is welcome..
-Harish Kumar Kalra

Real Application Cluster on Sun Solaris 8 and Sun Cluster 3

Hello,
we want to install Oracle 9i Enterprise Edition in combination with Oracle Real Application Cluster-Option on 2 Nodes. Every node (12-CPU-SMP-Machine) should running Sun Solaris 8 and Sun Cluster 3 Service.
Does this configuration work with ORAC? I found nowhere informations about. Is there anything I have to pay special attention for during installation?
Thank you for helping and best regards from Berlin/Germany
Michael Wuttke

Forms and report services work fine on solaris 8.
My problem is on the client side.
I have to use solaris 8 with netscape like forms clients
and I wasn't able to make it work with java plugins.
Any solution?
Mauro

Fe_rpc_command: cmd_type(enum) on Sun cluster

Similar Messages

Maybe you are looking for