Oracle SYS_CONTEXT Function

exec dbms_application_info.set_action(‘INSERTING‘);

SELECT sys_context(‘USERENV‘, ‘ACTION‘) FROM DUAL;

• Kerberos-authenticated enterprise user: kerberos principal name
• Kerberos-authenticated external user : kerberos principal name; same as the schema name
• SSL-authenticated enterprise user: the DN in the user‘s PKI certificate
• SSL-authenticated external user: the DN in the user‘s PKI certificate
• Password-authenticated enterprise user: nickname; same as the login name
• Password-authenticated database user: the database username; same as the schema name
• OS-authenticated external user: the external operating system user name
• Radius/DCE-authenticated external user: the schema name
• Proxy with DN : Oracle Internet Directory DN of the client
• Proxy with certificate: certificate DN of the client
• Proxy with username: database user name if client is a local database user; nickname if client is an enterprise user
• SYSDBA/SYSOPER using Password File: login name
• SYSDBA/SYSOPER using OS authentication: operating system user name

Note: You can change the return value of the   AUTHENTICATION_DATA attribute using the length parameter of the syntax. Values of up to 4000 are accepted. This is the only attribute of USERENV for which Oracle implements such a change.

• Password-authenticated enterprise user, local database user, or SYSDBA/SYSOPER using Password File; proxy with username using password: PASSWORD
• Kerberos-authenticated enterprise or external user: KERBEROS
• SSL-authenticated enterprise or external user: SSL
• Radius-authenticated external user: RADIUS
• OS-authenticated external user or SYSDBA/SYSOPER: OS
• DCE-authenticated external user: DCE
• Proxy with certificate, DN, or username without using password: NONE

exec dbms_session.set_identifier(USER || ‘ ‘ || SYSTIMESTAMP);

SELECT sys_context(‘USERENV‘, ‘CLIENT_IDENTIFIER‘) FROM DUAL;

exec dbms_application_info.set_client_info(‘TEST‘);

SELECT sys_context(‘USERENV‘, ‘CLIENT_INFO‘) FROM DUAL;

SELECT user#
FROM sys.user$
WHERE name = USER;

SELECT name, value
FROM gv$parameter
WHERE name LIKE ‘db%name‘;

SELECT name, value
FROM gv$parameter
WHERE name LIKE ‘db%name‘;

• For enterprise users: the Oracle Internet Directory DN.
• For external users: the external identity (Kerberos principal name, Radius and DCE schema names, OS user name, Certificate DN).
• For local users and SYSDBA/SYSOPER logins: NULL.

The value of the attribute differs by proxy method:

• For a proxy with DN: the Oracle Internet Directory DN of the client
• For a proxy with certificate: the certificate DN of the client for external users; the Oracle Internet Directory DN for global users
• For a proxy with username: the Oracle Internet Directory DN if the client is an enterprise users; NULL if the client is a local database user.

• IDENTIFIED BY password: LOCAL
• IDENTIFIED EXTERNALLY: EXTERNAL
• IDENTIFIED GLOBALLY: GLOBAL SHARED
• IDENTIFIED GLOBALLY AS DN: GLOBAL PRIVATE

language_territory.characterset.

CREATE OR REPLACE PACKAGE my_pkg IS

PROCEDURE set_session_id(p_session_id NUMBER);
PROCEDURE set_ctx(p_name VARCHAR2, p_value VARCHAR2);
PROCEDURE close_session(p_session_id NUMBER);

END;
/

CREATE OR REPLACE PACKAGE BODY my_pkg IS

g_session_id NUMBER;

PROCEDURE set_session_id(p_session_id NUMBER) IS
BEGIN
  g_session_id := p_session_id;
  dbms_session.set_identifier(p_session_id);
end set_session_id;
--===============================================
PROCEDURE set_ctx(p_name VARCHAR2, p_value VARCHAR2) IS
BEGIN
  dbms_session.set_context(‘App_Ctx‘,p_name,p_value,USER,g_session_id);
END set_ctx;
--===============================================
PROCEDURE close_session(p_session_id ) IS
BEGIN
  dbms_session.set_identifier(p_session_id);
  dbms_session.clear_identifier;
END close_session;
--===============================================
END;
/

col var1 format a10
col var2 format a10

exec my_pkg.set_session_id(1234);
exec my_pkg.set_ctx(‘Var1‘, ‘Val1‘);
exec my_pkg.set_ctx(‘Var2‘, ‘Val2‘);

SELECT sys_context(‘app_ctx‘, ‘var1‘) var1,
sys_context(‘app_ctx‘, ‘var2‘) var2
FROM DUAL;

-- Now we‘ll log out/log in
-- At first, the context is empty-but we rejoin the session & there it is

disconnect
connect uwclass/uwclass

SELECT sys_context(‘app_ctx‘, ‘var1‘) var1,
sys_context(‘app_ctx‘, ‘var2‘) var2
FROM DUAL;

exec my_pkg.set_session_id(1234);

SELECT sys_context(‘app_ctx‘, ‘var1‘) var1,
sys_context(‘app_ctx‘, ‘var2‘) var2
FROM DUAL;

-- Now we‘ll show that this context is tied to our user (we specified
-- USER above, if we used null anyone can join this session).

grant execute on my_pkg to scott;

conn scott/tiger

exec uwclass.my_pkg.set_session_id(1234);

SELECT sys_context(‘app_ctx‘, ‘var1‘) var1,
sys_context(‘app_ctx‘, ‘var2‘) var2
FROM DUAL;

-- Return to the set context again and clear it

conn uwclass/uwclass

exec my_pkg.set_session_id(1234);

SELECT sys_context(‘app_ctx‘, ‘var1‘) var1,
sys_context(‘app_ctx‘, ‘var2‘) var2
FROM DUAL;

exec my_pkg.close_session(1234);

SELECT sys_context(‘app_ctx‘, ‘var1‘) var1,
sys_context(‘app_ctx‘, ‘var2‘) var2
FROM DUAL;