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-09821: Numeric label is not valid

1 Answers  

---

ORA-08205: ora_addr: $ORACLE_SID not set in environment

1 Answers  

---

PCB-00305: Oracle extension to the COMMIT and ROLLBACK statements

1 Answers  

---

ORA-36389: (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.

1 Answers  

---

ORA-13186: fixed tile size tessellation failed

1 Answers  

---

UDE-00050: Unable to setup parameter processing.

1 Answers  

---

ORA-15046: ASM file name 'string' is not in single-file creation form

1 Answers  

---

ORA-02067: transaction or savepoint rollback required

1 Answers  

---

ORA-25117: MIN/MAX/Block Number expected

1 Answers  

---

ORA-39083: Object type string failed to create with error: string Failing sql is: string

1 Answers  

---

ORA-09708: soacon: failed to bind socket to port.

1 Answers  

---

ORA-01025: UPI parameter out of range

1 Answers   TCS,

---