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

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?

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;

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 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

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?

Viewing Binary data in SQL*PLUS

hi all,
when i select a table to view the content, i received an error which i shown below.
SP2-0678: Column or attribute type can not be displayed by SQL*Plus
the error seems that the binary data cannot be view thru SQL PLUS.
do anybody have idea to solve this issue.
thanks in advance
karthik.J

Probably you are trying to view BLOB data. Try this to view the data:
SQL> CREATE TABLE t (a BLOB)
2 /
Table created.
SQL> INSERT INTO t
2 VALUES (UTL_RAW.cast_to_raw ('Hello World'))
3 /
1 row created.
SQL> SELECT UTL_RAW.cast_to_varchar2 (a) a
2 FROM t
3 /
A
Hello World

Unable to load clob data through sql loader

Hi Experts ,
My ctl file is :
LOAD DATA infile '$di_top/conversion/devtrack_notes.csv'
truncate into table xxdi_proj
fields terminated by ','
optionally enclosed by '"'
trailing nullcols (bugid,note *clob*)
{code}
The problem is note column is a clob and one of the
values has line breaks like this :
{code}
Hi Sir,
Would you please inform when the reports are scheduled for automatic process?
Maria will stop his process to avoid duplication.
Please inform asap
With Regards ,
Ronaldinho
{code}
When the data gets loaded ,
The first column gets the sentence 'Would you please inform.....' i.e . the data of second columns gets loaded into first column as nulls are recognized as end delimiter.
How to overcome this problem?
Thanks

Pl post your exact OS and database versions, along with your complete sqlldr command, the table description and a sample of your input csv file.
HTH
Srini

Apex 4.0 - Can see view data in SQL*Plus but no data in Object Browser

Hi There,
I have just started using Apex 4.o and migrated some apps. I have an issue with a report, but see the same issue with Object browser, which is easier to describe.
I have a view:
create or replace view V_PLJ_USERDEF_CODES (
         CODE_SET_ID,
         CODE_SET_CODE,
         CODE_SET_DESC,
         CODE_ID,
         CODE_SYS_CODE,
         CODE_VALUE,
         CODE_DESC,
         DISPLAY_SEQ,
         DISPLAY_FLAG,
         LANGUAGE_CODE) as
select CS.CODE_SET_ID,
         CS.CODE_SET_CODE,
         CS.CODE_SET_DESC,
         C.CODE_ID,
         C.CODE_SYS_CODE,
         C.CODE_VALUE,
         C.CODE_DESC,
         C.DISPLAY_SEQ,
         C.DISPLAY_FLAG,
         C.LANGUAGE_CODE
    from PLJ_CODES C,
         PLJ_CODE_SETS CS
   where C.CODE_SET_ID         = CS.CODE_SET_ID
     and CS.CODE_SET_TYPE_CODE = SYS_CONTEXT('PLJUMPSTART','C_USERDEF_CODE_SET');This returns data in SQL*Plus, but no data in Object Browser OR report region based on this view.
Workspace parses in the same schema as tested in SQL*Plus.
If, in report, I swap out view, and use underlying table - no problem.
Any ideas -
thanks
P

Hi all,
Thanks for getting back so promptly.
It just seems weird to me, as tables are just fine, but not views.
In the underlying schema:
SQL> sho user
USER is "ICSREPORTING"
SQL> select count(*) from plj_codes;
COUNT(*)
       107
SQL> select count(*) from v_plj_userdef_codes;
COUNT(*)
        29And in the APEX schema
SQL> sho user
USER is "APEX_040000"
SQL> select count(*) from icsreporting.plj_codes;
select count(*) from icsreporting.plj_codes
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> select count(*) from icsreporting.v_plj_userdef_codes;
select count(*) from icsreporting.v_plj_userdef_codes
ERROR at line 1:
ORA-00942: table or view does not exist
SQL>However, in SQL browser, I can see the data in PLJ_CODES but in V_PLJ_USERDEF_CODES, just the message "This view has no data". Indeed, it is like this for all views.
I even explicitly granted access to APEX_040000 but no good.
In fact, I would like to know more about how Apex gets access to do DML against the underlying parsing schema(s).
This is a little frustrating though. It worked just fine in lots of apps in version 2.1 to 3.2
Am I missing something
paul
p.s I knew there would be a question about the context, but I had already checked that. :)
Edited by: PJ on Nov 19, 2010 4:09 AM

Pl/sql Procedure is Not Creating With the CLOB data Type

Hi,
I am Using Oracle 10g Express Edition Release2.... My Doubt is While creating a table With CLOB Data Type the table is created successfully,but while Creating a Procedure With the CLOB Data type i am getting an Error Message
2667/5 PL/SQL: Statement ignored
2667/24 PLS-00382: expression is of wrong type
then i tried With the Varchar2(30000) the Procedure is Created Successfully note i have not changed any thing in my code except the data type.
I am Just Confused ......Why the Procedure is not Created with CLOB Data type?
Please advice ...
Thank U
SHAN

hi,
Thanks for reply....Another Example
CREATE TABLE USER_MAS (USER_ID VARCHAR2 (20 Byte),MAIL_ID VARCHAR2 (255 Byte));
set serveroutput on
declare
atable varchar2(64) := 'USER_MAS';
acolumn varchar2(64) := 'MAIL_ID';
avalue varchar2(64) := 'NEWYORK' ;
dyn_sql clob;
begin
dyn_sql := 'update '||atable||' set '||acolumn||' = '''||avalue|| '''' ;
dbms_output.put_line(dyn_sql);
execute immediate dyn_sql;
end;
commit ;
Error at line 2
ORA-06550: line 9, column 23:
PLS-00382: expression is of wrong type
ORA-06550: line 9, column 5:
PL/SQL: Statement ignored
When i Changed the Data type to varchar2(64)
update USER_MAS set MAIL_ID = 'NEWYORK'
PL/SQL procedure successfully completed.
Commit complete.
I like to Know the Reason Why the Procedure is Not Created in Oracle 10g XE DB
Note :the Same Script i used in 11g DB the Procedure is Created Successfully....
Why you need use CLOB or VARCHAR2 in your temp_num variable as you sending parameters as number?
In the Procedure we are create some run time queries while executing the procedure. There are around 10 run time queries created.
The size of each query is more than 4000 characters . We then add all the queries using union all after each query to the clob variable as the normal varchar will not support.
Please Advice
Thank U
SHAN

How to view complete date stamp in query result view in sql developer?

Hi,
In the query result, the date present in db is shown as DD-MM-YYYY format but I want to view the complete date stamp. When I view the same data in aqua data studio, I see the complete time stamp. Please let me know if I need to do some settings in Oracle SQL Developer so that complete date is shown?
How to view complete date stamp in query result view in sql developer?
Thanks in advance,
Vineet

864793 wrote:
Hi,
In the query result, the date present in db is shown as DD-MM-YYYY format but I want to view the complete date stamp. When I view the same data in aqua data studio, I see the complete time stamp. Please let me know if I need to do some settings in Oracle SQL Developer so that complete date is shown?
How to view complete date stamp in query result view in sql developer?
Thanks in advance,
VineetAlternatively you can execute below
set nls_date_format='DD-MM-YYYY HH24:MI:SS';Regards,
Achyut K

SQL Developer - viewing table data while debugging

Apologies if this is in the wrong forum.
I'm using SQL Developer to debug a complex stored procedure line by line. There are a lot of inserts / updates / deletes in the procedure and I'd like to be able to view the data in the relevant tables after each statement has been run to see the effect of each statement.
Trouble is, when I try to do this, SQL Developer shows the contents of the tables as if they have been unaffected by the stored procedure. Is there a setting somewhere or some type of locking I can use to see the data changes as they happen?

Only the session that is inserting the data can see that new data until the session issues a commit, so I would doubt that you could do this. You probably want to a) view the data before the insert or b) (ugly but should work) put a trigger on the table being inserted so it inserts a copy of the data to a tracking table. This procedure will have to have the AUTONOMOUS TRANSACTION pragma in order to not be held until your debug session commits.

Using Discoverer 4i to view data on SQL Server

Hello,
We have Discoverer 4i set up to work with Oracle 9i. Now our Discoverer users want to use Discoverer to view data that is in SQL Severer. We don't want to rebuild data in SQL Server into 9i. What can we set up so 4i can view and maybe update data that is in SQL Severer. Thank you.

I can't tell exactly what the problem is, but why don't you try a different approach. See a couple of the tutorials from the link below, and try it again.
https://www.youtube.com/watch?v=sbkQEBrhl5M
https://www.youtube.com/watch?v=Grb9vWmtZe0
Knowledge is the only thing that I can give you, and still retain, and we are both better off for it.

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 not Load CLOB data 32k to target table

SQL> DESC testmon1 ;
Name Null? Type
FILENAME VARCHAR2(200)
SCANSTARTTIME VARCHAR2(50)
SCANENDTIME VARCHAR2(50)
JOBID VARCHAR2(50)
SCANNAME VARCHAR2(200)
SCANTYPE VARCHAR2(200)
FAULTLINEID VARCHAR2(50)
RISK VARCHAR2(5)
VULNNAME VARCHAR2(2000)
CVE VARCHAR2(200)
DESCRIPTION CLOB
OBSERVATION CLOB
RECOMMENDATION CLOB
SQL> DESC test_target;
Name Null? Type
LOCALID NOT NULL NUMBER
DESCRIPTION NOT NULL CLOB
SCANTYPE NOT NULL VARCHAR2(12)
RISK NOT NULL VARCHAR2(6)
TIMESTAMP NOT NULL DATE
VULNERABILITY_NAME NOT NULL VARCHAR2(2000)
CVE_ID VARCHAR2(200)
BUGTRAQ_ID VARCHAR2(200)
ORIGINAL VARCHAR2(50)
RECOMMEND CLOB
VERSION VARCHAR2(15)
FAMILY VARCHAR2(15)
XREF VARCHAR2(15)
create or replace PROCEDURE proc1 AS
CURSOR C1 IS
SELECT FAULTLINEID,VULNNAME,scanstarttime, risk,
dbms_lob.substr(DESCRIPTION,dbms_lob.getlength(DESCRIPTION),1) "DESCR",dbms_lob.substr(OBSERVATION,dbms_lob.getlength(OBSERVATION),1) "OBS",
dbms_lob.substr(RECOMMENDATION) "REC",CVE
FROM testmon1;
c_rec C1%ROWTYPE;
descobs clob;
FSCAN_VULN_TRANS_REC VULN_TRANSFORM_STG%ROWTYPE;
TIMESTAMP varchar2(50);
riskval varchar2(10);
pCTX PLOG.LOG_CTX := PLOG.init (pSECTION => 'foundscanVuln Procedure',
pLEVEL => PLOG.LDEBUG,
pLOG4J => TRUE,
pLOGTABLE => TRUE,
pOUT_TRANS => TRUE,
pALERT => TRUE,
pTRACE => TRUE,
pDBMS_OUTPUT => TRUE);
amount number;
buffer varchar2(32000);
BEGIN
---INITIALIZE THE LOCATOR FOR CLOB DATA TYPE
select observation into descobs from testmon1 where rownum=1;
OPEN C1;
loop
fetch C1 INTO c_rec;
exit when C1%NOTFOUND;
--LOAD THE DESCRIPTION FIELD FROM CURSOR AND WRITE IT TO THE CLOB LOCATOR descobs.
dbms_lob.Write(descobs,dbms_lob(c_rec.DESCR),1,c_rec.DESCR);
------APPEND THE OBSERVATION FIELD FROM CURSOR TO THE CLOB LOCATOR descobs.
dbms_lob.Writeappend(descobs,dbms_lob(c_rec.DESCR),c_rec.OBS);
-- dbms_output.put_line ('the timestamp is :'||c_rec.scanstarttime);
--dbms_lob.write(descobs,amount,1,buffer);
descobs:=c_rec.OBS;
--dbms_lob.read(descobs,amount,1,buffer);
--dbms_lob.append(c_rec.DESCR,c_rec.OBS);
--descobs:=c_rec.OBS;
--dbms_output.put_line ('the ADDED DESCROBS is :'||dbms_lob.substr(c_rec.DESCR,dbms_lob.getlength(c_rec.DESCR),1));
dbms_output.put_line ('the ADDED DESCRIPTION AND OBSERVATION is :'||descobs);
--dbms_output.put_line ('the DESCROBS buffer is :'||buffer);
SELECT DESCRIPTION INTO FSCAN_VULN_TRANS_REC.DESCRIPTION
FROM TESTMON1 WHERE ROWNUM=1;
---------LOAD THE DESCRIPTION+ observation value into the target table description
DBMS_LOB.WRITE(FSCAN_VULN_TRANS_REC.DESCRIPTION, dbms_lob.getlength(descobs),1,descobs);
TIMESTAMP:=substr(c_rec.scanstarttime,1,10)||' '|| substr(c_rec.scanstarttime,12,8);
IF c_rec.risk <3
THEN riskval:='Low';
ELSIF c_rec.risk <6
THEN riskval:='Medium';
ELSIF c_rec.risk <10
THEN riskval:='High';
END IF;
FSCAN_VULN_TRANS_REC.TIMESTAMP:=TO_DATE(TIMESTAMP, 'YYYY/MM/DD HH24:MI:SS');
FSCAN_VULN_TRANS_REC.risk:= riskval;
--dbms_lob.append(c_rec.DESCR,c_rec.OBS);
FSCAN_VULN_TRANS_REC.DESCRIPTION:=c_rec.DESCR;
FSCAN_VULN_TRANS_REC.RECOMMEND:=c_rec.REC;
FSCAN_VULN_TRANS_REC.LocalID:=to_number(c_rec.FAULTLINEID);
FSCAN_VULN_TRANS_REC.SCANTYPE:='FOUNDSCAN';
FSCAN_VULN_TRANS_REC.CVE_ID:=c_rec.CVE;
FSCAN_VULN_TRANS_REC.VULNERABILITY_NAME:=c_rec.VULNNAME;
-- dbms_output.put_line ('the plog timestamp is :'||timestamp);
-- dbms_output.put_line ('the timestamp is :'||riskval);
--dbms_output.put_line ('the recommend is :'||FSCAN_VULN_TRANS_REC.RECOMMEND);
--dbms_output.put_line ('the app desc is :'||FSCAN_VULN_TRANS_REC.DESCRIPTION);
insert into test_target values FSCAN_VULN_TRANS_REC;
End loop;
close C1;
commit;
EXCEPTION
WHEN OTHERS THEN
-- dbms_output.put_line ('Data not found');
-----------dbms_output.put_line (sqlcode|| ':'||sqlerrm);
end proc1;
using dbms_lob package is not helping. Either DB stops responding. Or the Observation field ( which has max length >300000) can not be loaed into a CLOB variable.
Please help or give me a sample code that helps.

select
     BANKING_INSTITUTION.BANK_REF_CODE     C1_BANK_ID,
     BANKING_INSTITUTION.NAME_BANK     C2_BANK_NAME,
     BANKING_INSTITUTION.BANK_NUMBER     C3_BANK_NUMBER,
     BANKING_INSTITUTION.ISO_CODE     C4_GBA_CODE,
     BANKING_INSTITUTION.STATUS     C5_STATUS,
     BANKING_INSTITUTION.SOURCE     C6_SOURCE,
     BANKING_INSTITUTION.START_DATE_BANK     C7_START_DATE,
     BANKING_INSTITUTION.ADDRESS_BANK     C8_BANK_ADDRESS1
from     REF_DATA_DB.BANKING_INSTITUTION BANKING_INSTITUTION
where     (1=1)
insert /*+ append */ into XXSVB.C$_0XXSVB_BANKS_STAGING
     C1_BANK_ID,
     C2_BANK_NAME,
     C3_BANK_NUMBER,
     C4_GBA_CODE,
     C5_STATUS,
     C6_SOURCE,
     C7_START_DATE,
     C8_BANK_ADDRESS1
values
     :C1_BANK_ID,
     :C2_BANK_NAME,
     :C3_BANK_NUMBER,
     :C4_GBA_CODE,
     :C5_STATUS,
     :C6_SOURCE,
     :C7_START_DATE,
     :C8_BANK_ADDRESS1
)

View clob data is sql

Similar Messages

Maybe you are looking for