Skip to Main Content

SQL Developer for VS Code

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORA-00600 [pevm_INSTC2] when opening database objects on non-CDB 19.28 — causes ORA-17008

Philip KwanApr 19 2026 — edited Apr 20 2026

Extension version: 26.1.0
Database: Oracle 19c Enterprise Edition 19.28.0.0.0, non-CDB, AL32UTF8
OS: Windows

Problem: Cannot open any database object in the connection navigator. Connecting and browsing the object tree works, but clicking any procedure/package to view its source immediately disconnects with ORA-17008.

Root cause: The extension's source-fetching query uses inline PL/SQL WITH FUNCTION with nested function calls referencing SYS.DBA_SOURCE and origin_con_id. This triggers ORA-00600 [pevm_INSTC2: bad sql string table] on non-CDB 19c, which kills the server session.

Reproducer SQL (from the extension's debug log):

WITH
FUNCTION cont (schema IN VARCHAR2, object_name IN VARCHAR2, object_type IN VARCHAR2) RETURN NUMBER IS
cont_id NUMBER;
BEGIN
SELECT origin_con_id INTO cont_id FROM sys.dba_source
WHERE owner = schema AND name = object_name AND type = object_type AND ROWNUM < 2;
RETURN cont_id;
END cont;
FUNCTION code (schema IN VARCHAR2, name IN VARCHAR2, pltype VARCHAR2) RETURN CLOB IS
cont_id NUMBER; ...
BEGIN
cont_id := cont(schema, name, pltype); ...
END code;
SELECT code('TEST_REPORT','REP_RUN_TEST_PRC','PROCEDURE') text FROM dual;

Suggestion: Fall back to SELECT text FROM dba_source ... ORDER BY line or DBMS_METADATA.GET_DDL when the database is non-CDB, or avoid nested inline PL/SQL functions entirely.

This post has been answered by Philip Kwan on May 12 2026
Jump to Answer
Comments
Post Details
Added on Apr 19 2026
2 comments
135 views