Answer / guest

Cause: a warning issued whenever the server has continuously
failed for three days in its attempts to connect to the
configuration database. The server disables reload checking.
Reload checking can later be re-enabled from the Oracle
Network Manager or the Oracle Names control program.

Action: Make sure that the database is running, that its
name and password as specified in the Oracle Network Manager
are accurate, and that there is SQL*Net connectivity between
the Oracle Names server and the database. To force the
server to start up anyway, using its checkpoint data, start
the server with the names.no_region_database parameter set
to TRUE. If no checkpoint data is available, the server will
shut down.

Please add more information about this Error

ORA-01919: role 'string' does not exist

1 Answers  

---

ORA-28153: Invalid client initial role specified: 'string'

1 Answers  

---

ORA-01180: can not create datafile 1

1 Answers  

---

NNO-00303: server "string" started with process ID number

1 Answers  

---

ORA-14323: cannot add partition when DEFAULT partition exists

1 Answers  

---

DRG-12306: column string is too long for index set columns

1 Answers  

---

ORA-16501: the Data Guard broker operation failed

1 Answers  

---

ORA-12232: TNS:No path available to destination

1 Answers  

---

ORA-19335: Invalid format type object

1 Answers  

---

ORA-01100: database already mounted

3 Answers   Oracle, Wipro,

---

DRG-50939: parser not set

1 Answers  

---

ORA-02402: PLAN_TABLE not found

1 Answers  

---