Issue Information
| Issue Number | 701359a |
| Issue | When a NOT NULL constraint is set on a LONG column, passing a value through a Deferred parameter always results in a NOT NULL constraint violation error even when the actual value is not null. When performing an INSERT or UPDATE using a Deferred parameter with a LOB column, the NOT NULL constraint is not checked. When data with a length of 0 is passed as a bind parameter to a LOB column, an empty LOB is inserted or updated in the Deferred state, whereas null is inserted or updated when deferred evaluation is not used. Abnormal and inconsistent results occur when binding data to LOB or LONG columns using deferred evaluation parameters. |
| Cause | When a value is passed using the deferred method, the value is initially set to null and then directly inserted. Because the passed value is not properly reflected during this process, it is always recognized as null when the NOT NULL constraint is checked. In addition, when a value is provided using the deferred method, the system does not properly handle the fact that the data is not null. |
| Solutions | When inserting or updating LOB or LONG data using a Deferred parameter, the NOT NULL constraint is now validated during the locator insert/update stage. When a Deferred parameter is applied during data updates, processing now treats the NOT NULL validation as completed. When inserting or updating LOB or LONG data using a Deferred parameter, data with a length of 0 is now processed as a NULL value instead of an empty LOB. When binding data to LOB or LONG data using a Deferred parameter, the system now returns normal and consistent results. |
| Occurrence Date | 26.09.07. |
| Required Patch Version | 6FS07PS 7FS02PS |
Patch Information
| Patch Name | FS02PS_701359a |
| Major Version | 7 |
| Minor Version | FS02PS |
| Version Title | Fixed an Error in Handling NOT NULL Constraints When Using Deferred Parameters with LOB or LONG Columns |
| Available for Deployment | 26.10.06. |
| Compatibility | • TAC rolling patch: Available • TSC rolling patch: Available • Backup data compatibility: Available • Protocol compatibility: Available • Data format compatibility: Available |
| AP Impact | • Plan change: No • Result value change: Yes • SQL syntax change: No • System object change: No • Existing functionality change: No |
| Parameter | - |
| Workaround | - |