Code assist on objects in a particular schema not working

[IncredibleMrT]

Hi,
When doing a select statement, after typing the schame followed by full stop, the code assist process gives me a list of all available objects available. This is great.
However, I have one schema where it only shows 1 single object available.
It's bugged me for ages.
Thinking it might be some setting or configuration file i've somehow messed up, i've tried with a fresh install, but it still does the same for that exact same schema.
Any ideas?
Thanks
Matt.

PL/SQL Developer
Version 12.0.7.1837 (32 bit)
01.105297 - 5 user license
Service Contract: 01/01/2019
Windows 10 (64-bit) Build 16299

 

[Marco Kalter]

Does the user have any additional object privileges for this schema, other than the one object that is listed?

 

[IncredibleMrT]

The users are all identical in their setup.

If I fully type out the command featuring a table/procedure/etc in that schema, it works without issue, but if I rely on code assist it does not work. Also, rather oddly considering what i've just said, if I try to compile something in my schema referencing something in the other, then it is unable to see it.

I've tried the same thing from Oracle SQL developer, and it has no such issue. Compilations work, code-assists works.

Would a copy of debug.txt give you any further insight? Let me know where I can email it.
Thanks.

 

[Marco Kalter]

If you can generate a debug.txt file for the Code Assistant problem, that might help. Just enter schema followed by a dot, wait for the 1 object to appear in the list, and send me the debug.txt file.

 

[IncredibleMrT]

Sent. Thank you.

If you can generate a debug.txt file for the Code Assistant problem, that might help. Just enter schema followed by a dot, wait for the 1 object to appear in the list, and send me the debug.txt file.

 

[IncredibleMrT]

Solved.
It turns out I had a package in my one with the same name as the schema I couldn't see objects for.
So, when I was doing 'select * from schema2. ', I was actually seeing the schema2 package and not the schema2 err schema.
Hadn't spotted it in all this time as that package didn't display in the package/package body object browser.

Marco spotted it in quick time. Thanks for your help.