SQL Developer Export Limitation of CLOB columns

Hello Everyone,
Would anyone happen to know if there is a column size limitation when exporting data (excel, text, etc) from the results query results pane? There appears to be a 4000 byte limitation. Specifically, I am attempting to export sql results that contain clobs which are storing XML messages.
Is this a known limitation and if so, is there any expectation of this being enhanced?
I am using the following:
Windows XP SP3
SQL Developer 2.1.0.63 (also happens on the 1.5 branch)
Oracle Server 10.2.0.4
Oracle Client 10.2.0.1
Thanks,
Ronnie

Yes, that's correct.
If you want this enhanced, add a request at the SQL Developer Exchange, so other users can vote and add weight for possible future implementation.
Regards,
K.

Similar Messages

Limitation for CLOB columns? - ORA-01704: string literal too long

Hello!
I'm trying to update a CLOB column with more than 35000 characteres, but I get "ORA-01704: string literal too long".
The code:
declare
l_clob clob;
begin
update test set test = empty_clob()
WHERE ID = 1
returning test into l_clob;
dbms_lob.write( l_clob, length('A...here 35000xA...A'), 1,'A...here 35000xA...A');
end;
Is there any limitation for CLOB columns?
Thanks for help.
Daniel

user605489 wrote:
32768 characteres :)Actually it's 1 character less than 32K...
*32767*
SQL> declare
2 v_vc varchar2(32768);
3 begin
4 null;
5 end;
6 /
v_vc varchar2(32768);
ERROR at line 2:
ORA-06550: line 2, column 17:
PLS-00215: String length constraints must be in range (1 .. 32767)
SQL>I guess it comes from a legacy thing where signed words (2 bytes) are/were used to represent a value. As the most significant bit of the word is used to represent the sign of the number the range goes from -32768 to 32767.

Exporting Table with CLOB Columns

Hello All,
I am trying to export table with clob columns with no luck. It errors saying EXP-00011TABLE do not exist.
I can query the table and the owner is same as what i am exporting it from.
Please let me know.

An 8.0.6 client definitely changes things. Other posters have already posted links to information on what versions of exp and imp can be used to move data between versions.
I will just add that if you were using a client to do the export then if the client version is less than the target database version you can upgrade the client or better yet if possilbe use the target database export utility to perform the export.
I will not criticize the existance of an 8.0.6 system as we had a parent company dump a brand new 8.0.3 application on us less than two years ago. We have since been allowed to update the database and pro*c modules to 9.2.0.6.
If the target database is really 8.0.3 then I suggest you consider using dbms_metadata to generate the DDL, if needed, and SQLPlus to extact the data into delimited files that you can then reload via sqlldr. This would allow you to move the data with some potential adjustments for any 10g only features in the code.
HTH -- Mark D Powell --

SQL Developer Export Issue

I could export the query results to XLS by clicking the right mouse button from the results and the export window pops up with the flile name and works fine. However when I run certain queries and tries to export results by clicking the right mouse button and choosing XLS the export windows does not pop up and I am unable to export the data. The query results has about 15 columns displayed and I am using Ver 1.5.5. Any help appreciated.

Hi,
The 1.5.5 version is rather old. Best to upgrade to the latest 3.1 production version. If the same problem still occurs, provide specifics about the query that fails on export to xls.
Regards,
Gary
SQL Developer Team
Edited by: Gary Graham on Feb 24, 2012 8:54 AM
I see this is a duplicate thread. A while back we were getting lots of system generated duplicates. I hope that is not starting to happen again!

SQL Developer Data Modeler "Reports" Duplicate Columns in Index- Bug

I am using SQL Data Modeler of SQL Developer - 3.2.20.09
Problem Description:
In the "Indexes" section of report generated for a table, column appear twice.
Steps to Reproduce:
1. Create an Entity in Modeler: COMPANY, Add attributes COMP_ID and COMP_DESC to it, mark COMP_ID as PK
2. Engineer it to Relational Model
3. Go to 'File->Data Modeler->Reports'
4. Select 'Available reports' = 'Table' and press 'Generate Report'
5. View the report.
Indexes shown for the table contains duplicate columns for COMP_ID
Regards,

Hi
I've just tested with SQL Developer 3.2.20.09 and built in Data Modeler 3.1.4.710 with Data Modeler reports 11.2.0.09.87
There is no duplicate columns for COMP_ID in the report.
What are your versions? You can check them from Tools->Preferences->Extensions

SQL LOADER: how to load CLOB column using stored function

Hi,
I am a newbie of sql loader. Everything seems to be fine until I hit a
road block - the CLOB column type. I want to load data into the clob
column using a stored function. I need to do some manipulation on the
data before it gets saved to that column. But I got this error when I
run the sql loader.
SQL*Loader-309: No SQL string allowed as part of "DATA" field
specification
DATA is my CLOB type column.
here is the content of the control file:
LOAD DATA
INFILE 'test.csv'
BADFILE 'test.bad'
DISCARDFILE 'test.dsc'
REPLACE
INTO TABLE test_table
FIELDS TERMINATED BY ','
OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
codeid          BOUNDFILLER,
reason          BOUNDFILLER,
Checkstamp     "to_date(:CHECKSTAMP, 'mm/dd/yyyy')",
"DATA"          "GetContent(:codeid, :reason)"
All references are suggesting to use a file to load data on
CLOB column but I want to use a function in which it generates
the content to be saved into the column.
Any help is greatly appreciated.
Thanks,
Baldwin
MISICompany

*** Duplicate Post ... Please Ignore ***

SQL Developer export forgot to check to include semicolons in DDL

Hi,
I used the SQL Developers Export-function (select tables and right click on them, then select export) to backup tables.
However, I forgot to set the 'Abschlusszeichen' (sorry for the german). That apparently means my create table statements are not finished by an ';', and they sinmply don't execute using the @script.sql method, or the sql developers import-function.
One sql-file is 2 GB in size, so I currently have no idea how to edit it and add the semicolons manually. Is there any hope to rescue the data?
I'm running sql developer 3.2.20.09, oracle Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production as well as Windows 8.1
For clarification, this is how the create table part looks:
-- Datei erstellt -Montag-September-30-2013
-- DDL for Table ZZ_BEN_0
CREATE TABLE "PIERUSCHM"."ZZ_BEN_0"
   (    "BENUTZER_ID" NVARCHAR2(30),
    "NAME" NVARCHAR2(30),
    "GUELT_VON" NVARCHAR2(30),
    "GUELT_BIS" NVARCHAR2(30),
    "IST_KORREKTUR" NVARCHAR2(30),
    "IST_HALBTAGSKRAFT" NVARCHAR2(30),
    "LADE_DAT" DATE
-- DDL for Table ZZ_BEN_1
CREATE TABLE "PIERUSCHM"."ZZ_BEN_1"
   (    "BENUTZER_ID" NVARCHAR2(30),
    "NAME" NVARCHAR2(30),
    "GUELT_VON" NVARCHAR2(30),
    "GUELT_BIS" NVARCHAR2(30),
    "IST_KORREKTUR" NVARCHAR2(30),
    "IST_HALBTAGSKRAFT" NVARCHAR2(30),
    "LADE_DAT" DATE
-- DDL for Table ZZ_BEN_10

Also i'd like to add that the file begins with table definitions but then contains the actual (and randomly generated) data as well.
You still need to have the file regenerated or you should expect to have problems with ANY method you use to try to automatically 'fix' the problem.
1. No experienced developer that I have worked with would EVER try to execute such a monolithic script because there is virtually NO chance that a 2 GB script will EVER run successfully without an error of some sort. Objects have to be created in the proper order when dependencies exist between them. For example, you can't create an index if the table hasn't been created yet. There can even be circular references that will prevent all objects from being VALID even if they are created.
2. There is virtually NO chance that ANY method you use will put terminators in EXACTLY the right place without causing a problem of some sort.
3. When there is an error the script may continue to try to executed and that usually causes further errors. It also creates garbage objects that are not valid but will keep the script from working correctly the next time since the objects will already exist.
You need to create a SET of scripts that are of manageable size so that you can control the process of executing them in the proper order.
If you don't take the time to do that, up front, you are going to wasted a tremendous amount of time when the script fails trying to cut and paste the pieces you need out of that 'master' script.
There are NO SHORTCUTS: take the time to do it right the first time.

SQL Developer Vs Aqua Studio Clob Size support

Hi,
I'm trying to run a query against 10g which returns huge volume of data.
In Aqua Studio the clob is returned, but in SQL Developer I didn't get any result. Is there any settings I've to do in SQL Developer to support larger volume.
Your help/pointer is appreciated.
Thanks
Senthil

When positioned in the result cell, there should be a button (...) to expand the contents. Does that work?
K.

SQL Developer Export hangs - version 3.2.20.09

Hi,
I installed SQL Developer Version 3.2.20.09 Build MAIN-09.87 and try to export a query into csv file,
it hangs after writing 100 rows, I don't see the file grows on OS, the progress-bar keeps saying 100 row
I also tried .xls format, the problem remains.
the downloaded file is sqldeveloper-3.2.20.09.87.zip (with JDK included)
Your help is appreciated.

I ran export for a different SQL, the .csv file was generated.
Not sure if the issue I encounter is data-related. I want to point out that some of the return data contains ASCII control characters:
This is the exact SQL for the hanged-export:
select c.email_addr,c.job_title, regexp_replace(c.job_title,'[[:cntrl:]]','#'),
t.job_title, regexp_replace(t.job_title,'[[:cntrl:]]','#')
from HZ_IMP_CONTACTS_T t, my_contact c
where t.batch_id=100002764150299
and t.REL_ORIG_SYSTEM_REFERENCE = c.pr_dept_ou_id || ':' || c.row_id
and rownum < 200
Hope you can reproduce this issue.
Thanks,
Wen

SQL Developer export files not visible

Hi All,
I've started using SQL Developer recently and I am completely new to this tool.
I've noticed a weird problem. All the export files and the folders I create from SQL Developer is not visible from the normal windows. Say I've executed a query and I need to export the output to a file. I right-click on the data grid; select Export Data -> xls/csv (anything) . I get a pop to mention the Location of the file. I click on Browse ; then select the location and then click on apply. I expect the file to be created. But when I go to that folder; I do not find any files.
To add on to my suprise; If i click on open a file and navigate to the above mentioned path; the pop-up shows that the file is present in that folder. But it is not visible from Windows. This is of no use as I cannot use those files.
BTW; version is 2.1.1.64
Note: I've also enabled the option of viewing all hidden files and folders in Windows.
Regards,
Arun

Hi Arun,
If you are using Windows Vista, Windows 7, or higher, and writing to a directory (like C:\, C:\Windows\, C:\Program Files\) that Microsoft wishes to protect from malware or just simple clutter , then you are running afoul of a redirect feature in the OS that puts the unwanted file in a VirtualStore folder for your user name, specifically:
C:\Users\<yourusername>\AppData\Local\VirtualStore\<full path where you think the file got stored>See the following for details:
http://answers.microsoft.com/en-us/windows/forum/windows_7-files/folder-redirect-in-windows-7/95218744-37e6-40cd-b890-2e647351df16
I just ran across this myself for the case of C:\ and perhaps this applies to your situation also.
Regards,
Gary

SQL Developer problem. Rows without columns on data tab

Hello,
I have a strange behavior in Oracle SQL Developer Version 2.1.0.63. When I'm trying to open the "Data tab" for some tables, SQL Developer shows data rows but without columns! It seems that I can select different rows but I can't see neither any data nor column names.
Under the filter setting there are no available columns either.
At the same time, when I'm trying to open sys tables they are displayed normally.
From the other side, those tables which are not displayed correctly in 2.1.0.63, could be opened in Version 1.5.5 without any problems.
Do you have any ideas?
Thanks in advance.

Hi,
Refer to the SQL Developer forum: SQL Developer for SQL Developer related questions

SQL Developer Export to PDF

Hi,
How to export the ER diagram to an PDF or Word format, i have used SQL Developer tool Build
Oracle IDE     3.1.07.42
Java(TM) Platform     1.6.0_11
Versioning Support     3.1.07.42
Thanks!

WRONG FORUM!
>
How to export the ER diagram to an PDF or Word format, i have used SQL Developer tool Build
>
Please mark this question ANSWERED and post it in the SQL Developer forum.
SQL Developer
Reverse Engineering Oracle Database Schema to ER Diagram
http://techxploration.blogspot.com/2012/06/reverse-engineering-oracle-database.html
>
11) To print your ER diagram to image/PDF. Go to Data Modeler >> Print Diagram >> To Image File.

SQL Developer Database Copy truncates DATE columns

Hope someone can help me. I want to copy all object from one schema to another schema in my Database. I have used the "tools - Database Copy" utility and it copies all of the objects and data however when I query the DATE columns in the destination schema the time element has been truncated? Why has this happened?
tab_h contains a column h_date of type DATE
Query
SELECT TO_CHAR(H_DATE, 'MM-DD-YYYY HH24:MI:SS') from tab_h;
returns
02-07-2012 09:54:14
from the source table
yet returns
02-07-2012 00:00:00
from destination schema? This is the case for all DATE columns in the tables.
I noticed this was happening in 3.0.04.34 and I upgraded to 3.1.07.42 and it still happens.
Thank you

Maybe there's a problem getting the OS settings right; try to add this to \sqldeveloper\bin\sqldeveloper.conf:
AddVMOption -Duser.region=USIf that works, you can try others closer to you.
Hope that helps,
K.

Crash in "Export" from SQL Developer Version 2.1.1.64

Hi,
Did a quick search and didn't find anything on this forum about this problem: any help
appreciated and thus Thanks in advance.
I was using a slightly older version of Developer to dump out a file (via Tools->Database Export)
when the blooming thing crashed in the middle of the export.
I hadn't upgraded the version for a while, so a quick "Check for Updates" revealed a more modern
version. I downloaded that and went through the procedure again, but the crash is as copied below:
java.io.IOException: ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 1
     at oracle.dbtools.raptor.format.InsertFormatter.printColumn(InsertFormatter.java:187)
     at oracle.dbtools.raptor.format.ResultSetFormatterWrapper.print(ResultSetFormatterWrapper.java:164)
     at oracle.dbtools.raptor.format.ResultsFormatter.print(ResultsFormatter.java:200)
     at oracle.dbtools.raptor.format.ResultsFormatter.print(ResultsFormatter.java:139)
     at oracle.dbtools.raptor.ddl.oracle.OracleDataDDL.doGetDDL(OracleDataDDL.java:55)
     at oracle.dbtools.raptor.ddl.oracle.OracleDataDDL.doGetDDLScript(OracleDataDDL.java:71)
     at oracle.dbtools.raptor.ddl.oracle.OracleObjectDDL.getScriptDDL(OracleObjectDDL.java:278)
     at oracle.dbtools.raptor.ddl.DDLGenerator.getScriptDDL(DDLGenerator.java:210)
     at oracle.dbtools.raptor.export.ExportAPI.writeExportImpl(ExportAPI.java:866)
     at oracle.dbtools.raptor.export.ExportAPI.writeExport(ExportAPI.java:416)
     at oracle.dbtools.raptor.export.ExportAPI$1.doWork(ExportAPI.java:928)
     at oracle.dbtools.raptor.export.ExportAPI$1.doWork(ExportAPI.java:922)
     at oracle.dbtools.raptor.backgroundTask.RaptorTask.call(RaptorTask.java:193)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at oracle.dbtools.raptor.backgroundTask.RaptorTaskManager$RaptorFutureTask.run(RaptorTaskManager.java:492)
     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
     at java.lang.Thread.run(Thread.java:619)
The only thing I can think of as being a problem is that the table in question (one of three small tables
I am exporting) has a CLOB column in it and some data in there is HTML format.
If anyone has a workaround, or I can elaborate further, please don't hesitate to drop me a reply.
Thanks
Mungo Henning

Many thanks for the "heads up".
I did take a look at the export file and inside it any CLOB's data
that has an apostrophe in it is not escaped.
Some of my CLOBs have HTML in them: if I had to answer the question
"Enter value for nbsp" once, I had to do this several times (the HTML had the
element for non-breaking-space whose sequence is ampersand-nbsp so
with the Defines on it asked me for a value for this substitution variable... sigh).
Looks like my problem has gone away for other reasons (the hosting company have
volunteered to migrate the data), but I wonder whether the SQL Developer
team know about this issue or not.
Thanks again.
Mungo

Statement terminator problems when exporting data with SQL Developer 3.2

I've ran across what appears to be a bug with SQL Developer 3.2.20.09. If someone can let me know if this is indeed a bug, or just something I need to configure differently, please let me know.
The problem is related to exporting a database as a SQL script, and terminator characters at the end of "create" statements, especially when columns have comments, and problems that occur when using SQLPlus to run the export script to create the tables. With the old SQL Developer 1.5.4, with the "Terminator" and "Pretty Print" options checked, statements like the following are generated:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
When I then run the script using SQLPlus, everything works fine. However, with SQL Developer 3.2.20.09, with the same options enabled, the same statements are generated like this:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
Notice all of the extra slashes in there. If a slash is not used as a statement terminator, SQLPlus treats slashes as a command to repeat the last SQL statement, which causes many errors about tables or sequences already existing. So, I tried removing the "Terminator" flag from the export options. This lead to statements that looked a bit more promising:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.'
The big problem, though, is in the statement for the table with a comment. Notice that there are two statements, but there is not a semicolon after either of them. This unfortunately causes the "COMMENT" statement to be appended to the "CREATE TABLE" statement before being executed, which causes the table to not be created (which causes even more errors later on when the script attempts to populate the table with data).
So, it would appear that this is a bug, but I'm not sure. Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
Thanks,
-Bill

>
So, it would appear that this is a bug, but I'm not sure.
>
That would be a bug. Thanks for reporting it and providing the detailed example.
>
Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
>
No.
Leave the thread open. One of the developers for sql developer should be monitoring the forum and can provide more information.

SQL Developer Export Limitation of CLOB columns

Similar Messages

Maybe you are looking for