My Oracle Support Banner

Problem with tracing parameters when using Oracle Database Provider for DRDA (Doc ID 2551885.1)

Last updated on OCTOBER 15, 2019

Applies to:

Oracle Database Provider for DRDA - Version 12.2.0.1 and later
Information in this document applies to any platform.

Symptoms

 Trace file don't get generated when  PROTOPROC_TRACE="ALL/ALL/NOTIMESTAMP"

All other combination works:

"ALL/INFO/NOTIMESTAMP"
"ALL/WARN/NOTIMESTAMP"
"ALL/ERROR/NOTIMESTAMP"
"ALL/ADMIN/NOTIMESTAMP"
"ALL/DEBUG/NOTIMESTAMP"

The documentation states:

The facility names used with PROTOPROC_TRACE parameter are as follows:


• TASK – Task-specific operations
• NET – Network-specific operations
• SQL – SQL-specific operations
• OCI – OCI resource operations
• MEM – Memory resource operations
• ALL – All facilities mentioned already

The values of PROTOPROC_TRACE level are additive. For example, setting ERROR(4) includes WARN(2) and INFO(1) messages. The following values are expected:
• 0 or NONE – No trace is generated; this is the default.
• 1 or INFO – Minimal trace is generated.
• 2 or WARN – Warning information is generated.
• 4 or ERROR – Error information is generated.
• 8 or ADMIN – Administration information is generated.
• 255 or ALL – All details are generated.

As you can see, there are level called ALL with the number 255. Can you confirm us if this a documentation mistake and there not are level 255/ALL?

Reference:  https://docs.oracle.com/en/database/oracle/oracle-database/12.2/drdas/provider-drda-users-guide.pdf
Chapter 3 page 3-14 (page 36)

Changes

 No changes, followed the manual as stated.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.