Oracle TP1996-9.2.2.1A User Manual

Database Upgrade Guide
Agile 9.2.2.1
TP1996-9.2.2.1A
Make sure you check for updates to this manual at the Oracle Technology Network Website
Agile 9.2.2.1
COPYRIGHT AND TRADEMARKS
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclo sure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency­specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software-­Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail­safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle and Agile are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to pu rchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
Wednesday, September 12, 2007
ii Database Upgrade Guide
CONTENTS
Preparing for the Upgrade................................................................................................vi
Preparing the System.......................................................................................................................................................vi
Downloading the Software..............................................................................................................................................vii
Creating the Agile PLM 9.2.2.1 Database Instance........................................................................................................vii
Validating the Databases................................................................................................................................................viii
Understanding the Property Files..................................................................................... 9
The aut.properties File......................................................................................................................................................9
Defining the aut.properties Parameters............................................................................................................................9
Source Details............................................................................................................................................................10
Destination Details.....................................................................................................................................................11
Averify Details............................................................................................................................................................12
Import Warnings.........................................................................................................................................................12
File Manager Internal Locator Details........................................................................................................................12
Destination Version....................................................................................................................................................12
Language Details.......................................................................................................................................................13
8.5 Only Details..........................................................................................................................................................13
The psupgrade.properties File........................................................................................................................................14
Defining the psupgrade.properties Parameters..............................................................................................................15
The peupgrade.properties File........................................................................................................................................17
Defining the peupgrade.properties Parameters..............................................................................................................18
Upgrading the Agile Database to Agile PLM 9.2.2.1....................................................... 21
Running the Automated Upgrade Tool............................................................................................................................21
Checking the Status of the Upgrade...............................................................................................................................21
Troubleshooting the Upgrade..........................................................................................................................................21
Configuring the Agile PLM 9.2.2 Database ..................................................................... 25
Reorganizing the Database.............................................................................................................................................25
Running Full Text Search Scripts....................................................................................................................................26
Configuring the Agile SDK ..............................................................................................................................................26
Configuring PG&C...........................................................................................................................................................27
Configuring PPM.............................................................................................................................................................27
Running the PPM Post Upgrade Utility......................................................................................................................28
Upgrading from Agile PLM 9.2.1.1..................................................................................................................................28
iii
Agile 9.2.2.1
AUT Maintenance............................................................................................................ 29
Updating the AUT............................................................................................................................................................29
Running Averify...............................................................................................................................................................29
iv Database Upgrade Guide
Preface
The Agile documentation set includes Adobe® Acrobat™ PDF files. The Oracle Technology Network (OTN) Web site
the latest versions of the Oracle|Agile PLM PDF files. You can view or download these manuals from the Web site, or you can ask your Agile administrator if there is an Oracle|Agile Documentation folder available on your network from which you can access the Oracle|Agile documentation (PDF) files.
Note To read the PDF files, you must use the free Adobe Acrobat Reader™ version 7.0 or later.
This program can be downloaded from the Adobe Web site (http://www.adobe.com).
The Oracle Technology Network (OTN) Web site
http://www.oracle.com/technology/documentation/index.html) can be accessed through Help >
(
Manuals
Oracle|Agile PLM documentation can be found on the (
in both the Agile Web Client and the Agile Java Client. If applicable, earlier versions of
http://www.agile.com/support).
(http://www.oracle.com/technology/documentation/index.html) contains
Agile Customer Support Web site
If you need additional assistance or information, please contact 284-3900 for assistance.
Note Before calling Agile Support about a problem with an Oracle|Agile PLM manual, please
have ready the full part number, which is located on the title page.
support@agile.com or phone (408)
Readme
Any last-minute information about Oracle|Agile PLM can be found in the Readme file on the Oracle Technology Network (OTN) Web site
http://www.oracle.com/technology/documentation/index.html).
(
Agile Training Aids
Go to the Agile Training Web page (http://training.agile.com) for more information on Agile Training offerings.
v

Preparing for the Upgrade

You can upgrade your database to Agile PLM 9.2.2.1 if you have any of the following products currently installed:
à Product Collaboration 8.5 SP1-SP7 à Product Service and Improvement 8.5 SP1-SP7 à Program Execution 8.5 SP2 à Product Cost Management 8.5 SP1 à Agile 9.0 SP1-SP7
Agile 9.1 SP1-SP4 à
à Agile 9.2 à Agile 9.2.0.1 à Agile 9.2.0.2 à Agile 9.2.1 à Agile 9.2.1.1 à Agile 9.2.1.3 à Agile 9.2.1.4 à Agile 9.2.1.5 à Agile 9.2.2
The upgrade databa database.
tool takes inputs from a property file and completes the upgrade using your existing
se as the source database, while the newly created 9.2.2.1 database is the destination

Preparing the System

Note You should prepare a separate test environment to become familiar with the
upgrade procedure.
vi Database Upgrade Guide
If you are upgrading from an 8.5 product an your database will be installed, you must ma
d your Oracle 8i home is not local to the machine where
p a local drive on the destination machine to point to
the existing Oracle 8i home. Agile PLM supports Oracle 9i and 10g databases. You MUST install either Oracle 9i or 10g on the
system whe
re you are installing the Agile database before starting the upgrade. Use the instructions in the Agile PLM Database Installation Guide to install Oracle 9i Release 2 or Oracle 10g Release 2, if it is not already installed.
Also, if you are upgrading from an 8.5 product, you should create a new Oracle instance for the new Agile PLM product version and try to reuse the existing 8.5 Oracle instance. It is further recommended that the new Oracle instance is created on Oracle 10g to take advantage of the latest Oracle
Y
ou must also have JRE 1.4.2 installed and the JAVA_HOME environment variable should be set
with the same JRE on the system where the AUT is run.
features.

Downloading the Software

The automated upgrade tool software can be downloaded from the Agile Support Website (http://ww server.
Extract the AUT.zip file to a local drive. After the AUT is extracted, all of the files are located in an AUT dire
w.agile.com/support). The software should be downloaded to your destination database
ctory on the local drive. In this document, this directory is known as the AUT_HOME.
Note As a result of SQL script optimization, the size of the AUT.zip file is now reduced to
approximately 40 MB (earlier 100 MB), enabling faster download.
Creating the Agile PLM 9.2
.2.1 Database Instance
The Agile PLM 9.2.2.1 database instance must be created before you can upgrade your existing database. The 9.2.2.1 database will be used as the destination database during the upgrade process.
To create the Agile PLM 9.2.2.1 database instance, follow the instructions in Installer” section of the Agile PLM Database Installation Guide, based on
em
syst .
r th 9.2.2.1 database instance is created, run
Afte e the useragile.sql script, located in the $AUT_HOME database
Note Change the token value
\scripts\Oracle\utilities\script_tools directory, to create a new, empty user in the
.
s inside of the % symbols in the useragile.sql file
the “Starting the
your specific operating
before running the script.
vii

Validating the Databases

You
should validate the source and destination databases to ensure a successful upgrade by
perf
orming the following checks:
à Run the latest averify script on the source database and fix any errors. à se to be upgraded, you should know the following:
For each databa
our
y S ce and destination database user and password y Destination system user and password y TNS configuration for source and destination database on the respective database
systems
y Paths to the Oracle Homes
Map the so
urce 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. Repeat this procedure for the destination database.
à Make sure the destination database user is empty and does not contain any schema objects in
its schema. Note This does not apply if your source database will also be 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 tablespace size in the destination database is more than that of the source
database.
viii Database Upgrade Guide
Chapter 1

Understanding the Property Files

This chapter includes the following:
The aut.properties File......................................................................................................................................... 9
Defining the aut.properties Parameters...............................................................................................................9
The psupgrade.properties File............................................................................................................................. 14
Defining the psupgrade.properties Parameters................................................................................................... 15
The peupgrade.properties File.............................................................................................................................17
Defining the peupgrade.properties Parameters................................................................................................... 18
AUT uses property files to supply the input information to the database scripts. If you are not upgrading a Product Cost Management 8.5 or Program Execution 8.5 database, you should only complete the aut.properties file. If you are also upgrading a Product Cost Management 8.5 or Program Execution 8.5 database, you should complete either the psupgrade.properties file or the peupgrade.properties file, in addition to the aut.properties file.

The aut.properties File

AUT uses property files to supply the input information to the database scripts. If you are not upgrading a Product Cost Management 8.5 or Program Execution 8.5 database, you should only complete the aut.properties file. If you are also upgrading a Product Cost Management 8.5 or Program Execution 8.5 database, you should complete either the psupgrade.properties file or the peupgrade.properties file, in addition to the aut.properties file.
The aut.properties file, located in the $AUT_HOME\config directory, contains user-supplied information on the source and destination databases. The source database parameters contain information about the database to be upgraded. The destination database parameters contain information about the user and host details of the database where the source database is being upgraded. These parameters are used by the database scripts during the upgrade process.

Defining the aut.properties Parameters

The aut.properties is divided into the following sections:
à Source Details—the database you are upgrading à Destination Details—the Agile PLM 9.2.2.1 database à Averify Details—how averify errors are handled à Import Warnings—how import warnings are handled à 8.5 Only Details—which Agile 8.5 components you are upgrading
Each parameter is followed by an example displaying the correct format for each parameter value.You must complete the source and destination details in order for the AUT to proceed with the upgrade.
Database Upgrade Guide Page - 9
Loading...
+ 20 hidden pages