| Agile Product Lifecycle Management Database Upgrade Guide Release 9.3.3 E39282-03 |
|
 Previous |
 Next |
| Agile Product Lifecycle Management Database Upgrade Guide Release 9.3.3 E39282-03 |
|
Previous |
Next |
You can upgrade your database from your currently installed version to Agile PLM 9.3.3 using the Automated Upgrade Tool.
The upgrade tool takes inputs from a property file and completes the upgrade using your existing database as the source database. When complete, the destination database is upgraded to the 9.3.3 release.
To become familiar with the upgrade procedure, it is recommended that you prepare a separate test environment and perform the upgrade there first. It is highly recommended that you run the upgrade on the system that is hosting the destination database.
Agile PLM supports Oracle 11g databases. You MUST have the Oracle Database Server on the system where you are installing the Agile database before starting the upgrade. For information on installing Oracle databases, refer to the related documentation available on the Oracle Technology Network (OTN) website http://www.oracle.com/technetwork/documentation/agile-085940.html.
If you are upgrading from an 8.5 product and your Oracle 8i home is not installed on the system where you are performing the upgrade, you must map (or mount) a local drive on the destination system to point to the existing Oracle 8i home. Also, if you are upgrading from an 8.5 product, you must create a new Oracle database instance for the new Agile PLM product version and try to reuse the existing 8.5 Oracle instance.
|
Note: Ensure binary compatibility of the mounted binaries (for example, ensure that you map a drive containing Windows binaries to a Windows system only). |
You must also have JRE 1.7 installed. The JAVA_HOME environment variable must be set to the path for that JRE on the system where AUT is run.
The entire upgrade process may take a considerable amount of time depending on the size of the database and the hardware configuration. Based on past experience, 75% of the upgrade process is spent on upgrading and backing up the database. We strongly recommend running the schema backup and upgrade on a test system so that appropriate time can be scheduled for the production deployment.
There are two types of upgrade:
Upgrade destination in place - Source database is upgraded with the existing database user. In the aut.properties file, the parameter sourceEqualsDestination is set to true.
Upgrade source to destination - A new database user is created in the destination database instance. In the aut.properties file, the parameter sourceEqualsDestination is set to false.
For Agile PLM or Agile Advantage (AA) upgrade, a new database user is created in the destination database instance using useragile.sql, and then the source database is upgraded to that user.
The sequence of actions to be performed for an upgrade is as follows:
Undeploy the Agile PLM application.
Upgrade the database to 9.3.3:
a. Download the Agile PLM database installer and Automated Upgrade Tool (AUT). For instructions on downloading the database installer, see the Agile PLM Database Installation Guide. For instructions on downloading the AUT, see "Downloading the Automated Upgrade Tool".
b. Configure and run AUT. For instructions on configuring AUT for each type of upgrade, see "Understanding the Property Files" and "Whether Source Equals Destination".
c. Generate maintenance scripts for the target release: Run the database installer, choosing the Generate Maintenance Scripts only option. See "Generating Database Maintenance Scripts Only".
d. Configure the database as described in "Configuring the Agile PLM Database".
Install the Agile PLM application software.
Deploy the Agile PLM application.
The Automated Upgrade Tool can be downloaded from Oracle Support Services.
To download the software:
Log in to My Oracle Support (https://support.oracle.com).
Under Patches & Updates, click Product or Family (Advanced Search).
1. Select the Include all products in a family check box.
2. Enter the following search parameters:
Product: Oracle Agile Applications
Release: Agile PLM Tools 9
Platform: Select the appropriate platform, for example, Microsoft Windows (32-bit).
3. Click Search.
4. Links to Averify and AUT are displayed in the search results.
5. Select the Patch ID and click Download.
From the Patchset zip file, extract the contents of the AUT.zip file to your destination database server. After the AUT is extracted, all of the files are located in an AUT directory on the local drive. In this document, this directory is named the AUT_HOME.
Averify is a scripting tool that performs an integrity check against the PLM database and reports on specific errors. Averify includes a check for missing indexes and inconsistent data stored in the various database tables. Averify only reports errors, and does not attempt to fix them or modify your database. You should run Averify periodically as part of your regular database maintenance procedures.
Download Averify from My Oracle Support (https://support.oracle.com). You should download the software to your destination database server.
When you download an updated version of AUT, the latest Averify scripts are also included.
Extract the averify.zip file to a local drive. The extracted files are located in the following directories on the local drive:
\bin
\config
\lib
\logs
\META-INF
\scripts
Unless you plan to upgrade in-place, a new database instance must be created before you can upgrade your existing database. This database instance will be used as the destination database during the upgrade process.
To create the Agile PLM 9.3.3 database instance, follow the instructions in the Agile PLM Database Installation Guide.
After the 9.3.3 database instance is created, run the useragile.sql script, located in the <ORACLE_HOME>/admin/<SID>/create/<agile schema user> directory, to create an empty user in the database.
|
Note: Change the token values inside the @ symbols in the .sql file before running the script. Replace username agile with the desired username to create the user. |
To upgrade an existing Agile schema, you do not need to recreate the database instance. You only need to generate the database maintenance scripts for the target release.
The procedure for generating maintenance scripts is detailed below.
On Windows:
Run the database installer and enter appropriate information for Destination Location, Database Size and Oracle home, as described in the Agile PLM Database Installation Guide.
When prompted for the Oracle SID, change the default SID agile9 to the existing SID.
Select the Generate database maintenance scripts only option. Click Next.
Follow on-screen directions to generate scripts.
A confirmation message appears when you have successfully generated the maintenance scripts.
On UNIX:
Run the agile9database.sh script as described in the Agile PLM Database Installation Guide.
$ chmod u+x agile9database.sh
$ ./agile9database.sh [Enter]
When prompted to choose the installation mode, enter S to generate maintenance scripts only. This action generates the database scripts but does not execute them.
Follow on-screen directions to generate scripts.
A confirmation message appears when you have successfully generated the maintenance scripts.
You should validate the source and destination databases to ensure a successful upgrade by performing the following checks:
Run the latest averify script on the source database and fix any errors.
For each database upgrade, you should know the following:
Source and destination database user and password
Destination sys user and password
TNS configuration for source and destination database on the respective database systems
Paths to the Oracle homes
Map the source and destination Oracle homes, if necessary.
Validate the TNS entries of the source and destination databases.
On a command line, change ORACLE_HOME to point to the Oracle home of the source database, then try to connect to it using the TNS name. Repeat this procedure for the destination database.
Make sure the destination database user exists and there are no objects in the schema.
|
Note: This does not apply if your source database is also your destination database. |
Make sure the source and destination database users have the same roles and privileges.
Make sure the Agile tablespaces in the destination and source databases match. Also, the destination database should have unlimited tablespace.
Verify that the available tablespace in the destination database is sufficient to complete the database upgrade.
