Long column as a datatype in htmlDB

Why am I not able to add a long column or display a long
column using htmlDB?
I am trying to add a new column of data type "LONG" to one of my tables and I am not seeing "LONG" as an option in the "Type" list provided by -->Workspace Sudheshna>SQL Workshop>Manage Table.
Thank you.

Long columns were deprecated several years ago as I remember it. They only exist now for legacy support. Use CLOB.
Thanks,
Tyler

Similar Messages

Selecting data from a table which has a LONG column

hi all,
In the table user_views there is a LONG column. Now i want to select rows from that table based on this LONG column. like....
select *from user_views where text like '%account%;
but i am getting the error.."ORA-00932: Inconsistent datatypes:Expected NUMBER got LONG".
How do I overcome this error.
Please give me some suggestions.
Thanks & Regards,
Vijay

In the table user_views there is a LONG column. Now i want to select rows from that >table based on this LONG column. like....LONG columns cannot appear in a WHERE or
AND clause.

Change Tablespace of a table with LONG column

I have a 9i database that I have just gotten control of. At this point there is just one big dictionary managed tablespace for everything created by users. I am trying to move to multiple locally managed tablespaces with fixed extent sizes but I have run into a problem.
I have one table with one LONG datatype column. Apparently there is a huge amount of work involved to change the code if I make it a BLOB so that is out.
At this point I would like to change the tablespace of this table but I can't move it the normal way because of the LONG column. I have found mention of being able to do this with "COPY" but I can't find any documentation on the "COPY" command in the 9i Docs.
Any help would be appreciated,
Chris S.

Chris-
Can't you create your new table ahead of time in your new tablespace?
You could then use a statement like:
COPY FROM old/your_password@olddb TO new/your_password@newdb -
REPLACE NEWTABLE -
USING SELECT * FROM OLDTABLE;

Select LONG column from Remote table

Hi to all.
I have the following problem: I can't select a LONG column from remote database, when there are Join operation in the query. Example:
SELECT long_column FROM remote_table@DB
-> that's OK, but:
SELECT long_column FROM remote_table@DB INNER JOIN remote_table2@DB ON ...
-> returns: "ORA-00997: Illegal use of LONG datatype"
I cannot even perform (because there a LONG column in the joined table):
SELECT nonlong_column FROM remote_table@DB INNER JOIN remote_table2@DB ON ...
That's very strange to me because:
SELECT long_column FROM local_table INNER JOIN local_table2 ON ...
-> is OK!
Can someone help me to SELECT a long column from remote in SELECT query with JOIN clause!
Thanks a lot!

Hi
"Distributed queries are currently subject to the restriction that all tables locked by a FOR UPDATE clause and all tables with LONG columns selected by the query must be located on the same database. " by otn docs.
I have no idea.
Ott Karesz
http://www.trendo-kft.hu

How to retrieve 'long' column with 32K length in Java stored procedure

For some reasons, we are not using CLOB, BLOB, or BFILE to store large objects and I have to live with LONG. So I wrote a Java stored procedure to insert, select and manipulate a LONG column by retrieving the LONG into a java.lang.String class (which happens to be the Java class mapped to the LONG SQL datatype). It all works fine as long as the length of the value being retrieved is less than the magic figure of 32767 bytes (which is the restriction on LONG and VARCHAR2 datatype in PL/SQL as well). So looks like Oracle's implementation of the JVM limits String values to a max of 32767 bytes. Suggestions on how to overcome this limitation (other classes that you suggest or do I have to move to files)?
Thanks,
Jeet
null

the jvm has nothing to do with it ...
this is a pol/sql limitation on parameters in stored procedures.
and java stored procedures require a clal spec that makes the j-s-p look like a pl/qsl stored proc.

How can find out LONG column database?

Hi,
in my database ORA-1461 error occured
01461, 00000, "can bind a LONG value only for insert into a LONG column
how can find out LONG column in my database ?

DESCRIBE
The description for tables, views, types and synonyms contains the following information:
each column's name
whether or not null values are allowed (NULL or NOT NULL) for each column
datatype of columns, for example, CHAR, DATE, LONG, LONGRAW, NUMBER, RAW, ROWID, VARCHAR2 (VARCHAR), or XMLType
precision of columns (and scale, if any, for a numeric column)
Extract of the link;
http://download.oracle.com/docs/cd/B19306_01/server.102/b14357/ch12019.htm#SQPUG040
Secondly with reference to the error;
Do not try to insert LONG datatypes into other types of columns.
Hope this helps.
Adith

Select LONG column into CLOB variable

Hi all,
I am trying retrieve the data present in a LONG column into a CLOB variable.
However I am getting an error, pls let me know how I can resolve it.
DECLARE
v_text CLOB;
BEGIN
SELECT TO_LOB(trigger_body)
INTO v_text
FROM
user_triggers
WHERE
ROWNUM <= 1;
END;
ERROR at line 8:
ORA-06550: line 8, column 20:
PL/SQL: ORA-00932: inconsistent datatypes: expected NUMBER got LONG
ORA-06550: line 8, column 5:
PL/SQL: SQL Statement ignored
Let me know if there is an alternate to this. I would like to get the data present in the LONG column into a variable.
The reason why I am not retrieving the LONG column into LONG variable is stated below (from Oracle Website):
You can insert any LONG value into a LONG database column because the maximum width of a LONG column is 2**31 bytes.
However, you cannot retrieve a value longer than 32760 bytes from a LONG column into a LONG variable.
Thanks and Regards,
Somu

There are couple of things I did (listed in order):
1) Create Global Temporary Table containing a CLOB column
2) Select LONG column and convert to CLOB by using TO_LOB and insert into Global Temporary Table containing a CLOB column
2) Select from this Global Temporary Table (which already contains data in CLOB) and assign it to a CLOB variable.
This is done because you can not directly use TO_LOB in a select statement to assign the value to a CLOB variable.
Stated below is an example:
-- Create Temporary Table
CREATE GLOBAL TEMPORARY TABLE glb_tmp_table_lob(
time TIMESTAMP WITH LOCAL TIME ZONE,
text CLOB
ON COMMIT DELETE ROWS;
-- PL/SQL Block to Execute
DECLARE
v_clob CLOB;
BEGIN
-- Insert into Temporary Table by converting LONG into CLOB
INSERT INTO glb_tmp_table_lob (
time ,
text
SELECT
sysdate ,
TO_LOB(dv.text)
FROM
dba_views dv
WHERE
ROWNUM <= 1
-- Select from the Temporary table into the variable
SELECT
gt.text
INTO
v_clob
FROM
glb_tmp_table_lob gt;
COMMIT;
-- Now you can use the CLOB variable as per your needs.
END;
/

Updating a LONG column !!!!

I have a column defined as a LONG in a table, I am trying to
update that column through a loop, everytime I update I have to
concatenate that with a new string, that's my requirement.
example:
update my_long_table
set my_long_column = my_long_column || 'My String';
but, it is not allowing me to do this operation as throws
"incosistent datatypes" error, how can I do this update
operation ?
can anyone help me out in this, I really appreciate your help.
you can email me at [email protected] or reply to my message.
Thanks in Advance,
$rinivas C.

A LONG is not a VARCHAR2; that's why you get the error message
that you do. It is very difficult to manipulate LONG columns:
they're really intended to hold information rather than data, so
Oracle made an assumption that people wouldn't want to do the
sort of thing you're trying to do. Personally I curse the
inventor of the LONG each time I try to manipulate the test of a
view by selecting from USER_VIEWS.
if you have any choice in the matter I suggest you redesign the
table to avoid the use of LONG - 8i supports VARCHAR2(32K) which
ought to be long enough to hold most things.
If that's not an option try looking at the DBMS_LOB package.
Using its procedures you can write a function that turns the LONG
into an array of VARCHARs, append your text and then squirt the
VARCHARs back into a LONG.
I'm not saying it'll be pretty, but it's the only game in town.
Good luck, APC

How to create a concatenated index with a long column (Urgent!!)

We have a situation where we need to create a concatenated unique
index with one of the columns as a "long" datatype. Oracle does
not allow a lot of things with long columns.
Does anyone know if this is possible or if there is a way to get
around it.
All help is appreciated!!!!

From the Oracle SQL Reference ...
"You cannot create an index on columns or attributes whose
type is user-defined, LONG, LONG RAW, LOB, or REF,
except that Oracle supports an index on REF type columns
or attributes that have been defined with a SCOPE clause."
Doesn't mention CLOB or BLOB types, so perhaps you
should consider using one of those types instead. I have a
feeling that the LONG type is now deprecated.

Can I increase the size of a Long column to 4000 characters?

Can I increase the size of a Long column to 4000 characters?

maximum sizeof 4 GB -1 byte RTFM there: Datatypes(click)
extracted: LONG: Character data of variable length up to 2 gigabytes, or 231 -1 bytes.
Not 4Gb. Or also, read Paul M post.
Regards,
Yoann.

LONG column Manipulation

Hi,
I want to put a message at a paricular position in a long column like
LONG Value Part1 ||message || LONG Value Part2.
As every body knows i can't use SUBSTR for the same since the Data Type is long and at the same time i can't change the dataType also.
So requesting you to provide some solution.....
Thanks
Dhabas

You want something like this ?
SQL> Create table with_long (long_dt LONG);
Table created.
SQL> insert into with_long values('This is a long datatype');
1 row created.
SQL> declare
2 l_tmp long;
3 l_str long;
4 begin
5 select long_dt into l_tmp from with_long;
6 l_str:=substr(l_tmp,1,10)||' long '||substr(l_tmp,14);
7 insert into with_long values(l_str);
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> select * from with_long;
LONG_DT
This is a long datatype
This is a long g datatypeAlso you might want to consult Oracle Documentation and Metalink/Asktom for examples.
By the way, If your long value is more than 32k then just convert it into lob and use the same approach.
Edited by: Saubhik on May 19, 2010 3:18 AM

LONG column handling problem

Hi all,
How can I read the LONG datatype column from table and insert the same LONG content into LONG column of another table ?
regards
sanjay

I did the following test in 10g but not with 8i:
dev001> set serveroutput on
dev001>
dev001> declare
2 v_b blob;
3 v_c varchar2(10);
4 begin
5 v_b := utl_raw.cast_to_raw('OK');
6 v_c := utl_raw.cast_to_varchar2(v_b);
7 dbms_output.put_line(v_c);
8 end;
9 /
OK
PL/SQL procedure successfully completed.However it is not a good idea to use BLOB data type to store character data: you should use CLOB for character data and BLOB for binary data.

Type long columns

I can't do "insert as select" statement on tables with long type column.

you will need to create some conversion codes to have the long converted into varchar2 datatype.
CREATE OR REPLACE Function convert_long_to_char( pTableName in varchar2,
                                                   pColumnName in varchar2,
                                                   pRowId in rowid ) return varchar2 As
    vCursor    integer default dbms_sql.open_cursor;
    vN         number;
    vLongVal varchar2(4000);
    vLongLen number;
    vBuflen    number := 4000;
    vCurPos    number := 0;
begin
    dbms_sql.parse( vCursor,'select ' || pColumnName || ' from ' || pTableName ||
                                                          ' where rowid = :x',
                    dbms_sql.native );
    dbms_sql.bind_variable( vCursor, ':x', pRowId );
    dbms_sql.define_column_long(vCursor, 1);
    vN := dbms_sql.execute(vCursor);
    if (dbms_sql.fetch_rows(vCursor)>0) then
      dbms_sql.column_value_long(vCursor, 1, vBuflen, vCurpos ,
                                 vLongVal, vLongLen );
    end if;
    dbms_sql.close_cursor(vCursor);
    return vLongVal;
end convert_long_to_char;
SQL> describe tmp1;
   Name                                      Null?    Type
   P_CODE                                             LONG
SQL> select p_code from tmp1;
P_CODE
1234567890 ABCDEFGHIJKLMNOPQRSTUVWXYZ 0987654321 QAZWSXEDCRFVTGBYHNUJMIKOLP 0192
SQL> describe tmp2;
   Name                                      Null?    Type
   P_CODE                                             LONG
SQL> select p_code from tmp2;
no rows selected
SQL> insert into tmp2
    2 select p_code from tmp1;
select p_code from tmp1
ERROR at line 2:
ORA-00997: illegal use of LONG datatype
SQL> insert into tmp2
    2 select convert_long_to_char('tmp1','p_code',rowid) p_code from tmp1;
1 row created.
SQL> commit;

Error ORA-01461: can bind a LONG value only for insert into a LONG column

Within an existing application , i need to create a new report , i created a new page in it and then tried to create classic report , during wizard when i enter the same query which i have used for previous page , it gives me following error during the creation of report.
The following bind variable i have already used for previous page. I want to reuse the same bind variables. There is no any long dataype within column predicates.
Error ORA-01461: can bind a LONG value only for insert into a LONG column
OK
Following is the query
SELECT
   "VWSR_ALL_MERGED_DATA_MV"."SR_AREA" "SR_AREA",
   "VWSR_ALL_MERGED_DATA_MV"."SR_STATUS" "SR_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_SUB_STATUS" "SR_SUB_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_CREATED" "SR_DATE_CREATED",
   "VWSR_ALL_MERGED_DATA_MV"."SR_OPEN_DATE" "SR_OPEN_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CLOSED_DATE" "SR_CLOSED_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT1" "SR_PRODUCT1",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT2" "SR_PRODUCT2",
   "VWSR_ALL_MERGED_DATA_MV"."SR_TIO_PRIORITY" "SR_TIO_PRIORITY",
   "VWSR_ALL_MERGED_DATA_MV"."SR_REF_NUMBER" "SR_REF_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_RECD" "SR_DATE_RECD",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CIDN" "SR_CIDN",
   "VWSR_ALL_MERGED_DATA_MV"."SR_BUS_UNIT" "SR_BUS_UNIT",
   "VWSR_ALL_MERGED_DATA_MV"."SR_NUMBER" "SR_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SOURCE_SYSTEM" "SOURCE_SYSTEM",
   "VWSR_ALL_MERGED_DATA_MV"."BATCH_ID" "BATCH_ID"
FROM VWSR_ALL_MERGED_DATA_MV
WHERE trunc(VWSR_ALL_MERGED_DATA_MV.SR_DATE_RECD)=trunc(sysdate-1)
AND VWSR_ALL_MERGED_DATA_MV.SR_TIO_PRIORITY IN
                                                :P2_SR_TIO_PRIORITY
                                               ,'CEO'
                                               ,'TER'
                                               ,'Priority Assistance'
                                               ,'Enquiry'
AND   (
        (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                                     'Business Support and Improvement'
                                   , 'Finance and Administration'
                                   , 'Cust Sat Simplification and Productivity'
                                   , 'Project New and Customer Experience'
                                   , 'Corp Strategy and Customer Experience'
                                   , 'Other'
            AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('BS&I'))
   OR   (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                                     'Consumer'
                                   , 'Consumer Telstra Country Wide'
                                   , 'Customer Service and Sales'
                                   , 'Offshore Sales and Service'
                                   , 'TC and TCW Operations'
                                   , 'Telstra Country Wide'
                                   , 'Other'
            AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TC&C'))
   OR   (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                         'Telstra Customer Sales and Service'
                        ,'Telstra Program Office'
                        ,'Human Resources'
                        ,'IT'
                        ,'Unallocated'
                        ,'Other'
            AND :P2_SR_BUSINESS_UNIT= 'OTHER')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                    'Telstra Operations'
                   ,'Telstra Networks and Services'
                   ,'Other'
            AND :P2_SR_BUSINESS_UNIT= 'TO')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Business'
            AND :P2_SR_BUSINESS_UNIT= 'TB')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Wholesale'
            AND :P2_SR_BUSINESS_UNIT= 'TW')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Enterprise and Government'
            AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TE&G'))
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Sensis'
                 ,'Sensis Pty Ltd'
            AND :P2_SR_BUSINESS_UNIT= 'SENSIS')
AND :P2_SR_TIO_PRIORITY = 'Level 0'
UNION
SELECT
   "VWSR_ALL_MERGED_DATA_MV"."SR_AREA" "SR_AREA",
   "VWSR_ALL_MERGED_DATA_MV"."SR_STATUS" "SR_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_SUB_STATUS" "SR_SUB_STATUS",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_CREATED" "SR_DATE_CREATED",
   "VWSR_ALL_MERGED_DATA_MV"."SR_OPEN_DATE" "SR_OPEN_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CLOSED_DATE" "SR_CLOSED_DATE",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT1" "SR_PRODUCT1",
   "VWSR_ALL_MERGED_DATA_MV"."SR_PRODUCT2" "SR_PRODUCT2",
   "VWSR_ALL_MERGED_DATA_MV"."SR_TIO_PRIORITY" "SR_TIO_PRIORITY",
   "VWSR_ALL_MERGED_DATA_MV"."SR_REF_NUMBER" "SR_REF_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SR_DATE_RECD" "SR_DATE_RECD",
   "VWSR_ALL_MERGED_DATA_MV"."SR_CIDN" "SR_CIDN",
   "VWSR_ALL_MERGED_DATA_MV"."SR_BUS_UNIT" "SR_BUS_UNIT",
   "VWSR_ALL_MERGED_DATA_MV"."SR_NUMBER" "SR_NUMBER",
   "VWSR_ALL_MERGED_DATA_MV"."SOURCE_SYSTEM" "SOURCE_SYSTEM",
   "VWSR_ALL_MERGED_DATA_MV"."BATCH_ID" "BATCH_ID"
FROM
   VWSR_ALL_MERGED_DATA_MV
WHERE trunc(VWSR_ALL_MERGED_DATA_MV.SR_DATE_RECD)=trunc(sysdate-1)
   and VWSR_ALL_MERGED_DATA_MV.SR_TIO_PRIORITY IN (:P2_SR_TIO_PRIORITY)
AND (
     (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN (
                     'Business Support and Improvement'
                   , 'Finance and Administration'
                   , 'Cust Sat Simplification and Productivity'
                   , 'Project New and Customer Experience'
                   , 'Corp Strategy and Customer Experience'
                   , 'Other'
AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('BS&I'))
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN (
                     'Consumer'
                   , 'Consumer Telstra Country Wide'
                   , 'Customer Service and Sales'
                   , 'Offshore Sales and Service'
                   , 'TC and TCW Operations'
                   , 'Telstra Country Wide'
                   , 'Other')
AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TC&C'))
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                         'Telstra Customer Sales and Service'
                        ,'Telstra Program Office'
                        ,'Human Resources'
                        ,'IT'
                        ,'Unallocated'
                        ,'Other'
        AND :P2_SR_BUSINESS_UNIT= 'OTHER')
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                      'Telstra Operations'
                      ,'Telstra Networks and Services'
                      ,'Other'
        AND :P2_SR_BUSINESS_UNIT= 'TO')
OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                     'Telstra Business'
        AND :P2_SR_BUSINESS_UNIT= 'TB')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Wholesale'
        AND :P2_SR_BUSINESS_UNIT= 'TW')
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Telstra Enterprise and Government'
        AND :P2_SR_BUSINESS_UNIT= htf.escape_sc('TE&G'))
   OR (VWSR_ALL_MERGED_DATA_MV.SR_BUS_UNIT IN
                  'Sensis'
                 ,'Sensis Pty Ltd'
        AND :P2_SR_BUSINESS_UNIT= 'SENSIS')
AND :P2_SR_TIO_PRIORITY = 'Level 1'Edited by: user13653962 on 30/01/2013 15:11
Edited by: user13653962 on 30/01/2013 15:14

You have an error in the code:
1. you don't provide a value for 'what' - you have to tell Oracle what it should execute when it submits the job.
And remember - with ISUBMIT the next_date parameter has datatype VARCHAR2 - SUBMIT uses datatype DATE. So make sure you provide a VARCHAR2 value and do not rely on implicit conversion.
>
PROCEDURE DBMS_JOB.ISUBMIT
(job IN BINARY_INTEGER
,what IN VARCHAR2
,next_date IN VARCHAR2
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);
PROCEDURE DBMS_JOB.SUBMIT
(job OUT BINARY_INTEGER
,what IN VARCHAR2
,next_date IN DATE DEFAULT SYSDATE
,interval IN VARCHAR2 DEFAULT 'null'
,no_parse IN BOOLEAN DEFAULT FALSE);

Table with a Long column

I had a problem, when i am creating a table with the SQL -->
"create table tab2 as (select * from tab1); "
i get an error --> ORA-00997: illegal use of LONG datatype
This i figured out happened because tab1 has a long column.
How to recreate a table with long column ?
null

You could use the COPY feature once your second table is created:
DROP TABLE one
DROP TABLE two
CREATE TABLE one
(n NUMBER
,l LONG)
INSERT INTO one
VALUES
(1
,'123'
CREATE TABLE two
(n NUMBER
,l LONG)
COPY FROM apps/apps@dblink TO apps/apps@dblink APPEND two USING SELECT * FROM one
SELECT * FROM one
SELECT * FROM two
null

Long column as a datatype in htmlDB

Similar Messages

Maybe you are looking for