Procedure sa_get_request_times is ignoring hostvars

[ThiagoReis]

After calling the sa_get_request_times procedure, the satmp_request_hostvar table has only the first hostvar of each statement.

Looking at the original request log file, all the host variables are there. It looks like sa_get_request_times is only considering the first one.

I reproduced this error in two different database versions: SA_1600_2127 and SA_1700_2053.

Am I doing something wrong or should I just open an incident for the SA_17 version?

Commands used to activate the request logging:

call sa_server_option( 'RequestLogging', 'SQL+hostvars');
call sa_server_option( 'RequestLogFile', '..\\\\requests.sql');
call sa_server_option( 'RequestLogMaxSize', 50000000);

Command used to analyze the generated request log file:

call sa_get_request_times('..\\\\requests.sql.old');

Thanks in advance.

[chris_keating]

Have you tried with a more current release since both versions are > 4 years old?

[ThiagoReis]

Not yet. I am trying to download the build 6175, but I got a message that the file is locked by SAP Export Department for processing. So I am waiting for this. Once I get this build, I will do the tests and report here.

[ThiagoReis]

Hi Chris. I tested the SQL Anywhere 17 build 6175 and noticed the same behavior. The procedure still considers only the first hostvar value.

Should I open an incident for this version?

[ThiagoReis]

I tested the latest build of SQL Anywhere 17 (v.7672) and noticed that the problem persists. Only the first hostvar value is considered.

[chris_keating · Accepted solution]

Sorry, I do not recall if I actually tried this at the time (likely because of not having a request log available with hostvars). I have confirmed your findings and have a fix in progress.

[ThiagoReis · Accepted solution]

Thank you, I really appreciate it.

[ThiagoReis · Accepted solution]

Hi Chris, can you please confirm if SA17 Build 7821 has this fix?

The release notes doc for this build is broken: "SAP Note/KBA 3515522 is being created."

[ThiagoReis · Accepted solution]

Hi Chris. Still waiting for the fix. Should I open an incident at SAP Support Portal?