My Oracle Support Banner

Debug, Error And Warning Messages Are Being Masked With ^@ Special Character In Log File (Doc ID 760441.1)

Last updated on MARCH 04, 2019

Applies to:

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


In pinlog file, error, warning and debug messages are being masked with ^@ as ^@D, ^@E, ^@W

For example,

^@D Sat Aug 01 02:17:12 2009 <HOSTNAME> cm:28011 fm_bill_item_refund.c:146 1:<HOSTNAME>:<PROGRAM_NAME>:0:AWT-EventQueue-0:925:123 3277624:0
op_bill_item_refund input flist
# number of field entries allocated 4, used 3
0 PIN_FLD_POID POID [0] /account 1152874 25
0 PIN_FLD_BILLINFO_OBJ POID [0] /billinfo 1153258 6
0 PIN_FLD_PROGRAM_NAME STR [0] "Customer Center"

Steps To Reproduce:
1. Clean the cm.pinlog.
2. Run testnap to call an opcode
3. Do a grep as shown below on the cm.pinlog file.

9mui> grep "^D" cm.pinlog | wc -l
11mui> grep "D Fri" cm.pinlog |wc -l

On HP-UX machine, doing a cat -v cm.pinlog, one can notice a special character ^@ symbol in the beginning of error (E), debug (D) and warning (W) messages. However, VI editor does not shows this symbol.
It looks like this is a problem with "PIN_ERR_LOG_MSG" provided by Portal 7.0.

Expected Result:
In the cm.pinlog there are 102 lines starting with the "D".

Actual Result:
Only 18 instances are shown with the "D".




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

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