Sonntag, 22. November 2009

PRKO-2007 is not always correct

This week I had to stop and start an instance in a CRS-cluster. Nothing special so far, I just hit a PRKO-2007 error. For those which does not know it by heart, here the short description:
PRKO-2007: "Invalid instance name: "
Cause: An invalid instance name was entered.
Action: Use the correct instance name for the database. Run 'srvctl config database
-d ' command to find out all instances of a database in the
Cluster Database Configuration.


and here the copy of my commands (solution included):
oracle@aves742p:~/ [EDWP031] srvctl stop instance -d EDWP03 -i EDWP031
PRKO-2007 : Invalid instance name: EDWP031
oracle@aves742p:~/ [EDWP031] srvctl stop instance -d EDWP03_SITE1 -i EDWP031


I'm sure, you see the difference, and it's not the instance!
Just once again: don't trust the error message 100%, sometimes it's still worth to use the brain ;-)

Kommentare:

Coskan Gundogar hat gesagt…

Just for make things a bit clear

EDWP03_SITE1

is not 8 character. is there a modification on it ?

Martin Berger hat gesagt…

maybe these 3 statements might make it clear:

desc v$database
Name Type
-------------------------------
1 DBID NUMBER
2 NAME VARCHAR2(9)
.
.
.
42 DB_UNIQUE_NAME VARCHAR2(30)


show parameter db_%name

NAME TYPE VALUE
-------------------
db_name string EDWP03
db_unique_name string EDWP03_SITE1


desc v$instance
Name Null? Typ
-------------------------------
1 INSTANCE_NUMBER NUMBER
2 INSTANCE_NAME VARCHAR2(16)
...

I think, there is no realy '8 character' limit anywhere around?

just one more thing: we use to set DB_UNIQUE_NAME to a _SITE1 string by default to be safe if we ever want to create a DataGuard config. There is only a small side effect: the default SERVICE is set to this name.

Dev hat gesagt…
Der Kommentar wurde von einem Blog-Administrator entfernt.