5 Appendix

5.1 Additional Upgrade Information

The following information describes the background process running while upgrading the database dump.

The database upgrade is based on a standard Agile upgrade tool and has the following directories:

• JAR archive

• SQL scripts

• Pre-configured XML control files

Note: All changes will be saved directly in the dump.

Note: For the patch upgrade, no reference dumps are needed. Therefore, pre-configured XML control files to delete, insert, and update actions are delivered with the upgrade package. During the execution of these files the conflict recognition helps to locate possible weak points.

Since the patch upgrade runs in silent mode, the whole procedure is combined in a single shell script. After calling this script, SQL files are executed on the specified dump, and data modifications will be made through a JDBC driver.

The following steps are executed during the database dump patch upgrade:

1. Parameters are passed to the application's ep_root path, environment name, host name, port number, and SID of the Oracle database.

2. Repository update with previously generated XML control (delivered with the package) is executed.

   During this update, conflicts are logged in an errors.log file.

3. The step "Synchronize repository" is executed.

   This ensures the customer database dump has the new table and index structure.

4. The SQL script del_and_save_lvmodel_diff.sql is executed.

   This deletes/saves logical models, which have to be re-inserted because they were modified in Agile e6.2.1.0.

5. All remaining configuration tables will be updated - similar to step 4.

6. Views, triggers, stored procedures, etc. must be recreated.

   This is possible with a cre_rep_edb_diff.sql script, which should be created for the Agile e6.1.3.0 dump.

   This script contains only objects that were changed since Agile e6.1.2.0. Additionally, a script containing all database objects has also DDL statements available (cre_rep_edb.sql).

7. Finally, all objects are recompiled, and a list of all objects, still invalid in the schema, is stored in an invalid_objects.log file.

5.2 LogiView Upgrade

Some standard LogiView procedures are changed in Agile e6.2.1.0. The following list shows the affected logic models:

• GdmOffice /VsdGet

• GdmTools /ChooseDialog

• GdmWorklist /StartCadimGdm

• EP_APP /AppViewAffObj

• GdmOffice /XlsSave

• EP_APP /AppRedline

• GdmBatch /StopSpooler

• GdmOffice /PptSave

• GdmOffice /XlsGet

• GdmOffice /DocGet

• GdmOffice /Print

• EP_APP /LoaDoc

• EP_APP /AppView

• GdmOffice /DocmPrint

• EP_APP /LoaDocAffObj

• EP_APP /LoaDocChgOpr

• EP_APP /AppChgOpr

• GdmProperty /Write

• GdmOffice /DocClose

• GdmOffice /DocSave

• GdmOffice /PptClose

• GdmOffice /PptGet

• GdmOffice /VsdSave

• PrpFavorite /GetEntInfo

• GdmMenu /Put

• PrpExplorer /AddExpObj

• GdmOffice /PptOpenFile

• GdmTools/ChooseDialog

All existing LogiView logic models in the current database dump that contain the above-mentioned procedures will be deleted if they are identical. Otherwise, they will be renamed automatically.

The new logic models will be re-inserted. After the patch upgrade, the renamed LogiView procedures have to be compared with the newly inserted procedures. If the previous changes are still required, they have to be added manually.

5.3 Dump Upgrade Log Files

Log files are created and stored in a separate environment subdirectory. After the database dump upgrade is finished, these files have to be reviewed. Especially the errors.log file, to make sure that no conflicts occurred. If conflicts have occurred, manual dump adaptations have to be made.

• Errors.log:
  Contains all errors that occurred during the dump upgrade.

The errors.log file points to the following log files:

• Errordetail.log
  Contains technical information.

• Testconnection_customer.log:
  Check this log file for successful connection via SQL*Plus.

Check these log files for errors.

• dtv6200-6210.log

• /log/dtv6200-6210.log

• Cre_rep_edb_diff*.log:

Check that this script was executed successfully. Following errors can be ignored:

• ORA-00001: unique constraint violated

• ORA-00904: invalid identifier

• ORA-00942: table or view does not exist

• ORA-00955: name is already used by an existing object

• ORA-01408: such column list already indexed

• ORA-01418: specified index does not exist

• ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found

• Ÿ ORA-04080: trigger does not exist

• del_and_save_lvmodel_diff.log:

Check which logic models were dropped / saved. Changes that were made during the save procedure must be re-implemented after the dump upgrade.

• db_defaults.log:
  Check this log file for errors.

• Invalid_objects.log:
  Check this file for invalid objects within the database dump.