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-12155: TNS:received bad datatype in NSWMARKER packet

1 Answers   IBM,

---

ORA-01282: date range specified is invalid

1 Answers  

---

ORA-26683: invalid value for value_type

1 Answers  

---

PCB-00301: Use of non-ANSI function is an Oracle extension

1 Answers  

---

ORA-39099: cannot create index for "string" on master table string

1 Answers  

---

UDI-00015: invalid context or job state for parameter, 'string'.

1 Answers  

---

ORA-07626: smsget: sga already mapped

1 Answers  

---

ORA-31600: invalid input value string for parameter string in function string

1 Answers  

---

ORA-02225: only EXECUTE and DEBUG privileges are valid for procedures

1 Answers  

---

ORA-06706: TLI Driver: service not found

1 Answers  

---

ORA-13293: cannot specify unit for geometry without a georeferenced SRID

1 Answers  

---

ORA-01271: Unable to create new file name for file string

1 Answers  

---