Answer / guest

Cause: An attempt was made to startup/shutdown database when
connected to a shared server via a dispatcher.

Action: Re-connect as user INTERNAL without going through
the dispatcher. For most cases, this can be done by connect
to INTERNAL without specifying a network connect string.

Please add more information about this Error

ORA-24383: Overflow segment of an IOT cannot be described

1 Answers  

---

ORA-19608: %s is not a backup piece

1 Answers  

---

ORA-16181: SGA specified for Logical Standby is too large

1 Answers  

---

ORA-19732: incorrect number of datafiles for tablespace string

1 Answers  

---

CLSS-00004: unable to allocate memory resources

1 Answers  

---

---

ORA-01605: missing numbers in clause "string" of string

1 Answers  

---

PLS-00261: Java CALL Specification not yet allowed as a method in an object type

1 Answers  

---

ORA-02469: Hash expression does not return an Oracle Number.

1 Answers  

---

SQL*Loader-00476: count of elements for collection is not set or null, 0 will be used

1 Answers  

---

ORA-08278: Cannot get CPU statistics

1 Answers  

---

TNS-00248: Unable to get information from file :string: Exiting with NR error:number

1 Answers  

---

QSM-00787: the tablespace string is invalid for directive string

1 Answers  

---