Failed to unlock deployment list

Question

Hi guys!
I need help because when I run a workflow that call several mappings, it stops in the middle of one of the mappings, looks like it ended up successfully (all green, 0 errors in the log). I have no log file in the $OWB_HOME/owb/log folder, and the only error message I can find is in the xterm where I launched OWB client :
doAsynchronousExecution
Task notification null PRC_DMT_MAIN
Execute operation NativeExecution OWF_BIDEALERS_LOCATION PRC_DMT_MAIN
Task notification null PRC_DMT_MAIN:MPG_DIM_SOCIETE_SITE_MARQUE
Task notification OK PRC_DMT_MAIN
Execute operation NativeExecution OWF_BIDEALERS_LOCATION PRC_DMT_MAIN
Task notification OK PRC_DMT_MAIN:MPG_DIM_DMT_TEMPS
Task notification OK PRC_DMT_MAIN:MPG_DIM_SOCIETE_SITE_MARQUE
Task notification OK PRC_DMT_MAIN:MPG_DIM_DMT_TEMPS
Failed to unlock deployment list
Failed to unlock deployment list
PRC_DMT_MAIN is my workflow, and all the MPG are the mappings is calls. Several are missing.
A bit more about the context :
- we have a dev. environment running on windows server and everything is fine,
- we have a test environment running on linux SLES where I have this issue,
- we have written an OMB*Plus script to perform the erport/import/deployment and it has run perfectly so far,
- we already have been through the OS-specific problems (folder separator, case sensitiveness, ...)
I googled the error message "Failed to unlock deployment list" but didn't get anything helpful.
Can anybody please advise?
Thanks in advance!
Ced.

Answer 1

Nigel,
My fault, on the log : I renamed the log file, expecting OWB to create a new one but everything was actually logged in the renamed file.
My client is working on the server. I use putty and XMing to get it displayed on my PC.
I did not try with today delta load, but with the Monday full load, to run each part separately. It allowed me to complete the process. Thus it's not the workflow contents that fails.
One weird thing is in the log file today. I have to explain a bit more:
Both full and delta workflow contain 1 workflow for each layer (ODS, DWH, DMT) the difference is the DWH workflow that is not exactly the same. The two DWH workflows and the DMT workflow all call some mappings and also call a set of workflows.
The strange thing is that the delta didn't reach the end of the ODS. The DWH and DMT weren't even started. But the log file reports a start of the DMT workflow called by the delta workflow at the same time as the ODS. The DWH isn't started, while the main workflow sequentially calls ODS, DWH and then DMT.
The funny thing is that the DMT seems to run ( while it is not supposed to ) and to stop at the same place as in the full : I have a log for the same 2 DMT mappings.
I believe that there is something somewhere that remains from former executions and that is re-executed for some reason.
I also think that if my delta stops, it is not due to the ODS, but due to the fact that this ghost DMT session that runs in parallel says "stop" to the whole process while the ODS is running.
2008/07/02-15:15:19-CEST      1DE0C09     Initializing execution for auditId= 227186 parentAuditId= 227181 topLevelAuditId=227181 taskName=PRC_SCH_DELTA:PRC_ODS_MAIN
2008/07/02-15:15:19-CEST      1F2F70A     Initializing execution for auditId= 227205 parentAuditId= 227181 topLevelAuditId=227181 taskName=PRC_SCH_DELTA:PRC_DMT_MAIN
Finally, I think that the issue isn't in the workflows themselves as the same issue happens on 2 different workflows.
Can you please advise?
Thanks for your help so far!
Ced.
Unfortunately I can't go any further :