I don't know the "Oracle DAC Scheduler", but I can say that in most competitive solutions Control-m stands out in the following points:
1- One of the oldest job scheduling solutions on the market, most used among the largest companies in the world.
2- It has knowledge modules that allow native integration with various solutions.
3- It has a large community that helps you solve situations where others already know a solution.
4- Allows you to integrate and monitor job schedule routines from various environments in a simplified and end-to-end way, own Datacenter, mainframe, cloud (AWS, Azure, and Google), containers (Kubernets) etc...
5- Allows you to identify delays in routines, what is the root cause and impact on your business through the "Impact Manager" and take actions before executing SLAs.
6- Allows the creation of workflows from multiple applications using the Jobs-as-Code approach. This allows you to build and test these workflows in a CI/CD pipeline.
The points above are great, but see more details at this link:
Control-M simplifies application and data workflow orchestration on premises or as a service. It makes it easy to build, define, schedule, manage, and monitor production workflows, ensuring visibility, reliability, and improving SLAs.
Accelerate new business applications into production—by embedding workflow orchestration into your CI/CD pipeline
Scale Dev and Ops collaboration, with a Jobs-as-Code approach
Simplify workflows across hybrid and multi-cloud environments with AWS, Azure and...
Hi!
I don't know the "Oracle DAC Scheduler", but I can say that in most competitive solutions Control-m stands out in the following points:
1- One of the oldest job scheduling solutions on the market, most used among the largest companies in the world.
2- It has knowledge modules that allow native integration with various solutions.
3- It has a large community that helps you solve situations where others already know a solution.
4- Allows you to integrate and monitor job schedule routines from various environments in a simplified and end-to-end way, own Datacenter, mainframe, cloud (AWS, Azure, and Google), containers (Kubernets) etc...
5- Allows you to identify delays in routines, what is the root cause and impact on your business through the "Impact Manager" and take actions before executing SLAs.
6- Allows the creation of workflows from multiple applications using the Jobs-as-Code approach. This allows you to build and test these workflows in a CI/CD pipeline.
The points above are great, but see more details at this link:
www.bmc.com
Regards,
Anderson Amaro