Page 1 of 1

unable to insert data into a table

Posted: Mon Apr 02, 2007 11:59 am
by ravi468
hi ,


i had a job with a sequential file and a oracle stage .when i connected to one instance it worked fine.i was able to load data into the table.


i had the same job but connected to different instance of oracle . now i am i am getting an error say

The runLocally() of the operator failed.
Operator terminated abnormally: runLocally did not return APT_StatusOk.

but one thing is i am import matadata form that instance.

please help me out.

Posted: Mon Apr 02, 2007 12:10 pm
by ray.wurlod
Do you have appropriate table privileges in the new instance?

Posted: Mon Apr 02, 2007 12:14 pm
by ravi468
i do have all the privilages required

Posted: Mon Apr 02, 2007 12:16 pm
by Madhusv
Your error Message is not complete, Provide more info. Because this message is common.

Posted: Mon Apr 02, 2007 12:24 pm
by ravi468
Oracle_Enterprise_2,1: Unable to insert a record into the table.
racle_Enterprise_2,1: Records inserted: 0
Records used for update: 0
Records rejected: 0
Total records: 0.

Oracle_Enterprise_2,1: The runLocally() of the operator failed.
Oracle_Enterprise_2,1: Operator terminated abnormally: runLocally did not return APT_StatusOk

racle_Enterprise_2,0: Array execute failed for insert:
insert is: INSERT
INTO
incntv
(SELLING_SRC_CD, INCNTV_LVL_NBR, MODEL_YEAR, INCNTV_CD, INCNTV_LVL_DESC, LOAD_ID, LOAD_TIMSTM)
VALUES
( :SELLING_SRC_CD, :INCNTV_LVL_NBR, :MODEL_YEAR, :INCNTV_CD, :INCNTV_LVL_DESC, :LOAD_ID, :LOAD_TIMSTM)
sqlcode is: -1843
esql complaint: ORA-01843: not a valid month
.

Posted: Mon Apr 02, 2007 12:27 pm
by Madhusv
See this is because of bad data or date , "esql complaint: ORA-01843: not a valid month "
Do date validation before inserting or correct the source data.

Posted: Mon Apr 02, 2007 1:43 pm
by novneet
I agree this must be due to a invalid date, verify the date before inserting. Which genrally should be followed to avoid any issues in live environment.
Check the format of date u are inserting the data in?

Posted: Tue Apr 03, 2007 8:30 pm
by csrazdan
I think you need to check structure of table in both databae instances. It might be VARCHAR2 in one and DATE in another. Also execute this SQL on the SQL prompt: select sysdate from dual;
Verify that the database date format is same for both the instances.

Hope it helps......