Showing results for 
Search instead for 
Did you mean: 

srvctl config got error

Fauziah Mahdan
Super Advisor

srvctl config got error

Hi all, My hpux11.11 installed with oracle 9i using Oracle Realtime Application Cluster.
When we run srvctl config an error appear as:

hostname:/u01/oracle# srvctl config
java.rmi.NotBoundException: OPSMDaemon
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Compiled Code)
at sun.rmi.transport.StreamRemoteCall.executeCall(
at sun.rmi.server.UnicastRef.invoke(
at sun.rmi.registry.RegistryImpl_Stub.lookup(
at java.rmi.Naming.lookup(
at oracle.ops.mgmt.cluster.GetActiveNodes.createDaemon(
at oracle.ops.mgmt.cluster.GetActiveNodes.getReference(
at oracle.ops.mgmt.command.RemoteCommand.createDaemon(
at oracle.ops.mgmt.command.RemoteCommand.(
at oracle.ops.mgmt.cluster.Cluster.listParallelServers(
at oracle.ops.opsctl.OPSCTLDriver.executeConfig(Compiled Code)
at oracle.ops.opsctl.OPSCTLDriver.execute(
at oracle.ops.opsctl.OPSCTLDriver.main(
PRKC-1019 : Error creating handle to daemon on the node hostname

pls help why this happen?
Fauziah Mahdan
Honored Contributor

Re: srvctl config got error

>>PRKC-1019 : Error creating handle to daemon on the node hostname

This error indicates that GSD daemon is not running on the server. SRVCTL uses this daemon.

Check if it is running. If it is not running, you can start it using

$ORACLE_HOME/bin/gsdctl start
Fauziah Mahdan
Super Advisor

Re: srvctl config got error

The GSD is running actually.
When I check cmviewcl command I found one of the package is not up but in starting mode.
I ahve to restart the server the server hang at Stop highly Available Cluster.
Then I stop using TC from GSP command.
Check again the cmviewcl both package are running.
And my srvtl is ok NOW.
How to check why is the package in starting mode.
Normally cronjo will issue command srvctl to stop instance and listener for hot backup.
Why this time the pkg is not up?

Honored Contributor

Re: srvctl config got error

Check the pkg log file, you would see the activity log of package statup. Something was not getting started as it should be while pkg was getting started. For the same reason, the pkg stop wouldn't work either as pkg initial status was consistent. That's why it got looped and appeared as hanged.

The pkg log would give you the clue of possible cause.