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

PROC-00101: Operating System error [string]

1 Answers  

---

ORA-01692: unable to extend lob segment string.string partition string by string in tablespace string

1 Answers  

---

ORA-07286: sksagdi: cannot obtain device information.

1 Answers  

---

NNL-00509: set|show cache_checkpoint_interval [<seconds>] [<server_list>] : set|show the server's cache checkpoint interval

1 Answers  

---

PLS-00551: character set ANY_CS is only allowed on a subprogram parameter

1 Answers  

---

ORA-02180: invalid option for CREATE TABLESPACE

1 Answers   IBM,

---

ORA-01032: no such userid

1 Answers  

---

ORA-01166: file number string is larger than string (string)

1 Answers  

---

DRG-11808: Reset Content

1 Answers  

---

ORA-14172: invalid ALTER TABLE EXCHANGE SUBPARTITION option

1 Answers  

---

NNO-00265: warning: cannot load data from checkpoint file

1 Answers  

---

ORA-21701: attempt to flush objects to different servers

1 Answers  

---