search from google.PRKC-1007 "Problem in creating directories on the nodes"Cause: Attempted directory create operation(s) from the local node to one or more nodes in the cluster and one or multiple of those directory create operations failed. This can occur either because one or more nodes failed during the operation or the destination directory did not have write permission for the user on one or more of the nodes or the source file did not exist or on UNIX platforms 'rcp' command to one or more nodes failed.Action: See earlier error messages for details.
Subject: PRK% Errors - Cause and Action Required
Type: BULLETIN
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 01-MAR-2002
Last Revision Date: 02-JUL-2002
PURPOSE
-------This note was created to document PRK errors as there is very little information
written about these in 9.0.X
SCOPE & APPLICATION
-------------------This note is for DBA's needing to resolve PRK% Errors.
PRK% ERRORS - CAUSE & ACTION REQUIRED
--------------------------------------PRK% Errors can be broken up into the following categories:Global Services Daemon Error Messages (PRKA)
Cluster Command Error Messages (PRKC)
Cluster Setup for Windows NT Error Messages (PRKI)
Server Control (SRVCTL) Utility Error Messages (PRKO)
Cluster Database Management Error Messages (PRKP)
Repository Error Messages (PRKR)The following sections list the cause and actions required for each of these types:Global Services Daemon Error Messages (PRKA)
--------------------------------------------PRKA-2001: GSD already exists
Cause: An attempt was made to create the Global Services Daemon (GSD)
application while there is a GSD application already running.
Action: You cannot create the GSD application at this moment since it already
exists. Stop the running GSD and create the GSD application again using 'srvctl
add nodeapps'. You can also use the existing GSD application.PRKA-2002: Listener already exists
Cause: An attempt was made to create a Listener application while there is a
running Listener application.
Action: You cannot create the Listener application at this moment since it
already exists. Stop the running Listener and create the Listener application
again using 'srvctl add nodeapps'. You can also use the existing Listener application.PRKA-2003: Agent already exists
Cause: An attempt was made to create an Agent application while there is a
running Agent application.
Action: You cannot create the Agent application at this moment since it already
exists. Stop the running Agent and create the Agent application again using
'srvctl add nodeapps'. You can also use the existing Agent application.PRKA-2004: VIP already exists
Cause: An attempt was made to create a Virtual IP application while there is a
running Virtual IP application.
Action: You cannot create the Virtual IP application at this moment since it
already exists. Stop the running Virtual IP application and create the Virtual IP
application using 'srvctl add nodeapps'. You can also use the existing Virtual IP
application.PRKA-2006: Netmasks are different
Cause: Invalid range of VIP addresses specified for the cluster
Action: Check if the starting and ending addresses in the VIP range being
added, belong to the same netmask.PRKA-2007: No free VIP is available
Cause: No free Virtual IP address available from the list of Virtual IP addresses
added to the cluster database. All of the of Virtual IP addresses added are in use.
Action: Add new Virtual IP addresses using to the cluster database using
'srvctl add vip_range'PRKA-2008: VIP is not found
Cause: A Virtual IP address was not found in the Virtual IP range added to the
cluster database.
Action: Add Virtual IP addresses to the cluster using 'srvctl add vip_range'PRKA-2009: Remote command failed
Cause: An error occurred while trying to execute an operation by the Global
Services Daemon either on a local node or a remote node.
Action: Check whether the Global Services Daemon is up and responsive by
doing 'srvctl config'.
Book Fixed font Go to End Doc ID: Note:169454.1
Subject: What to do with PRKR-1007, PRKR-1001, PRKO-2008, or PRKR-1020 errors
Type: PROBLEM
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 28-DEC-2001
Last Revision Date: 02-JUL-2002
Problem Description
-------------------What to do when you get the following errors:
PRKR-1007, PRKR-1001, PRKO-2008 or PRKR-1020For example:srvctl config -p V901
PRKR-1007 : getting of cluster database V901 configuration failed, PRKR-1001
PRKR-1020 : reading of version information failed, open() for /dev/ptrs401/
rsrcfg device failed, No such file or directory
PRKO-2008 : Application error: Failure in getting Cluster Database Configuratio1
frtru2:ora901> srvctl config -p V901 -n frtru1
PRKR-1007 : getting of cluster database V901 configuration failed, PRKR-1001
PRKO-2008 : Application error: Failure in getting Cluster Database Configuratio1
Solution Description
--------------------You need to follow the steps below:1. Check /var/opt/oracle/srvConfig.loc or
/etc/srvConfig.loc or
$ORACLE_HOME/srvm/config/srvConfig.loc file exists. If the srvConfig.loc file does not exists you have to create it as 'root'
with the file permissions set to: 755, owned by your oracle:dba user.:
2. Check the srvConfig.loc file contains
srvconfig_loc=[symbolic link to shared device you created] Example: srvconfig_loc=/dev/vx/rdsk/usupportdg/V9iOPSM.dbf that should point to an existing raw device if you are not on Tru64
platform. In this case the file must be created on a filesystem.
Please issue the following commands to check the srvConfig.loc file points
to an existing raw device (if not on tru64)
$ srvconfig -version If the config file is pointing to a raw device the following type of output
should be returned: $ raw device version "9.0.0.0.0" If it isn't a raw device, if you are on tru64 platform, you will get the
following: $ "oracle.ops.mgmt.rawdevice.RawDeviceException: PRKR-1020 :
reading of version information failed,
/u01/ora/oradata/RAC_Cluster_Configuration_File
is not a raw device file, No such file or directory"
3. Find the 'gsd' daemon on both nodes. $ ps -ef | grep jre
4. Shutdown the 'gsd' daemon on both nodes. $ kill -9 <gsd process> (in 9.2, you can enter $ gsdctl stop)
5. Format the srvConfig file only from one node. $ srvconfig -init -f This will read the srvConfig.loc file so if the shell prompt comes back,
this would be successful.
6. Restart the 'gsd' on both nodes. $ gsd
When it's started, you should get a message:
'Successfully started the daemon on the local node'. Then go to the other node and run the same command.
If you get the same message, go to the next step.7. Check that gsd is running on both nodes. $ ps -ef |grep jre
8. Reconfigure the Cluster Database:in 9.0.X: $ srvctl add db -p <db_name> -o $ORACLE_HOME
$ srvctl add instance -p <db_name> -i <instance_name> -n <node1> $ srvctl add instance -p <db_name> -i <instance_name> -n <node2> $ srvctl config -p <db_name>in 9.2.X:
$ srvctl add database -d <db_name> -o $ORACLE_HOME
$ srvctl add instance -d <db_name> -i <instance_name> -n <node1> $ srvctl add instance -d <db_name> -i <instance_name> -n <node2> $ srvctl config database -d <db_name>
Explanation
-----------You need to reinitialize the config shared file through srvconfig -init .
You may have to use -f (force) option.
Then you have to configure instance information before being able to see it from srvctlReferences
----------[BUG:2048730]
[NOTE:178683.1]
[NOTE:178435.1]
Additional Search Words
-----------------------PRKR-1005 : adding of cluster database ARAC configuration failed
PRKR-1007 : getting of cluster database V901 configuration failed
PRKR-1020 : reading of version information failed, open() for
device failed, no such file or directory.
PRKO-2008 : Application error: Failure in getting Cluster Database Configuration
. --------------------------------------------------------------------------------
Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal Notices and Terms of Use.