Is there a reason (any at all), not to alter all the custom packages in my
database to compile them with PLSCOPE_SETTINGS='IDENTIFIERS:ALL'? Performance?
Security? Anything?
If there are reasons not to do it in production, I'm considering giving out
DBAs a script to turn it on for everything as part of their instance-cloning
procedures, so it would be turned on in all non-production environments. That
script would include an ALTER SYSTEM SET PLSCOPE_SETTINGS='IDENTIFIERS:ALL', so
that PLScope data will be maintained as developers do their work. Any reasons
this is a bad idea?
Thanks,Matt
