M204.2453: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
m (add <var>'s) |
||
| Line 1: | Line 1: | ||
{{Template:M204.2453 skeleton}} | {{Template:M204.2453 skeleton}} | ||
<P>An SQL column is detected, such that it is referenced in the request and its SQL datatype is not consistent with the Model 204 datatype of the underlying Model 204 field. If such a column is used in a retrieval condition | <P> | ||
of an SQL request, the whole file resource is locked at evaluation time and Table B is searched instead of index. If the file is big, substantial performance degradation results.</P> | An SQL column is detected, such that it is referenced in the request and its SQL datatype is not consistent with the Model 204 datatype of the underlying Model 204 field. If such a column is used in a retrieval condition of an SQL request, the whole file resource is locked at evaluation time and Table B is searched instead of index. If the file is big, substantial performance degradation results.</P> | ||
<P>This message might be produced during SQL query compilation or evaluation in the following cases:</P> | <P> | ||
<ul><LI>Field is | This message might be produced during SQL query compilation or evaluation in the following cases:</P> | ||
<ul> | |||
<LI>Field is <var>ORDERED CHARACTER</var>, but SQL column type is not <var>CHARACTER</var>.</LI> | |||
<LI>Field is <var>ORDERED NUMERIC</var>, but SQL column type is <var>CHARACTER</var>.</LI> | |||
<LI>Field is <var>KEY STRING</var>, but SQL column type is not <var>CHARACTER</var>.</LI> | |||
<LI>Field is <var>KEY</var> or <var>HASH</var>, its datatype is <var>BINARY</var> or <var>FLOAT</var>, but SQL column type is <var>CHARACTER</var>.</LI> | |||
<LI>Field is <var>KEY</var> or <var>HASH</var>, its datatype is <var>STRING</var>, but SQL column type is not <var>CHARACTER</var>.</LI> | |||
</ul> | |||
<p> | |||
<b>Response:</b> Notify the system manager.</p> | |||
<p> | |||
<b>System manager response:</b> If possible, alter or recreate the table to change the column datatype, so that there are no datatype mismatches. | |||
</p> | |||
{{Template:M204.2453 footer}} | {{Template:M204.2453 footer}} | ||
<!-- skeleton as it was in pdf/SQL REQUEST MAY TRIGGER TABLE B SEARCH IN FILE filenameAND THE WHOLE FILE MAY BE LOCKED/--> | <!-- skeleton as it was in pdf/SQL REQUEST MAY TRIGGER TABLE B SEARCH IN FILE filenameAND THE WHOLE FILE MAY BE LOCKED/--> | ||
Latest revision as of 19:51, 19 March 2018
M204.2453 SQL request may trigger Table B search in file token and the whole file may be locked
An SQL column is detected, such that it is referenced in the request and its SQL datatype is not consistent with the Model 204 datatype of the underlying Model 204 field. If such a column is used in a retrieval condition of an SQL request, the whole file resource is locked at evaluation time and Table B is searched instead of index. If the file is big, substantial performance degradation results.
This message might be produced during SQL query compilation or evaluation in the following cases:
- Field is ORDERED CHARACTER, but SQL column type is not CHARACTER.
- Field is ORDERED NUMERIC, but SQL column type is CHARACTER.
- Field is KEY STRING, but SQL column type is not CHARACTER.
- Field is KEY or HASH, its datatype is BINARY or FLOAT, but SQL column type is CHARACTER.
- Field is KEY or HASH, its datatype is STRING, but SQL column type is not CHARACTER.
Response: Notify the system manager.
System manager response: If possible, alter or recreate the table to change the column datatype, so that there are no datatype mismatches.
Message attributes:
| RETCODEO=0 | Sets online return code |
|---|---|
| RETCODEB=0 | Sets batch (single user) return code |
| CLASS=I | Information class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter |
| AUDITAD | Writes the message with line type AD to the audit trail |
| NOCOUNT | Does not increment the error count (ERCNT) parameter |