ORA-00997: illegal use of LONG datatype - while inserting a record

Hello,
I have this table:
create table TEST
USER VARCHAR2(20) not null,
WINCFG LONG RAW
There are a few records, some with user='OLDUSER'.
I want to add new records with a statement like this one:
insert into TEST
select 'NEWUSER',wincfg from TEST where user='OLDUSER'
But Oracle returns the error:
"ORA-00997: illegal use of LONG datatype"
I have no idea...
Thank you

SQL> insert into TEST
2 (
3 select 'NEWUSER',wincfg from TEST where user='OLDUSER'
4 );
select 'NEWUSER',wincfg from TEST where user='OLDUSER'
ERROR at line 3:
ORA-00997: illegal use of LONG datatype
SQL> copy from scott/tiger@mydb insert test using select * from test;
Array fetch/bind size is 15. (arraysize is 15)
Will commit when done. (copycommit is 0)
Maximum long size is 80. (long is 80)
   1 rows selected from scott@mydb.
   1 rows inserted into TEST.
   1 rows committed into TEST at DEFAULT HOST connection.Hope it help

Similar Messages

ORA - 00997 Illegal Use Of Long Datatype when no Long is used

I have a query that was working fine for years. We have upgraded to 10.2.0.5 on a test instance and we now get this error.
The view in the FROM clause is an org specific view on xxc_affi_relation_headers_all. All of the fields in the view and underlying table are either VARCHAR2, NUMBER, or DATE.
I have simplified the query to one that still gives the error.
The query is:
SELECT *
FROM xxc_affi_relation_headers xarh
WHERE xarh.affi_relation_id = (select xarh.affi_relation_id
from xxc_affi_relation_headers xarh
where xarh.execute_vendor_id = 125
connect by prior xarh.affi_relation_id = xarh.parent_relation_id
start with xarh.affi_relation_id = 214
If I run the sub query by itself, as below, there is no error and the result is 214.
select xarh.affi_relation_id
from xxc_affi_relation_headers xarh
where xarh.execute_vendor_id = 125
connect by prior xarh.affi_relation_id = xarh.parent_relation_id
start with xarh.affi_relation_id = 214
If I run the main query and replace the sub query with 214, as below, thre is no error.
Is there something that would cause an implicit conversion to a LONG datatype in this query? I am not able to find a reason for this error message that fits the query.
The original query that caused the error was:
SELECT xarh.affi_relation_id
FROM
xxc_affi_relation_headers xarh
WHERE NOT EXISTS (SELECT 1 FROM xxc_oe_order_line_dist xold
WHERE xold.line_id = p_line_id AND xold.dist_type = 'I'
AND xold.affi_relation_id = xarh.affi_relation_id)-- 1704
AND v_creation_date
BETWEEN NVL(xarh.start_date,v_creation_date-1) AND NVL(xarh.end_date,v_creation_date+1) --ES fix not a valid month
AND xarh.sale_segment1 = (SELECT gcco.segment1 --RT 9631
FROM oe_transaction_types_all otty, ra_cust_trx_types_all rctt, gl_code_combinations gcco
WHERE otty.transaction_type_id = p_order_type_id
AND otty.cust_trx_type_id = rctt.cust_trx_type_id
AND rctt.gl_id_rev = gcco.code_combination_id )
AND EXISTS(SELECT 1 FROM xxc_affi_relation_lines xarl WHERE xarl.affi_relation_id = xarh.affi_relation_id
AND NVL(xarl.element_value,v_item_type) = v_item_type)
connect by prior xarh.parent_relation_id = xarh.affi_relation_id
Start with
xarh.affi_relation_id = (select xarh.affi_relation_id
from xxc_affi_relation_headers xarh
where xarh.execute_vendor_id = p_vendor_id
AND xarh.affi_relation_id != p_parent_relation_id
AND NOT EXISTS (SELECT 1 FROM xxc_affi_relation_headers xarh2
WHERE xarh2.parent_relation_id = xarh.affi_relation_id)
AND v_creation_date BETWEEN NVL(xarh.start_date,v_creation_date-1) AND NVL(xarh.end_date,v_creation_date+1)--ES fix not a valid month
start with xarh.affi_relation_id = p_parent_relation_id
connect by prior xarh.affi_relation_id = xarh.parent_relation_id)
--ORDER BY NVL(parent_relation_id,-1), NVL2(xarl.element_value,1,2)
;

Its a bug
See this Oracle Document
Bug 9726739 - ORA-997 from SQL with CONNECT BY and UNION [ID 9726739.8]
Best Regards
mseberg

ORA-00997 - Illegal use os LONG Datatype

Hello
I'm having this error in my query, and I know I can't use one column LONG with a INSERT statement, but I can't change this column to VARCHAR2(4000) because of the short space.
Somebody have the solution for this? Or how I make this insert? Some function or procedure... anything...
Tnks
Rafael

Since you cannot use LONG into a INSERT...SELECT... statement, you may use a procedure with a loop.
By the way, what about CLOB ?
Nicolas.

Illegal use of LONG datatype

While I was insert a rows into the same table I am getting an error. I am having one long column in table list. I am getting following error while I was inserting a row.
ORA-00997: illegal use of LONG datatype
Please let me know how do I insert long data type values for this kind of insert.

[duplicate thread|http://forums.oracle.com/forums/message.jspa?messageID=3770321#3770321]

Illegal use of LONG datatype error message when i create materialized view

Hello to all
I want create read only materialized view replication environment two of our tables have LONG datatype when i create materialized view against on them
I recieve this error message
CREATE MATERIALIZED VIEW MDB.TOAD_PLAN_TABLE TABLESPACE aramis REFRESH FORCE WITH ROWID AS SELECT * FROM MDB.TOAD_PLAN_TABLE@arahisto
Error report:
SQL Error: ORA-00997: illegal use of LONG datatype
00997. 00000 - "illegal use of LONG datatype"
Do you know any resort solution for it?
thanks

You can not use longs in materialized views over a database link, you can however take a part of a long over to a materialized view.
I have gotten this to work in the past l had to create a PL/SQL function that you can use to extract the character data from the long column and use that to
as part of the function you will need to pass in the columns of the table that will identify the unique records so you can pick out the long column
example function
-- you will need to make sure this funtion is in the remote location as you can not select longs accross a DB LINK.
CREATE OR REPLACE FUNCTION MDB.TOAD_PLAN_LONG_CONV
(pass in the primary key columns for the table)
RETURN VARCHAR2
IS
v_long VARCHAR2(32767) ;
BEGIN
BEGIN
-- need to select the long column into the PL/SQL variable
SELECT long_column
INTO v_long
FROM MDB.TOAD_PLAN_TABLE
WHERE key_columns = passed columns ;
EXCEPTION
WHEN OTHERS THEN
IF SQLCODE = '-01406' THEN
NULL ;
ELSE
RAISE ;
END IF ;
END ;
RETURN SUBSTR(v_long,1,4000) ;
END ;
Then when you create the materialized view utilize that function on the long column.
create or replace materialized view MDB.TOAD_PLAN_TABLE TABLESPACE aramis REFRESH FORCE WITH ROWID
AS
SELECT column1, .... columnx,
MDB.TOAD_PLAN_LONG_CONV@arahisto (primary key column list) as long_column_name
FROM MDB.TOAD_PLAN_TABLE@arahisto ;
See if this will work for you? Keep in mind however this solution will not get the entire long column only as much as a PL/SQL variable will hold of it.
Mike

Illegal use of LONG

I create on table say "TAB" with a column as long datatype
create table tab
(name long);
now i need to create another table structure similar to "TAB" say "TMP_TAB"
create table tmp_tab
as
select * from tab;
But this gives the following error..< ORA-00997: illegal use of LONG datatype >
Can anyone please explain me the reason for the following error?

If you have Oracle 9i, then
Quick and correct solution: Don't use LONG - Datattype !
It's obsolete, use CLOB instead.
If LONG- Datatype is inevitable (why ?), then
declare
v_sql VARCHAR2(32767);
begin
select dbms_metadata.get_ddl('TABLE', 'TAB', 'SCOTT') INTO v_sql
from dual;
v_sql := replace (v_sql, '"SCOTT"."TAB"', '"SCOTT"."TMP_TAB"');
execute immediate v_sql;
end;
/but it's a bit tricky ....

Problem while inserting a record to infotype 416

Iam facing a problem while inserting a record to the infotype 416 for a personnel no using the FM 'HR_INFOTYPE_OPERATION'.I have created a FM to insert a record to the infotype 416.In that FM iam using the FM 'HR_INFOTYPE_OPERATION' to create a record for infotype 416.while executing my FM the FM 'HR_INFOTYPE_OPERATION' is returning the return value 0.But when i check in PA30 for the infotype 416,there is no record created for that personnel no.Also in the table PA0416 the record is not get created.SO what might be the problem.can anyone please provide me help on this.
I have attached the code of my FM for ur reference.
FUNCTION Y_ESS_FL_ENCASH.
DATA: G_COMPENSATION_AMOUNT LIKE PA0416-AMONT,
      G_RETURN TYPE BAPIRETURN1.
DATA T_PA0416 LIKE P0416 OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'HR_READ_INFOTYPE'
    EXPORTING
       TCLAS                 = 'A'
       PERNR                 = '00000014'
       INFTY                 = '0416'
     BEGDA                 = sy-datum
     ENDDA                 = sy-datum
       BYPASS_BUFFER         = 'X'
     LEGACY_MODE           = ' '
IMPORTING
     SUBRC                 =
      TABLES
        INFTY_TAB             = T_PA0416
EXCEPTIONS
INFTY_NOT_FOUND       = 1
OTHERS                = 2
    LOOP AT T_PA0416
    WHERE SUBTY = '1002'.
    ENDLOOP.
    IF SY-SUBRC <> 0.
      CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
        EXPORTING
           NUMBER = '00000014'
        IMPORTING
           RETURN = G_RETURN.
      IF SY-SUBRC <> 0.
         MESSAGE I016(RP) WITH ' RECORD IS ALREADY LOCKED'.
      ENDIF.
      T_PA0416-PERNR = '00000014'.
      T_PA0416-SUBTY = '1002'.
      T_PA0416-INFTY = '0416'.
      T_PA0416-OBJPS = ''.
      T_PA0416-SPRPS = ''.
      T_PA0416-SEQNR = ''.
      T_PA0416-AEDTM = SY-DATUM.
      T_PA0416-UNAME = SY-UNAME.
      T_PA0416-ENDDA = SY-DATUM.
      T_PA0416-BEGDA = SY-DATUM.
      T_PA0416-NUMBR = '10'.
      T_PA0416-WGTYP = '1530'.
      T_PA0416-AMONT = '15000'.
      T_PA0416-WAERS = 'INR'.
      T_PA0416-QUONR = '1'.
      APPEND T_PA0416.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          INFTY                  = '0416'
          NUMBER                 = '00000014'
          SUBTYPE                = '1002'
OBJECTID               =
LOCKINDICATOR          =
         VALIDITYEND            = '31129999'
         VALIDITYBEGIN          = SY-DATUM
        RECORDNUMBER           = ''
          RECORD                 = T_PA0416
          OPERATION              = 'INS'
          TCLAS                  = 'A'
DIALOG_MODE            = '0'
        NOCOMMIT               = 'X'
VIEW_IDENTIFIER        =
SECONDARY_RECORD       =
        IMPORTING
          RETURN                 = G_RETURN.
KEY                    =
      IF G_RETURN+0(1) EQ 'E'.
              MESSAGE I086(ZHR) WITH 'Record is not inserted in IT416'.
      ELSE.
          COMMIT WORK.
      ENDIF.
      CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
        EXPORTING
          NUMBER = '00000014'
        IMPORTING
          RETURN = G_RETURN.
    ENDIF.
ENDFUNCTION.

Hi Murthy
With a first glance, I think you have given a wrong parameter value to "validityend". It should be '99991231' not '31129999' .
If your problem still persists, try inserting the data online from PA30. If your input causes no errors, then please state what the return parameter contains.
Regards
*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

Row Level Locking while inserting a record.

It is a good practice to lock the whole table or do the row level locking while performing any DELETE / UPDATE / MODIFY actions on a database table. Is it necessary to do the same thing while inserting a record via INSERT statement?
One point may arise if two users are inserting same records at a same time....
Well i am little bit confused here bcos if a record doen't exist in a table what is the point of locking it.
Please help me.

create a lock object using SE11 for that perticular table and include field names in Lock parameters. Then it will generate two FMs one for locking and another for unlocking.
Call the lock FM before updating the table and pass that row key value(For fields which taken in lock parameters for creating lock objects) to the exporting parameters.
Then do the updation.
Reward if useful...................

How to convert varchar to date datatype while insert or update in table

Hai All
I need to convert to varchar to date.
I have two Tables T1,T2
T1 Structure
Code varchar
Time varchar
Date varchar
T2 Structure
Empname var
Empcode var
Intime date
Outtime date
Intrin date
Introut date
Att_date
Now i need to move Time form T1 to T2 Intime,outtime,intrin,introut according some condition
So now i need to convert Varchar to Date while insert or update
I have tried something
Insert into T1 (code,intime,att_date)values
(code,To_date(Date||time,'dd-mon-yyyy hh24mi'),att_date);
OR While update
Update T2 set Outtime=To_date(Date||time,'dd-mon-yyyy hh24mi') where...
I got an error Ora-01861
Regards
Srikkanth.M

You didn't show any example of your date or time values, butyou might need to add a space between them, like
To_date(Date || ' ' || time,'dd-mon-yyyy hh24mi')

Use of sequence numbers while inserting into tables

Hi,
Consider i have a stored procedure where i insert records into 30 to 40 tables.
for example i have a table A and a sequence SEQ_A for that table.
Is there any difference in performance in the following two ways of
insertion,
1. select SEQ_A.NEXTVAL into variable_a FROM DUAL;
INSERT INTO A VALUES(variable_a);
2.INSERT INTO A VALUES (SEQ_A.NEXTVAL).
I have 30 to 40 insert statements like that in method 1.
if i replace it by method 2. will there be any improvement in performance?
Thanks & Regards
Sundar

This could be interesting. I agree that triggers should be used for data integrity, though even better is to only allow write access to tables via stored procedures.
Anyway while you are waiting for the test case that shows triggers are faster, which could take some time, it is quick and easy to come up with a test case that shows the opposite.
SQL> create table t (id number, dummy varchar2(1));
Table created.
real: 40
SQL> insert into t select s.nextval, 'a' from all_objects;
29625 rows created.
real: 5038
SQL> rollback;
Rollback complete.
real: 40
SQL> create trigger tt before insert on t
2 for each row
3 begin
4 select s.nextval into :new.id from dual;
5 end;
6 /
Trigger created.
real: 291
SQL> insert into t select null, 'a' from all_objects;
29626 rows created.
real: 13350
SQL> rollback;
Rollback complete.
real: 1082
SQL>Note with triggers even the rollback took longer.
Martin

Use of Condition update while creating Condition Records

Hi Experts,
I have to maintain MRP for a product which will be applicable for only 1 particular order. after which system should pick up old MRP.
By using CONDITION UPDATE feature , i have tried to do it , but once maintained , its always picking new MRP for every order.
(If it being a record where only new price to be defaulted in one order and no need to create 2nd order , this is ok ., but not in my case)
Can any one suggest me how to go with this
Thanks in advance,
Jignesh

Hi,
This can be done using the CONDITION UPDATE
In the condition type check the CONDITION UPDATE AND SAVE IT
While creating the CONDITION RECORDS, maintain the values and click ont he ADDITIONAL DATA (F7) then maintain the value in the field MAXIMUM NUMBER OF ORDERS , PUT The sales order as 1.
Then try
Please revert if you need further details
thanks,
santosh

How we use group by function while inserting data through datablock

Hi All
i have datablock in tabulor form
i want when i insert data (commit) then data will insert in group by
example
my table is like that
desc table
dress_name     color             qty
and i am inserting data into it like this
dress_name    color     qty
nice_dress      BLK       1
nice_dress      BLK       1
nice_dress      BLK       1
vik_dress        GRY      1
vik_dress        GRY      1
vik_dress        GRY      1
i want when i retrive the data it will like this
dress_name    color     qty
nice_dress      BLK       3
vik_dress        GRY      3Thanks and Regards
Vikas Singhal
Edited by: vikas singhal on Feb 14, 2011 4:05 PM

Hi vikas singhal
before insert i need to group it is possible or notPls note : Whenever you do a "group by" or "order by" operation, Oracle will invoke a sorting operation. Using the "group by" inside SQL syntax is also useful for doing summaries
i want when i retrive the data it will like this Pls try the following...
SQL> select
2    dress_name,
3    color ,
4    qty,
5    count(quantity) Num , sum(quantity)summation -- may be the same
6   from
8    ur_table_name
9 group by dress_name   , color ,   qty ;u can also try Francois's Suggestion by creating a view based on the last Query...
want when i insert data (commit) then data will insert in group by
make the view to be insert from it as follow...
http://www.java2s.com/Tutorial/Oracle/0160__View/PerforminganINSERTUsingaView.htm
Hope this helps...
Regards,
Abdetu...

Getting Error While inserting a record in table PDSNR through Tcode PA30

Hi Experts,
Im doing a transaction in TCode PA30 by entering a pernr and infty as 14 and wage type.
My need is when im entering a particular wage type in PA30 with infotype 14 , for that particular wage type and infotype i need to assign a different cost centre. This requirement was doing now manually by changing the cost centre form EDIT - > Maintain Cost Assignment.
But my Client Needs to do it automatically. by comparing the wage type and infotype the cost centre needs to get automatically updated.
So i use the Enhancement EXIT_SAPFP50M_002 * INCLUDE ZXPADU02.* and wrote coding like below
CASE innnn-infty.
To check whether the record belong to pa0014
If so,check the wage type for the updation
If so update the values of cost center assignments in the table assob and asshe
when '0014'.
if innnn-subty eq '2211'.
Select the last updated sequence number in the table pdsnr
if sy-ucomm eq 'UPD' or sy-ucomm eq 'INS'.
select single * from pa0001 into wa_0001 where pernr eq INNNN-pernr and
                                               endda eq '99991231'.
if sy-subrc = 0.
call function 'ENQUEUE_EPPRELE'
EXPORTING
   MODE_PREL            = 'E'
   MANDT                = SY-MANDT
   PERNR                = INNNN-pernr
   INFTY                = INNNN-INFTY
   SUBTY                = INNNN-SUBTY
EXCEPTIONS
   FOREIGN_LOCK         = 1
   SYSTEM_FAILURE       = 2
   OTHERS               = 3
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
CLEAR : lv_pdsnr.
select MAX( pdsnr ) from pdsnr into lv_pdsnr.
lv_pdsnr = lv_pdsnr + 1.
    ls_assob-pdsnr = lv_pdsnr.
    ls_assob-pernr = INNNN-pernr.
    ls_assob-bukrs = wa_0001-bukrs. "'1001'.
    ls_assob-gsber = wa_0001-gsber. "'0001'.
    ls_assob-kokrs = wa_0001-kokrs. "'1000'.
    ls_assob-kostl = '1-1361'.
    ls_asshr-pdsnr = lv_pdsnr.
    ls_asshr-pernr = INNNN-pernr.
    ls_asshr-infty = innnn-infty.
    ls_asshr-subty = innnn-subty.
    ls_asshr-begda = sy-datum.
    ls_asshr-endda = '99991231'.
    ls_PDSNR-pdsnr = lv_pdsnr.
    ls_PDSNR-PDGRP = '5B'.
insert into pdsnr values ls_pdsnr.
insert into asshr values ls_asshr.
insert into assob VALUES ls_assob.
call function 'DEQUEUE_EPPRELE'
EXPORTING
   MODE_PREL       = 'E'
   MANDT           = SY-MANDT
   PERNR           = INNNN-pernr
   INFTY           = INNNN-INFTY
   SUBTY           = INNNN-SUBTY.
    ENDIF.
ENDIF.
ENDIF.
COMMIT WORK.
ENDCASE.
This is to update the three tables PDSNR, ASSOB,ASSHR.
Its getting Updated correctly, But when i goto EDIT - > Maintain Cost Assignment to do some changes and while saving the data i get the following Error Message :
You Cannot insert data in table : PDSNR.
Message no. P2715
Can Anyone please suggest me how to solve this issue.
Thanks,
Vijayan.R

Hi. Were you able to fix the error?

DAC Error: Error while inserting a record!

Hi,
I want to create a new DAC on my system but I am getting below error while trying to create record or saving any records.
Can't create reference
MESSAGE:::INSERT INTO W_ETL_OBJ_REF(OBJ_WID, OBJ_REF_WID, OBJ_TYPE, OBJ_REF_TYPE_CD, APP_WID, LAST_UPD, SOFT_DEL_FLG, ROW_WID) VALUES (?, ?, ?, ?, ?, ?, ?, ?)
Values :
KEY : 1
VALUE : 202CB962AC5975B964B7152D234B70
KEY : 2
VALUE : 202CB962AC5975B964B7152D234B70
KEY : 3
VALUE : W_ETL_SA
KEY : 4
VALUE : 1
KEY : 5
VALUE : null
KEY : 6
VALUE : 2011-10-12 15:17:11.586
KEY : 7
VALUE : N
KEY : 8
VALUE : 7716EB6EA78A5B2E2D3C2AE1CF204A2C
EXCEPTION CLASS::: com.siebel.etl.database.IllegalSQLQueryException
com.siebel.etl.database.DBUtils.batchUpdate(DBUtils.java:1946)
com.siebel.etl.gui.util.UncommitUpdateHelper.executeUpdate(UncommitUpdateHelper.java:84)
com.siebel.analytics.etl.client.data.dataobject.BaseDACObject.createReference(BaseDACObject.java:1362)
com.siebel.analytics.etl.client.data.dataobject.DACObject.createReference(DACObject.java:78)
com.siebel.analytics.etl.client.data.dataobject.BaseDACObject.createUpdateReference(BaseDACObject.java:1274)
com.siebel.analytics.etl.client.data.dataobject.BaseDACObject.createOwnedObject(BaseDACObject.java:565)
com.siebel.analytics.etl.client.data.dataobject.BaseDACObject.create(BaseDACObject.java:544)
com.siebel.analytics.etl.client.data.dataobject.UpdatableDataObject.createUpdate(UpdatableDataObject.java:210)
com.siebel.analytics.etl.client.data.dataobject.DACObject.createUpdate(DACObject.java:213)
com.siebel.analytics.etl.client.data.dataobject.UpdatableDataObject.createUpdate(UpdatableDataObject.java:198)
com.siebel.analytics.etl.client.data.model.ResultSetParser.insertNewRecord(ResultSetParser.java:226)
com.siebel.analytics.etl.client.data.model.UpdatableDataTableModel.insertNewRecord(UpdatableDataTableModel.java:122)
com.siebel.analytics.etl.client.data.model.DACTableModel.insertNewRecord(DACTableModel.java:335)
com.siebel.analytics.etl.client.data.model.DACTableModel.insertNewRecord(DACTableModel.java:320)
com.siebel.analytics.etl.client.data.model.UpdatableDataTableModel.updateRecord(UpdatableDataTableModel.java:76)
com.siebel.analytics.etl.client.view.edit.EditObject.save(EditObject.java:326)
com.siebel.analytics.etl.client.view.edit.EditObject.actionPerformed(EditObject.java:616)
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
java.awt.Component.processMouseEvent(Component.java:6041)
javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
java.awt.Component.processEvent(Component.java:5806)
java.awt.Container.processEvent(Container.java:2058)
java.awt.Component.dispatchEventImpl(Component.java:4413)
java.awt.Container.dispatchEventImpl(Container.java:2116)
java.awt.Component.dispatchEvent(Component.java:4243)
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
java.awt.Container.dispatchEventImpl(Container.java:2102)
java.awt.Window.dispatchEventImpl(Window.java:2440)
java.awt.Component.dispatchEvent(Component.java:4243)
java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
::: CAUSE :::
MESSAGE:::ORA-01400: cannot insert NULL into ("DW"."W_ETL_OBJ_REF"."APP_WID")
EXCEPTION CLASS::: java.sql.SQLIntegrityConstraintViolationException
oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:737)
oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:647)
oracle.jdbc.driver.T2CPreparedStatement.executeForDescribe(T2CPreparedStatement.java:530)
oracle.jdbc.driver.T2CPreparedStatement.executeForRows(T2CPreparedStatement.java:713)
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307)
oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3449)
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3530)
oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1350)
com.siebel.etl.database.cancellable.CancellablePreparedStatement.executeUpdate(CancellablePreparedStatement.java:91)
com.siebel.etl.database.DBUtils.batchUpdate(DBUtils.java:1942)
com.siebel.etl.gui.util.UncommitUpdateHelper.executeUpdate(UncommitUpdateHelper.java:84)
com.siebel.analytics.etl.client.data.dataobject.BaseDACObject.createReference(BaseDACObject.java:1362)
com.siebel.analytics.etl.client.data.dataobject.DACObject.createReference(DACObject.java:78)
com.siebel.analytics.etl.client.data.dataobject.BaseDACObject.createUpdateReference(BaseDACObject.java:1274)
com.siebel.analytics.etl.client.data.dataobject.BaseDACObject.createOwnedObject(BaseDACObject.java:565)
com.siebel.analytics.etl.client.data.dataobject.BaseDACObject.create(BaseDACObject.java:544)
com.siebel.analytics.etl.client.data.dataobject.UpdatableDataObject.createUpdate(UpdatableDataObject.java:210)
com.siebel.analytics.etl.client.data.dataobject.DACObject.createUpdate(DACObject.java:213)
com.siebel.analytics.etl.client.data.dataobject.UpdatableDataObject.createUpdate(UpdatableDataObject.java:198)
com.siebel.analytics.etl.client.data.model.ResultSetParser.insertNewRecord(ResultSetParser.java:226)
com.siebel.analytics.etl.client.data.model.UpdatableDataTableModel.insertNewRecord(UpdatableDataTableModel.java:122)
com.siebel.analytics.etl.client.data.model.DACTableModel.insertNewRecord(DACTableModel.java:335)
com.siebel.analytics.etl.client.data.model.DACTableModel.insertNewRecord(DACTableModel.java:320)
com.siebel.analytics.etl.client.data.model.UpdatableDataTableModel.updateRecord(UpdatableDataTableModel.java:76)
com.siebel.analytics.etl.client.view.edit.EditObject.save(EditObject.java:326)
com.siebel.analytics.etl.client.view.edit.EditObject.actionPerformed(EditObject.java:616)
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
java.awt.Component.processMouseEvent(Component.java:6041)
javax.swing.JComponent.processMouseEvent(JComponent.java:3265)
java.awt.Component.processEvent(Component.java:5806)
java.awt.Container.processEvent(Container.java:2058)
java.awt.Component.dispatchEventImpl(Component.java:4413)
java.awt.Container.dispatchEventImpl(Container.java:2116)
java.awt.Component.dispatchEvent(Component.java:4243)
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
java.awt.Container.dispatchEventImpl(Container.java:2102)
java.awt.Window.dispatchEventImpl(Window.java:2440)
java.awt.Component.dispatchEvent(Component.java:4243)
java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
Why it happened and how to solve it?

The error is not because a table is MISSING..it is because its trying to insert a NULL and its failing: ORA-01400: cannot insert NULL.
I would check the following:
Make sure all DAC related patches are applied (you can find these on metalink) for the DAC version you are on
Is this your first time to try a load? Is there any load that may not have cleaned up all process that was previously runninng..if so restart the DAC services and retry
Make sure the DAC repository metadat tables are created properly. Go to the table in question W_ETL_OBJ_REF and see if it is correctly created
Did you assemble all Subject Areas and successfully Build the execution plan? If not, do that and retry.
Let me know how it goes.
if this is helpful, please mark as correct or helpful.

Getting error msg while inserting a record

HI
Am getting error msg while am inserting a new record. Am unable to view the data that i inserted in to database. If any one can help in sorting of the problem plz help. I used the following code in Application Module(AM) and Controller(CO)
processRequest()
-- am.invokeMethod("insertmethod");
processFormRequest()
-- if(pageContext.getParameter("Create")!=null)
-- am.invokeMethod("savemethod");
In AM Code
public void insertmethod()
EOVOImpl vo=getEOVO1();
if(!vo.isPreparedForExecution())
{ vo.executeQuery(); }
Row ro=vo.createRow();
vo.insertRow(ro);
ro.setNewRowState(Row.STATUS_INITIALIZED);
public void savemethod()
{ OADBTransaction oa=getOADBTransaction();
oa.commit(); }
Error
Attribute SummaryFlag in kiInsertAM.kiInsertEOVO1 is required

Hi,
Either on the form you don't have SummaryFlag field or you forgot to map VO attribute i.e. SummaryFlag to that field.
If you don't have SummaryFlag field on form then you need to set it programatically before committing record.
Please check and let us know.
Regards,
Mukesh Uchaniya

ORA-00997: illegal use of LONG datatype - while inserting a record

Similar Messages

Maybe you are looking for