Dm_fusa Logs Shows Debug Messages Even Though The Pin.Conf Is Set Against It (Doc ID 1098023.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.1.0.0 and later   [Release: 7.3.1 and later ]
Information in this document applies to any platform.

Symptoms

The dm_fusa logs show debug messages even though the pin.conf is set against it.
The debug message that shows up in the logs is as follows:

dm_fusa_one_send_and_recv: After Select..n value: 1
D Fri Sep 11 16:19:51 2009 xxxxx.com dm_fusa:30718 dm_fusa_socket.c(1.38):670 1:<machine>:<program>:0:0:0:0:0
dm_fusa_one_send_and_recv: After Select..n value: 1
D Fri Sep 11 16:19:55 2009 xxxxx.com dm_fusa:30718 dm_fusa_socket.c(1.38):670 1:<machine>:<program>:0:0:0:0:0

Note: They are the ONLY debug messages seeing in the entire logs; repeated regularly.

The pin.conf setting for debug is as follows:

# For the main debugging entry:
#
# 1 = Print detailed error information.
# 2 = Print main loop tracing.
# 4 = Print transaction tracing.
#
# For the front-end and back-end debugging entries:
#
# 1 = Print information on new connections.
# 2 = Print input information.
# 4 = Print operation done information.
# 8 = Print output information.
#========================================================================
#- dm_fusa qm_debug 0x07 # example: print all debug info
#- dm_fusa qm_debug_front 0x0F # example: print all debug info, front end
#- dm_fusa qm_debug_back 0x0F # example: print all debug info, back end


-- Steps To Reproduce:
Regular dm_fusa operation

The users need to clear logs regularly as a workaround. This is hazardous, since the users are unable to find out any genuine errors since all logs are cleared.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms