Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
1.1.6, 1.2.2
-
None
-
None
-
Vmware 6.5 with 3 Performance Module and 2 user module.
Os : Oracle Linux 7
Pentaho : 8.1 with repository
-
2019-01, 2019-02
Description
Hi,
I've a job with Pentaho with some dml transaction (dml) and as the last step the bulk loader columnstore is launched.
The job failed caused by this error :
step until steps finish.0 - Finished processing (I=0, O=0, R=11, W=11, U=0, E=0)
2019/01/08 09:36:02 - Delete 2.0 - ERROR (version 8.1.0.0-365, build 8.1.0.0-365 from 2018-04-30 09.42.24 by buildguy) : Error in step, asking everyone to stop because of:
2019/01/08 09:36:02 - Delete 2.0 - Error inserting/updating row
2019/01/08 09:36:02 - Delete 2.0 - (conn=79) Internal error: IDB-2009: Unable to perform the delete operation because mcsapi with PID 7599 is currently holding the table lock for session 103737.
In my opinion, when the job starts the bulk loader starts immediately and performs the exclusive lock of the table even if it will start as the last step, in fact, if the bulk step is disabled, the job is executed successfully.
This is very blocking for us because it binds us to perform complex jobs on pentaho.
Thanks,
Regards
Nicola Battista
