Code Assistant not appearing when connected to 23ai

[Knut2025]

Hi folks,

my shortcut for the code assistant to appear is CTRL+SPACE. When I am connected to ATP 19c (Cloud DB 19c Transaction Processing) the code assistant appears when hitting CTRL+SPACE. It does not when I change the connection to an ATP 23ai.

It does not list packages or tables but it lists columns and methods inside a package.

When writing

select * from all_tab

and hitting CTRL+SPACE then nothing is listed. But when writing

select * from all_tables where owne

it will show the column named "OWNER".

Are the any different approaches to collect the information from the DBs?

Cheers
Knut

 

[Marco Kalter]

For the "all_tab" case he Code Assistant will check all object names to find matching names, and it should have found the public synonym ALL_TABLES for SYS.ALL_TABLES.

To verify, can you perform the following query and let me know the result?

select * from all_synonyms
where synonym_name = 'ALL_TABLES'

 

[Knut2025]

Hi Marco,

thank you for your fast reply. Here is the result:

OWNER SYNONYM_NAME TABLE_OWNER TABLE_NAME DB_LINK ORIGIN_CON_ID
1 PUBLIC ALL_TABLES SYS ALL_TABLES 1

 

[Knut2025]

And this is not only a table problem but a problem for all kind of objects like functions, procedures, UDT, sequences, ...

 

[Marco Kalter]

The list of public synonyms for the Code Assistant are fetched in a background thread when you connect for the first time in PL/SQL Developer. It may be that this query takes a little longer on your 23ai database, so it may be that you type "all_tab" before the list is complete. Can you wait a few minutes before checking the "all_tab" list?

If this still fails, then to obtain some more diagnostic information, can you modify the PL/SQL Developer shortcut and add the DebugSQL parameter? For example:

"C:\Program Files\PLSQL Developer 16\plsqldev.exe" DebugSQL

Reproduce the problem and send me the debug.txt file that is generated in the %APPDATA%\PLSQL Developer 16 directory (e.g. C:\Users\\AppData\Roaming\PLSQL Developer 16).

 

[Knut2025]

Hi Marco,

thank you for your help. It works now but I can't tell you why.

Cheers Knut

 

[Marco Kalter]

Okay. Maybe it was a database performance issue as described in my previous reply.