Step 3. Upgrading the database - HxGN EAM - Version 11.7.1 - Installation & Upgrade - Hexagon

HxGN EAM Oracle Database Installation Guide

Language
English
Product
HxGN EAM
Search by Category
Installation & Upgrade
HxGN EAM Version
11.7.1

Ensure that all open invoices are approved or canceled before beginning the upgrade, and that all drivers on the Transaction driver control form (BXDCTL) have been stopped. Also disable Flex SQL and email triggers if present.

Before beginning the upgrade, back up the current database by exporting the existing Datastream 7i production schema.

The 7ISET.SQL script contains a setting to modify the number of rows processed at once by some of the large-scale updates; you may want to increase the number of rows when the rollback segments are sufficiently large enough to improve performance (the default setting of 5000 rows is a conservative estimate). The upgrade does not use the definition of the index tablespace that can be set here.

HxGN recommends performing a trial upgrade before upgrading a production database.

Execute the following scripts from the \ORACLE\<SCRIPTS>\ directory:

Script

Function

00CK75U.SQL

Checks the version, the Oracle RDBMS version, any users still logged in, the available space, and the presence of auxiliary tables remaining from previous upgrades (these must be dropped or renamed before proceeding)

10TB75U.SQL

Upgrades the table structure to Datastream 7i Version 7.5 using the storage parameters defined in the 7ISET.SQL file

7ICOMP.SQL

Run this script to recompile any invalid database objects; however, not all objects need to be valid at this point. Run the next scripts from this SQLPlus session or from a new session.

20IP75U.DMP

Imports "seed" data for the application.

Import the export file with this command

imp DBA/Pass@alias file=20IP75U.DMP fromuser=D7idmp touser=<user> log=20IP75U.LOG

Where DBA/Pass = an Oracle account with DBA privileges, alias = the database alias for the Oracle instance to be used, and <user> = the Datastream 7i Oracle schema.

Ensure that the log file shows a list of imported tables. Including ignore=y on the command line is not necessary and in the case of an upgrade is not recommended. If any remainders from a previous upgrade are still present, not including ignore=y alerts you to this problem by the Oracle error messages that appear. The dump file contains tables that are used only temporarily by the installation procedure, and they are dropped later. They occupy less than 10 MB in the database.

28LC75U.SQL

Updates the basic Datastream 7i setup to 7.5

30DT75U.SQL

Data manipulation for 7.5. This script reads the number of rows to be updated at once from the 7ISET.SQL file.

50CS75U.SQL

New 7.5 database constraints, indexes, and views. Indexes are created in the same tablespace as the primary key index on the r5events table (R5PRIK_EVT).

60PRC75.SQL

Replaces all database procedures, functions, packages, and views (in dependency order)

70TRG75.SQL

Replaces all database triggers

7ICOMP.SQL

Can be used to recompile any invalid database objects; however, these invalid database objects should not be present at the end of the 7.5 database installation.