PLSCOPE_SETTINGS='IDENTIFIERS:ALL' downsides?

From: Matt McPeak <mcpeakm_at_tempus-consulting-group.com>
Date: Mon, 18 Oct 2021 16:17:04 +0000 (UTC)
Message-ID: <1268724432.1798496.1634573824446_at_mail.yahoo.com>

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

--
http://www.freelists.org/webpage/oracle-l

Received on Mon Oct 18 2021 - 18:17:04 CEST

This message: [ Message body ]
Next message: Howard Latham: "Manageengine application Manager"
Previous message: Jonathan Lewis: "Re: SQL Statements responsible for huge redo generation"
Next in thread: Jacek Gębal: "Re: PLSCOPE_SETTINGS='IDENTIFIERS:ALL' downsides?"
Reply: Jacek Gębal: "Re: PLSCOPE_SETTINGS='IDENTIFIERS:ALL' downsides?"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message