|
Problem IT41463
|
Status: Closed |
QUERY ON COLUMNS SQL_HVAR_TYPE AND SQL_HVAR_DATA OF TABLE SYSSQLTRACE_HVAR SHOWS INVALID INFORMATION
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
After enable SQLTRACE with "SQLTRACE
level=high,ntraces=2000000,size=16,mode=global" and run a query
on syssqltrace_hvar table it shows invalid information in
columns sql_hvar_type and sql_hvar_data.
For example :
$
$ dbaccess sysmaster FROM syssqltrace_hvar
> WHERE sql_id IN ( SELECT sql_id FROM syssqltrace WHERE
sql_sid = 4);
> !
Database selected.
sql_id 2
sql_address 1192071248
sql_hvar_id 0
sql_hvar_flags 0
sql_hvar_typeid 0
sql_hvar_xtypeid 0
sql_hvar_ind 0
sql_hvar_type unknown
sql_hvar_data
sql_id 3
sql_address 1192071256
sql_hvar_id 0
sql_hvar_flags 0
sql_hvar_typeid 0
sql_hvar_xtypeid 0
sql_hvar_ind 0
sql_hvar_type unknown |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.xC9. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC9. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.xC9. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC9. *
**************************************************************** |
| Comment |
Fixed in Informix Server 14.10.xC9. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.07.2022
04.10.2022
04.10.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
