View CLOB data

All,
How should i view CLOB records? Though I am using pl/sql developer, i am unable to view it. It is showing 'system.byte[]' only. Actually we stored an word document in that column as a byte.
Edited by: karthikeyan_ORACLE on Jul 1, 2009 12:10 AM

1) How to store document files in CLOB/BLOB column?
2) Which mechanism do we have to use?
3) How to update the CLOB/BLOB column? say for example i have stored test.doc in CLOB column, now i want to replace it with dummy.doc. how should i do this?
4) How to view the CLOB/BLOB data?

Similar Messages

View CLOB data in SQL Developer

Hi,
Can anyone let me know how to view CLOB data in SQL Developer 2.1.
I am having images stored in a column of datatype CLOB. How to view this image.
Database is 10.2.0.4.

Since SQL Developer has no idea about the type of data stored in LOB columns, one cannot view that content in desired format.
You need a tool to extract the LOB data and render it accordingly.
BTW, do you mean BLOB here?

Viewing CLOB data in sql developer

In SQL Developer 1.1, if CLOB data was returned from a query, you could place your mouse over the column and get most of it.
But in 1.2, all you get is "(CLOB) <some data> ...", and nothing else. Is there something I need to set?

You should look in the SQL Developer forum. I think your question is answered here:
How to view the entire CLOB in results table?
Regards Nigel

How to view clob data using sql

Hi,
In our database, we have one table that is having one column of CLOB datatype but now i want to view the data using sql select query but it throws error: "Datatype not supported".
Could any one please let me know how to view the clob data using select query.
Oracle DB version : 10.2.0.3
Thanks

h5.
use read procedure
PROCEDURE READ (
lobsrc IN BFILE|BLOB|CLOB ,
amount IN OUT BINARY_INTEGER,
offset IN INTEGER,
buffer OUT RAW|VARCHAR2 );
example Updating LOB by Using DBMS_LOB in PL/SQL
DECLARE
lobloc CLOB; -- serves as the LOB locator
text VARCHAR2(32767):='Resigned: 5 August 2000';
amount NUMBER ; -- amount to be written
offset INTEGER; -- where to start writing
BEGIN
SELECT resume INTO lobloc
FROM employees
WHERE employee_id = 405 FOR UPDATE;
offset := DBMS_LOB.GETLENGTH(lobloc) + 2;
amount := length(text);
DBMS_LOB.WRITE (lobloc, amount, offset, text );
text := ' Resigned: 30 September 2000';
SELECT resume INTO lobloc
FROM employees
WHERE employee_id = 170 FOR UPDATE;
amount := length(text);
DBMS_LOB.WRITEAPPEND(lobloc, amount, text);
COMMIT;
END;

View clob data is sql

i have a column name "Description" with clob datatype.
In one of the records, the 'description' has 5mb of text data.
Is there a way to display the whole 5mb of data.
Thanks in advance,
Regards

If you are using PL/SQL Developer its very easy to see the CLOB oblects just clicking ... button infront of that column .
OR
If you are using SQL*PLUS
SET LONG 10000 -- to the size u want
select col_clob from test
Else
set the offset LOBOFFSET from where u want to see the out put, 1 will give u the out put from begining
SET LOBOFFSET 1
Select col_clob from test

How can you SELECT via Database Link CLOB data using Application Express?

Customer Issue:
Developer using Oracle's Application Express 3.1. The Developer is trying to SELECT a CLOB datatype column from a remote (10.2.0.3) database, via a database link on her 10.2.0.4 based client Application. The Developer wants to be able to select CLOB data from the remote database which has limitation that she can't make any changes to the remote database.
Developer's Comments:
I do a select and get the error. Getting error ORA-22992: cannot use LOB locators selected from remote tables. So she feels she can't use dbms_lob.substr in this configuration I can do a "select into" but that is for one value. I am trying to run a select statement for a report that brings back more than one row. I do not have permission to change anything on the remote database. I want to access the remote database and multiple tables.
This is not something I work with, would greatly appreciate help or ideas. Is this a limitation of the 3.1; or does she just not have this set up correctly; or should she be using a Collection (if yes, please share example)
Thanks very much,
Pam
Edited by: pmoutrie on Jun 4, 2009 12:01 PM
Hello???
Would really appreciate an answer.
Thanks,
Pam

This may not be a perfect solution for you but it worked for my situation.
I wanted to grab some data from Grid Control's MGMT$JOB_STEP_HISTORY table but I couldnt' create an Interactive Report due to the existance of a CLOB column. I cheated this by creating a view on the GC DB, grabbing the first 4000 characters and turning it into a varchar2 column:
create view test_job_step_history as
select job_Name, target_name, status, start_time, end_time, to_char(substr(output,1,4000)) output
from MGMT$JOB_STEP_HISTORY where trunc(end_time) > trunc(sysdate)-90
In an APEX Interactive Report:
select * from test_job_step_history@GCDB
Granted, the output looks aweful right now but I am only looking for a very particular output (failed, denied, ORA-, RMAN-, etc) so the formatting isn't the most important thing to me right now.
If anyone can improve -- and I'm sure you can -- on this I'd love to hear about it.
Thanks,
Rich

Component to display a CLOB data

Hi, i'm looking for a component which can render a CLOB type xml data. The expected size of the xml could be upto 6mb which needs to be presented in the xml format. Thanks .

Thanks for your response. The use case is , we need to show a xml message file which is stored as a CLOB data type(because of it''s size upto 6mb. ). To the user the xml message needs to be presented as in a xml editor. User can view and edit the xml and should able to save it back to database. Thanks .

How to read zipped CLOB data in SQL developer

hi,
We have recently switched to SQL developer from TOAD,
And i have few tables with CLOB column types , and having data in it in zipped form
Functionality to view zipped CLOB data is there in Toad, please suggest how can i use same in SQL dev.
Thanks,
Mayank
Lead DBA
Budapest

Hi,
I downloaded the SQL Server 2000 Driver for JDBC Service Pack 1 at http://www.microsoft.com/downloads/details.aspx?familyid=4f8f2f01-1ed7-4c4d-8f7b-3d47969e66ae&displaylang=en#filelist.
I put the mysql jdbc driver to tomcat before.
However, I write an application program running on console window.
Where should I put that msbase.jar, mssqlserver.jar and msutil.jar on the windows 2000 server?
Also, how can I make the application program as a service running on windows 2000 server?
Thanks for help

Compressing clob data

Hi,
In my CRM applicatipn database 9i , we have few large tables having clob data . Due to space issues , we are looking for a procedure to compress the Clod data.
Is there any way to do so ? if yes , then how can we do that ?
Thanks,
Anks

Yes, but not very frequently. So how much effrot are you prepared to go through?
One possible solution would be to use a trigger on insert and/or update which takes the CLOB and uses a Java Stored Procedure to compress it. The compressed data would have to be stored in a BLOB column. Getting at the data would require a mechanism to reverse that process , probably a view which has a user-defined function on the BLOB column to return a CLOB.
Caveat: this is off the top of my head and I make no guarantees that any of it would actually work. However, it seems plausible :)
Cheers, APC
Blog : http://radiofreetooting.blogspot.com/

Display clob data

Can some one tell me is it possible to view a clob data with a simple select statement.I mean for non clob data type we can view the table by a simple select statement but for clob column type the data displayed is some junk.
Currently I have to run some java code to display the clob data colum,which sometimes becomes very irritating.
Please help

boost it with a p4 3.06Ghz HT....
no sorry i don't know...

Clob data type oracle to oracle issue

Hi Guys
i am unable to load clob data type and am getting the following error
" java.lang.NumberFormatException: For input "string: "4294967295"
i also have checked for clob data type in topology manager -- technology -- oracle -- data type
and it is available.
i have added the following statement in my parameter file
set ODI_ADDITIONAL_JAVA_OPTIONS=%ODI_ADDITIONAL_JAVA_OPTIONS% " -Doracledatabasemetadata.get_lob_precision=false";
but i don't see any statement like the one below after which i have to add the above statement.
set ODI_ADDITIONAL_JAVA_OPTIONS="-Djava.security.policy=server.policy";
please let me know how to make the clob data type work
Regards
janakiram

Hi Sutirtha
Yes i am able to view source data with clob data type by Right click onto your source datastore ---> View data
I have checked metalink
it says
1. Oracle recommends the setting of the "get_lob_precision" flag to FALSE to avoid this message when dealing with LOB family datatypes (CLOB, BLOB, NCLOB, BFILE...).
i have used the follwoing setting
set ODI_JAVA_OPTIONS="-Djava.security.policy=server.policy"
set ODI_ADDITIONAL_JAVA_OPTIONS=%ODI_ADDITIONAL_JAVA_OPTIONS% "-Doracledatabasemetadata.get_lob_precision=false"
2. checked the internal id of CLOB data type and it ends with 999
but still i have the same problem
Regards
janakiram

BIP cannot handle large CLOB data.

We have OBIEE 1.3.4.1 on Redhat, database is Oracle 11.2.0.2 on the same box.
In Publisher, I build a report with table with a CLOB type.
BIP can handle of the clob data over 4000 limit of varchar2, but failed at one of the rows that with clob size over 25000 character. The error message isThe report cannot be rendered because of an error, please contact the administratorIs this really beyond the limit of Publisher, or there is a place I can configure BIP to handle it.
Thanks

If I do not use any template and just show the XML in BIP View, I get a more meaningful error A semi colon character was expected. Error processing resource 'http://cchdb.thinkstream.com:9704/xmlpserver/servlet/xdo'. ...
10/31/2006 LA-DOC P&P W ORLEANS, LA PROB: POSS OF COCAINE BEGIN 10/30/2006 END 10/30
----------------------^This appear to due to the '&'. How can make BIP treat '&' as an ordinary character?

Getting an error while viewing a data in owb

Hi,
I created an External table based on a flat file. But I am not able to view the data in the external table while the flat file has the data.
I am using this external table as a source in my mapping but no data is getting loaded even after the successful execution of the mapping.I am getting the following error while viewing the data
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-29400: data cartridge error
KUP-04040: file ATLAS in ATLAS_LOCATION1 not found
Please help me regarding this. I am new to the owb 11g.

Thanks for you reply. Still I can't view the data. Actually what i did is imported a .csv file using files then created a external table configured , validated and deployed.In next step created a mapping with this excel this using table operator validated and genrated code. In next step using the control center manager i deployed it. But i can't view the data still in the external table.
Is this procedure is correct for loading the excel sheet in to databse. My client environment is on windows xp and database is on linux environment.
Please help me regarding this.I am new to owb.

Can't view my data on my table in EM

Can anyone tell me why I am getting the error below after executing my control file and also why I can't view that data which was loaded.
SQL*Loader: Release 10.2.0.1.0 - Production on Thu Jul 12 16:28:57 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Control File: workattribute2.ctl
Data File: workattribute.dat
Bad File: workattribute.bad
Discard File: none specified
(Allow all discards)
Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array: 64 rows, maximum of 256000 bytes
Continuation: none specified
Path used: Conventional
Table WORKATTRIBUTE, loaded from every logical record.
Insert option in effect for this table: APPEND
Column Name Position Len Term Encl Datatype
RESUMEID FIRST * CHARACTER
Terminator string : 'x'09''
WORKID NEXT * CHARACTER
Terminator string : 'x'09''
ID NEXT * CHARACTER
Terminator string : 'x'09''
TYPE NEXT * CHARACTER
Terminator string : 'x'09''
Record 1: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 2: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 3: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 4: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 5: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 6: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 7: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 8: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 9: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 10: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 11: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 12: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 13: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 14: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 15: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 16: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 17: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 18: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 19: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 20: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 21: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 22: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 23: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 24: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 25: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 26: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 27: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 28: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 29: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 30: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 31: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 32: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 33: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 34: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 35: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 36: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 37: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 38: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 39: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 40: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 41: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 42: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 43: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 44: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 45: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 46: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 47: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 48: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 49: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 50: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
Record 51: Rejected - Error on table WORKATTRIBUTE, column RESUMEID.
Field in data file exceeds maximum length
MAXIMUM ERROR COUNT EXCEEDED - Above statistics reflect partial run.
Table WORKATTRIBUTE:
0 Rows successfully loaded.
51 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
Space allocated for bind array: 66048 bytes(64 rows)
Read buffer bytes: 1048576
Total logical records skipped: 0
Total logical records read: 51
Total logical records rejected: 51
Total logical records discarded: 0
Run began on Thu Jul 12 16:28:57 2007
Run ended on Thu Jul 12 16:29:05 2007
Elapsed time was: 00:00:08.09
CPU time was: 00:00:00.12
thank you in advance

Hi User572297,
This is the wrong forum for a SQL Loader Q, not a bad thing, you just won't get as many responses.
That said, it seems either your terminator string is not present, incorrect or you are simply trying to load to many characters into a column that is too small. For ex: trying to load 50 characters into a Varchar2(40). You get this error for every row, hence you can not see any of the data, becuase none of the rows loaded. See below:
0 Rows successfully loaded.
51 Rows not loaded due to data errors.
What would help is to know the datatype and size of the RESUMEID column AND to see the first lines of your workattribute.dat file.

Can't view changed data in journal data

Hi,
I have implemented JKM Oracle 10g Consistent Logminer on Oracle 10g with the following option.
- Asynchronous_mode : yes
- Auto_configuration : yes
1. Change Data Capture -> Add to CDC, 2.Subscriber->subscribe (sunopsis),
3. Start Journal
The journal has been started correctly wothout errors. The journalized table has always the symbol "green clock". All is gook working.
And then i inserted 1 record in source table, but i can't view changed data in journal data. I can't understand why journal data was generated.
There are no errors.
Help me !!!

Did your designer was on the good context ?
Look the list box at the top right of the Designer interface.
You must have the same as the one where you define your journalization.

View CLOB data

Similar Messages

Maybe you are looking for