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

EXP-00003: no storage definition found for segment(number, number)

2 Answers  

---

ORA-39310: illegal clean_failed_clone() call: it only applys to failed clones

1 Answers  

---

ORA-25443: duplicate column value for table alias: string, column number: string

1 Answers  

---

ORA-24900: invalid or unsupported mode paramater passed in call

1 Answers  

---

ORA-09910: Unable to find ORACLE password file entry for user.

2 Answers  

---

ORA-09215: sfqio: error detected in IOCompletionRoutine

1 Answers  

---

ORA-07272: spwat: invalid semaphore set id.

1 Answers  

---

ORA-24405: error occured while trying to create connections in the pool

1 Answers  

---

ORA-29280: invalid directory path

1 Answers  

---

ORA-15011: failure group "string" contains no members

1 Answers  

---

ORA-07645: sszfsl: $CHANGE_CLASS failure

1 Answers  

---

ORA-14072: fixed table may not be truncated

1 Answers  

---