Each transient database file is named using the following convention.
tdb_<host-name>_<pid>_<node-number><designator>.tmp
In this format:
The <pid> value is the operating system process identifier and the <designator> value is one of the following.
[kbp_nnnnnn], for transient files associated with a kernel background process
[process‑oid], for transient files associated with a user process
The <node-number> value is zero (0) in normal circumstances.
You can identify the application process to which a transient database (TDB) file belongs by locating the process identifier in the jommsg.log; for example:
2014/02/22 14:23:26.897 000b8-0af4 Jom: Local process sign-on:oid=[187.2], process=0x58f7fe8, no=2, id=2804, type=1 (non-prodn),scm=JadeSchema, app=Jade, 2016.0.0
In this log entry example, [187.2] is the oid for the process object.
The transient database files reside in the directory specified in the TransientDbPath parameter in the [
The JADE Monitor displays information about transient files. You can also retrieve the information about the transient database file of a process by using the
Method | Returns… |
---|---|
|
A string containing a detailed analysis of the transient database file, including counts of objects by class number plus other useful information |
|
The physical size of the transient database file in use by the executing process |
|
The name of the transient database file in use by the executing process |
Alternatively, you can use the
Method | Requests a process to send notifications containing… |
---|---|
|
A detailed analysis of the contents of the transient database file |
|
The oid of the process, and the name and length of the transient database file |