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-16719: unable to query V$ARCHIVE_DEST fixed view

1 Answers  

---

ORA-30344: number of child cols different from number of parent level cols

1 Answers  

---

RMAN-08090: channel string: starting proxy restore

1 Answers  

---

TNS-00265: Navigator: Reloaded network configuration data

1 Answers  

---

ORA-01340: NLS error

1 Answers  

---

ORA-01205: not a data file - type number in header is string

1 Answers  

---

RMAN-06176: no recovery required; all files are readonly or offline

1 Answers  

---

NNL-00809: Queries received, multiple types: number

1 Answers  

---

QSM-01056: no query rewrite for this DDL expression

1 Answers  

---

NZE-28768: bad magic number

1 Answers  

---

ORA-16529: bad sender id

1 Answers  

---

TNS-00040: INTCTL: failed to initialize trace context- Continuing anyway

1 Answers  

---