Business Objects Data Services Error 54003
+ Analytics Conference: Oct 18, Mastering SAP BI, Melbourne: Oct 23. Job errors Search this topic...|Search DI: Designer and Job Design...|Search Box Select a search Explain These Choices... --------------------Recent Topics (All Forums) Unanswered Posts Register or Login to Post Forum Index -> Data Integrator -> DI: Designer and Job Design Author Message ay1224Principal MemberJoined: 30 Jul 2007Posts: 182Location: USA Posted: Sun Jul 04, 2010 8:53 amPost subject: Job errors Hi Guys, When a chain of Workflows are run as one job, we are getting the following error after executing a workflow which loades 2 millins of rows . job error log: SQL submitted to ODBC data source resulted in error <[MySQL][ODBC 5.1 Driver][mysqld-5.0.77-log]MySQL server has gone away>. The SQL submitted is . job Trace log: Workflow is terminated due to an error <70404>. But when we seperate out the workflows into different jobs, they executed fine for the first time. But when the recurrent schedule executed next time we are getting the following error job error log: SQL submitted to ODBC data source resulted in error <[MySQL][ODBC 5.1 Driver][mysqld-5.0.91-rs]Subquery returns more than 1 row>. job trace log: workflow is terminated due to an error <54003>. Any help is appreciated. Thanks Back to top Werner DaehnForum DevoteeJoined: 17 Dec 2004*6Posts: 10590Location: Germany Posted: Mon Jul 05, 2010 12:50 amPost subject: Re: Job errors I'd guess the two errors are unrelated. The first one might happen because of timeouts in mysql. The dataflow starts, connects to the repo, reads and loads all the data and in the meantime there is nothing to do for the repo connection but wait. Once all the data has been processed the repo should get updated with the load statistics of the dataflow......but mysql dropped the connection as it was idle too long. The second one could be cause be query/data. Example: select * from table1 where changedate >= (select startdate from statusta
Data Services and Data QualityWhere is this place located?All Places Data Services and Data Quality 7 Replies Latest reply: Sep 3, 2012 4:19 PM by Lelian Cestari Tweet Data Services Error 50316 Sam Varughese Jun 16, 2011 5:15 PM Currently Being Moderated Hello, I am getting the following error when I try to run a job in Data Services (DS) that contains a ABAP Data Flow. It's pulling data from a http://www.forumtopics.com/busobj/viewtopic.php?p=737457 table in R/3 and putting data in Teradata. In my DS job, I can specify which date range to pull. For some date ranges, I am getting this error. Other date ranges, the DS job runs fine. This tells me, there is something wrong with the data..but, not exactly sure https://scn.sap.com/thread/1976716 which record in the data is causing the problem. I tried running the job with "trace row" turned on..and didn't find any problems with the record it's trying to process.This is the error I am getting:(12.2) 06-15-11 18:19:20 (E) (9109546:0001) FIL-080101: Cannot open file /BODI/dev/DS/dataservices/log/JobServer_5/dbods__dsdev8/error_06_15_2011_18_18_12_637__3936d82e_535a_4fbb_b4d2_416473b80f53.txt.idx in 'rb' mode. OS error message . OS error number <2>. al_engine reached 'fileopen_retry_time' limit so exiting (12.2) 06-15-11 18:19:20 (E) (9109546:0001) RUN-050316: |Session JOB_CON_SAP_BCONT Error during the execution of the job:JOB_CON_SAP_BCONT (12.2) 06-15-11 18:19:20 (E) (9109546:0001) RUN-050304: |Session JOB_CON_SAP_BCONT Function call failed, due to error <50316>: . (12.2) 06-15-11 18:19:20 (E) (9109546:0001) RUN-050316: |Session JOB_CON_SAP_BCONT Error during the execution of the job:JOB_CON_SAP_BCONTThis is our Installation Details: Designer Version: 12.2.2.2 Job Server: 12.2.3.0 Job Engine: 1
while callingonChangeDocID How to pass value of Input control to othertabs → Data flow is terminated due to error. December 4, 2014 1 Comment SAP BODS job is running till the end but at the last data flow failing with the below error: Data flow is https://arjunjune.wordpress.com/2014/12/04/data-flow-is-terminated-due-to-error/ terminated due to error <70301>. Further error: Execution of for target failed. Possible causes: (1) Error in the SQL syntax; (2) Database connection is broken; (3) Database related errors such as transaction log is full, etc.; (4) The user defined in the datastore has insufficient privileges to execute the SQL. If the error is for preload or postload operation, or if it is for regular load operation and load triggers are defined, check business objects the SQL. Otherwise, for (3) and (4), contact your local DBA. Oracle <> error message for operation : .|| Share this:TwitterFacebookLike this:Like Loading... Related Filed under BODS Tagged with BODS One Response to Data flow is terminated due to error. rajgadiraju says: December 21, 2014 at 8:27 pm the actual problem is that the partitio key value you are trying to insert is out of bounds. business objects data It is not an ETL issue. It is a data issue. "ORA-14400: inserted partition key does not map to any partition". please give more details if you still have th eissue. Reply Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. Blog Stats 55,688 hits All Posts All Posts Select Month September 2016 (6) August 2016 (5) April 2016 (2) March 2016 (1) February 2016 (1) December 2015 (1) July 2015 (1) May 2015 (1) February 2015 (3) December 2014 (17) November 2014 (34) October 2014 (12) September 2014 (10) August 2014 (7) April 2014 (5) March 2014 (2) December 2013 (1) October 2013 (1) September 2013 (1) August 2013 (13) July 2013 (4) June 2013 (4) April 2013 (7) March 2013 (13) February 2013 (3) January 2013 (21) December 2012 (4) Facebook Page Facebook Page Top Posts & Pages EMP and DEPT table script - SQL Server Account information not recognized: Could not reach CMS ':6400'. Failed to update cache for execution. Program will e