Interesting find. It looks like it depends what format you export as. I just tried it in SQLN 7.1.0.3676 and if I export it as Table Inserts like your screen shot shows, I also get the empty_clob() field. If I export it as delimited text, I just get the word “(CLOB)”. Yet if I export as HTML, XML, Spool text, or Excel, I do get the CLOB contents. I would think this should at least be an export option for the table insert or delimited text exports (Include BLOB/CLOB content: Y/N).
Thanks for your report this issue. we have fixed this issue in v7.2 Beta, so v7.2 will full support export clob field, and we will sent out the beta soon.
Michael, to follow up on the original thread. I have the same issue as the original poster. While attempting to save results as Table INSERTs (not Excel), I get the EMPTY_CLOB for long character fields. Is there a setting that I could have accidentally flipped? I’m thinking maybe, because this was working OK last week. In TOAD, I helped a user with simiar issue fix the appropriate setting, but I can’t find where the setting is in SQL*Nav.
Thanks for your feedback, we have created a new story (SQLNAV-1800 :Get EMPTY_CLOB() when export data from CLOB field with Table INSERTs) for this problem.
In addition, we also offer some workarounds for you:
you can export data from CLOB field with Spool Text:
2.upgrade SQLNav to version 7.2, you can use "Export LOBs "(in the right-click menu) to export COLB field data:
3.Or in accordance with the way Michael said to do.
Alan, thank you for confirming my issue with exporting CLOBS when using TABLE INSERT.
Just to clarify, when I said it had working previously, that was in fact for a different type, LONG CHARACTERS. Looking forward to the patch for CLOBs in future releases. Thanks for your prompt reply.