By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,237 Members | 1,224 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,237 IT Pros & Developers. It's quick & easy.

SQL3525N on import/export in stored procedure

P: n/a
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 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
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.