Trigger appeared with strange name

Question

Oracle 11g
Suddenly we get this error when updating a certain table:
ORA-04098: trigger 'AM_DEV.BIN$our4yawU287gQBMKOxY2NA==$0' is invalid and failed re-validation
I see this trigger listed in user_triggers, but deleting fails:
SQL> drop trigger 'BIN$our4yawU287gQBMKOxY2NA==$0' ;
drop trigger 'BIN$our4yawU287gQBMKOxY2NA==$0'
ERROR at line 1:
ORA-04070: invalid trigger name
I see similar named triggers on other tables too.
What are they, and how do I get rid of them?

Answer 1

xerces8 wrote:
Thanks.
I tried single quotes first and got an error.
I guess I have to learn more about quoting...If you have database objects created without double quotes then they are automatically converted to UPPERCASE when stored in the data dictionary...
SQL> select table_name from user_tables where table_name like 'F%';
no rows selected
SQL> create table fred (x number);
Table created.
SQL> select table_name from user_tables where table_name like 'F%';
TABLE_NAME
FREDIf you have objects created with double quotes then the case of the name is preserved...
SQL> create table "Fred" (x number);
Table created.
SQL> select table_name from user_tables where table_name like 'F%';
TABLE_NAME
Fred
FREDThus if I try and drop the table without double quotes it will default to the object in UPPERCASE...
SQL> drop table fred;
Table dropped.
SQL> select table_name from user_tables where table_name like 'F%';
TABLE_NAME
FredAgain if I try and drop the other table without double quotes it won't find it because it's assuming UPPERCASE...
SQL> drop table Fred;
drop table Fred
ERROR at line 1:
ORA-00942: table or view does not existwhereas the database object is case specific, so we need double quotes to get it exactly right...
SQL> drop table "Fred";
Table dropped.
SQL> select table_name from user_tables where table_name like 'F%';
no rows selected
SQL>Of course if you specify double quotes when creating it, but you specify the name in UPPERCASE anyway...
SQL> create table "FRED" (x number);
Table created.
SQL> select table_name from user_tables where table_name like 'F%';
TABLE_NAME
FRED... then you don't need double quotes to drop it because UPPERCASE is already assumed...
SQL> drop table FRED;
Table dropped.
SQL> select table_name from user_tables where table_name like 'F%';
no rows selectedIt is always better to create your database objects without using double quotes, especially if you use anything but UPPERCASE, because if it contains any lower case letters then any developers trying to access those tables need to know the case of the object and always need to specify it in double quotes. It's a pain in the @rse, so best avoided.
Of course we can't help that Oracle uses mixed case for internal reasons, such as dropped objects in the recyclebin.