Answer / guest

Cause: The user issued a SET SERVER request and the current
managed Oracle Names server was unable to translate that
name into an address. Alternatively, the user issued a
control program request to a specific server, and that
server's name could not be translated into an address. Both
problems are almost always caused by mis-typing the server name.

Action: Re-issue the request with a valid server name.

Please add more information about this Error

TNS-12634: Memory allocation failed

1 Answers  

---

NCR-01007: NCRS: Operation is not supported in a given mode.

1 Answers  

---

ORA-19554: error allocating device, device type: string, device name: string

1 Answers  

---

ORA-01409: NOSORT option may not be used; rows are not in ascending order

1 Answers  

---

SQL*Loader-00272: Table level OPTIONS statement ignored.

1 Answers  

---

ORA-27488: unable to set string because string was/were already set

1 Answers  

---

ORA-13008: the specified date format has an invalid component

1 Answers  

---

RMAN-06517: KEEP option is not supported for archive log backups

1 Answers  

---

EXP-00086: Primary key REFs in table "string"may not be valid on import

1 Answers  

---

DRG-11819: Bad Request

1 Answers  

---

PLS-01471: The keyword DISTINCT must be present in a COUNT(DISTINCT sim_expr)

1 Answers  

---

TNS-00078: * log_on - ask process_name to turn logging on

1 Answers  

---