Basic question that you need to be asking is why am i creating trigger on the fly. Can you answer that?
The table gets created from stored procedure based on configuration, which is decided by front end user , it has an id column which was not in use, we were using two columns to find unique record,
now i want to generate unique id in that one column,i do not want to depend on two columns ,i do not want to change the entry page also, so only solution
is to create a sequence and trigger with the table which is getting created from stored proc.
it is automatic felicity, so that no body should bother us to create a table for their new module.
so kindly answer my question.
i do not have access
Well, since you already got the suggestion, I think I can 'safely' confirm it (or else: 'mod' me):
One workaround to try is to set PLSCOPE_SETTINGS='identifiers:none'
in the session or init.ora. Then drop the affected package and any synonym
for the package and recreate.
> 3) is there any disadvandage of setting PLSCOPE_SETTINGS to NONE .
You can read more about it here: