Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-30687: session terminated by debugger
- 1 Answers
- 3717 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: Your program's execution has been stopped by the
debugger. This can occur because of an explicit request to
do so sent by the debugger, or because the debugger
disconnected without first telling Oracle to let your
program continue to run after the disconnection. To stop
your program completely, Oracle needs to fully terminate the
process.
Action: This is in response to a debugger request; it is not
an error. No action required.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-30688: maximum program calling depth exceeded
ORA-13625: %s is an invalid advisor object type.
ORA-09352: Windows 32-bit Two-Task driver unable to spawn new ORACLE task
ORA-00379: no free buffers available in buffer pool string for block size stringK
ORA-09212: sfwfbmt: error writing to file
CLSS-00002: unable to determine local node number. type string
ORA-22909: exceeded maximum VARRAY limit
ORA-12203: TNS:unable to connect to destination
NID-00350: string (number) string
PLS-00337: "string" matches too many object table aliases
ORA-38499: expression set already configured for stored/indexed attributes
KUP-04029: numeric field overflowed
Oracle Errors 
