Examine these statements which execute successfully: Which are the two reasons that no rows Are returned from the query?

Question

Exhibit

Options

• AOnly DBA users can query SESSION_CONTEXT view contents.
• BAn administrator issues the ALTER SYSTEM FLUSH global context statement.
• CThe set_empno_crx_proc procedure must be in a package.
• DThe application context is global.
• EEnterprise User Security is not configured and used for the user.

• A
  4% (2)
• B
  13% (6)
• C
  21% (10)
• D
  62% (29)

Explanation

Options D and E are correct because they identify a fundamental dependency in Oracle's application context architecture: when an application context is created with the ACCESSED GLOBALLY clause, it becomes a global context that is tightly coupled to Enterprise User Security (EUS). Global contexts store values keyed to enterprise usernames from an LDAP/directory service, so if EUS is not configured and the current user is not an enterprise user, Oracle has no valid key to retrieve context values - resulting in zero rows returned.

Why the distractors are wrong:

• A is false because SESSION_CONTEXT and SYS_CONTEXT are accessible to any database user, not just DBAs.
• B describes a real command (ALTER SYSTEM FLUSH GLOBAL CONTEXT) that would clear values, but the scenario states all statements executed successfully - no flush is implied.
• C is false because the trusted procedure used to set a context value can be a standalone procedure; it does not have to be packaged.

Memory tip: Think "Global needs Enterprise" - a Global context is useless without EUS. No EUS configured = no enterprise username = no context values = no rows.

No community discussion yet for this question.