Oracle Agile Engineering Data Management Upgrade Tool Release e6.2.0.0 E52564-02 |
|
![]() Previous |
![]() Next |
This guide is intended to guide you through upgrading the Agile e-series products to Agile e6.2.0.0 with the Upgrade Tool.
The Upgrade Tool also allows a direct upgrade to Agile e6.2.0.0 from one of the following product versions.
Eigner PLM 5.x
Agile e6.0.x
Agile e6.1.x
Please contact Oracle support, if you intend to upgrade an older legacy version.
Do not use the software in any situation where significant damage to property or business could occur from a software error. In no event will Oracle or any other party who has been involved in the creation, production, or delivery of the software be liable for special, direct, indirect, incidental, punitive or consequential damages, including loss of profits, revenue, business, goodwill, data or computer programs, or inability to use the software, however, caused and regardless of the theory of liability even if Oracle or such other party has been advised of the possibility of such damages.
The Upgrade Tool addresses experienced project engineers and EDM administrators with customizing and database experience. Do not use the tool without the necessary knowledge. Read the complete manual in order to get all necessary information.
Do not attach to, or even change the production system. Always work on a copy of the production database dump. Avoid working on production computers to exclude any influence on the system. Never insert database connections of production database users in any configuration file or script except for exporting the dump or a source for copying tables (Production Database).
You should always be able to restart an older EDM version (Agile e6.0.x or e6.1.x, axalant, or Eigner PLM 5.x) as a fallback strategy.
The best performance is reached when installing the Upgrade Tool on your database server. It is also possible to work on any machine in the LAN.
Note: Dump upgrade can take a few hours runtime for every environment - please be patience. |
The Upgrade Tool is running on Windows and UNIX platforms officially supported for Agile e6.2.0.0.
Java 1.7 JRE, latest version, should be installed on the machine and configured in the environment. JAVA_HOME must be set - this can be done manually in upg_env.cmd resp. upg_env.sh script.
Database version supported in this upgrade tool is Oracle Database 12c (12.1.0.2) (English/German).
ORACLE_HOME variable must be set for Unix operating system. This can be done in upg_env.cmd (upg_env.sh) script.
SQL*PLUS must be installed on the machine.
On the local hard disk, on which the tool will be installed, at least 250 MB hard disk space must be available for the software, and generated log and data files.
At least 2 GB free RAM must be available to run a dump upgrade.
Sufficient disc space must be available to store copies of your production database and reference dumps on the machine / within the database.
All database users have to be assigned to the role AGILE_E_ROLE. The default table space must be EDB. Additionally, the users must have quota permissions on the following table spaces: EDB, EDB_IDX, EDB_LOB, EDB_TMP, EDB_TMPIDX.
AGILE_E_ROLE role and plm schema can be created by executing the SQL script:
sqlplus ora/sql/cre_plm_usr.sql <username> <password>
The Upgrade Tool is implemented in Java. The tool accesses the databases directly using a JDBC connection. The configuration of all upgrade steps is stored in a set of xml control files. In addition, SQL scripts are used for special steps.
Organization phases of the upgrade process:
Pre-actions on the original production environment
Customizing Upgrade
The customization and configuration stored in the database is updated to Agile e6.2.0.0. Depending on the system, this step can take a few hours. Main parameter is memory!
Make a copy of your production database dump. Do not attach your production system. Always work on a copy of your data.
Customizing / Test phase
The upgrade tool will create a dump on which you can run Agile e6.2.0.0. All functionalities must be tested to run correctly, including the whole customer-specific functionality. This dump is not error free. You have to check all functionalities and clear out the errors caused by setting up the upgrade tool.
Take over production data
All tables containing production data, like document and item master data, are copied from the production system to your new Agile e6.2.0.0 dump. They will be adapted so that you can work on this data within Agile e6.2.0.0.
Log files are created and stored in the log/ directory. After the dump upgrade is done, these files have to be reviewed, especially the errors.log file, to make sure there are no errors, otherwise, manual dump changes have to be made. Further "synchronize step" log files, placed in data/sync, have to be reviewed. Please control log files after each upgrade step and correct occurred errors manually before proceeding with upgrade.