|
Problem IC87063
|
Status: Closed |
DB2 RETURNS -901 FOR TARGET TYPE IS NOT TYPED WHEN COMPILING MERGE STATEMENT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
DB2 may throw -901 error message "target type is not typed"
while compiling a MERGE statement whose source table is a single
row value box involving untyped parameter marker.
This creates FODC directory for APPerror and the call stack
looks
sqlnn_cmpl
sqlnp_main
sqlnp_parser
sqlnp_smactn
sqlnq_sem_merge
sqlnq_udi
sqlnq_iu_convSourcePid
sqlnq_conv_source_pid_w_ta[
sqlnq_pid::fix_parmm_for_a
sqlnq_pid::fix_untyped
This happens when MERGE statement has UPDATE or INSERT action,
and target table doesn't include the target column name
specified by UPDATE or INSERT. In other word, the MERGE
statement has syntax error and this APAR will address this issue
and throw the correct error message to the users. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users running merge statement. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to fix the issue. or use check the column *
* name and correct the syntax to avoid the issue. *
**************************************************************** |
| Local Fix: |
Correct target column name. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
APAR will first fixed in V9.7 fixpack 8. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC89708
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2012
01.04.2013
01.04.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.8
|
 |
