Return
-
Title
Why there are Toad Tables in dba_common_audit_trail? -
Description
Why there are Toad Tables in dba_common_audit_trail?
Toad Objects list: DELL_COM_TEAM_CODING, QUEST_COM_TEAM_CODING, SQLNAV4_VCS_CONFIG, PLSQL_PROFILER_DATA, PS_MMC_AMC_DATA_VW.
-
Cause
The records in the AUDIT Table are created because Toad is checking for certain privileges by attempting a SELECT statement from those tables, considering that Toad may or may not have access to them, Oracle finds that as a good enough reason to create an AUDIT record. -
Resolution
Toad used to check if those objects exists by looking for the synonym in DBA/ALL_SYNONYMS, and then, if they were found, look for the actual object in DBA/ALL_OBJECTS. The problem with this approach, is that it's very slow for some users, and there were a lot of complaints about connection times being too slowConsidering that we know they are not really a problem (such as someone trying to hack, etc), Toad Team asks you, if it's possible for you, to "ignore" these records.