DM_VERTEX And Any Custom DM Programs Incorrectly Logging Debug Messages
Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.1 to 18.104.22.168.0 [Release 7.3.1]
Information in this document applies to any platform.
Checked for relevance on 24-Jan-2014.
The dm_vertex program is logging an "input flist" debug message in the pinlog in spite of the pin.conf file having no debugging turned on (qm or loglevel). Even trying to set loglevel ("-", "dm", "dm_vertex", "qm") and explicitly setting the qm_debug values to zeroes.
Comment out below mentioned entries in the dm_vertex/pin.conf:
The expected result is:
Debug messages as a rule (there are small exceptions coded otherwise) should show up only when DM is configured to log debug messages.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms