The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The 3.5.1SP1 upgrade calls the needed SQL scripts to perform the upgrade operation based on the existing version found.
Important: Follow manual upgrade steps if the database schema has been modified for this setup.
■You must have the appropriate database rights to run the scripts.
1. Install the OCI client that is compatible with the Oracle database server, if it not already installed.
3. On the Run dialog box, in the Open field, type cmd and press Enter.
4. Run the following scripts in the order as they are listed.
a. Log in as the user/schema that the process db is named ( OrchestratorProcess is the default user/schema for previous versions of Cisco Process Orchestrator), then enter:
b. Log in as the user/schema that the report db is named ( OrchestratorReporting is the default user/schema for previous versions of Cisco Process Orchestrator), then enter:
– Execute OrchestratorReportingUpgrade.sql
5. Install Cisco Process Orchestrator 3.5.1SP1. To upgrade the previous Cisco Process Orchestrator server, see Installing Using Oracle).
Important: If the Process Orchestrator server is configured to use Windows authentication to access the process database, manually upgrade the Process database and Reporting database before upgrading to Cisco Process Orchestrator 3.5.1SP1.
Note: If you are upgrading from Cisco Process Orchestrator 3.5.1 to 3.5.1SP1 using SQL server, you must have db_owner role assigned for OrchestratorProcess and OrchestratorReporting to make db schema changes.
Note: If needed, you must rename the database names in the scripts to the current database names on your environment before running the scripts.
■You must have the appropriate database rights to run the scripts.
1. Open Microsoft SQL Server Management Studio.
a. \Release\DatabaseScripts\MSSQL\OrchestratorProcessUpgrade.SQL
b. \Release\DatabaseScripts\MSSQL\OrchestratorReportingUpgrade.SQL
3. Edit \Release\DatabaseScripts\MSSQL\OrchestratorProcessViews.SQL :
a. Change the database name in the script if it is not the default name OrchestratorProcess.
4. Install Cisco Process Orchestrator 3.5.1SP1. To upgrade the previous Cisco Process Orchestrator server, see Installing Using MSSQL.
■Back up process and reporting databases.
■You must have the appropriate database rights to run the scripts.
\Release\DatabaseScripts\MYSQL\OrchestratorProcessUpgrade.SQL
3. Edit \Release\DatabaseScripts\MYSQL\OrchestratorProcessViews.SQL :
–Change the database name in the script if it is not the default name OrchestratorProcess.
4. Run the following script manually on reporting database:
– OrchestratorReportingUpgrade.SQL
–Change the database name in the script if it is not the default name OrchestratorReporting.
Note: MariaDB for reporting database is not supported. It could be either SQL Server Or Oracle. Use the appropriate connection to run the script.
5. Install Cisco Process Orchestrator 3.5.1SP1. To upgrade the previous Cisco Process Orchestrator server, see Installing Using MariaDB.