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

Tags: Business Intelligence

Similar Questions

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

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

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

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

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.

EXECUTE IMMEDIATE in error > > 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.

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

I had some difficulties with dropApplicationTableIndex. He raised an exception ORA-00972:
java.sql.SQLException: ORA-00972: identifier is too long

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210)
at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:961)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1190)
at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1657)
at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1626)
at oracle.spatial.rdf.client.jena.Oracle.executeUpdate(Oracle.java:769)
at oracle.spatial.rdf.client.jena.GraphOracleSem.dropApplicationTableIndex(GraphOracleSem.java:3695)

However, the longer name of my models is 23 characters, making it the longest name of characters 27A table (+ _TPL).
Is there a still shorter limit for the length of model name?

Thank you

Kind regards
Julien
Hi Julien,

In fact, the limit for a semantic model, created using the Jena adaptor is 19 characters. This is because the application table index uses TRIPLEIDX as a suffix.

Best,
Vlad

Variable recovery of ODI in Java Beanshell (target Beanshell Source Oracle)
Hi guys:

I am faced with a simple problem, but I am not able to find the solution in the documentation or any post in this forum. I have a procedure where I use the two tabs (Source and target) and need to retrieve the result of the 'StrParam' (query Oracle) in a variable BeanShell (OracleMessageData).

In the target tab, I have these commands (Java BeanShell Techonology):

< @.
to import java.io.FileNotFoundException;
import java.io.InputStream;
import java.io.BufferedReader;
import java.io.File;
import java.io.FileInputStream;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.io.PrintWriter;
import java.io.UnsupportedEncodingException;
import java.util.ArrayList;

String OracleMessageData = "#strParam";
String PathOfXMLFiles = "< %=odiRef.getSchemaName ("LS_FILE_XMLFULL","D") % > ';
.
.
.
@ >

In the Source tab, I have this command (Techonology Oracle):

SELECT MESSAGEDATA < %=odiRef.getSchemaName ("LS_ORACLE_ODI_WRK", "D") % >. CONTENT_RIB_MSGDATA strParam

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

How can I recover the contents of the command Source in the variable in the target? The line below does not work:

String OracleMessageData = "#strParam";

I use ODI_11.1.1.6.0_GENERIC_111219.1055

Kind regards.
Luiz Araujo

Published by: Luiz_Araujo on 25/07/2012 06:43

Published by: Luiz_Araujo on 25/07/2012 06:45
Hello Luiz

Use under query on the source tab.

SELECT STRPARAM MESSAGEDATA< %="odiRef.getSchemaName" ("ls_oracle_odi_wrk",="" "d")="" %="" >.="">

Then use the target tab

String OracleMessageData = "#STRPARAM";

If it does not try to put colon.

String OracleMessageData = ": STRPARAM «;»»

Thank you.

identifier too long on heterogeneous services-> MSSQL

Got a strange problem, a little
We got the heterogeneous services, pointing to a MSSQL Server.

When I run

Select * from table_name32charslong@mssql_server

I get: SQL error: ORA-00972: identifier is too long

Logic because the name of the table msserver is over 30 characters.

Can it be solved without renaming the table / side view msserver?

Thank you

4Eyes

BluShadow wrote:
HS can only deal in restraint of Oracle specifications. i.e. table names must be is no longer than 30 characters that oracle would expect of his own paintings.

I came across the same problem myself with a HS connection to an Excel spreadsheet that allows 32 chrs for worksheet names.

Looks like you will need to rename the table, either create a view against it. ;)

Well, OP has not to rename the table or create a view against it on the side MSSQL. He or she can use DBMS_HS_PASSTHROUGH:

SQL> SELECT * FROM LONGER_THAN_THIRTY_CHARACTERS_TABLE_NAME@MDB
  2  /
SELECT * FROM LONGER_THAN_THIRTY_CHARACTERS_TABLE_NAME@MDB
              *
ERROR at line 1:
ORA-00972: identifier is too long

SQL> SET SERVEROUTPUT ON
SQL> DECLARE
  2          c  INTEGER;
  3          nr INTEGER;
  4          id NUMBER;
  5          a  VARCHAR2(10);
  6      BEGIN
  7          c := DBMS_HS_PASSTHROUGH.OPEN_CURSOR@MDB;
  8          DBMS_HS_PASSTHROUGH.PARSE@MDB(c,'SELECT * FROM LONGER_THAN_THIRTY_CHARACTERS_TABLE_NAME');
  9          LOOP
 10            nr := DBMS_HS_PASSTHROUGH.FETCH_ROW@MDB(c);
 11            EXIT WHEN nr = 0;
 12            DBMS_HS_PASSTHROUGH.GET_VALUE@MDB(c,1,id);
 13            DBMS_HS_PASSTHROUGH.GET_VALUE@MDB(c,2,a);
 14            DBMS_OUTPUT.PUT_LINE('ID = ' || id || ' A = ' || a);
 15          END LOOP;
 16          DBMS_HS_PASSTHROUGH.CLOSE_CURSOR@MDB(c);
 17  END;
 18  /
ID = 1 A = test

PL/SQL procedure successfully completed.

SQL>

If OP wants to query the SQL table:

SQL> CREATE OR REPLACE
  2    TYPE LONG_TBL_NAME_OBJ_TYPE
  3      AS OBJECT(
  4                ID NUMBER,
  5                A  VARCHAR2(50)
  6               )
  7  / 

Type created.

SQL> CREATE OR REPLACE
  2    TYPE LONG_TBL_NAME_TBL_TYPE
  3      AS TABLE OF LONG_TBL_NAME_OBJ_TYPE
  4  / 

Type created.

SQL> CREATE OR REPLACE
  2    FUNCTION get_data_from_link
  3      RETURN LONG_TBL_NAME_TBL_TYPE
  4      PIPELINED
  5      IS
  6          c                 INTEGER;
  7          nr                INTEGER;
  8          long_tbl_name_obj LONG_TBL_NAME_OBJ_TYPE := LONG_TBL_NAME_OBJ_TYPE(NULL,NULL);
  9      BEGIN
 10          c := DBMS_HS_PASSTHROUGH.OPEN_CURSOR@MDB;
 11          DBMS_HS_PASSTHROUGH.PARSE@MDB(c,'SELECT * FROM LONGER_THAN_THIRTY_CHARACTERS_TABLE_NAME');
 12          LOOP
 13            nr := DBMS_HS_PASSTHROUGH.FETCH_ROW@MDB(c);
 14            EXIT WHEN nr = 0;
 15            DBMS_HS_PASSTHROUGH.GET_VALUE@MDB(c,1,long_tbl_name_obj.id);
 16            DBMS_HS_PASSTHROUGH.GET_VALUE@MDB(c,2,long_tbl_name_obj.a);
 17            PIPE ROW(long_tbl_name_obj);
 18          END LOOP;
 19          DBMS_HS_PASSTHROUGH.CLOSE_CURSOR@MDB(c);
 20          RETURN;
 21  END;
 22  / 

Function created.

SQL> SELECT  *
  2    FROM  TABLE(get_data_from_link)
  3  / 

        ID A
---------- --------------------------------------------------
         1 test

SQL>

SY.

Column name is too long
When loading the data from the XML source I get following error
ORA-00972: identifier is too long
I understand that some are the name of the column over source of dansMon then 30 tank (limit of Oracle) but I would like to know what it
to be changed in the revenge to choose only thirty first characters of the name of the column if the column name is Char, then 30.
Works LKM fine as she take only the first 30 tank to create the name of the table, I think that it take this crib of the topology setting.
But what have to change in revenge to take only the first 30 tank for the column name.
I'm creating table target on the fly and I don't want to change the name of each column in the target table, it's going to be a lot of work for me.
Please let me know your opinion on this.

Thank you
I have prepared the KM for you because we had to change some steps... send me an email and I will answer it with the attached IKM.

You can get my email on my profile...

fan stays on too long and the battery level decreases rapidly: any problem identified?

Fan stays on too long and the battery level decreases rapidly: all identified cause problem or possible?

MacBook Air mid-2013

OS 10.11.13

Processor 1.7 GHz Intel Core i7

8 GB of DDR3 memory at 1600 MHz

Thank you, Paolo

Hi Paskowski,

Can you give us a little more information about your problem? What applications or processes are you using when you encounter the problem with your fan and battery? The activity monitor application can provide you with some basic information.

Use the monitor activity on your Mac.

The resources below provides general information on how optimize the battery life and troubleshoot the battery on your MacBook Air.

On batteries for laptops Mac

Take care

Identify too long to backup file names.

Using Vista on my laptop and the complex file names are required because of the research that I do.

When you run a regular backup to an external drive, I get an error message that some file names are too long for the files to copy, but no list of crime files is given. I am informed to shorten them, but not how to identify them.

Is there a quick way to find these files so that I can change the names?

Hi John,.

I just went to that link without problem using IE9 RC - but if you send you elsewhere to get the download, then maybe you'll have more success with the download page: http://www.parhelia-tools.com/products/pathscanner/Download.aspx. It is the only near the top (or you can try the alternate).

If specific filenames are not so long (assuming 260 is the number we need to worry and we are not quite sure of this), then it's probably the length of the path. The path includes everything, like C:\Users\\Appdata\local\microsoft\temp\iooiee90939ntgngjoiga909ri4jt09049japgaopjgp\...\filename.doc and if this WHOLE thing is too long (260 or other), then it cannot copy or paste. Chances are that these files were created by programs or automatically, not by you.

My guess is that these are temporary files of IE (they tend to be very long) and if first delete you IE temporary files (Tools / Options / history / delete / don't check the Temp files and save them favorite boxes above, uncheck everything else for this test), then you find out that you don't really have the problem more.

What is the external hard drive formatted in NTFS or FAT32 or FAT16? If this isn't NTFS, I recommend that use the command convert to change to NTFS. Not only is a better choice, but it can also solve this problem (although it's more a guess that based on specific research-, then it makes a difference with the size of the file and the file information, I saw say anything specifically made a difference in path length). http://windows.microsoft.com/en-US/windows-vista/Convert-a-hard-disk-or-partition-to-NTFS-format.

I hope this helps.

Good luck!

"Source path too long".

Music folder contains the music folder that contains the music folder; ad infinitum.

When I try to 'delete' files a new window States "Source path too long" to get it into the trash.

Hello

You can scan System File Checker to fix corrupted files.
How to use the System File Checker tool to fix the system files missing or corrupted on Windows Vista or Windows 7
http://support.Microsoft.com/kb/929833

ORA-24019: QUEUE_TABLE identifier too long, should not be greater than
OS: WINXP
DB: XE 10.2.0.1

Problem: SQL > START DBMS_AQADM.drop_queue_table (queue_table = > ' NAQ$ _QT_ORDERS_HYBRID_IN_)
G', FORCE = > TRUE); END;
2.
BEGIN DBMS_AQADM.drop_queue_table (queue_table = > ' NAQ$ _QT_ORDERS_HYBRID_IN_G ", F)
ORCE = > TRUE); END;
*
ERROR on line 1:
ORA-24019: QUEUE_TABLE identifier too long, should not be more than 24
characters
ORA-06512: at "SYS." DBMS_AQADM_SYS', line 4084
ORA-06512: at "SYS." DBMS_AQADM", line 197
ORA-06512: at line 1

I try to delete a queue, I'm not capable of the drop.

PL. inform me how to solve this problem?
[email protected] wrote:
OS: WINXP
DB: XE 10.2.0.1

Problem: SQL > START DBMS_AQADM.drop_queue_table (queue_table => ' _QT_ORDERS_HYBRID_IN_$ AAQ)
G', FORCE => TRUE); END;
2.
BEGIN DBMS_AQADM.drop_queue_table (queue_table => ' NAQ$ _QT_ORDERS_HYBRID_IN_G ", F)
ORCE => TRUE); END;
*
ERROR on line 1:
ORA-24019: QUEUE_TABLE identifier too long, should not be more than 24
characters
ORA-06512: at "SYS." DBMS_AQADM_SYS', line 4084
ORA-06512: at "SYS." DBMS_AQADM", line 197
ORA-06512: at line 1

I try to delete a queue, I'm not capable of the drop.

PL. inform me how to solve this problem?

Try to rename the table and then drop.

concerning

11g ODI identifier is too long on source ORACLE

Similar Questions

Maybe you are looking for