Answer / guest

Cause: The control program was unable to contact its default
name server during startup. There are a number of possible
causes for this error. The control program's SQLNET.ORA file
must exist in the correct system-specific location, and must
be readable by the control program. The file must contain a
names.preferred_servers entry with valid name server
addresses. The first server in the preferred-server list
must be running, and there must be network connectivity
between the control program and that server.

Action: Check to see that all of the above are true. If the
control program is still unable to contact its default
server, turn on tracing and restart the control program. If
the error persists, contact Worldwide Customer Support.

Please add more information about this Error

NNL-00995: Unmatched responses received: number

1 Answers  

---

ORA-25199: partitioning key of a index-organized table must be a subset of the primary key

1 Answers  

---

RMAN-12007: cannot allocate more than number channels

1 Answers  

---

ORA-19322: An error occurred while reading from host (string): port (string)

1 Answers  

---

ORA-08450: invalid specification of CR in picture mask

1 Answers  

---

LCD-00207: nested parentheses encountered [string]

1 Answers  

---

NNL-00247: General request processing is now enabled

1 Answers  

---

ORA-02430: cannot enable constraint (string) - no such constraint

1 Answers  

---

ORA-28151: more than one user name specified for command

1 Answers  

---

ORA-22339: cannot alter to not final since its attribute column is substitutable

1 Answers  

---

ORA-32600: RETENTION and PCTVERSION cannot be used together

1 Answers  

---

ORA-01188: Block size string in header does not match physical block size string

1 Answers  

---