Posted: Sun Sep 09, 2007 8:31 pm Post subject: Unreadable Characters being returned in DB2 Connect Error
Knight
Joined: 15 May 2001 Posts: 540 Location: New Zealand
We are trying to get our broker talking to Content Manager on Linux,via a JavaCompute node. The Connect, which uses the CM client not ODBC, fails and returns the following, taken from a Service trace of the flow:
This presents a problem, as it prevents us from determining in why the Connect fails!
Has anyone seen similar unreadable characters in an error situation. The Java code executes correctly outside the broker, and also correctly from the broker when run under Windows. We have checked locale, classpath etc. and currently have raised a PMR. However I thought I would post here just in case anyone has experienced something similar.
The hex representation of the first part of the above is:
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum