Author Topic: corrupted trace file - 10.1.0.4  (Read 1731 times)

jsquizz

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 573
    • View Profile
corrupted trace file - 10.1.0.4
« 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.
#CMOD #DB2 #AFP2PDF #TSM #AIX #RHEL #AWS #AZURE #GCP #EVERYTHING

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2228
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: corrupted trace file - 10.1.0.4
« Reply #1 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.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

jsquizz

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 573
    • View Profile
Re: corrupted trace file - 10.1.0.4
« Reply #2 on: August 26, 2019, 08:02:40 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
« Last Edit: August 26, 2019, 09:30:25 AM by jsquizz »
#CMOD #DB2 #AFP2PDF #TSM #AIX #RHEL #AWS #AZURE #GCP #EVERYTHING

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2228
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: corrupted trace file - 10.1.0.4
« Reply #3 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.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR