#50 Invalid column name 'QueryOptimizationTime' and 'NumAQTs'

[Simon Thackeray]

Hello,

I am running asemon logger V3.2.1 in order to monitor a few ASE database servers and until now all worked perfectly well. Great tool!

I recently upgraded to SP03 PL03/EBF 27745.

Since then I get below error in the log:

2024/12/23 14:32:00.895 BILKDB02D_StmtCache - Error in loop. Error=207 state=ZZZZZ SQL message=Invalid column name 'NumAQTs'.

2024/12/23 14:32:03.585 BILKDB02D_MonSQL - Error in loop. Error=207 state=ZZZZZ SQL message=Invalid column name 'QueryOptimizationTime'.

Is there a way I can easily bypass these columns?

The same configuration runs smootlhy against a 16.0 SP02 PL05 HF1/EBF 26759 system.

I would appreciate a little help regarding this matter.

Many thanks

Simon

[Jean-Paul Martin]

Hi Simon
what do you have in your config file ?

For StmtCache : you should have StmtCcahe_switch.xml whil will redirect to StmtCache_V16SP03.xml

For MonSQL : MonSQL_switch.xml redirects to MonSQL_V16SP03.xml

You should take a look at sampleConfig.xml who shows which collector should be used

Best regards

JPM

[Simon Thackeray]

Hi JP,

Thanks for the swift answer.

I use both these ASE version:

ASE Version = 16.0.03.03
ASE Version = 16.0.02.05

I confirm that I have the "switch" xml activated.

I have attached my config file for reference.

Could it be I need to be more granular on the versionSwitch instead of using the MAX?

[Jean-Paul Martin]

May be it's because you didn't run the "installmaster" script when you migrated to SP03
(you should run "updatease" after patching ASE)
You can check by executing "sp_version" on this SP03 server
You should get "installmaster 16.0 SP03 PL03 ..."

Regards
JPM

[Simon Thackeray]

Excellent point JP. You actually nailed it. That's the problem. I will check with the techies...

Joyeux Noël et Bonne année 2025!

[Jean-Paul Martin]

Good, thank you et bonnes fêtes