Upgrading to Simphony Release 18.2

Simphony version 18.2 performs an upgrade from Simphony version 2.9 or later. To enhance your system’s security, during upgrades, the Simphony installation application enables you to physically separate the Transaction (MCRSPOS) database from the Security (MCRSCACHE) database (onto another database server), and then proceed with the upgrade. Oracle strongly recommends storing these databases on separate database servers. The following sections review three possible upgrade scenarios:

When upgrading in certain environments, you may experience the error ORA-25408, which is an Oracle Client related issue outside of Simphony. This condition is caused by environmental network timeouts being reached. To work around this issue, add the parameter SQLNET.INBOUND_CONNECT_TIMEOUT=120 to the Sqlnet.ora file on the database server.

  1. Ensure that the Simphony application and database servers meet the requirements listed in Pre-Installation Tasks.
  2. Log in and download the Simphony release 18.2 installation application from the Oracle Technology Network (OTN) website at https://edelivery.oracle.com/.
  3. Run the Setup, and then click Next.

    If the application and the database are on separate servers, run the installation application on the application server.

  4. Enter the logon credentials for a database administrator, and then click OK.

    • If you are using an Oracle database, enter the credentials for the SYS user.

    • If you are using Microsoft SQL Server, enter the credentials for the SA user.

    Beginning with the Simphony 2.10 release and later, you can upgrade application components on servers with or without downloading CAL Packages to the Simphony database. This flexibility can speed up the upgrade process on properties using multiple application servers.

    Figure 1-1 Simphony Components Installation Options

    This figure shows the options when installing Simphony components during an upgrade.

Parent topic: Upgrading Simphony