BigData Intelligence Exception domain
All of the exceptions and exception-related data. These are SQL exceptions sent from a database server and collected by inspection engines, as well as exceptions generated by Guardium itself. This topic describes the domain's entities and attributes.
Available to roles: all.
This domain is available in Guardium systems that have a defined datasource of type GBDI.
BigData Exception Entity
| Attribute | Description |
|---|---|
| Analyzed Client IP | Applies only to encrypted traffic; when set, client IP is set to zeroes. Analyzed Client IP has a map for CEF source. If the query used for the CEF does NOT contain the Client IP but contains the analyzed client IP, the analyzed client IP will be used for the source. If both included in the query, then Client IP takes precedence. |
| App User Name | Application user name. |
| Client Host Name | Client hostname |
| Database Error Text | A database error code followed by a short text description of the error. The error code is
taken from the Exception Description attribute of the Exception entity. Using the error code as a
key, the error text is obtained from an internal table on the Guardium appliance, which contains the
most common error messages (about 54,000 of them). Example: ORA-00942: table or view does not exist |
| Database Name | Database Name |
| Database Protocol | Database protocol for the exception. |
| DB User Name | The DB user that connected to the database, either local or remote. |
| Description | For a database exception, this is an error code from the database management system. For most common messages (about 54,000 of them), a longer text description is available in the Database Error Text attribute. That text comes from the internal Guardium database table of error messages, not from the exception itself. |
| Destination Address | Destination IP address. |
| Error Code | The database error code. |
| Exception Date | Date only from the timestamp. |
| Exception ID | Uniquely identifies the exception. |
| Exception Timestamp | Date and time when this Exception entity was logged. |
| Exception Type | Uniquely identifies the exception type. |
| Guardium Appliance | Host name of collector that reported this data. |
| Link to more information about the exception | Link that is sometimes available, depending on the exception source. |
| OS User | OS user account for the interaction |
| Server Host Name | Server Host Name |
| Server IP | Server IP address |
| Server Port | Server port number |
| Server Type | DB2, Oracle, Sybase, and so on. |
| Service Name | Service name for the interaction. In some cases (AIX® shared memory connections, for
example), the service name is an alias that is used until the actual service is connected. In those
cases, once the actual service is connected, a new session is started - so what the user experiences
as a single session will be logged as two sessions. For Teradata, Service name contains the session logical host ID value. |
| Session Id | Uniquely identifies the session |
| Source Address | Source IP address of the exception. |
| Source Program | Source program for the interaction |
| SQL string that caused the Exception | The SQL string that caused the exception. |
| User Name | Database user name. |
| UTC Offset | The difference in time between UTC time and time of collector that reported that data |