Answer / guest

Cause: There are the following possible causes: The backend
is not reachable. This could happen if the permissions are
not set correctly for a shared device backend. CSS could not
be contacted because of communication failure. This could
happen if the cluster registry was never initialized at
PROCR_INSTALL_LEVEL and one tried to initialize it at other
OCR levels.

Action: Make sure that cluster registry was initialized
properly. Make sure that the clusterware is working.

Please add more information about this Error

ORA-31444: parameter error while acquiring lock on string

1 Answers  

---

DRG-11802: Switching Protocols

1 Answers  

---

ORA-13381: table:string not found in network:string

1 Answers  

---

TNS-00002: INTCTL: error while starting the Interchange

1 Answers  

---

DRG-12012: Proxy authentication failed - retry?

1 Answers  

---

SQL*Loader-00266: Unable to locate character set handle for string.

1 Answers  

---

ORA-12720: operation requires database is in EXCLUSIVE mode

1 Answers  

---

ORA-36980: (XSRELGID02) Variable workspace object must have a numeric data type.

1 Answers  

---

NNL-00831: Deletes refused, name is not a leaf name: number

1 Answers  

---

ORA-01149: cannot shutdown - file string has online backup set

2 Answers  

---

RMAN-06590: tablespace string cannot be converted

1 Answers  

---

PLS-00375: illegal GOTO statement; this GOTO cannot branch to label 'string'

1 Answers  

---