Behavior Of Demantra Programs Using DBMS_JOB Utility In A RAC Enabled Instance.
(Doc ID 1560138.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Demantra Demand Management - Version 7.3.1 and later
Information in this document applies to any platform.
Demantra installed in a RAC enabled instance. We found there are couple of seeded Demantra Procedure/Packages (e.g. PROPORT, CTO_CALC, UPGRADE_DB_AUDIT etc) which are using DBMS_JOB utility without using the instance_id parameter. We have some other custom programs which were using DBMS_JOB utility without using the instance_id parameter. Those are running fine in a Non-RAC instance. But while those are running in a RAC enabled instance, those are running fine in one node while not running at all when switching to another node. So we had to change those programs to use instance_id parameter in the DBMS_JOB utility & forcing those to run in a given node.
Sometimes we are switching node in our RAC instance. Since we had issue with our custom programs, we are suspecting the same would happen for Demantra seeded programs.
So can you please confirm the behavior of the seeded Demantra programs which are using DBMS_JOB utility without using the instance_id parameter in a RAC enabled instance?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document