Symptom:
When I install an Orchestrator and provide the runtime database in the Runtime Database screen, the following exception is thrown:
The Runtime Database is being used by another orchestrator.
Solution:
CA Process Automation Version 4.0 does not allow you to share the same runtime database across Orchestrators. Typically the solution for this is to create the Runtime Database using another name, or hosted by a separate database server.
Use the following procedure only if you want to retain the runtime information in this database in a new CA Process Automation instance. This is rarely the case, and resetting the RuntimeDbOrchestratorID has many undesirable side effects, including making it impossible for running operators in this runtime database to complete. All agents and secondary Orchestrators must also be reinstalled, among other issues. If you have any doubt whether this procedure is appropriate for your problem, consult Technical Support before you proceed.
In this release, a new Properties table is created in the database with the following columns:
Whenever an Orchestrator uses a Runtime database, a new row is inserted in the Properties table. The PropKey is RuntimeDbOrchestratorID and the PropValue is the unique ID of the Orchestrator.
When another Orchestrator requests for the same database, the database is validated in the Properties table. If the unique ID of the requesting Orchestrator is not similar to the Propvalue, then the following message appears:
The Runtime Database is being used by another Orchestrator.
Important! The runtime database entries are not deleted even after you uninstall the product.
To use the same database again for Runtime, execute the following SQL query and delete the corresponding row form the Properties table.
delete from properties where propkey = 'RuntimeDbOrchestratorID'
Note: For an alternative solution that retains the Orchestrator ID, see TEC596124
|
Copyright © 2014 CA.
All rights reserved.
|
|