home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC11 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT09218 Status: Closed

TEXT OF RAISE EXCEPTION IN STORED PROCEDURE TRUNCATED AFTER 72 C HARACTERS
AND CONTAINING UNEXPECTED CHARACTERS IN THE TRACE FILE

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
When you are using an error text in a RAISE EXCEPTION statement 
within a stored procedure this text is truncated after 72 
characters when it is returned as error message to the client. 
 
If you have activated stored procedure tracing the debug file 
content will contain unexpected characters in the message text 
after the first 72 characters of the error message.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Making use of specific error -746 for stored procedures in   * 
* order to utilize user supplied error message specified in    * 
* the stored procedure.                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IBM Informix Server 12.10.xC6 or newer.            * 
****************************************************************
Local Fix:
Solution
Problem Fixed In IBM Informix Server 12.10.xC6 or newer.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.06.2015
30.12.2015
30.12.2015
Problem solved at the following versions (IBM BugInfos)
12.10.xC6
Problem solved according to the fixlist(s) of the following version(s)
12.10.xC6 FixList