CLOB to LONG

Hi all
We have changed one Long Data type column to CLOB
We need to revert back to Long Data type,
we changed the Data type from Long to CLOB
Can we change back to Long Again
we use oracle 10g Rel 2 on Hp-Unix
thanks all in Advance

http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/datatype.htm#sthref3806
Do not create tables with LONG columns. Use LOB columns (CLOB, NCLOB) instead. LONG columns are supported only for backward compatibility.
Oracle also recommends that you convert existing LONG columns to LOB columns. LOB columns are subject to far fewer restrictions than LONG columns. Further, LOB functionality is enhanced in every release, whereas LONG functionality has been static for several releases.
Why would you want to revert, and do exactly the opposite from what Oracle recommends??

Similar Messages

Mapping CLOB and Long in xml schema

Hi,
I am creating an xml schema to map some user defined database objects. For example, for a column which is defined as VARCHAR2 in the database, I have the following xsd type mapping.
<xsd:element name="Currency" type="xsd:string" />
If the oracle column is CLOB or Long(Oracle datatype), could you please tell me how I can map it in the xml schema? I do not want to use Oracle SQL type like:
xdb:SQLType="CLOB" since I need a generic type mapping to CLOB. Would xsd:string still hold good for CLOB as well as Long(Oracle datatype) ?
Please help.
Thanks,
Vadi.

The problem is that LONGs are not buffered but are read from the wire in the order defined. The problem is the same as
rs = stmt.executeQuery("select myLong, myNumber from tab");
while (rs.next()) {
int n = rs.getInt(2);
String s = rs.getString(1);
The above will fail for the same reason. When the statement is executed the LONG is not read immediately. It is buffered in the server waiting to be read. When getInt is called the driver reads the bytes of the LONG and throws them away so that it can get to the NUMBER and read it. Then when getString is called the LONG value is gone so you get an exception.
Similar problem here. When the query is executed the CLOB and BLOB locators are read from the wire, but the LONG is buffered in the server waiting to be read. When Clob.getString is called, it has to talk to the server to get the value of the CLOB, so it reads the LONG bytes from the wire and throws them away. That clears the connection so that it can ask the server for the CLOB bytes. When the code reads the LONG value, those bytes are gone so you get an exception.
This is a long standing restriction on using LONG and LONG RAW values and is a result of the network protocol. It is one of the reasons that Oracle deprecates LONGs and recommends using BLOBs and CLOBs instead.
Douglas

How to get an XML string store in CLOB or LONG column ?

How to get an XML string store in CLOB or LONG column ?
We use XSU with the following command
String str = qry.getXMLString();
but all the "<" are replace by "<"
It's impossible to parse the result for XSLT transformation
Thank's for your help
Denis Calvayrac
Example :
in the column "TT_NAME"
"<name><firstname>aaa</<firstname><lastname>bbb</lastname></name>
I want this result
<TT_NAME>
<name>
<firstname>aaa</firstname>
<lastname>bbb</lastname>
</name>
</TT_NAME>
but, I have this result
<TT_NAME>
<name>
<firstname>aaa</firstname>
<lastname>bbb</lastname>
</name>
</TT_NAME>

Can you post some of your code, so I can take a look ?
Thanks

Extracting clob/blob/long datatypes in delimited file

I have a few tables in database that have clob/blob/long datatypes. I need to unload this data into delimited file and reload the data into another database. I don't want to use export/import.
Currently the code that i have can handle varchar2, number, date datatypes quite easily using sqlloader.
The tables are not too big (hundred to 10k rows approximately) and performance is important but not crucial. The script can run for a few minutes unloading data, that is fine. Code maintenance is of higher priority with pl/sql being the preferred scripting language.
From the sqlloader manual, i glean that use of special delimiter is important, something like <startlob> and <endlob> .
I need ideas on how to do this.

Hi Buddy.
I am having same kind of Problem. I am using very similar procedure Instead of PUT_RAW I am using put line.
Writing is not a problem after writing the image into a file I cannot open that. That means Image got corrupted. If you find out some solutions for your problem please help me
My email id is [email protected]
Thanks
AJI

Can't fetch clob and long in one select/query

I created a nightmare table containing numerous binary data types to test an application I was working on, and believe I have found an undocumented bug in Oracle's JDBC drivers that is preventing me from loading a CLOB and a LONG in a single SQL select statement. I can load the CLOB successfully, but attempting to call ResultSet.get...() for the LONG column always results in
java.sql.SQLException: Stream has already been closed
even when processing the columns in the order of the SELECT statement.
I have demonstrated this behaviour with version 9.2.0.3 of Oracle's JDBC drivers, running against Oracle 9.2.0.2.0.
The following Java example contains SQL code to create and populate a table containing a collection of nasty binary columns, and then Java code that demonstrates the problem.
I would really appreciate any workarounds that allow me to pull this data out of a single query.
import java.sql.*;
This class was developed to verify that you can't have a CLOB and a LONG column in the
same SQL select statement, and extract both values. Calling get...() for the LONG column
always causes 'java.sql.SQLException: Stream has already been closed'.
CREATE TABLE BINARY_COLS_TEST
PK INTEGER PRIMARY KEY NOT NULL,
CLOB_COL CLOB,
BLOB_COL BLOB,
RAW_COL RAW(100),
LONG_COL LONG
INSERT INTO BINARY_COLS_TEST (
PK,
CLOB_COL,
BLOB_COL,
RAW_COL,
LONG_COL
) VALUES (
1,
'-- clob value --',
HEXTORAW('01020304050607'),
HEXTORAW('01020304050607'),
'-- long value --'
public class JdbcLongTest
public static void main(String argv[])
throws Exception
Driver driver = (Driver)Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
DriverManager.registerDriver(driver);
Connection connection = DriverManager.getConnection(argv[0], argv[1], argv[2]);
Statement stmt = connection.createStatement();
ResultSet results = null;
try
String query = "SELECT pk, clob_col, blob_col, raw_col, long_col FROM binary_cols_test";
results = stmt.executeQuery(query);
while (results.next())
int pk = results.getInt(1);
System.out.println("Loaded int");
Clob clob = results.getClob(2);
// It doesn't work if you just close the ascii stream.
// clob.getAsciiStream().close();
String clobString = clob.getSubString(1, (int)clob.length());
System.out.println("Loaded CLOB");
// Streaming not strictly necessary for short values.
// Blob blob = results.getBlob(3);
byte blobData[] = results.getBytes(3);
System.out.println("Loaded BLOB");
byte rawData[] = results.getBytes(4);
System.out.println("Loaded RAW");
byte longData[] = results.getBytes(5);
System.out.println("Loaded LONG");
catch (SQLException e)
e.printStackTrace();
results.close();
stmt.close();
connection.close();
} // public class JdbcLongTest

The problem is that LONGs are not buffered but are read from the wire in the order defined. The problem is the same as
rs = stmt.executeQuery("select myLong, myNumber from tab");
while (rs.next()) {
int n = rs.getInt(2);
String s = rs.getString(1);
The above will fail for the same reason. When the statement is executed the LONG is not read immediately. It is buffered in the server waiting to be read. When getInt is called the driver reads the bytes of the LONG and throws them away so that it can get to the NUMBER and read it. Then when getString is called the LONG value is gone so you get an exception.
Similar problem here. When the query is executed the CLOB and BLOB locators are read from the wire, but the LONG is buffered in the server waiting to be read. When Clob.getString is called, it has to talk to the server to get the value of the CLOB, so it reads the LONG bytes from the wire and throws them away. That clears the connection so that it can ask the server for the CLOB bytes. When the code reads the LONG value, those bytes are gone so you get an exception.
This is a long standing restriction on using LONG and LONG RAW values and is a result of the network protocol. It is one of the reasons that Oracle deprecates LONGs and recommends using BLOBs and CLOBs instead.
Douglas

CLOB and LONG datatypes

I have a problem with needing to display fields in a report that are stored in the database as CLOB.
The report isn't too complicated, and can be put together using folders in Admin.
There is a table in the database that stores text from reports. Each report is identified by its case id, and then there may be a number of reports for each case (let's say 1-5 for the purposes of this explaination). There will then be three sections of text in each report, identifed in the database by section numbers.
The fields needed are the case number (case_id), the report number (report_no), the section number (sect_no) and the section text (sect_text)
All of the fields are numeric, except sect_text, which is a CLOB datatype.
There are two queries, one to select the case id, min report number and first section of text and the other to select the case id, max report number and last section of text. The aim being a report that shows the start of the first report and the end of the last one.
So, that's the background. All of the queries to select the data work fine in sqlplus. However they can't be displayed in Disco because it brings in CLOB fields as LONG, and can't group them (which it has to do for the MAX and MIN)
I'd rather not set the whole thing up as a view on the DB, as I'd prefer to have the flexibiility of editing it in discoverer
Any tips?

Hi
I do have a tip. Please take a look at this thread that I was involved in a couple of years ago:
CLOB show up as item
And here is another one that might help:
Possible for Discoverer to display BLOB type documents stored in database?
Best wishes
Michael

Convert CLOB to LONG

I have an app that has a CLOB column in a table. The reporting software, which is separate from the application, cannot read CLOBs. So the solution that was revealed to me was to setup a trigger to copy any data going into the CLOB table to another table where the column is a LONG.
Of course, no DBA in their right mind would be happy with this. So, I'm trying to set about creating a view that will convert the CLOB to a LONG, so as to relieve my poor SAN from all the I/O. There is no TO_LONG function, nor can I find anywhere how to do this.
Anyone feel like taking a stab at this?

Tom,
My guess is you might have to use dbms_lob.substr subprogram. Anyway, LONG datatype has a limit of 2gb while clob or blob can be bigger (theoritically upto 8TB ). So, you have to decide if you wanna truncate your data and store only the first 2gb. Also, just for information purposes, this is what Oracle says in documentation.
----------ORACLE DOCUMENTATION------
Note:
Do not create tables with LONG columns. Use LOB columns (CLOB, NCLOB) instead. LONG columns are supported only for backward compatibility.
Oracle also recommends that you convert existing LONG columns to LOB columns. LOB columns are subject to far fewer restrictions than LONG columns. Further, LOB functionality is enhanced in every release, whereas LONG functionality has been static for several releases.
HTH,
Rahul.

Unable to insert XML in CLOB (for Long Lived Processes)

I am trying to insert XML/XDP in a CLOB column of an Oracle Database. It seems to work in a short lived process. However, I get all sorts of errors when I convert it to long lived.
Anyway one know why?
I extract the XML/XDP using a process form submission module and convert it to string. Then, I run the insert through a custom script as setString.
Aditya

This has been an issue in the past. When I try to change the string size to unlimited, it doesn't allow me to save the process. However, when I create a new string variable and assign it to unlimited, it worked.
I am thinking, when the string variable is saved the first time with a limit or a lower limit, it saves it to a Varchar2 and it is unable to change to a different column type when a higher char limit or unlimited it set. Don't you think this is a serious issue in existing processes with lower limits on string variables. Do you know a stable work around?
Also, how can I get value from an XML variable, using a custom script? "patExecContext.getProcessDataValue" doesn't work.
Aditya

How to Convert Data type from CLOB to LONG

Hi all
We changed one Long Data type column to CLOB
We need to revert back to Long Data type,
we changed the Data type from Long to CLOB
Can we change back to Long Again
we use oracle 10g Rel 2 on Hp-Unix
thanks all in Advance
Edited by: jrDba - atm on Apr 6, 2009 4:45 AM

Hi Satish
thanks a alot for the Info'
Can you please provide the
Notes MOS note 437021.1 for this purpose
thanks a lot

Export CLOB field (long= 4202083) to a file with UTL_FILE.PUT or PUT_LINE

Hello,
I'm trying to export a CLOB field to a txt file. It's a xml string in the CLOB. I have used different methods but the only which i can use is PUT, PUT_LINE.
But:
- PUT does only export the 32565 characters. I see that the output of l_pos is 4202084 but these are not exported. I have tried FFLUSH, but this gives a error or my syntax is not correct.
- PUT_LINE is exporting the complete CLOB, but after every 32656 is new line is added and if I want to look with altove then I have to remove 129 times the new line. Thats not the way I want to go.
Is it an idea, if it is possible, that I write 32565 chars to the buffer (file), read these 32565 from the buffer minus one (=without \r\n), delete the last 32565 chars from buffer and append/put the chars 32565 minus the \r\n to the buffer again. I hope there will be a better idea but....
Has anybody an idea how I can solve this? Or what do I wrong?
Any help would be appreciated.
Beneath my code.
Nico
CREATE OR REPLACE DIRECTORY documents AS 'D:\TEST';
SET SERVEROUTPUT ON
DECLARE
l_file    UTL_FILE.FILE_TYPE;
l_clob    CLOB;
l_buffer VARCHAR2(32767);
l_amount BINARY_INTEGER := 32565;
l_pos     INTEGER := 1;
l_lengte number;
l_lineCount number := 0;
BEGIN
SELECT PAYLOAD
INTO   l_clob
FROM   icepayloadext ext
WHERE EXT.PAYLOADTYPE in ('POST')
    AND substr(payload, 0, 2000) like '%181015%'
    AND ext.LSTIME between to_date('10-10-2012 00:00:00', 'dd-mm-rrrr HH24:mi:ss') and to_date('10-10-2012 17:30:00', 'dd-mm-rrrr HH24:mi:ss');
l_lengte := DBMS_LOB.GETLENGTH (l_clob);
DBMS_OUTPUT.PUT_LINE('lengte clob veld: ' || l_lengte);
l_file := UTL_FILE.fopen('DOCUMENTS', 'Sample1.txt', 'w', 32767);
LOOP
    DBMS_LOB.read (l_clob, l_amount, l_pos, l_buffer);
    UTL_FILE.PUT(l_file, l_buffer);
    UTL_FILE.FFLUSH (l_file);
    --UTL_FILE.PUT_LINE(l_file,'alles geschreven');
    l_pos := l_pos + l_amount;
    DBMS_OUTPUT.PUT_LINE('Offset position: ' || l_pos);
    if (l_pos > l_lengte) then
        exit;
    end if;
END LOOP;
UTL_FILE.fclose(l_file);
--EXCEPTION
--WHEN OTHERS THEN
-- DBMS_OUTPUT.put_line(SQLERRM);
    --UTL_FILE.fclose(l_file);
END;
/

You can always try it the binary way:
DECLARE
l_file UTL_FILE.FILE_TYPE;
l_clob CLOB;
l_buffer VARCHAR2(32767);
l_amount BINARY_INTEGER := 32565;
l_pos INTEGER := 1;
l_lengte number;
l_lineCount number := 0;
BEGIN
l_clob := rpad( to_clob( 'test' ), 60000, 'test' );
l_lengte := DBMS_LOB.GETLENGTH (l_clob);
DBMS_OUTPUT.PUT_LINE('lengte clob veld: ' || l_lengte);
l_file := UTL_FILE.fopen( 'MY_DIR', 'Sample1.txt', 'wb', 32767 );
LOOP
    begin
      DBMS_LOB.read (l_clob, l_amount, l_pos, l_buffer);
    exception
      when no_data_found then exit;
    end;
--    UTL_FILE.PUT_RAW( l_file, utl_raw.cast_to_raw( l_buffer ) ); -- file in database character set
    UTL_FILE.PUT_RAW( l_file, utl_i18n.string_to_raw( l_buffer, 'WE8MSWIN1252' ) );
    l_pos := l_pos + l_amount;
DBMS_OUTPUT.PUT_LINE('Offset position: ' || l_pos);
END LOOP;
UTL_FILE.fclose(l_file);
END;Anton

How to convert clob column to long

Hi,
Is there any way to convert clob column to long.
Here below is my scenario..
Instead of using substr function
CREATE OR REPLACE PROCEDURE proc AS
sql2 clob := '';
sqlstring1 LONG;
sqlstring2 LONG;
sqlstring3 LONG;
sqlstring4 LONG;
sqlstring5 LONG;
sqlstring6 LONG;
sqlstring7 LONG;
sqlstring8 LONG;
sqlstring9 LONG;
sqlstring10 LONG;
BEGIN
FOR sql1 IN (SELECT info FROM emp)
LOOP
sql2 := sql1.sql_string;
sqlString1 := dbms_lob.SUBSTR(sql2, 8000, 1);
sqlString2 := dbms_lob.SUBSTR(sql2, 8000, 8001);
sqlString3 := dbms_lob.SUBSTR(sql2, 8000, 16001);
sqlString4 := dbms_lob.SUBSTR(sql2, 8000, 24001);
sqlString5 := dbms_lob.SUBSTR(sql2, 8000, 32001);
sqlString6 := dbms_lob.SUBSTR(sql2, 8000, 40001);
sqlString7 := dbms_lob.SUBSTR(sql2, 8000, 48001);
sqlString8 := dbms_lob.SUBSTR(sql2, 8000, 56001);
sqlString9 := dbms_lob.SUBSTR(sql2, 8000, 64001);
sqlString10 := dbms_lob.SUBSTR(sql2, 8000, 72001);
EXECUTE IMMEDIATE sqlString1 || sqlString2 || sqlString3 ||
sqlString4 || sqlString5 || sqlString6 ||
sqlString7 || sqlString8 || sqlstring9 ||
sqlstring10;
END LOOP;
COMMIT;
END proc;
Any help really appreciated
Thanks

We cannot execute clob dynamically.That's what I said: execute immediate doesn't support CLOB!
But you can concatenate two long's:
SQL> DECLARE
   l_stmt1   LONG;
   l_stmt2   LONG;
BEGIN
   l_stmt1 := RPAD ('BEGIN ', 32500, ' ');
   l_stmt2 :=
       RPAD (' dbms_output.put_line(''Hello World'');', 32500, ' ')
       || 'END;';
   DBMS_OUTPUT.put_line ('Length of statement: '
                         || LENGTH (l_stmt1 || l_stmt2)
   EXECUTE IMMEDIATE (l_stmt1 || l_stmt2);
END;
Length of statement: 65004
Hello World
PL/SQL procedure successfully completed.So if you strip some extra spaces or try to compact your statement somehow, you might be able use above method.

When overwritting CLOB longer previous value still remains

Hi,
I have a problem with updating CLOB's. Below is how I write them:
String selectStatement = "select description from modules where " +
"system = ? and version = ? and module = ? for update";
PreparedStatement selStmt = con.prepareStatement(selectStatement);
selStmt.setString(1, system);
selStmt.setString(2, version);
selStmt.setString(3, module);
ResultSet rset = selStmt.executeQuery();
ResultSetInPool rpool = (ResultSetInPool)rset;
if (rpool.next()) {
desclob = (CLOB)((OracleResultSet)rpool.getUnderlyingResultSet()).getCLOB(1);
// Write character stream (description) to CLOB variable
writer = ((CLOB)desclob).getCharacterOutputStream();
writer.write(description.toCharArray());
writer.flush();
} else {
throw new NoSuchEntityException("Row does not exist");
The problem is that when there is a value already written which is longer then new one, part of the old value (which has not been overwriten) still remains in the database. Is that normal behavior? Is there any way how to address this problem better/faster then updating row with EMPTY_CLOB() and writting string again?
Thanks for response in advance,
RAF

Hi Rafal,
If you are using Oracle9i JDBC Drivers, then use the
oracle.sql.CLOB.trim(long offset) method to clear the contents of the CLOB.
like ,
// clear the contents of clob
clob.trim(0);
else If you are using JDK 1.4 , use java.sql.Clob.truncate(long offset)
clob.truncate(0);
then start streaming the new contents into the clob.
I guess its the normal behaviour of CLOB.
Regards
Elango.

Using DBMS_DATAPUMP with LONG data type

I've got a procedure below that calls the DBMS_DATAPUMP procedure using a REMOTE_LINK to move a schema from one database to another. However, a couple of the tables within that schema have columns with the LONG data type. And when I run it I get an error saying that you cannot move data with the LONG data type using a REMOTE LINK. So no data in those particular tables gets moved over.
Has anyone else had this issue? If so, do you have a work around? I tried adding a CLOB column to my table and setting the new CLOB to equal the LONG, but I couldn't get that to work either...even when I tried using a TO_LOB. If I could get that to, then I could just drop the LONG, move the schema, then recreate the LONG column on the opposite side.
Here's my procedure....
DECLARE
     /* EXPORT/IMPORT VARIABLES */
     v_dp_job_handle                    NUMBER ;          -- Data Pump job handle
     v_count                              NUMBER ;          -- Loop index
     v_percent_done                    NUMBER ;          -- Percentage of job complete
     v_job_state                         VARCHAR2(30) ;     -- To keep track of job state
     v_message                         KU$_LOGENTRY ;     -- For WIP and error messages
     v_job_status                    KU$_JOBSTATUS ;     -- The job status from get_status
     v_status                         KU$_STATUS ;     -- The status object returned by get_status
     v_logfile                         NUMBER ;
     v_date                              VARCHAR2(13) ;
     v_source_server_name          VARCHAR2(50) ;
     v_destination_server_name     VARCHAR2(50) ;
BEGIN
     v_project := 'TEST' ;
     v_date := TO_CHAR(SYSDATE, 'MMDDYYYY_HHMI') ;
     v_source_server_name := 'TEST_DB' ;
     v_dp_job_handle := DBMS_DATAPUMP.OPEN(
          OPERATION     => 'IMPORT',
          JOB_MODE     => 'SCHEMA',
          REMOTE_LINK => v_source_server_name,
          JOB_NAME     => v_project||'_EXP_'||v_date,
          VERSION          => 'LATEST') ;
     v_logfile := DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE ;
     DBMS_DATAPUMP.ADD_FILE(
          HANDLE          => v_dp_job_handle,
          FILENAME     => v_project||'_EXP_'||v_date||'.LOG',
          DIRECTORY     => 'DATAPUMP',
          FILETYPE     => v_logfile) ;
     DBMS_DATAPUMP.METADATA_FILTER(
          HANDLE          => v_dp_job_handle,
          NAME          => 'SCHEMA_EXPR',
          VALUE          => '= '''||v_project||''' ') ;
     DBMS_DATAPUMP.START_JOB(v_dp_job_handle) ;
     v_percent_done := 0 ;
     v_job_state := 'UNDEFINED' ;
     WHILE (v_job_state != 'COMPLETED') AND (v_job_state != 'STOPPED')
     LOOP
          DBMS_DATAPUMP.GET_STATUS(
               v_dp_job_handle,
               DBMS_DATAPUMP.KU$_STATUS_JOB_ERROR + DBMS_DATAPUMP.KU$_STATUS_JOB_STATUS + DBMS_DATAPUMP.KU$_STATUS_WIP,
               -1,
               v_job_state,
               v_status) ;
               v_job_status := v_status.JOB_STATUS ;
          IF v_job_status.PERCENT_DONE != v_percent_done THEN
               DBMS_OUTPUT.PUT_LINE('*** Job percent done = '||TO_CHAR(v_job_status.PERCENT_DONE)) ;
               v_percent_done := v_job_status.PERCENT_DONE ;
          END IF ;
          IF BITAND(v_status.MASK, DBMS_DATAPUMP.KU$_STATUS_WIP) != 0 THEN
               v_message := v_status.WIP ;
          ELSIF BITAND(v_status.mask, DBMS_DATAPUMP.KU$_STATUS_JOB_ERROR) != 0 THEN
               v_message := v_status.ERROR ;
          ELSE
               v_message := NULL ;
          END IF ;
          IF v_message IS NOT NULL THEN
               v_count := v_message.FIRST ;
               WHILE v_count IS NOT NULL
               LOOP
                    DBMS_OUTPUT.PUT_LINE(v_message(v_count).LOGTEXT) ;
                    v_count := v_message.NEXT(v_count) ;
               END LOOP ;
          END IF ;
     END LOOP ;
     DBMS_OUTPUT.PUT_LINE('Job has completed') ;
     DBMS_OUTPUT.PUT_LINE('Final job state = '||v_job_state) ;
     DBMS_DATAPUMP.DETACH(v_dp_job_handle) ;
END ;

But the application we have that uses the database cannot be changed to read from a CLOBWhy can't you change the application?
Well, anyway you should point out to your superiors that Oracle documented years ago to not use LONGS anymore...
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/datatype.htm#sthref3806
It clearly states:
LONG Datatype
Note:
Do not create tables with LONG columns. Use LOB columns (CLOB, NCLOB) instead. LONG columns are supported only for backward compatibility.
Oracle also recommends that you convert existing LONG columns to LOB columns. LOB columns are subject to far fewer restrictions than LONG columns. Further, LOB functionality is enhanced in every release, whereas LONG functionality has been static for several releases.
How do I go from CLOB to LONG?I'm sorry, cannot help you on that one, I don't think you can do that at all (Oracle wants us to stop using LONGS, so, it's a one-way conversion...):
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1037232794454#15512131314505
So: NO built_in, you'll need to write a program if the clob is ALWAYS LESS THAN 32k in size, you can use plsql..but is that the case in your case? Only you know that.
I believe that question is still unanswered on this forum, but you might try searchin for answers on this forum, and
the 'Database-General' forum: General Database Discussions
Perhaps you can google a Q&D workaround...
( And consider convincing your collegues to just convert your LONGS to LOBS)
Edited by: hoek on Apr 8, 2009 5:43 PM

Execution of Clob through dynamic sql

Hi,
Here in below code.I am trying to execute the CLOB dynamically.Its giving an error as
ORA-6502
Numeric or value error.
Declare
SQL3 CLOB := '';
SQLSTRING1 LONG;
SQLSTRING2 LONG;
SQLSTRING3 LONG;
Begin
SQL3 := GENUPD(RECTABLE => 'REC_TARGET_TABLE',
TGTTABLE =>'TARGET_TABLE',
AUDITTABLE => 'DATA_AUDIT_DETAILS');
SQLSTRING1 := DBMS_LOB.SUBSTR(SQL3, 8000, 1);
SQLSTRING2 := DBMS_LOB.SUBSTR(SQL3, 8000, 8001);
SQLSTRING3 := DBMS_LOB.SUBSTR(SQL3, 8000, 16001);
EXECUTE IMMEDIATE SQLSTRING1 || SQLSTRING2 || SQLSTRING3 ;
When I am doing the same in below way its giving an above error
for i in 0 .. 2 loop
SQLSTRING1 := SQLSTRING1 ||
DBMS_LOB.SUBSTR(SQL3, 8000, 8000 * i +
end loop;
EXECUTE IMMEDIATE SQLSTRING1;
end;
Is there any way to write the aboive code in optimized manner.
Any help really appreciated.
Thanks in Advance

DECLARE
stmt_str varchar2(200);
cur_hdl int;
rows_processed int;
name varchar2(10);
salary int;
v_type DBMS_SQL.varchar2s;
BEGIN
cur_hdl := dbms_sql.open_cursor;
v_type(1) := 'SELECT 1'||chr(10);
v_type(2) := ' FROM DUAL'||chr(10);
DBMS_SQL.PARSE ( c                  => cur_hdl,
                   statement          => v_type,
                   lb                 => 1,
                   ub                 => 2,
                   lfflg              => FALSE,
                   language_flag      => dbms_sql.native );
-- describe defines
dbms_sql.define_column(cur_hdl, 1, name, 200);
rows_processed := dbms_sql.execute(cur_hdl);
LOOP
      -- fetch a row
      IF dbms_sql.fetch_rows(cur_hdl) > 0 then
      -- fetch columns from the row
      dbms_sql.column_value(cur_hdl, 1, name);
      Dbms_Output.put_line(name);
      ELSE
        EXIT;
      END IF;
END LOOP;
dbms_sql.close_cursor(cur_hdl); -- close cursor
END;

Extracting data from clobs

Hi,
I want to get the first line from a comments field. The data type is set to clob. I use the below section to get the data from the first line
Replace(dbms_lob.substr(comments,instr(comments,chr(10),1),1), Chr(10), '' ) from
The issue I have is it only gets the first line if there is a second comments line due to the character line feed.
Is there a way of just getting the data back from the first line only even if the length of the line varies?
Thanks regards
Adam
Edited by: user3924223 on 30-Jan-2009 06:51

Adam
You can try
select substr ( comments                       -- you want to pull out a varchar
                   , 1                                   -- if you want the very first line
                   , case instr(comments,chr(10)) when 0 then 100 else instr(comments,chr(10)) end    -- capture to chr(10) if present, or to 100 chars if not
from   yourtable
/Note: if the CLOB is longer than the max SQL varchar supported on your Oracle version (4000 on 9i iirc), you can use DBMS_LOB.SUBSTR and DBMS_LOB.INSTR. If you are doing this programmatically rather than in SQL, you can save the INSTR result into a local variable
HTH
Regards Nigel

CLOB to LONG

Similar Messages

Maybe you are looking for