Long data type value does not block PL/SQL

Similar Questions

• ODI-15005: data type "varchar" does not close in technology: file?

  Hello

  I created the interface that loads data from flat file (source) oracle (target).

  For this, I took LKM SQL FOR SQL and SQL TO ADD FILE IKM.

  Please check the source and target data types.

  

  When I am executing this interface, I get the error as

  ODI-15005: data type "varchar" does not close in technology: file.

  
  

  To resolve this error, I changed the types of flat file data.

  I went to the Manager of topology-> select technology of files-> data types: string - > orcle to the number data type.

  Even if I do not correct this error. Please help me.

  
  

  Thanks in advance,

  A.Kavya.
  

  Hello

  Can you please check what are the data types for the columns in your data target store. As you say it's a file, can you check if the data type for the two columns has the String value (and not varchar).

  Thank you

  Ajay

• Date of Condition does not, not cming point value.

  Hi friends,
  
  I create a form to place order and I have created a MASTER table for fixed point rate between two appointments with price as A, B, C, D code.
  
  In the form, I for item
  
  : P1_ORDER_DATE
  : P1_ITEM_CODE
  : P1_PRICE_CATEGORY check the mailing list
  
  : P1_ITEM_RATE
  
  Rate of point, I put in Source,
  Source Type SQL - Quary
  Vale of source
  

  select RATE_1 from SAM_ITEM_MAS where ITEM_CODE =:P1_ITEM_CODE and  PRICE_CATEGORY=:P1_PRICE_CATEGORY and :P1_ORDER_DATE
   between FROM_DATE and TO_DATE

  My Table
  

  CREATE TABLE  "SAM_ITEM_MAS" 
     (     "ID" NUMBER NOT NULL ENABLE, 
       "ITEM_CODE" NUMBER, 
       "PRICE_CATEGORY" VARCHAR2(5), 
       "FROM_DATE" DATE, 
       "TO_DATE" DATE, 
       "RATE_1" NUMBER, 
       CONSTRAINT "SAM_ITEM_MAS_PK" PRIMARY KEY ("ID") ENABLE
     )
  /

  that does not code but if I run this code in the SQL command, then there working fine.but not to the order of the DAY: P1_ITEM_RATE.
  
  I want when I select P1_PRICE_CATEGORY as A, B, C, D, then the respective rates of Table SAM_ITEM_MAS should come point: P1_ITEM_RATE.
  
  Date condition oredr does not work.
  
  Thank you
  
  Published by: 805629 on December 28, 2010 23:32

  Hello

  Have you tried running the item as dates using TO_DATE() values:

  select RATE_1
  from SAM_ITEM_MAS
  where ITEM_CODE =:P1_ITEM_CODE
  and  PRICE_CATEGORY=:P1_PRICE_CATEGORY
  and TO_DATE(:P1_ORDER_DATE,'DD/MM/YYYY') between "FROM_DATE" AND "TO_DATE"
  

  (change the date format string to match the format of the page P1_ORDER_DATE element)

  You should probably change the name of the field to something else that TO_DATE since it is a name of Oracle function - try DATE_FROM and DATE_TO start_date and end_date or something like that. Otherwise, you need to use double quotes, as I have indicated above

  Andy

• How to insert the value of a LONG data type?

  Hi all
  
  Developers what to change the type of data in the PRODUCTS table.
  
  PRODUCT
  ======
  ID number (10) not null,
  NAME varchar2 (50) not null,
  DESCR varchar2 (250) not null
  
  
  They want the DESCR to change datataype at LENGTH
  
  So I got back it up first:
  
  create the table product_bak in select * from product;
  remove the product;
  change the product table change (descr, null);
  Edit the product table change (long descr);
  Insert into select product * from product_bak;
  
  ORA - 997 - illegal use of LONG data type
  
  
  How can I recover my data?
  
  
  Thank you very much.

  Use TO_LOB to convert long on the CLOB type, then use TO_CHAR to convert CLOB VARCHAR2.

• Error (21,100): PL/SQL: ORA-00997: illegal use of the LONG data type

  CREATE or REPLACE (name in varchar2) procedure Compress_tab_partition
  is
  last_mnth_var varchar2 (8);
  curr_mnth_var varchar2 (8);
  number of last_mnth;
  number of curr_mnth;
  last_partition varchar2 (8);
  high_val varchar2 (4000);
  Start

  Select to_char (add_months (trunc (sysdate, 'MM'),-1), 'YYYYMM') | ' 00' in the double last_mnth_var;
  Select to_char (sysdate, 'YYYY') | TO_CHAR (sysdate, 'mm') | ' 00' in the double curr_mnth_var;
  Select to_number (last_mnth_var) in the double last_mnth;
  Select to_number (curr_mnth_var) in the double curr_mnth;

  Dbms_output.put_line ('Compression of GOLDMGR Table scores.' | table-name |) "to go". ») ;
  Dbms_output.put_line(' ');

  / * Step 1 - identify the name of the partition of the specified table must be compressed * /.
  Select high_value from high_val from user_tab_partitions where table_name = table-name;
  Select nom_partition into last_partition from user_tab_partitions where table_name = table-name and high_value = rtrim (high_val);

  / * Step 2 - Alter partition table to compress * /.

  run immediately "ALTER TABLE GOLDMGR." | table_name | ' CHANGE THE PARTITION '. last_partition | "COMPRESS by low query";

  / * Step 3 - Index rebuild step * /.

  I'm in (select index_name in user_indexes where table_name = table-name)
  loop
  run immediately "ALTER INDEX GOLDMGR." | i.index_name |' REBUILD ";
  end loop;

  Dbms_output.put_line (' COMPLETED: compress the Table partitions change.) ") ;

  end;
  /

  I'm getting an error like: Error (21,100): PL/SQL: ORA-00997: illegal use of the LONG data type

  Please resolve.

  HIGH_VALUE datatype is LONG. You may not use for a long TIME in WHERE clause expressions. You need to loop through the partitions by selecting HIGH_VALUE and then comparing. Secondly, there is no need to select double to calculate expressions. For example:

  Select to_char (add_months (trunc (sysdate, 'MM'),-1), 'YYYYMM') | ' 00' in the double last_mnth_var;

  should be replaced by

  last_mnth_var: = to_char (add_months (trunc (sysdate, 'MM'),-1), 'YYYYMM') | ' 00'.

  and there is no need to add_months here:

  last_mnth_var: = to_char (trunc (sysdate, 'MM') - 1, "YYYYMM"). ' 00'.

  But the main question is simply ALTER TABLE MODIFY PARTITION COMPRESS allows compression but does not compress. You must issue ALTER TABLE MOVE PARTITION COMPRESS:

  SQL > create table tbl (n) partition by range (n)
  2 (partition p1 values less than (maxvalue))
  3. Select lpad('X',4000,'X') from dual connect by level<=>
  4.

  Table created.

  SQL > select bytes
  2 from WHERE user_segments
  3 where nom_segment = 'TBL '.
  4 and nom_partition = 'P1 '.
  5.

  BYTES
  ----------
  830472192

  SQL > alter table tbl
  2. change the partition p1 compress
  3.

  Modified table.

  SQL > select bytes
  2 from WHERE user_segments
  3 where nom_segment = 'TBL '.
  4 and nom_partition = 'P1 '.
  5.

  BYTES
  ----------
  830472192

  SQL > alter table tbl
  2. move the partition p1 compress
  3.

  Modified table.

  SQL > select bytes
  2 from WHERE user_segments
  3 where nom_segment = 'TBL '.
  4 and nom_partition = 'P1 '.
  5.

  BYTES
  ----------
  8388608

  SQL >

  SY.

• Using DBMS_DATAPUMP with the LONG data type

  I have a procedure below that calls the DBMS_DATAPUMP procedure using a REMOTE_LINK move a schema of one database to another. However, some tables in this schema have columns with the data type of LONG. And when I run it I get an error saying that you cannot move the data with the LONG data type using a REMOTE CONNECTION. So no data in these specific tables gets flying over.
  
  Does anyone else have this problem? If so, do you have a work around? I tried to add a CLOB column in my table and affecting the new CLOB equal THROUGHOUT, but I couldn't get that to not work either... even when I tried to use a TO_LOB. If I could get that pass, then I could just slide ALONG, the schema, and then re-create the LONG column on the opposite side.
  
  Here is my procedure...
  
  
  
  DECLARE
  / * IMPORT/EXPORT VARIABLES * /.
  v_dp_job_handle NUMBER;          -The handful of job data pump
  v_count NUMBER;          -Index of the loop
  v_percent_done NUMBER;          -Percentage of job complete
  v_job_state VARCHAR2 (30);     -To keep track of job status
  v_message KU$ _LOGENTRY;     -For error messages and work in PROGRESS
  v_job_status KU$ _JOBSTATUS;     -The State of the work of get_status
  v_status KU$ _STATUS;     -The status returned by get_status object
  v_logfile NUMBER;
  T_DATE VARCHAR2 (13).
  v_source_server_name VARCHAR2 (50);
  v_destination_server_name VARCHAR2 (50);
  
  BEGIN
  v_project: = 'TEST ';
  T_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_' | T_DATE,
  VERSION = > 'LAST');
  
  v_logfile: = DBMS_DATAPUMP. KU$ _FILE_TYPE_LOG_FILE;
  
  DBMS_DATAPUMP. ADD_FILE)
  MANAGE = > v_dp_job_handle,
  FILENAME = > v_project | ' _EXP_' | T_DATE |'. JOURNAL '.
  DIRECTORY = > 'DATAPUMP. "
  FILETYPE = > v_logfile);
  
  DBMS_DATAPUMP. () METADATA_FILTER
  MANAGE = > 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 ('* percent of the job 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. WORK IN PROGRESS;
  ELSIF BITAND (v_status.mask, DBMS_DATAPUMP. KU$ _STATUS_JOB_ERROR)! = 0 THEN
  v_message: = v_status. ERROR;
  ON THE OTHER
  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 (' State of the Final work = ' | v_job_state);
  
  DBMS_DATAPUMP. Detach (v_dp_job_handle);
  END;

  TO_LOB can be used to insert, create table in select and update the instructions to convert

  So: You simply cannot use it in SELECT..., you can use CREATE TABLE BLAH AS SELECT TO_LOB (LONG_COLUMN) OF DREADED_TABLE_WITH_LONG_COL;

• Impact on performance when you use the LONG data type

  Hi all
  
  
  Only I have a doubt about the use of LONG data type
  
  I use the data type LONG for some columns in a table and I created indexes on the columns separately, but these column values can be easily fit into the varchar data type.
  
  (Just to see the performance on this issue)
  
  Suppose that a common select query with WHERE condition on any of the column which has LONG data type will affect the performance of the query?
  
  Please explain.
  
  Thank you

  (1) the LONG (and LONG RAW) data types have been depricated for quite a while. Oracle has been strongly recommends that you move to 8.1.5 CLOB and BLOB data types. Why you use the LONG data type? You're still on Oracle 7?

  (2) have you tried to write a query that has a WHERE condition that refers to a LONG column? In general, you can not because it does not support the type of data LONG. For example

  SQL> ed
  Wrote file afiedt.buf
  
    1  create table a (
    2    col1 varchar2(30),
    3    col2 long
    4* )
  SQL> /
  
  Table created.
  
  SQL> select * from a where col2='abc';
  select * from a where col2='abc'
                        *
  ERROR at line 1:
  ORA-00997: illegal use of LONG datatype
  

  LONG data types are a royal pain to work with. They also have implications on the performance of wicked on the client.

  Justin

• long data type in where clause

  Hello
  
  I need to select in an Oracle table with a column having
  Long data type and Oracle does not use this column in the
  WHERE clause. Doco Oracle suggests that the columns with LARGE data types may
  only be used in the select statement (not in the CASE or any other
  conditional clause).
  
  Anyone know any work around for this problem?
  
  What is the way to see the value of long data type?
  
  How can we use them in where clause?
  
  We can all utility to display the specified records? There are Lakes of records...
  
  
  I ned use it in where clause...
  
  Thanks and greetings
  VD
  
  Published by: vikrant dixit on November 23, 2008 22:47

  So can OK we use CLOB/BLOB in where clause?

  Yes, you can query the LOB columns using the package (F.ex.SUBSTR or INSTR) DBMS_LOB functions.

  Why u say that the result is FTS?

  This would result in FTS as you cannot index LARGE data or create a function based on the column index.

  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14200/sql_elements001.htm#sthref149

  
  LONG columns cannot be indexed.
  

  No other way to my knowledge.

  You can convert the LOB column with function TO_LOB as described in

  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14200/functions185.htm#i79464

  Published by: Sissi Kandi on November 24, 2008 12:28

• long data type error

  Hi all

  Hope all are fine, I got stuck in a query, and I need your help, I will be grateful for this.

  I was using the query below to copy all the data of table x to y.

  SQL > insert y select * from x@dblnkname;

  ERROR on line 1:

  ORA-00997: illegal use of the LONG data type

  I m getting the error above, tables x and there does not "long" datatype.your help will be appreciated, thanks in advance.

  DB: 11.2.0.3

  OS: RHEL 6.1

  Thank you

  Kind regards.

  copy of user/password@sid to user1/password@sid add user1.new_table using select * from user.old_table;

• How can I set the long data type by default

  a query that I want to run:

  exec DBMS_METADATA. SET_TRANSFORM_PARAM (DBMS_METADATA. False SESSION_TRANSFORM, 'SEGMENT_ATTRIBUTES',);

  result:

  E

  ;

  ;

  45

  ;

  45

  ;

  45

  ;

  45

  ;

  S

  45

  I'm not sure but maybe I need set the long size before the race top query. But when I try to put long size gives below error. Also, I put below an explanation so help.

  "The output of DBMS_METADATA.GET_DDL is a LONG data type." When you use SQL * Plus, your output may be truncated by default. "Deliver the following SQL * Plus command before issuing the DBMS_METADATA.GET_DDL statement to make sure your output is not truncated:

  SQL> SET LONG 9999

  error:

  Unhandled SET statement:

  "SET 9999 LONG."

  Change SQL * PLus (login.sql) user profile or the site profile (glogin.sql) and add:

  THE VALUE LONG 9999

  SY.

• View the long data type

  Hello
  
  I use coldfusion 7 and oracle 10g.
  
  I'm trying to display a field (aprconf_comment) who have a LONG data type and that is formatted with carriage return.
  The problem I have, is the maintenance of wagons return entered by the user.
  The text that is displayed is all in a single paragraph, that all the wagons back had been withdrawn.
  
  Does anyone know how to keep the return transport?
  
  Thank you
  Chantal
  
  Here is my select code
  < name cfquery "allWealth' datasource = #TheDataSrc # dbtype = #TheDataType = # >
  Select *.
  of avwh_bio_wealth
  where aprconf_pidm = ' #ThePidm #
  and aprsubj_subj_code = 'WHLT.
  < / cfquery >
  
  Here is my code to display
  < cfoutput query = "allWealth" >
  < b >
  < td align = "Left" > < class p = "text" > #aprconf_comment # < /p > < table >
  < /tr >
  < / cfoutput >

  For future references.

  In fact, looking for others, I found this function
  ParagraphFormat() worked a little better for me
  because the text remained inside the window, not as
  

  .

  I guess that ParagraphFormat() creates "soft returns.

  Thank you all,.
  Chantal

• long data type

  If USER_CONSTRAINTS. SEARCH_CONDITION is the LONG data type,
  How can filter us "NOT NULL" LINES in a SELECT Clause where:
  
  Select constraint_name
  of user_contraints
  where search_condition not like '% NO NLL %'
  
  
  Any ideas are appreciated! Thank you!

  Unfortunately you can not do this,

  The use of LONG values is subject to these restrictions:

  A table can have only one column.

  You cannot create an object with a long attribute type

  LONG columns may not appear in the WHERE clause or in integrity constraints (except that they may appear in null and NOT NULL value constraints).

  LONG columns cannot be indexed.

  Cannot specify LONG data in regular expressions.

  A stored function cannot return a value of type LONG.

  You can declare a variable or argument to a PL/SQL program unit using the long data type However, you cannot call then the SQL program unit.

  Within a single SQL statement, all the columns LONG, updated tables and locked tables must reside on the same database.

  LONG and LONG RAW columns cannot be used in distributed SQL queries and cannot be replicated.

  If a table has columns ALONG both LOB, then you can not bind more than 4000 bytes of data to the two LONG and LOB columns in the same SQL statement. However, you can bind more than 4000 bytes of data in the long RUN or the LOB column.

  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14200/sql_elements001.htm#SQLRF00201

• File error Windows Media Player mp4 "Windows Media Player cannot play the file. The player might not support the file type or does not support the codec used to compress the file"

  I got this error message when you try to play an MP4 video. Help please!

  Windows Media Player cannot play the file. The player might not support the file type or does not support the codec used to compress the file.

  You can try to download the http://www.microsoft.com/en-gb/download/details.aspx?id=507 Codec Installation Package

  If this does not work, you may need to get some third party software to convert MP4 video to the longer Windows Media Player video format supported like WMV, AVI in order to solve the problem

• OBIEE error - Datetime-01-01 value does not match the specified format

  I get this error after the promotion of Production. It works perfectly well on the Test Server.

  I am using SQL server. After launching the date as a varchar, it works fine.

  State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error occurred. [nQSError: 43113] The message returned by OBIS. [nQSError: 43119] Query Failed: [nQSError: 46046]-01-01 Datetime value does not match the specified format. (HY000)

  Gurus of OBIEE please help

  JD

  I found the solution as well.

  The Windows Server ODBC driver was old (Version 6). I have who has upgraded to SQL Server Native Client 11.0 and everything works fine.

• LONG data type in a database read-only

  I would only run this query...
  
  SELECT MAX (nrr_id) AS nrr_id, LENGTH (nrr_narrative) AS nrr_narrative_length
  Stories
  GROUP OF LENGTH (nrr_narrative)
  ORDER BY 2;
  
  The problem is, nrr_narrative is a LONG data type, so LENGTH won't work.
  
  I did the game of legs (on the web) and saw several interesting ways to get around this restriction for the long data type The problem is, they need either SysEx in a new table and redesign of the LONG like a LOB (or similar) or write a stored procedure or function that re - throws the column and returns the length. I can't do either (or one of the other more esoteric suggestions) because the table exists in a database I am not and that I don't have very few privileges.
  
  I could create a link to db on my server to the external source and make the overhaul in a table (or by using a stored procedure) on my server, but the connection is slow and even a simple select on a db link expires quite frequently.

  You can write the PL/SQL code. Something like:

  DECLARE
      TYPE nrr_id_tbl_type IS TABLE OF NUMBER
        INDEX BY PLS_INTEGER;
      v_nrr_id_tbl nrr_id_tbl_type;
      v_len NUMBER;
  BEGIN
      FOR v_rec IN (SELECT nrr_id,nrr_narrative FROM narratives) LOOP
        IF v_nrr_id_tbl.EXISTS(LENGTH(v_rec.nrr_narrative))
          THEN
            v_nrr_id_tbl(LENGTH(v_rec.nrr_narrative)) := GREATEST(
                                                                  v_nrr_id_tbl(LENGTH(v_rec.nrr_narrative)),
                                                                  v_rec.nrr_id
                                                                 );
          ELSE
            v_nrr_id_tbl(LENGTH(v_rec.nrr_narrative)) := v_rec.nrr_id;
        END IF;
      END LOOP;
      v_len := v_nrr_id_tbl.FIRST
      FOR v_i IN 1..v_nrr_id_tbl.COUNT LOOP
        DBMS_OUTPUT.PUT_LINE('LENGTH(nrr_narrative) = ' || v_len || ', MAX(nrr_id) = ' || v_nrr_id_tbl(v_len));
        v_len := v_nrr_id_tbl.NEXT(v_len);
      END LOOP;
  END;
  /
  

  SY.
  P.S. It will not work if nrr_narrative is greater than 32760, which is the maximum length of the LONG PL/SQL data type.

  Published by: Solomon Yakobson on 13 December 2011 14:52