Identifying Process Name through Logs

The Log file contains records of events, activities, or errors generated by CAKM for Oracle TDE. These logs can help track usage, understand system performance, or troubleshoot issues.

It is difficult to track the database that performed specific actions through the Process ID (PID) in the CAKM for Oracle TDE client logs, as PIDs are temporary. To resolve this, the Process/Service name is added to the CAKM for Oracle TDE client logs against the respective PID. To analyze the working of a specific process, you can track the same through the Process/Service name in CAKM for Oracle TDE client logs.

Command (for both Windows and Linux)

To obtain the instance name, run the following command:

SELECT instance_name FROM v$instance;

** Output**

INSTANCE_NAME
----------------
ORCL

Windows

You can identify the Process/Service name of desired Process ID (PID) which is obtained using the API OpenSCManager present in the header file winsvc.h.

In the above image, Process/Service name is OracleServiceORCL, PID is 8600, and Log Level is DEBUG.

For more information, click here.

Linux

You can identify the Process/Service name of desired Process ID (PID) which is obtained using the API program_invocation_short_name provided by GNU C library (glibc).

Example 1

In the above image, Process/Service name is oracleorcl, PID is 903118, and Log Level is DEBUG.

Example 2

In the above image, Process/Service name is ora_gen0_orcl, PID is 903015, and Log Level is INFO.

For more information, click here.