OnDemand User Group

Support Forums => MP Server => Topic started by: jsquizz on August 19, 2019, 05:42:24 PM

Title: corrupted trace file - 10.1.0.4
Post by: jsquizz on August 19, 2019, 05:42:24 PM

I'm running on - CMOD 10.1.0.4, RHEL 7.4, DB2 11, ICOS..

Has anyone ever seen this in 10.1 (or even an older version...)

I did a system trace (ALL=15) and I'm trying to format the trace file so I can take a look at it..

[jeff@cmodtech tmp]$ arstfmt -i 08092019_cmodtech.trace.log -o trxout
fatal error 'invalid character 0x10' at line: 3999​

This is happening on 3 otherwise fully functioning systems with the same specs. Ive tried permissions, different file systems, etc. No luck.

Title: Re: corrupted trace file - 10.1.0.4
Post by: Justin Derrick on August 26, 2019, 05:39:28 AM

You may need to use the -c option to change the codepage.

Alternatively, you may have found a bug in the debugging code...  if that's true, I think you deserve a prize.  :D

-JD.

Title: Re: corrupted trace file - 10.1.0.4
Post by: jsquizz on August 26, 2019, 08:02:40 AM

Quote from: Justin Derrick on August 26, 2019, 05:39:28 AM

You may need to use the -c option to change the codepage.

Alternatively, you may have found a bug in the debugging code...  if that's true, I think you deserve a prize.  :D

-JD.

I'll try -c. But, I've opened a case and IBM said they can't duplicate the issue, lol.

Update -

[cmodtech@techbox~]$ arstfmt -i 0811092019_cmodtech.trace.log -o trace.codepage -c 1208

This works, no error, and I can read the trace file. strange. will follow up with IBM.

thanks jd

Title: Re: corrupted trace file - 10.1.0.4
Post by: Justin Derrick on August 26, 2019, 11:59:53 AM

Check your environment variables for the LANG parameter.  It might be set to a codepage/region that's different from your CMOD database / environment.

-JD.