Answer / guest

Cause: The server encountered an error while trying to get
its configuration ID from the configuration database. The
error can occur any time the server is unable to access the
configuration database. This error will cause the server to
shut down.

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-24199: message store is overflow

1 Answers  

---

LPX-00601: Invalid token in: '~S'

1 Answers  

---

ORA-01912: ROW keyword expected

1 Answers  

---

ORA-01968: Only specify RESETLOGS or NORESETLOGS once

1 Answers  

---

ORA-28181: proxy 'string' failed to enable one or more of the specified initial roles for client 'string'

1 Answers  

---

ORA-23411: materialized view "string"."string" is not in refresh group "string"."string"

1 Answers  

---

ORA-07225: sldext: translation error, unable to expand file name.

1 Answers  

---

ORA-36276: (XSCGMDLAGG06) Current operator does not need the weight variable.

1 Answers  

---

ORA-02899: smscre: Cannot create SGA with Extended Shared Memory feature

1 Answers  

---

ORA-32802: value for string must be string

1 Answers  

---

ORA-16105: Logical Standby is already running in background

1 Answers  

---

ORA-28156: Proxy user 'string' not authorized to set role 'string' for client 'string'

1 Answers  

---