This content has been marked as final. Show 5 replies
I think this information will be useful. Can you please give me the example of API with STARTSCEN ? The Use of OK and KO I know but with your example, its difficult to understand. If required, please mail me the screen shot of package digram on email@example.com
I am using $U scheduler and it is a product developed by ORSYP (French company) www.orsyp.com
Requirement in details:
$U does indeed accept return codes, however, it seems that ODI is sending back “return code 0” when the PKG fails, which is understood by $U as “all OK”, the idea would be to have a different return code when the PKG fails (I am just rep-phrasing the original statement)
In Knowledge Module Developer's Guide for Oracle Data Integrator you could find information about this and other Substitution APIs. Note that RC (Return code) = 0 indicates no error. My proposition is:
1) You have some scenario SCEN_A and you want to know the status of its execution
2) You could make PKG_B with steps SCEN_A and the next step you could place procedure, inserting the value of <%=odiRef.getPrevStepLog("RC")%> in a temp table like
create table ODI_SCENS
set SCEN_STATUS = case when <%=odiRef.getPrevStepLog("RC")%> = 0 then 'OK' else 'KO' end
where SCEN_NAME = <your scenario name>;
And you third party app could use this table. It seems to be appropriate for different third party app.
Another possible solution may be to write some java code with ODI SDK (Calling ODI scenario fom java program
I am using below command to call different packages one by one-
D:\oracle\product\11.1.1\Oracle_ODI_1\oracledi\agent\bin\startscen "PKG_POZ_BOSS_OMP_BSMASTERSTOCK" "-1" "TEST" "-NAME=btvmd79_odi_agent"
Isn't there any way to return the failure/success of package execution using any option with STRTSCEN command? As suggested by you how can I asked each time $U scheduler to read from the error table. The above mentioned cmd is used to call different packages one by one sequentially. So the $U is scheduled with above command for all developed packages--near about 50-80 packages are called using above STARTSCEN cmd with different package name
Thanks for the quick response.