Database Upgrade Guide Agile 9.2.2.1 TP1996-9.2.2.
Agile 9.2.2.1 COPYRIGHT AND TRADEMARKS Copyright © 1995, 2007, Oracle. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws.
CONTENTS Preparing for the Upgrade ................................................................................................vi Preparing the System....................................................................................................................................................... vi Downloading the Software .............................................................................................................................................. vii Creating the Agile PLM 9.2.2.
Agile 9.2.2.1 AUT Maintenance ............................................................................................................ 29 Updating the AUT............................................................................................................................................................29 Running Averify...............................................................................................................................................................
Preface The Agile documentation set includes Adobe® Acrobat™ PDF files. The Oracle Technology Network (OTN) Web site (http://www.oracle.com/technology/documentation/index.html) contains 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.
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.
If you are upgrading from an 8.5 product and your Oracle 8i home is not local to the machine where your database will be installed, you must map 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 where you are installing the Agile database before starting the upgrade.
Validating the Databases 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.
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.........................................................................
Agile 9.2.2.1 Source Details P a r am et er Valu e defin it ion src.jdbc.url The JDBC connection string to the source database. The format is jdbc:oracle:thin@:: where SOURCE_DB_HOST_NAME is the hostname of the source database, PORT is the listener port of the source database (1521 is the default), and SID is the database instance. src.jdbc.driver The database driver of the source database. The default is oracle.jdbc.driver.OracleDriver. src.db.
Chapter 1 Destination Details P a r am et er Valu e Definit ion dest.jdbc.url The JDBC connection string to the destination database. The format is jdbc:oracle:thin@:: where DESTINATION_DB_HOST_NAME is the hostname of the destination database, PORT is the listener port of the destination database (1521 is the default), and SID is the database instance. dest.jdbc.driver The database driver of the destination database. The default is oracle.jdbc.driver.OracleDriver.
Agile 9.2.2.1 Averify Details P a r am et er Valu e Definit ion averify.error.count Specifies the number of averify errors to occurs before the AUT stops the upgrade. Specify -1 to ignore the errors and continue with the upgrade. Import Warnings P a r am et er Valu e Definit ion ignore.imp.warnings Decide if the AUT ignores the import warnings or not while importing the database. If set to true, the warnings are ignored. AUT will stop if there is a critical error.
Chapter 1 Language Details P a r am et er Valu e Definit ion i18n.lang Specifies the language of the operating system where the database is located. The values are English, Japanese, Chinese, or French. 8.5 Only Details P a r am et er Valu e Definit ion isPC Each of the parameters must have a value if the source database is either 8.5 or 8.5 SPx only. Set the parameter to true for the components that are installed on the source database and to false for the components that are not installed.
Agile 9.2.2.1 The psupgrade.properties File The psupgrade.properties file, located in the $AUT_HOME\config directory, contains user-supplied information on the existing Product Cost Management database. During an upgrade of a Product Cost Management database, the data is merged into the Agile PLM database. The parameters in the file are used by the database scripts during the upgrade process to determine how the data is migrated. This file should be completed in addition to the aut.
Chapter 1 Defining the psupgrade.properties Parameters P a r am et er Valu e Definit ion pcm.jdbc.url The JDBC connection string to the Product Cost Management database. The format is jdbc:oracle:thin@:: where SOURCE_DB_HOST_NAME is the hostname of the Product Cost Management database, PORT is the listener port of the database (1521 is the default), and SID is the database instance. pcm.jdbc.driver The database driver of the Product Cost Management database.
Agile 9.2.2.1 P a r am et er Valu e Definit ion migrate.pcm.items.not.found.in.pc If set to true, all Product Cost Management items not found in the Agile 8.5 database are migrated. convert.mfrName.to.upperCase If set to true, all manufacturer names are converted to uppercase. migrate.pcm.mpns.not.found.in.pc If set to true, all Product Cost Management manufacturer parts not found in the Agile 8.5 database are migrated. update.matched.mfr.data If set to true, all Agile 8.
Chapter 1 The peupgrade.properties File The peupgrade.properties file, located in the $AUT_HOME\config directory, contains user-supplied information on the existing Program Execution database. During an upgrade of a Program Execution database, the data is merged into the Agile PLM database. The parameters in the file are used by the database scripts during the upgrade process to determine how the data is migrated. This file should be completed in addition to the aut.
Agile 9.2.2.1 Defining the peupgrade.properties Parameters P a r am et er Valu e Definit ion pe.jdbc.url The JDBC connection string to the Program Execution database. The format is jdbc:oracle:thin@:: where SOURCE_DB_HOST_NAME is the hostname of the Program Execution database, PORT is the listener port of the database (1521 is the default), and SID is the database instance. pe.jdbc.driver The database driver of the Program Execution database. The default is oracle.jdbc.
Chapter 1 Page - 19
Chapter 2 Upgrading the Agile Database to Agile PLM 9.2.2.1 This chapter includes the following: Running the Automated Upgrade Tool ................................................................................................................ 21 Checking the Status of the Upgrade.................................................................................................................... 21 Troubleshooting the Upgrade .................................................................................
Agile 9.2.2.1 y Verify that the service name exists in one of the tnsnames.ora files. Add the service name, if necessary. y Make sure there are no syntax errors in the tnsnames.ora file, especially unmatched parentheses or stray characters. Why did I receive an Invalid User Name or Password error in the AUT.log file? You may receive this error if the database connection was not successful.
Chapter 2 What should I do if AUT suddenly exits? Check the AUT.log file. If no information is available, then the AUT could not start because of invalid settings. Check the pre-requisites and the contents of the aut.properties file before retrying. If I have database connection problems, what Oracle errors will I get? Database connection errors can occur if the SQL connection to the source or destination database is lost. Make sure that the database connections are available before running the AUT.
Agile 9.2.2.1 I received an ORA-01555 error. What should I do? ORA-01555: "snapshot too old (rollback segment too small" when using Automatic Undo Management (AUM). Solution: The UNDO tablespace is too small. Increase the size of the UNDO tablespace. Note that the UNDO tablespace should be large enough to store the undo data generated by active transactions as well as those preserved to honor the undo retention setting. Increase the value of the Undo_retention parameter.
Chapter 3 Configuring the Agile PLM 9.2.2 Database This chapter includes the following: Reorganizing the Database ................................................................................................................................. 25 Running Full Text Search Scripts ........................................................................................................................ 26 Configuring the Agile SDK ....................................................................
Agile 9.2.2.1 6. Run the Agile9exp script again. The Agile9exp.dmp file created can be used as a backup of the system after the Agile PLM 9.2.2.1 database reorganization. 7. Rename the agile9exp.dmp file to agile9exp_reorg9221.dmp for backup. Also rename the agile9exp.log file to agile9exp_reorg9221.log. 8. Change to the Agile9Tmp directory: (Windows) cd Agile9Tmp (UNIX) $ORACLE_BASE/admin/$ORACLE_SID/create 9. Start SQL*Plus from a command line and log in as agile/tartan or agile/tartan@agile9.
Chapter 3 Configuring PG&C If you have the PG&C component installed, additional configuration may be needed for substance migration. Substance migration is necessary if you meet ALL of the following requirements: à à à Upgraded your database from Agile PLM 9.2 to Agile PLM 9.2.2.1. Imported the JGPSSI substances and substance groups. In Agile PLM 9.2.2.1, you want to use IPC declarations with IPC substances and substance groups.
Agile 9.2.2.1 The Agile Administrator is still allowed to delete a role assigned to a user in the object’s ACL. If a role is deleted, an error message stating “Node does not exist in cache” displays when the object is accessed. Also, in earlier releases of Agile PLM, the Dashboard or other PPM-related home pages were allowed to be selected as the start page. In Agile PLM 9.2.2.1, a license check is added for default home pages.
Appendix A AUT Maintenance Before you upgrade your database, you should always make sure you are using the latest version of the AUT. Changes to the scripts, like averify, may occur after the initial version has been released. So, to ensure your database is correctly upgraded, always check the Agile Support website for updates. Updating the AUT If updates are needed to the AUT, you can always find the latest version on the Agile Support Web Site (http://www.agile.com/support). Download the AUT.
