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

ORA-07701: sksatln: internal exception: output buffer too small

1 Answers  

---

ORA-38708: not enough space for first flashback database log file

2 Answers  

---

ORA-40225: model is currently in use by another process

1 Answers  

---

ORA-14305: List value 'string' specified twice in partition 'string'

1 Answers  

---

ORA-02715: osnpgetbrkmsg: message from host had incorrect message type

1 Answers  

---

TNS-04232: Trace Assistant WARNING: Not retrieving all rows

1 Answers  

---

DRG-11835: Requested Range Not Satisfiable

1 Answers  

---

ORA-02801: Operations timed out

1 Answers  

---

KUP-11003: bad data encountered while reading from file string

1 Answers  

---

ORA-23290: This operation may not be combined with any other operation

1 Answers  

---

ORA-23603: STREAMS enqueue aborted due to low SGA

1 Answers  

---

DRG-50608: unexpected end of data

1 Answers  

---