User Defined Collection (UDC) Wizard - Dimension
Use this step to define the dimensions of interest for which data is to be collected. For this specific UDC, limit the dimensions to only those relevant for the purpose of this collection.
Limitation of requested dimensions (and confining the collection periods) to only those of interest is the principal means to minimize the size of the storage files required by the UDC.
Available Oracle Dimensions:
SQL Statement - The executed SQL command.
Program - Name of the program connecting to Oracle and executing the SQL statements.
DB User - Oracle user used by the program to connect to the Oracle instance.
OS User - Operating system user running the client program.
Client Machine - The machine on which the client executable (connected to Oracle) is running.
Command Types - Executed SQL command type (for example INSERT, SELECT, and so on).
Module - Optional value in the V$SESSION.MODULE column during SQL execution.
Action - Optional value in the V$SESSION.ACTION column during SQL execution.
Client Info - Optional value in the V$SESSION.CLIENT_INFO column during SQL execution.
Session [SID, Serial]: DB RunID - Identifying the executing session.
Note:
The identifying session format is as follows: [SID, Serial]: DB RunID.
The SID and Serial combination identifies the session. Historically speaking
this combination is not unique because the combination can reappear when
a database has been restarted. The DB RunID uniquely identifies periods
that occur between a database start and shutdown, therefore making this
combination of SID, Serial and DB RunID a historical unique identifier
for the session.
The dimension list will be automatically expanded in accordance with any site ERP configurations. For more information, see ERP Extensions.
Caution: Once the UDC has been created, the dimension list cannot be modified.