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

RMAN-02003: unrecognized character: string

1 Answers  

---

IMG-00830: boundary queue is full

1 Answers  

---

ORA-38769: FLASHBACK DATABASE failed after modifying data.

1 Answers  

---

ORA-24098: invalid value string for string

1 Answers  

---

SQL*Loader-00251: Sort devices are not used by SQL*Loader

1 Answers  

---

ORA-02453: duplicate HASH IS specification

1 Answers  

---

PLS-00386: type mismatch found at 'string' between FETCH cursor and INTO variables

1 Answers  

---

ORA-12922: concurrent ALTER DATABASE [NO] FORCE LOGGING command is running

1 Answers  

---

RMAN-06001: error parsing job step library

1 Answers  

---

ORA-03230: segment only contains string blocks of unused space above high water mark

1 Answers  

---

RMAN-06528: CHANGE ... KEEP not supported for BACKUPPIECE

1 Answers  

---

ORA-16151: Managed Standby Recovery not available

1 Answers  

---