To Get Current Container:
SQL> SELECT sys_context ('USERENV','CON_NAME') from dual;
SYS_CONTEXT('USERENV','CON_NAME')
------------------------------------------------------
CDB$ROOT
SQL> Select Name,Con_name,Con_ID from v$active_services;
SQL> Show CON_NAME;
Table 5-12 lists the parameters of namespace 
SQL> SELECT sys_context ('USERENV','CON_NAME') from dual;
SYS_CONTEXT('USERENV','CON_NAME')
------------------------------------------------------
CDB$ROOT
SQL> Select Name,Con_name,Con_ID from v$active_services;
SQL> Show CON_NAME;
SQL> SELECT pdb FROM dba_services;
 SQL> SELECT sys_context(‘userenv’,’con_name’) “MY_CONTAINER” FROM dual;
DBA_PDBS --> Gives list of PDBS (PDB$SEED,PDB1)
v$PDBS --> Gives list of PDB's along with open_mode,start time..
CDB_PDBS
DBA_PDB_HISTORY
| Parameter | Return Value | 
|---|---|
| ACTION | Identifies the position in the module (application name) and is set through the DBMS_APPLICATION_INFOpackage or OCI. | 
| AUDITED_CURSORID | Returns the cursor ID of the SQL that triggered the audit. This parameter is not valid in a fine-grained auditing environment. If you specify it in such an environment, then Oracle Database always returns NULL. | 
| AUTHENTICATED_IDENTITY | Returns the identity used in authentication. In the list that follows, the type of user is followed by the value returned: 
 | 
| AUTHENTICATION_DATA | Data being used to authenticate the login user. For X.503 certificate authenticated sessions, this field returns the context of the certificate in HEX2 format. Note: You can change the return value of the AUTHENTICATION_DATAattribute using thelengthparameter of the syntax. Values of up to 4000 are accepted. This is the only attribute ofUSERENVfor which Oracle Database implements such a change. | 
| AUTHENTICATION_METHOD | Returns the method of authentication. In the list that follows, the type of user is followed by the method returned: 
 IDENTIFICATION_TYPEto distinguish between external and enterprise users when the authentication method is Password, Kerberos, or SSL. | 
| BG_JOB_ID | Job ID of the current session if it was established by an Oracle Database background process. Null if the session was not established by a background process. | 
| CLIENT_IDENTIFIER | Returns an identifier that is set by the application through the DBMS_SESSION.SET_IDENTIFIERprocedure, the OCI attributeOCI_ATTR_CLIENT_IDENTIFIER, or Oracle Dynamic Monitoring Service (DMS). This attribute is used by various database components to identify lightweight application users who authenticate as the same database user. | 
| CLIENT_INFO | Returns up to 64 bytes of user session information that can be stored by an application using the DBMS_APPLICATION_INFOpackage. | 
| CURRENT_BIND | The bind variables for fine-grained auditing. You can specify this attribute only inside the event handler for the fine-grained auditing feature. | 
| CURRENT_EDITION_ID | The identifier of the current edition. | 
| CURRENT_EDITION_NAME | The name of the current edition. | 
| CURRENT_SCHEMA | The name of the currently active default schema. This value may change during the duration of a session through use of an ALTERSESSIONSETCURRENT_SCHEMAstatement. This may also change during the duration of a session to reflect the owner of any active definer's rights object. When used directly in the body of a view definition, this returns the default schema used when executing the cursor that is using the view; it does not respect views used in the cursor as being definer's rights.Note: Oracle recommends against issuing the SQL statement ALTERSESSIONSETCURRENT_SCHEMAfrom within all types of stored PL/SQL units except logon triggers. | 
| CURRENT_SCHEMAID | Identifier of the currently active default schema. | 
| CURRENT_SQLCURRENT_SQLn | CURRENT_SQLreturns the first 4K bytes of the current SQL that triggered the fine-grained auditing event. TheCURRENT_SQLnattributes return subsequent 4K-byte increments, wherencan be an integer from 1 to 7, inclusive.CURRENT_SQL1returns bytes 4K to 8K;CURRENT_SQL2returns bytes 8K to 12K, and so forth. You can specify these attributes only inside the event handler for the fine-grained auditing feature. | 
| CURRENT_SQL_LENGTH | The length of the current SQL statement that triggers fine-grained audit or row-level security (RLS) policy functions or event handlers. You can specify this attribute only inside the event handler for the fine-grained auditing feature. | 
| CURRENT_USER | The name of the database user whose privileges are currently active. This may change during the duration of a session to reflect the owner of any active definer's rights object. When no definer's rights object is active, CURRENT_USERreturns the same value asSESSION_USER. When used directly in the body of a view definition, this returns the user that is executing the cursor that is using the view; it does not respect views used in the cursor as being definer's rights. | 
| CURRENT_USERID | The identifier of the database user whose privileges are currently active. | 
| DATABASE_ROLE | The database role using the SYS_CONTEXTfunction with theUSERENVnamespace. The role is one of the following:PRIMARY,PHYSICALSTANDBY,LOGICALSTANDBY,SNAPSHOTSTANDBY. | 
| DB_DOMAIN | Domain of the database as specified in the DB_DOMAINinitialization parameter. | 
| DB_NAME | Name of the database as specified in the DB_NAMEinitialization parameter. | 
| DB_UNIQUE_NAME | Name of the database as specified in the DB_UNIQUE_NAMEinitialization parameter. | 
| DBLINK_INFO | Returns the source of a database link session. Specifically, it returns a string of the form: SOURCE_GLOBAL_NAME=dblink_src_global_name, DBLINK_NAME=dblink_name, SOURCE_AUDIT_SESSIONID=dblink_src_audit_sessionidwhere: 
 | 
| ENTRYID | The current audit entry number. The audit entryid sequence is shared between fine-grained audit records and regular audit records. You cannot use this attribute in distributed SQL statements. The correct auditing entry identifier can be seen only through an audit handler for standard or fine-grained audit. | 
| ENTERPRISE_IDENTITY | Returns the user's enterprise-wide identity: 
 
 | 
| FG_JOB_ID | Job ID of the current session if it was established by a client foreground process. Null if the session was not established by a foreground process. | 
| GLOBAL_CONTEXT_MEMORY | Returns the number being used in the System Global Area by the globally accessed context. | 
| GLOBAL_UID | Returns the global user ID from Oracle Internet Directory for Enterprise User Security (EUS) logins; returns null for all other logins. | 
| HOST | Name of the host machine from which the client has connected. | 
| IDENTIFICATION_TYPE | Returns the way the user's schema was created in the database. Specifically, it reflects the IDENTIFIEDclause in theCREATE/ALTERUSERsyntax. In the list that follows, the syntax used during schema creation is followed by the identification type returned:
 | 
| INSTANCE | The instance identification number of the current instance. | 
| INSTANCE_NAME | The name of the instance. | 
| IP_ADDRESS | IP address of the machine from which the client is connected. If the client and server are on the same machine and the connection uses IPv6 addressing, then ::1is returned. | 
| ISDBA | Returns TRUEif the user has been authenticated as having DBA privileges either through the operating system or through a password file. | 
| LANG | The abbreviated name for the language, a shorter form than the existing ' LANGUAGE' parameter. | 
| LANGUAGE | The language and territory currently used by your session, along with the database character set, in this form: language_territory.characterset | 
| MODULE | The application name (module) set through the DBMS_APPLICATION_INFOpackage or OCI. | 
| NETWORK_PROTOCOL | Network protocol being used for communication, as specified in the ' PROTOCOL=protocol' portion of the connect string. | 
| NLS_CALENDAR | The current calendar of the current session. | 
| NLS_CURRENCY | The currency of the current session. | 
| NLS_DATE_FORMAT | The date format for the session. | 
| NLS_DATE_LANGUAGE | The language used for expressing dates. | 
| NLS_SORT | BINARYor the linguistic sort basis. | 
| NLS_TERRITORY | The territory of the current session. | 
| OS_USER | Operating system user name of the client process that initiated the database session. | 
| POLICY_INVOKER | The invoker of row-level security (RLS) policy functions. | 
| PROXY_ENTERPRISE_IDENTITY | Returns the Oracle Internet Directory DN when the proxy user is an enterprise user. | 
| PROXY_USER | Name of the database user who opened the current session on behalf of SESSION_USER. | 
| PROXY_USERID | Identifier of the database user who opened the current session on behalf of SESSION_USER. | 
| SERVER_HOST | The host name of the machine on which the instance is running. | 
| SERVICE_NAME | The name of the service to which a given session is connected. | 
| SESSION_EDITION_ID | The identifier of the session edition. | 
| SESSION_EDITION_NAME | The name of the session edition. | 
| SESSION_USER | The name of the database user at logon. For enterprise users, returns the schema. For other users, returns the database user name. This value remains the same throughout the duration of the session. | 
| SESSION_USERID | The identifier of the database user at logon. | 
| SESSIONID | The auditing session identifier. You cannot use this attribute in distributed SQL statements. | 
| SID | The session ID. | 
| STATEMENTID | The auditing statement identifier. STATEMENTIDrepresents the number of SQL statements audited in a given session. You cannot use this attribute in distributed SQL statements. The correct auditing statement identifier can be seen only through an audit handler for standard or fine-grained audit. | 
| TERMINAL | The operating system identifier for the client of the current session. In distributed SQL statements, this attribute returns the identifier for your local session. In a distributed environment, this is supported only for remote SELECTstatements, not for remoteINSERT,UPDATE, orDELETEoperations. (The return length of this parameter may vary by operating system.) | 
USERENV that have been deprecated. Do not specify any of these parameters. Instead use the alternatives suggested in the Comments column.| Parameter | Comments | 
|---|---|
| AUTHENTICATION_TYPE | This parameter returned a value indicating how the user was authenticated. The same information is now available from the new AUTHENTICATION_METHODparameter combined withIDENTIFICATION_TYPE. | 
| EXTERNAL_NAME | This parameter returned the external name of the user. More complete information can now be obtained from the AUTHENTICATED_IDENTITYandENTERPRISE_IDENTITYparameter. | 
 
 
No comments:
Post a Comment