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-10563: Test recovery had to corrupt data block (file# string, block# string) in order to proceed

1 Answers  

---

LPX-00114: element "~1S" attribute "~2S" has invalid enumeration value "~3S"

1 Answers  

---

DRG-52104: the Oracle Text environment could not initialize

1 Answers  

---

ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance

1 Answers  

---

SAP log on Error Message: "Msg E14 645 not found"

0 Answers  

---

PCB-00001: %s

1 Answers  

---

ORA-22328: object "string"."string" has errors. string

1 Answers  

---

TNS-12564: TNS:connection refused

6 Answers   Oracle,

---

PCC-02415: Cannot manipulate Object attributes in an OBJECT GET or SET

1 Answers  

---

ORA-10566: Test recovery has used all the memory it can use

1 Answers  

---

IMP-00013: only a DBA can import a file exported by another DBA

1 Answers  

---

ORA-06736: TLI Driver: server not running

1 Answers  

---