From db tools such as SQL Developer, the message, "could not get schema object ORA 06552 Compilation unit analysis terminated ORA 06553" from db tools like SQl Developer can be encountered. Because of this error, a user cannot see the tables when they click on “Build using wizard” in the JDBC query activity under the Configuration tab.

From db tools like SQL Developer, the message, "could not get schema object ORA 06552 Compilation unit analysis terminated ORA 06553", could be encountered. User cannot see all tables clicking “Build using wizard”.

If running the query below :

select distinct(nls_charset_name(charsetid)) CHARACTERSET,
decode(type#, 1, decode(charsetform, 1, 'VARCHAR2', 2, 'NVARCHAR2','UNKOWN'),
9, decode(charsetform, 1, 'VARCHAR', 2, 'NCHAR VARYING', 'UNKOWN'),
96, decode(charsetform, 1, 'CHAR', 2, 'NCHAR', 'UNKOWN'),
112, decode(charsetform, 1, 'CLOB', 2, 'NCLOB', 'UNKOWN')) TYPES_USED_IN
from sys.col$ where charsetform in (1,2) and type# in (1, 9, 96, 112) order by CHARACTERSET;

A user may see two different character sets returned for CHAR, CLOB & VARCHAR2 etc. data.

Example:

AL16UTF16 NCHAR
AL16UTF16 NCLOB
AL16UTF16 NVARCHAR2
KO16MSWIN949 CHAR
KO16MSWIN949 CLOB
KO16MSWIN949 VARCHAR2
UTF8 CHAR
UTF8 CLOB

UTF8 VARCHAR2

indicates an error in the database character set setup, which is the cause of this ORA-06553: PLS-553 error.

Alter the database character set.

Example:

ALTER DATABASE CHARACTER SET INTERNAL_USE &CHARSET;

After altering the database characters, restart the listener. The user should be able to see the tables from Designer.