Historical database tables created during installation
Database creation
differs depending on the database vendor
you are using. If you are using DB2®, two
databases are created by default when the dynamic workload broker server
is installed. If you are using Oracle, two schemas are created in
the same database. The names for both the databases and the schemas
are as follows:
- IBMCDB (DB2 )/ CDB (Oracle)
- Contains Agent manager data. The name is fixed and cannot be changed.
- TDWB
- Contains dynamic workload broker data. You can change the name.
The
following three historical tables are created during
the installation process in the TDWB database. These tables
are used to contain historical data about job instances.
- JOA_JOB_ARCHIVES
- Contains archived job instances. See Table 1.
- JRA_JOB_RESOURCE_ARCHIVES
- Contains resource information related to a job. See Table 2.
- MEA_METRIC_ARCHIVES
- Contains metrics collected for a job. See Table 3.
Column Name | DB2 Data Type | Oracle Data Type | Length | Nullable | Description |
---|---|---|---|---|---|
JOA_ID | CHAR () FOR BIT DATA | RAW | 16 | No | Contains the unique identifier of the job |
JOA_START_TIME | TIMESTAMP | TIMESTAMP | 26 | Yes | The start time of the job, if started |
JOA_END_TIME | TIMESTAMP | TIMESTAMP | 26 | Yes | The end time of the job, if ended |
JOA_JSDL_INSTANCE | CLOB | CLOB | No | The JSDL (job definition), stored in binary format | |
JOA_SUBMIT_USERNAME | VARCHAR | VARCHAR2 | 120 | No | The submitter |
JOA_TIMEZONE | VARCHAR | VARCHAR2 | 40 | Yes | Not used in this release |
JOA_STATE | DECIMAL | NUMBER | 2 | No | The job state code |
JOA_RETURN_CODE | DECIMAL | NUMBER | 10 | No | The job return code |
JOA_SUBMIT_TIME | TIMESTAMP | TIMESTAMP | 26 | No | The submit time |
JOA_NAME | VARCHAR | VARCHAR2 | 250 | No | The job definition name |
JOA_NAMESPACE | VARCHAR | VARCHAR2 | 250 | Yes | The job definition namespace |
JOA_ALIAS_NAME | VARCHAR | VARCHAR2 | 250 | Yes | The job definition alias |
JOA_SUBMITTER_TYPE | VARCHAR | VARCHAR2 | 80 | Yes | The submitter type (for example, TDWB CLI, TDWB UI) |
JOA_UPDATE_TIME | TIMESTAMP | TIMESTAMP | 26 | No | The last update timestamp of actual row |
Column Name | DB2 Data Type | Oracle Data type | Length | Nullable | Description |
---|---|---|---|---|---|
JOA_ID | CHAR () FOR BIT DATA | RAW | 16 | No | Contains the unique identifier of the job |
JRA_RESOURCE_NAME | VARCHAR | VARCHAR2 | 250 | No | The resource internal name |
JRA_RESOURCE_TYPE | VARCHAR | VARCHAR2 | 30 | No | The resource type (for example, ComputerSystem, FileSystem, ...) |
JRA_RESOURCE_GROUP | DECIMAL | NUMBER | 5 | No | The group code (grouping an allocation for actual job) |
JRA_DISPLAY_NAME | VARCHAR | VARCHAR2 | 250 | Yes | The displayed name |
JRA_IS_TARGET | DECIMAL | NUMBER | 1 | No | A flag indicating the root resource (typically the ComputerSystem) |
Column Name | DB2 Data Type | Oracle Data Type | Length | Nullable | Description |
---|---|---|---|---|---|
JOA_ID | CHAR () FOR BIT DATA | RAW | 16 | No | Contains the unique identifier of the job |
MEA_NAME | VARCHAR | VARCHAR2 | 80 | No | The metric name (for example, JOB_MEMORY_USAGE, JOB_CPU_USAGE, ...) |
MEA_TYPE | CHAR | CHARACTER | 10 | No | The metric datatype (for example, DECIMAL, ...) |
MEA_VALUE | VARCHAR | VARCHAR2 | 250 | No | The metric value |
Table 4 lists the status of jobs as stored in the historical tables in association with the job status available in the Dynamic Workload Console and in the command line, mapping them with the related options in the movehistorydata command.
movehistorydata option | Job status in tables | Dynamic Workload Console status | Command line status |
---|---|---|---|
SuccessfulJobsMaxAge | 43 | Completed successfully | SUCCEEDED_EXECUTION |
44 | Canceled | CANCELED | |
UnsuccessfulJobMaxAge | 41 | Resource allocation failed | RESOURCE_ ALLOCATION_FAILED |
42 | Run failed | FAILED_EXECUTION | |
45 | Unknown | UNKNOWN | |
46 | Unable to start | NOT_EXECUTED |