Hi,
After upgrading to 11.1.0.7 we have also upgraded our IDE to 8.0.4. The server/client s/w has also been upgraded to 11.1.0.7, so all interfaces are certified. I assume that PL/SQL Dev 8.0.4 is also certified against 11g.
We are hitting several issues, however one of the main ones at the moment is ORA-600s being recorded whilst using the debugging tool (Test Window). If the debug option of 'Update call stack after each step' is switched on, and whilst debugging we hit the Break button (Shift+Esc), the session hangs and has to be killed off.
If we choose not to use the call stack trace option, the process works.
In the trace file produced there is a note of a ORA-0600 detected. I have raised this with Oracle Support, however since this is not an IDE tool under their support and since I cannot reproduce the error on say SQL Developer, they cannot help further.
The error noted and feedback from Oracle is as follows:
The error ORA-600 [ 17090] refers to the condition when the kernel error handling layer is called to pop and resignal the topmost error on the errorstack and it finds the stack empty.
This is the case here as the trace file generated is already empty ( no call stack function)
the error is of the type memory corruption, means no harm on the underlying database.
You mentioned that you hit BREAK or called specific process in the PL/SQL developer tool, unfortunately this is not oracle property tool so i can not help you in what exactly this button/process do.
Thanks
Lise
After upgrading to 11.1.0.7 we have also upgraded our IDE to 8.0.4. The server/client s/w has also been upgraded to 11.1.0.7, so all interfaces are certified. I assume that PL/SQL Dev 8.0.4 is also certified against 11g.
We are hitting several issues, however one of the main ones at the moment is ORA-600s being recorded whilst using the debugging tool (Test Window). If the debug option of 'Update call stack after each step' is switched on, and whilst debugging we hit the Break button (Shift+Esc), the session hangs and has to be killed off.
If we choose not to use the call stack trace option, the process works.
In the trace file produced there is a note of a ORA-0600 detected. I have raised this with Oracle Support, however since this is not an IDE tool under their support and since I cannot reproduce the error on say SQL Developer, they cannot help further.
The error noted and feedback from Oracle is as follows:
The error ORA-600 [ 17090] refers to the condition when the kernel error handling layer is called to pop and resignal the topmost error on the errorstack and it finds the stack empty.
This is the case here as the trace file generated is already empty ( no call stack function)
the error is of the type memory corruption, means no harm on the underlying database.
You mentioned that you hit BREAK or called specific process in the PL/SQL developer tool, unfortunately this is not oracle property tool so i can not help you in what exactly this button/process do.
Thanks
Lise
