Monitoring Data Integration Tasks using Oracle PLSQL
One of the coolest stories for OCI SDKs was the availability as PLSQL APIs from within the OCI Autonomous Database family — both ADW and ATP. This lets you do all kinds of interesting stuff with OCI Data Integration, Data Catalog and all other services! This post is a follow on to the post on ‘Executing Data Integration Tasks using Oracle PLSQL’, here we will see how to monitor them.
In that post we saw how you could execute tasks in Data Integration using a PLSQL anonymous block, here we will create a couple of wrapper PLSQL functions — one to execute the Data Integration task;
If you have parameters to pass to your task then check this example here;
Then to monitor the task run, this example function simply returns the status;
These functions can be used to execute tasks and monitor status, remember the jobs can also be monitored in the OCI Console as below;
Monitor the jobs executed earlier using the PLSQL API or using the PLSQL APIs to monitor task runs.
All of the PLSQL OCI Data Integration functions are defined here and the types are defined here. In this example I used the SQL Developer Web from within OCI Console to execute this…..
Very cool, and what makes it better is that as new functionality is added into the OCI Data Integration service and any other service, the ADBs are automatically updated.
See here for more information on OCI Data Integration;
There’s a post here on using python SDK to execute these tasks too;
Have fun, check out the functions!
