* ORA-00972: identifier is too long * when drop index table app

Similar Questions

• ORA-00972: identifier is too long

  Hai all,
  
  SQL > delete / * parallel nologging * / of DWEvent where EVENTTIME < to_date('2012-02-01','YYYY-MM-DD');
  
  ERROR:
  ORA-00972: identifier is too long
  
  No idea why?

  You have a double quote at the end of your statement.
  What happens if you change:

  delete /* nologging parallel */ from DWEvent where EVENTTIME < to_date('2012-02-01','YYYY-MM-DD')";
  {code}
  into:
  {code}
  delete /* nologging parallel */ from DWEvent where EVENTTIME < to_date('2012-02-01','YYYY-MM-DD');
  {code}
  ?
  
  And by the way: your 'hint' is not really a hint, but only a comment.
  Hints start with /*+ YOUR_HINT */, you forgot the + sign.
  
  You can search the syntax easily from http://www.oracle.com/pls/db112/homepage                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        
  

• PL/SQL: ORA-00972: identifier is too long.

  Hi all
  
  I have a question on the Express request form. I have my form fields that must be completed to save information about the database. It works fine until I click on create a button - I get the following error:

  ORA-06550: line 1, column 243: PL/SQL: ORA-00972: identifier is too long ORA-06550: line 1, column 7: PL/SQL: SQL Statement ignored
  
  
  Unable to process row of table FIS_REPAT_WITH_APPLICANT_INFO.

  I checked the length of table name, & he is 28 characters long. What could be the problem with this? Any help is appreciated. Thank you in advance.
  
  Concerning
  Kamo

  Hi Tom,

  Sorry for the late reply. It turns out that my problem was with date formats: I changed the format of the date of my entire application of MON/DD/YY to YYYY-MM-DD, which worked well. However, on a a date field forms I changed the Capture_Date source to to_char (Capture_Date, 'YYYY-MM-DD') that's why I got the error I got.

  At one point, I got an error message: ORA - 06502:PL / SQL: digital or value error: character string buffer too small
  That's why I started another thread: Re: ORA - 06502:PL / SQL: digital or value error: character string buffer too small

• EXECUTE IMMEDIATE in error &gt; &gt; ORA-00972: identifier is too long

  Hello
  
  I wrote a code using execute immediate command. This command essentially creates a cursor that selects user_tab_columns table names. These table names are then used inside the statement immediately execute in order to apply the same select statement on the table being selected within the cursor names. The problem is that the above error is thrown saying identifier is too long. I can't understand how to solve this problem.
  
  Please find the below code:
  
  Declare
  Cursor C_1 is select distinct table_name
  of user_tab_columns
  where column_name = 'PROGRAM_UPDATE_DATE' AND table_name LIKE '% MISPA '.
  intersect
  Select unique table_name
  of gsi_daily_count;
  table_names varchar2 (100);
  Begin
  C_1 open;
  Loop
  Extract the C_1 in table_names;
  WHEN THE EXIT C_1% NOTFOUND;
  
  EXECUTE IMMEDIATE "select last_extract_date,
  TO_CHAR (min (largest (nvl (last_update_date, "1 January 10"), nvl (program_update_date, "1 January 10"))), "MON-DD-YY HH24:MI:SS") mi.
  TO_CHAR (max (greatest (nvl (last_update_date, "1 January 10"), nvl (program_update_date, "1 January 10"))), "MON-DD-YY HH24:MI:SS") my
  of ' | table_names |
  "Last_extract_date group".
  order of last_extract_date desc;';
  
  End loop;
  Close C_1;
  COMMIT;
  End;
  /
  
  
  Help, please.
  
  Kind regards
  Hossam

  declare
    cursor C_1
    is
    select distinct table_name
      from user_tab_columns
     where column_name = 'PROGRAM_UPDATE_DATE'
       and table_name LIKE 'MISPA%'
    intersect
    select unique table_name
      from gsi_daily_count;
  
    table_names varchar2(100);
  begin
    open C_1;
    loop
      fetch C_1 into table_names;
      exit when c_1%notfound;
  
      execute immediate
        'select last_extract_date,
                to_char(min(greatest(nvl(last_update_date,''01-Jan-10''),nvl(program_update_date,''01-Jan-10''))),''DD-MON-YY HH24:MI:SS'') mi,
                to_char(max(greatest(nvl(last_update_date,''01-Jan-10''),nvl(program_update_date,''01-Jan-10''))),''DD-MON-YY HH24:MI:SS'') ma
           from'|| table_names ||
        'group by last_extract_date
          order by last_extract_date desc;';
    end Loop;
    close C_1;
    commit;
  End;
  

  Here is the list of question I see in this code.

  1. in the SQL string, you must have a after the keyword and before the GROUP BY keyword.

  2. you should not use ';' in EXECUTE IMMEDIATE. You must remove it.

  3. the result set returned by the EXECUTE IMMEDIATE should be stored in a Variable. You use the INTO LEDGES INTO clause or in BULK to this effect.

• identifier is too long, when you create a view

  Hi all
  When I am trying to run the initial load using OBI apps 7.9.5.2 SCCM with I get the following error for the SDE mappings...

              72 : 42000 : java.sql.SQLException: ORA-00972: identifier is too long
  
  java.sql.SQLException: ORA-00972: identifier is too long
  
  
       at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
  
       at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
  
       at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)
  
       at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639)
  
       at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:185)
  
       at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:633)
  
       at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1086)
  
       at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2984)
  
       at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3057)
  
       at com.sunopsis.sql.SnpsQuery.executeUpdate(SnpsQuery.java)
  
       at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execSrcOrders(SnpSessTaskSql.java)
  
       at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
  
       at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
  
       at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
  
       at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
  
       at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
  
       at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
  
       at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
  
       at com.sunopsis.dwg.cmd.e.i(e.java)
  
       at com.sunopsis.dwg.cmd.g.y(g.java)
  
       at com.sunopsis.dwg.cmd.e.run(e.java)
  
       at java.lang.Thread.run(Unknown Source)   

  This is my sql code in the description tab
  
  

    
  create or replace view APPS.C$_0W_ORA_INT_ORG_D
  (
       C1_ORGANIZATION_ID,
       C2_ORGANIZATION_CODE,
       C3_ORGANIZATION_NAME,
       C4_BUSINESS_GROUP_ID,
       C5_BUSINESS_GROUP_NAME,
       C6_SET_OF_BOOKS_ID,
       C7_OPERATING_UNIT,
       C8_OPERATING_UNIT_NAME,
       C9_LEGAL_ENTITY,
       C10_LEGAL_ENTITY_NAME
  )
  as select     
       
       TO_CHAR(SQ_ORG_ORGANIZATION_DEFINITION.ORGANIZATION_ID)        C1_ORGANIZATION_ID,
       SQ_ORG_ORGANIZATION_DEFINITION.ORGANIZATION_CODE        C2_ORGANIZATION_CODE,
       SQ_ORG_ORGANIZATION_DEFINITION.ORGANIZATION_NAME        C3_ORGANIZATION_NAME,
       TO_CHAR(SQ_ORG_ORGANIZATION_DEFINITION.BUSINESS_GROUP_ID)        C4_BUSINESS_GROUP_ID,
       SQ_ORG_ORGANIZATION_DEFINITION.BUSINESS_GROUP_NAME        C5_BUSINESS_GROUP_NAME,
       TO_CHAR(SQ_ORG_ORGANIZATION_DEFINITION.SET_OF_BOOKS_ID)        C6_SET_OF_BOOKS_ID,
       TO_CHAR(SQ_ORG_ORGANIZATION_DEFINITION.OPERATING_UNIT)        C7_OPERATING_UNIT,
       SQ_ORG_ORGANIZATION_DEFINITION.OPERATING_UNIT_NAME        C8_OPERATING_UNIT_NAME,
       TO_CHAR(SQ_ORG_ORGANIZATION_DEFINITION.LEGAL_ENTITY)        C9_LEGAL_ENTITY,
       SQ_ORG_ORGANIZATION_DEFINITION.LEGAL_ENTITY_NAME        C10_LEGAL_ENTITY_NAME
  from     APPS.ODI_SQ_ORG_ORGANIZATION_DEFINITION   SQ_ORG_ORGANIZATION_DEFINITION
  where     (1=1)

  Any suggestions? Please help me
  
  Thank you
  saichand.v

  Hello

  Try changing the "maximum Table name length' and '"column name maximum length"in Manager topology ODI.» This is, in the "other" tab of the chosen technology.

  Set the new value = original value - 5

  You must assign the appropriate value to 'column name maximum length ".
  setting for staging technology.

  Thank you
  Fati

• 11g ODI identifier is too long on source ORACLE

  Hello

  I just migrated to ODI 10 ODI 11 g g but it seems that one of my script doesn't work. Whenever I run, I have the following error message:

  ODI-1227: SS_0 (load) task fails on the source of connection ORACLE POM

  Caused by: java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long

  After some research it seems that on ODI 11 g, the identifier must be a maximum of 30 characters in the alias column, so my problem is the following application

  Select	*
  END
  	NVL(ENCADRANT_INTERVENANT.SI_APTITUDE_TRAJET_LONG,0)	C15_ENC_SI_APTITUDE_LONG_TRAJET
  Of	PROD_DSN.
  where	(1 = 1)

  So I went (physical) topology, change the field 'Maximum length of name of column' 25 on Advanced tab but it does not work.

  
  

  Any idea, please?

  
  

  Kind regards

  Jean

  There is limitation aka oracle. See the Oracle SQL language reference.

  Module IKM look the parameter 'Maximum length of ColumnName', this setting works for tear. So if you're boning now, ODI truncates all the columns including more then 25 characters.

  You can solve the problem:

  (1) module knowledge of change in the production of alias

  (2) create view your alias small columns table PROD_DSN

• identifier is too long

  Hello
  I run the script but I got problem below. How will I know which column is the reason for the problem?
  
  ERROR on line 1:
  ORA-00972: identifier is too long

  Hello

  Human Chen wrote:
  no column above is really with over 30 char

  Really?
  Format your code to make it easier to identify:

  insert into tw.EDI_PARTNER_MESSAGE
  (     edi_partner_code
  ,     edi_event_code
  ...
  ,     outbound_file_location
  ,     dest_email_addr
  --              1         2         3         4
  --     1234567890123456789012345678901234567890
  ,     edi_bk_directflow_indedi_partner_code
  ,     edi_event_code
  ,     edi_message_code ...
  

  A comma is missing.

• identifier is too long: expdp filtering using QUERY off TABLES =.

  All,

  I run large expdp work using a .bat file.  An example of one of the lines is the following:

  expdp directory "" / as sysdba "" = IMPORT_DB dumpfile=vismag_brightness%%U.dmp logfile = vismag_brightness.log ALL TABLES = sat_cat_owner.vismag_brightness QUERY = sat_cat_owner.vismag_brightness = compression:'------"where exists (" select visual_magnitude_uuid in the sat_cat_owner.visual_magnitude where sat_cat_owner.visual_magnitude.visual_magnitude_uuid=sat_cat_owner.vismag_brightness.visual_magnitude_uuid)\ "')"

  Present the results of .bat to this:

  

  I then tried to put it in a settings file.  As always, you can see in the picture above, he already gave me an error, but I corrected which and he always gave me the same error.  The application was the same as above, only had no slashes return of evasion.

  Now this is why I am sure that I am right escape.  Now, I just need to find the reason for the identifier is too long.

  Here's a picture showing other odd behavior, trying to simplify the query to see if its because the query is too long.  AND if it is because its too long..how for I can config so it can handle?

  

  The difference in the image above, is that the first test has only \"...while the second is what worked for me before top (if I try without the single quotes, it fails on citing the issue for the important query).  So the second cmd, as I have said, has "\" instead of just \"...and it does not work!"  When he did above for the larger request, but it gives error separated.

  Help, please!  Thank you

  Hello

  Try this instead

  Query ='sat_cat_owner.vismag_brightness: "Where exists (select visual_magnitude_uuid from the sat_cat_owner.visual_magnitude where sat_cat_owner.visual_magnitude.visual_magnitude_uuid = ku$ .visual_magnitude_uuid)" "

  Ku$ is an alias of special for the object currently being extraction - I think that in case you want to use exists, you must use this syntax - give it a try and see what happens.

  Other than that can replace you an IN clause instead?

  See you soon,.

  Rich

• SQL error: ORA-00910: specified length too long for its data type

  Using Oracle 11.2.0.1 on Oracle Linux 5.8 x 64
  
  I try to install Zabbix http://www.zabbix.com and uses the Oracle database as the data store. The script of the diagram provided below does not work.
  

  CREATE TABLE maintenances (
       maintenanceid            number(20)                                NOT NULL,
       name                     nvarchar2(128)  DEFAULT ''                ,
       maintenance_type         number(10)      DEFAULT '0'               NOT NULL,
       description              nvarchar2(2048) DEFAULT ''                ,
       active_since             number(10)      DEFAULT '0'               NOT NULL,
       active_till              number(10)      DEFAULT '0'               NOT NULL,
       PRIMARY KEY (maintenanceid)
  );

  When I run it, I get

  Error at Command Line:5 Column:42
  Error report:
  SQL Error: ORA-00910: specified length too long for its datatype
  00910. 00000 -  "specified length too long for its datatype"
  *Cause:    for datatypes CHAR and RAW, the length specified was > 2000;
             otherwise, the length specified was > 4000.
  *Action:   use a shorter length or switch to a datatype permitting a
             longer length such as a VARCHAR2, LONG CHAR, or LONG RAW

  According to the oracle documentation for nvarchar2 limit is 4000. What am I missing here?

  "4000 bytes is the ultimate maximum." You can say 4000 * characters *, but it will always be limited to 4000 * bytes *. "
  http://asktom.Oracle.com/pls/Apex/f?p=100:11:0:P11_QUESTION_ID:1224836384599 #201073000346459201\

  "The maximum length of the column is determined by the definition of national character set. The width of the character NVARCHAR2 data specifications match the number of characters. The authorized maximum column size is 4000 bytes. »
  http://docs.Oracle.com/CD/E11882_01/server.112/e26088/sql_elements001.htm#SQLRF50976

  Furthermore, you treat numbers as STRINGS, remove the quotes around your zero.

• error "result of concatenating string is too long" when I try to run the following code. Help me!

  When I try to perform the following PROCEDURE, he throws me an error:

  Error from line: 2 in command.

  BEGIN

  FACT_UPDATE;

  END;

  Error report-

  ORA-01489: result of concatenating string is too long

  ORA-06512: at "AFLOBIDW. FACT_UPDATE', line 22

  ORA-06512: at line 2

  01489 00000 - "result of concatenating string is too long."

  * Cause: Result of concatenation of string exceeds the maximum size.

  * Action: Make sure that the result is less than the maximum size.

  ---------------------------------------------------------------------------

  I can't change the logic of the code since I'm trying to do Informatica at the back done and compare performance between Informatica and Oracle DB. Is there another solution for errors? I add only the SQL query that is part of the PROCEDURE for easy viewing. Please help me. Thank you!

  SELECT "UPDATE XXAFL_MON_FACTS_F SET TASK_WID ='"

  || NVL (TO_CHAR (TASK_WID), 'NULL')

  |', EXECUTION_PLAN_WID ='

  || NVL (TO_CHAR (EXECUTION_PLAN_WID), 'NULL')

  || ', DETAILS_WID ='

  || NVL (TO_CHAR (DETAILS_WID), 'NULL')

  |', SOURCE_WID ='

  || NVL (TO_CHAR (SOURCE_WID), 'NULL')

  |', TARGET_WID = '

  || NVL (TO_CHAR (TARGET_WID), 'NULL')

  || ', RUN_STATUS_WID ='

  || NVL (TO_CHAR (RUN_STATUS_WID), 'NULL')

  |', SEQ_NUM ='

  || NVL (TO_CHAR (SEQ_NUM), 'NULL')

  |', NAME = "'

  || NVL (TO_CHAR (NAME), 'NULL')

  || ' ', NO_POSITION = "'

  || NVL (TO_CHAR (INSTANCE_NUM), 'NULL')

  ||'' ', INSTANCE_NAME = "'

  || NVL (TO_CHAR (INSTANCE_NAME), 'NULL')

  || ' ', TYPE_CD = "'

  || NVL (TO_CHAR (TYPE_CD), 'NULL')

  ||'' ', STATUS_CD = "'

  || NVL (TO_CHAR (STATUS_CD), 'NULL')

  ||'' ', START_TS ='

  || DECODE (START_TS, ",' to_date(''e))

  || To_char (START_TS, "mm/dd/yyyy hh)

  ||'' ((', "dd/mm/yyyy hh")')

  || ', END_TS ='

  || DECODE (END_TS, ",' to_date(''e))

  || To_char (END_TS, "mm/dd/yyyy hh)

  ||'' ((', "dd/mm/yyyy hh")')

  |', DURATION = '

  || NVL (TO_CHAR (DURATION), 'NULL')

  |', STATUS_DESC = "'

  || NVL (TO_CHAR (STATUS_DESC), 'NULL')

  || ' ', DBCONN_NAME = "'

  || NVL (TO_CHAR (DBCONN_NAME), 'NULL')

  ||'' ', SUCESS_ROWS ='

  || NVL (TO_CHAR (SUCESS_ROWS), 'NULL')

  || ', FAILED_ROWS ='

  || NVL (TO_CHAR (FAILED_ROWS), 'NULL')

  |', ERROR_CODE = '

  || NVL (TO_CHAR (ERROR_CODE), 'NULL')

  |', NUM_RETRIES ='

  || NVL (TO_CHAR (NUM_RETRIES), 'NULL')

  || ', READ_THRUPUT ='

  || NVL (TO_CHAR (READ_THRUPUT), 'NULL')

  |', LAST_UPD = '

  || DECODE (LAST_UPD, ",' to_date(''e))

  || To_char (LAST_UPD, "mm/dd/yyyy hh)

  ||'' ((', "dd/mm/yyyy hh")')

  |', RUN_STEP_WID = "'

  || NVL (TO_CHAR (RUN_STEP_WID), 'NULL')

  || ' ', W_INSERT_DT = '

  || DECODE (W_INSERT_DT, ",' to_date(''e))

  || To_char (W_INSERT_DT, "mm/dd/yyyy hh)

  ||'' ((', "dd/mm/yyyy hh")')

  |', W_UPDATE_DT = '

  || DECODE (W_UPDATE_DT, ",' to_date(''e))

  || To_char (W_UPDATE_DT, "mm/dd/yyyy hh)

  ||'' ((', "dd/mm/yyyy hh")')

  || ', START_DATE_WID ='

  || NVL (TO_CHAR (START_DATE_WID), 'NULL')

  |', END_DATE_WID = '

  || NVL (TO_CHAR (END_DATE_WID), 'NULL')

  |', START_TIME ='

  || NVL (TO_CHAR (START_TIME), 'NULL')

  |', END_TIME ='

  || NVL (TO_CHAR (END_TIME), 'NULL')

  ||' WHERE INTEGRATION_ID = "'

  || INTEGRATION_ID

  ||''';' AS Column

  OF XXAFL_MON_FACTS_F;

  Hello

  ORA-01489 is one of these error messages that really means what he says. The error message you posted pretty much sums up the situation.

  What version of Oracle are you using?  (You must still include this whenever you have a question.  See the FAQ forum: Re: 2. How can I ask a question on the forums? )

  From 12.1 of the Oracle, there is an option to allow VARCHAR2s in SQL to be as big as 32767octets.  (The default is 4000).

  Otherwise, if you can't change the code, either do not run. or ensure that the concerned channels are quite short so the error does not occur.

• "File Name Too Long" when copying files on USB using Windows 7 Home Premium (64-bit)

  When I copy about 60 GB of library files in a backup folder on a USB key, at the end of the copy, it is a dialog box indicating "file name too Long for the Destination Folder.  It shows that there are 62 records like that, and I can choose to ignore these files.

  1. I had formatted the USB stick to NTFS - which does not allow large file names?

  2. How can I see which files have this problem so I can shorten the file names?

  Thank you!

  Hello

  What is the capacity of the USB?

  Were you able to copy before?

  Try to format the drive once and then try and check if it is beneficial because it can also happen when there are viruses.

  You can also check the drive for errors.

  Here is the link:

  http://Windows.Microsoft.com/en-us/Windows7/check-a-drive-for-errors

  It will be useful.

• 'File name' error too long when you copy a folder to a DVD disc

  When I copy a folder that contains a large number of files on an external hard drive, I have no problem, but if I try to copy the same folder to a DVD disc, I get a message indicating that a file name is too long.  My first question is why do I get the message for DVD and not the external hard drive?  My second question is: How can I generate a list of files in my folder that have too long names? My second question is already other post on the forum, but there was no answer.  Is it because it is not possible to generate such a list?

  Thank you

  It depends on what is called the 'file system '. File systems are how files are stored on a disk. Many of them have limits on how long the total file path can be. DVD and external hard drives use different file systems.

  If you want a list of all the files in a folder, open a command prompt. Type this in:

  CD "C:\path\to\folder".

  and press ENTER. Replace path\to\folder with the path of the file in your file that you want to check to make sure this filepath is in quotes!

  Now type:

  dir /s > 'output.txt '.

  and press ENTER. This will tell the guest to make a list of all the files in this folder and in each subfolder, and then store in a text file. This will allow you to view the list and I hope to find the long file names. Once you have found the long file name, go to that file, and then change the name.

  Here is an example of the above commands. Let's say I have a folder named "foo" in the My Documents folder. I first type:

  CD "C:\Users\Entegy\Documents\foo".

  and press ENTER. Now, I want the list of files to be placed on my desk. Then I type:

  dir /s > "C:\Users\Entegy\Desktop\filelist.txt."

  And voila, I have a list of all the content of foo on my desktop files. Just make sure that your path ends with .txt and you'll be fine. And don't forget to put quotes around filepaths!

• Why do I get "413 header too long" when I try to download Photoshop elements 13 free trial on yosemite OSX?

  When I try to download Photoshop elements 30 trail day on my computer of yosemite OSX for help

  Safari, it fails with "413 header too long" as the only line on the window.  What gives?

  OSX all patches have been applied as of today 08/01/15.

  Thank you

  Jim

  remove the cookies from the adobe.com site or use another browser.

• Name of the item too long when you use ROWTYPE

  I encountered a problem with the xml elements names longer than 30 characters. Seems that it has something to do with ROWTYPE. Creation of this function is successful:
  
  < pre >
  FUNCTION to CREATE or REPLACE test_fnc
  RETURN OF XMLTYPE
  AS
  var_return XMLTYPE.
  l_dummy DUAL.dummy%TYPE;
  BEGIN
  SELECT dummy INTO l_dummy FROM DUAL;
  
  SELECT XMLCONCAT (XMLELEMENT)
  "TEST."
  XMLFOREST)
  l_dummy "THIS_IS_OVER_30_CHARACTERS_LONG".
  )
  ))
  data_set
  IN var_return
  FROM DUAL;
  
  
  RETURN var_return;
  END test_fnc;
  /
  < / pre >
  
  However, the specification of the ROWTYPE variable gives error ORA-00972 (except if I shorten the name of the item...):
  
  < pre >
  FUNCTION to CREATE or REPLACE test_fnc
  RETURN OF XMLTYPE
  AS
  var_return XMLTYPE.
  l_dummy DOUBLE % ROWTYPE;
  BEGIN
  SELECT dummy INTO l_dummy FROM DUAL;
  
  SELECT XMLCONCAT (XMLELEMENT)
  "TEST."
  XMLFOREST)
  l_dummy. Dummy "THIS_IS_OVER_30_CHARACTERS_LONG."
  )
  ))
  data_set
  IN var_return
  FROM DUAL;
  
  
  RETURN var_return;
  END test_fnc;
  /
  < / pre >
  
  Has anyone previously met, or have any ideas for a solution? I could specify all my variables as TYPE, but as there are many in the tables it would be easier to use ROWTYPE.
  
  Oracle Database 11 g Enterprise Edition Release 11.1.0.6.0 - 64 bit Production
  
  Thank you.

  This works if you add 'AS' after l_dummy.dummy

  SQL> CREATE OR REPLACE FUNCTION test_fnc
    2     RETURN XMLTYPE
    3  AS
    4     var_return   XMLTYPE;
    5     l_dummy      DUAL%ROWTYPE;
    6  BEGIN
    7     SELECT   dummy INTO l_dummy FROM DUAL;
    8
    9     SELECT   XMLCONCAT(XMLELEMENT (
   10                           "TEST",
   11                           XMLFOREST (
   12                              l_dummy.dummy AS "THIS_IS_OVER_30_CHARACTERS_LONG"
   13                           )
   14                        ))
   15                 data_set
   16       INTO   var_return
   17       FROM   DUAL;
   18  RETURN var_return;
   19  END test_fnc;
   20  /
  
  Function created.
  

  Ants

• String control GPIB, too long when you use a multicore processor machine

  I have a HP 3457 A multimeter I communicate with the help of GPIB. I have two machines that have identical operating systems installed. CentOS 4.8 (equivalent to Red Hat Enterprise Linux 4.8) with the version of the kernel: 2.6.9 - 89.0.25.ELsmp.

  The first machine has a Pentium 2.8 GHz processor. We used this setup for a few years now without any problems. Given that the core processors go far, we need get our system working on a multi-core computer software. So, I loaded all our software on a new machine with an Intel Core 2 Duo processor. I have only this one all deadlines irregular left before calling this experience.

  In our code, we issue the following command to the multimeter and check a response:

  char * pm_init = "QR 0; PRESET; BACK OF THE TERM; END; LOCK ON; SREAL OFORMAT; « ;

  If (!) () (er = ibwrt (pm_ud, pm_init, strlen (pm_init))) & ERR))

  On the Pentium machine, it works fine. The multimeter does not have on the Core2 Duo computer. If I have this divide into two commands as follows:

  ER = ibwrt (pm_ud, "QR 0;") PRESET; BACK of the TERM; ", strlen (" QR 0; ") PRESET; TERM BACK ;")) & ERR

  If (!) () (er = ibwrt (pm_ud, "END; LOCK ON; OFORMAT SREAL. ", strlen ("END; LOCKING IN ONTARIO; OFORMAT SREAL ;"))) "& ERR))

  It works on both machines. However, it is a ugly real difficulty. Can someone tell me what is so different from the way in which the driver NOR past the verses of the long chain the two shorter chains?

  Thank you.

  Sorry, I thought that VISA facility would bring along the difficulty that we need, but when I look back it did not include a fix for Linux.

  This means that we don't currently have a driver available that will solve this problem, but there is a solution, if this is indeed the problem you see.

  The workaround is to disable DMA for your GPIB interface. To do this, you will need to open a handle to the jury and use the ibdma command to disable DMA. For example:

  handle = ibfind ("GPIB0");

  ibdma (handle, 0);

  At this point you should probably keep the handle open until your program is out, to ensure nothing resets the jury and allows again to DMA.

  As you can imagine, disable DMA can have an impact on performance in your application. If you make small, such transfers would probably be with a multimeter, you are unlikely to notice a difference in performance. If you transfer large size pads, you may encounter CPU utilization and more low than you would when using DMA.

  Please let me know if this workaround lets your program works, because this will tell us if this is the problem you are having, or if something goes wrong.

  -Jason S.