Post-Upgrade Steps for SAS Web Infrastructure Platform Data Server

You need to run PostgreSQL commands to upgrade the database. These commands are located in the following directory:

!SASHOME/SASWebInfrastructurePlatformDataServer/9.4/bin

Note: If you are performing the upgrade on the UNIX operating environment and these commands fail, you might need to set environment variables.See Set Environment Variables for UNIX for more information.

When you run these commands, substitute the correct values for the host name, port number, and user ID for your database. These commands prompt you to enter a password.

On the upgraded server, run the pg_dump command. This command creates a script file that contains the SQL commands that are needed to reconstruct the database:
```
pg_dump --host=host_name --port=nnnn --username=database_owner_userID 
--password –Fp -O brmdb > brmdb.dump
```
The –O option exports the database without commands that set ownership of any of the database objects.
Stop SASServer7.
If SAS Model Manager 13.1 is installed on the upgraded server, run the following command to create a backup of the SAS Model Manager tables:
```
pg_dump --host=host_name --port=nnnn --username=userID 
--password -t sas mm* database_name > mmbackup-131.dump
```
Note: Specify the user ID for Decision Manager Common Middle Tier. Do not specify the user ID of the database owner account.
On the upgraded server, run the dropdb command to drop the database that was created by the SAS Deployment Wizard:
```
dropdb --host=host_name --port=nnnn --username=database_owner_userID 
--password database_name
```
On the upgraded server, run the createdb command to create a new, empty database:
```
createdb --host=host_name --port=nnnn --username=database_owner_userID 
--password database_name
```
On the upgraded server, restore the exported database:
```
psql --host=host_name --port=nnnn -f brmdb.dump database_name userID
```
Note: Specify the user ID for Decision Manager Common Middle Tier. Do not specify the user ID of the database owner account.

Note: You might see messages such as no privileges were granted for "public" or role name does not exist. These messages mean that these users are no longer applicable to the upgraded database instance and can be ignored.
Run the migration_brm_2.1_to_brm_2.2_sql migration script that is located in the following directory:

!SASHOME/SASDecisionManagerCommonMidTierforDecisionManager/2.2/Config/Deployment/dbscript/postgres/migration

Note: In a multi-tier environment, copy the script to the server tier before you run it.
Run the edm_workflow_interface_create_*.sql scripts. These scripts are located in the following directory:

!SASHOME/SASDecisionManagerCommonMidTierforDecisionManager/2.2/Config/Deployment/dbscript/postgres

Note: In a multi-tier environment, copy the scripts to the server tier before you run them.
Run the following scripts, in the order listed:
1. edm_workflow_interface_create_table.sql
2. edm_workflow_interface_create_sequence.sql
3. edm_workflow_interface_create_constraint.sql
4. edm_workflow_interface_create_trigger.sql
5. edm_workflow_interface_required_inserts.sql
Restore the SAS Model Manager tables by using the backup that you created in Step 3:
```
psql --host=host_name --port=nnnn -f mmbackup-131.dump database_name userID
```
Note: Specify the user ID for Decision Manager Common Middle Tier. Do not specify the user ID of the database owner account.
Review the configuration properties in SAS Management Console. Ensure that the values are appropriate for the new environment. See Review Business Rules Manager Web Properties for more information.
Update your user group memberships as needed. See Update User Group Membership for more information.