DB2 - Problem description
Problem IC72775 | Status: Closed |
SQL0171N ERROR WHEN TRIMMING LARGE OBJECT TO 0 LENGTH USING DBMS_LOB.TRIM_CLOB or DBMS_LOB.TRIM_BLOB | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
PL/SQL procedure gets SQL0171N error when attempts to trim a large object by TRIM_CLOB or TRIM_BLOB to 0 length. Sample procedure CREATE OR REPLACE PROCEDURE TEST AS DECLARE req CLOB := EMPTY_CLOB' ; str VARCHAR (300); BEGIN DBMS_LOB.open_clob (req, 1); str := 'aaa,'; DBMS_LOB.writeappend_clob (req, LENGTH(str), str); DBMS_LOB.trim_clob (req, 1); DBMS_OUTPUT.put_line ('req: ' || VARCHAR(req)); DBMS_LOB.trim_clob (req, 0); DBMS_OUTPUT.put_line ('req: ' || VARCHAR(req)); DBMS_LOB.close_clob (req); END; The second trim results in SQL0171N. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * PL/SQL procedure gets SQL0171N error when attempts to trim a * * large object to 0 length by TRIM_CLOB or TRIM_BLOB routine. * **************************************************************** * RECOMMENDATION: * * Upgrade to version 9.7 FixPack4 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
This was first fixed by V97 FP4 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC72905 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.11.2010 09.05.2011 09.05.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7., 9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |