1Z0-146 · Question #90
You executed the following command to alter the session parameter: SQL> ALTER SESSION SET PLSCOPE_SETTINGS = 'IDENTIFIERS:ALL'; Which two statements are true in this scenario? (Choose two.)
The correct answer is A. If the SYSAUX tablespace is unavailable, and you compile a program unit, PL/Scope does not C. All the identifiers declared in compiled program units before altering the parameter settings do not. A: PL/Scope stores the data that it collects in the SYSAUX tablespace. If the SYSAUX tablespace is unavailable, and you compile a program unit with PLSCOPE_SETTINGS='IDENTIFIERS:ALL', PL/Scope does not collect data for the compiled object. The compiler does not issue a warning…
Question
You executed the following command to alter the session parameter:
SQL> ALTER SESSION SET PLSCOPE_SETTINGS = 'IDENTIFIERS:ALL'; Which two statements are true in this scenario? (Choose two.)
Options
- AIf the SYSAUX tablespace is unavailable, and you compile a program unit, PL/Scope does not
- BAll the identifiers declared in compiled program units before altering the parameter settings appear
- CAll the identifiers declared in compiled program units before altering the parameter settings do not
- DIf the SYSAUX tablespace is unavailable, and you compile a program unit, PL/Scope collects data
How the community answered
(32 responses)- A81% (26)
- B13% (4)
- D6% (2)
Explanation
A: PL/Scope stores the data that it collects in the SYSAUX tablespace. If the SYSAUX tablespace is unavailable, and you compile a program unit with PLSCOPE_SETTINGS='IDENTIFIERS:ALL', PL/Scope does not collect data for the compiled object. The compiler does not issue a warning, but it saves a warning in USER_ERRORS. C: Identifiers declared in compilation units that were not compiled with PLSCOPE_SETTINGS='IDENTIFIERS:ALL' do not appear in *_IDENTIFIER static data dictionary views.
Topics
Community Discussion
No community discussion yet for this question.