469,362 Members | 2,441 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,362 developers. It's quick & easy.

SQL3525N on import/export in stored procedure

As importing/exporting data ist not directly supported for JDBC/SQLJ,
we call a c-stored procedure which uses the administrative API for
exporting/importing. Now with the newest DB2 8.1 Fixpack (#13), we get
an error "SQL3525N CODEPAGE option is incompatible with the LOBSINFILE
option during IMPORT".

Using the workaround described under
http://www-1.ibm.com/support/docview...id=swg21220689 works, if you
call the c-stored procedure directly from the command prompt, but not
if its called from the Java stored procedure. So the codepaget set in
db2set seems not to affect the java stored procedure. Is there a way to
change the codepage too for java stored procedure or do we need to
start using inline-lobs?


Aug 28 '06 #1
0 2647

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Doug R | last post: by
2 posts views Thread by Ted Theodoropoulos | last post: by
5 posts views Thread by Mark A | last post: by
2 posts views Thread by WP | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.