Problems with the Long data type conversion

Similar Questions

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

• As an operator with the long data type

  Oracle 10g.

  Hi gurus

  I want to apply as an operator on the long data type, but I get the error message, can you please help me why is that I use as an operator with the long data type. I did some research and but unable to find a solution, see query for more details below...

  Query

  SELECT trigger_body FROM user_triggers

  WHERE trigger_body LIKE '% UPDA % CASE % ';

  Error

  ORA-00932: inconsistent data types: expected NUMBER got LONG

  00932 00000 - ' incompatible data types: wait %s %s got. "

  * Cause:

  * Action:

  Error on line: column 2: 7

  Concerning

  Muzz

  Adrian Billington wrote to the top of your options.

  working with long columns

• Problem with the CLOB data type.

  Greetings,
  
  I am facing a problem with the CLOB data type. I know that the CLOB data type is 4 GB (I use Oracle 9i). But in the Pl Sql procedure, I can only store 34305 size for a CLOB variable character data.
  
  This is the test script that I am trying to run.
  
  DECLARE
  -Local variables here*.
  I have INTEGER;
  C_1 CLOB.
  BEGIN
  FOR Rec IN (SELECT
  *
  ACCORDING TO THE TABLE)
  LOOP
  C_1: = c_1 | Rec.Clo_1;
  END LOOP;
  EXCEPTION
  WHILE OTHERS THEN
  Dbms_Output.put_line (SQLERRM);
  END;
  
  
  Here variable C_1 range value 34305 good character regardless of type CLOB. Now the above script fails if query my buckle - huge number of return values. It is throwing the exception "error during transfer of files ORA-06502: PL/SQL: digital error or value."
  
  He would be grateful if someone can help me on this.
  
  Thank you.

  You are probably better off using DBMS_LOB.append, instead of the concatenation of varchar2 (|).

  And... take off your when-other Manager exceptions, please...

• Syntex to create the table with the long data type

  I'm looking to create a table based on another table that having the column long data type. Throw the error ORA-00997: illegal use of the LONG data type

  
  I tired it

  create table abc_long (ag bgd long number);

  create table abc_long_dummy as ( ) Select *of abc_long); - ORA-00997 error: illegal use of the LONG data type

  How to get there?

  I'm looking to create a table based on another table that having the column long data type.

  You really don't want to do that.

  LONG data type has been deprecated for some time now, use CLOB.

  The TO_LOB() function will do the conversion on the fly:

  create table abc_long_dummy
  as
  select ag
       , to_lob(bgd) as bgd
  from abc_long ;
  

• problem with the blob data type

  Hello
  Hi just created a blob table data type and insert a text file of the directory - file "DG" and text contain text "Hello dba.
  
  CREATE TABLE blob_sample (id, NUMBER, blob_data BLOB);
  
  DECLARE
  l_bfile BFILE.
  l_blob BLOB;
  BEGIN
  INSERT INTO blob_sample (id, blob_data)
  VALUES (1, empty_blob())
  RETURN blob_data INTO l_blob;
  l_bfile: = BFILENAME ("'DG', ' hello.txt");
  DBMS_LOB. FileOpen (l_bfile, Dbms_Lob.File_Readonly);
  DBMS_LOB. LoadFromFile (l_blob, l_bfile, DBMS_LOB.getlength (l_bfile));
  DBMS_LOB. FileClose (l_bfile);
  COMMIT;
  END;
  /
  
  SQL > select * from blob_sample;
  ID BLOB_DATA
  1 68656C6C6F206462612773
  
  Above is coded image shape & I try this with the Insert as below... IT WORKS
  SQL > insert into blob_sample (id, blob_data) values (1, '68656C6C6F206462612773');
  
  1 line of creation.
  
  
  But this does not work when encoded length is too large (size 10 KB text file or more)
  
  It returns error
  
  insert into blob_sample (blob_data) values ('416374697
  *
  ERROR on line 1:
  ORA-01704: string literal too long
  
  
  Please HELP how how can I insert with this method
  
  Published by: Mr. singh on 9 October 2012 18:54
  
  Published by: Mr. singh on October 9, 2012 19:38

  It does not make sense to try to build a literal string that represents the binary data in a GIF file and that insert a BLOB using an INSERT... Statement of VALUES.

  You can use the first approach (dbms_lob.loadfromfile) to load a GIF file (or any file) into a BLOB.
  If the image you are trying to load is not a file on the filesystem of database, you can use SQL * Loader on the client machine to load the data, or you can write an application in any language you want that reads the data from the file and inserts it into the BLOB by using the API in your language / framework. You have not told us what language and framework you use, but it shouldn't be too hard to find a suitable example. For example, if you use Java and JDBC, here is an example of loading a GIF in a table.

  Justin

• Problem with the percentage data type

  Hello
  
  I understand that if a member account data type is percentage, then the corresponding value in the form of data is displayed as a percentage. For example, if I need to get 50% against the particular account member, then I can type either 0.5 or 50%. But is there the parameters by which if I hit 50, system will consider as 50%, not 5 000%.
  
  Thank you.

  You can type either 0.5 or 50%

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Problem with the incompatible data type

  Hi all
  
  I wrote this query and trying to run it and got the following error.
  
  I got this error when I add column.if description I do not add the description column query works fine. _
  
  Attempted to solve by other means but did not work.
  
  Please help on this.
  
  SELECT the description, product, /*Defect.Product*/
  TO_CHAR (BG_DETECTION_DATE, 'yyyy') year,
  TO_CHAR (BG_DETECTION_DATE, 'Q'). ' Q'Quarter
  BUG
  where service_type as "Incident".
  and produced in ("Siebel", "Intg_Mgmt", "SOA", "NICE", "Genesys", "DW Analytics")
  AND DETECTION_DATE
  BETWEEN TO_DATE('01-01-2009','MM-DD-YYYY')
  AND TO_DATE (OCTOBER 30, 2010 ","DD-MM-YYYY")
  
  Group of to_char(bg_detection_date,'yyyy'), to_char(bg_detection_date,'Q'),
  product, description
  
  order by product, year desc, asc quarter
  
  
  error: ORA-00932: given inconsistent type.expected get clob_

  Try to replace every occurrence of "description" by 'dbms_lob.substr (description, 100, 1)' in your query, for example.

  It of OK if you want to show how only and group using the first 100 characters of the column "description".

• Create the view with the CLOB of TABLE data type with the LONG data type

  Please need support to create the table view
  Source table: (itemid varchar2, longrec)
  need to create the table view Source
  (itemid varchar2, CLOBrec)

  A BUSINESS object must have a storage in the database, so you can't have a CLOB column in a view by pointing to a not lob data column.

  Max
  [My Italian blog Oracle | http://oracleitalia.wordpress.com/2010/01/17/supporto-di-xml-schema-in-oracle-xmldb/]

• DLL for LabWindows/CVI 8.0 with the bool data type

  Hello

  I want to use a new SWIR camera in LabWindows/CVI 8.0 (Windows XP 32bits).

  The company delivered with the camera produced a 32-bit dll by using Microsoft Visual C++ 2010. The .dll and .lib and .h files include a working SDK/API (some functions with the bool data type)

  Compilation-online syntax error, variable Boolean is not a data type in LabWindows/CVI 8.0

  Generate the import of DLL-online syntax error library

  I tried to convert bool char (typedef unsigned char bool => no more syntax error but the functions does not work.)

  What can I do?

  Martin

  Hello again, Naumann!

  Microsoft Visual C++ 2010 represents Boolean using 1 byte, as stated by MSDN: https://msdn.microsoft.com/en-us/library/tf4dy80a(v=vs.100).aspx

  I guess that you import C++ functions using the syntax for extern "C". Otherwise, because of the C++ name mangling wouldn't you able to bind C++ library against your code CVI.

  You can also specify how you import C++ functions?

  In addition, because you have not described the problem as a corruption of heads or runtime error, I guess the C++ library function is called correctly the CVI. That said, I tend to believe that the problem is not really in the mechanism of interaction of C/C++, but in the C++ library. If you would start calling a dummy C++ function returning an integer from a simple CVI application that should work, because redefine bool in CVI 1 byte must ensure that settings are correctly transferred onto the stack.

  If you need to create a wrapper function of C++ that is not using bool and calls the C++ function, I expect to return the same result.

  Maybe you are missing a few prior initialization steps required? The provider of the camera also comes all example code?

  Best regards!

  -Johannes

• 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

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

• ORA-00997: illegal use of the LONG data type

  Hi all

  11.2.0.1

  ALTER TABLE SAFDB MOVE TABLESPACE DATA_TS_ENC

  *

  ERROR on line 1:

  ORA-00997: illegal use of the LONG data type

  Why illegal? How can I move this table?

  Thank you very much

  pK

  Take a look who

  http://aprakash.WordPress.com/2011/01/06/how-to-move-table-containing-long-or-LOB-columns/

  Concerning

• Insert/update the column with the clob data type

  Hi all

  ORCL Version: 11g.

  I have a table with the clob data type.

  Test12

  (col1 clob);

  I'm trying to insert/update to update the column with more than 4000 characters.

  But due to the limitation of tank 4000, I could not Insert/Update.

  Need your help in resolving this issue.

  THX

  Rod.

  The limit of 4000 characters is incorrect.  That pertains only to the varchar2 data type.  A clob can hold more than 4 G.

  Here is an example that shows how to insert it, I found...

  Otherwise, here is a way 'dirty' to do.

  insert into your_table (COLA, COLB)

  values

  (PRIMARY_KEY, PART 1 OF DATA)

  ;

  Update your_table

  Define COLB = COLB | PART 2 OF BIG DATA

  where COLA = PRIMARY_KEY;

  Update your_table

  Define COLB = COLB | PART 3 OF BIG DATA

  where COLA = PRIMARY_KEY;

  .. and so on...

  I don't know that I personally recommend the second style...  But he could do the job.

• 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