Go to primary content
Oracle Agile Engineering Data Management Upgrade Tool
Release e6.2.0.0
E52564-02
  Go To Table Of Contents
Contents

Previous
Previous
 
 

5 Appendix

5.1 CMD Scripts

Here is a short description of all shell scripts included in the upgrade download package.

Shell script Description Called SQL scripts
batch_upgrade.cmd Performs a complete upgrade in the batch mode
convert_it.cmd Converts XML data file for a single table to HTML files. This script is called from xml2html.cmd. --
exp_dmp.cmd This script helps you to export Oracle database to a dump file. --
imp_dmp.cmd This script helps you to create database users and import Oracle dump files. --
preaction_template.cmd Note: This file is for upgrade internal use only!

It is used as a template for creating the file preaction.cmd, which is needed if all upgrade steps are executed in batch mode.

--
start_upg.cmd Start upgrade user interface. --
upg01_pre_cleanlog.cmd Cleanup all log files within current upgrade project. --
upg03_preaction_sql.cmd Run several SQL scripts depending on source, target and customer product versions. Called SQL scripts are saved in the file 03_preaction_sql.log source: CRE_REP_EDB.SQL > 03_01_CRE_REP_EDB.LOG

source: TRUNC_LVTABS.SQL > 03_TRUNC_LVTABS.LOG

source: GRANT_SELECT_T_CONSTRAINT.SQL target: CRE_REP_EDB.SQL > 03_15_CRE_REP_EDB.LOG

CLEANUP_C_ID_NULL.SQL > 03_03_CLEANUP_C_ID_NULL.LOG

ANA_LV.SQL > 03_04_ANA_LV.LOG

<=e6 GA: DTV407-430.SQL > 03_13_DTV407-430.LOG

<= e6.0.1: DTV430-431.SQL > 03_14_DTV430-431.LOG

<= e6.0: DTV431-432.SQL >

03_15_DTV431-432.LOG

<= e6.0: DTV432-433.SQL >

03_16_DTV432-433.LOG

<= e6.1.0: DTV433-434.SQL > 03_16_DTV433-434.LOG

<= e6.1.2.2: DTV434-435.SQL > 03_21_DTV434-435.LOG

<= e6.1.2.2: DTV6122-6130.SQL > 03_24_DTV6122-6130.LOG

CUSTOMER_DATABASE_TASKS.SQL > 03_17_CUSTOMER_DATABASE_TASKS.LOG

upg04_dtv_get.cmd Get XML files for the step "DTV-Upgrade" in shell mode. --
upg05_dtv_update.cmd Proceed XML files for the step "DTV-Upgrade" in shell mode. --
upg06_sync_get.cmd Run the step "Analyze repository" in shell mode.
upg07_sync_update.cmd Run the step "Synchronize repository" in shell mode. Called SQL scripts are saved in the file 07_sync_update.log <= PLM5.x: before_sync.sql > 07_01_before_sync.log
upg08_postaction.cmd Run some SQL scripts, which are necessary after performing "Synchronize repository" upgrade step. Called SQL scripts are saved in the file 08_postaction.log cre_rep_edb.sql > 08_01_cre_rep_edb.log cleanup.sql > 08_02_cleanup.log

db_defaults.sql > 08_03_db_defaults.log artmeh_1.sql > 08_04_artmeh_1.sql update_defartmehr.sql > 08_05_update_defartmehr.log artmeh_2.sql > 08_06_artmeh_2.sql

special602.sql > 08_07_special602.log

get_compile_all.sql > compile_all.sql

compile_all.sql > 08_08_compile_all.log

invalid_objects.sql > 08_09_invalid_objects.log

upg09_common_get.cmd Generate XML files for several upgrade steps, one for each common EDM module. Called SQL scripts are saved in the file 09_common_get.log del_and_save_lvmodel.sql > 09_01_del_and_save_lvmodel.log
upg10_common_update.cmd Proceed common EDM modules XML files. Called SQL scripts are saved in the file 10_common_update.log <=PLM5.x: edb_explorer.sql > 10_02_edb_explorer.log
upg11_cla.cmd Upgrade EDM Classification. --
upg13_prod1_takeover.cmd Start a user interface to proceed with "Takeover production data". Scripts upg14_prod2_rep_update and upg15_prod3_postaction have to be executed after that. --
upg14_prod2_rep_update.cmd Synchronize repository (this script includes all necessary pre-action and post-action calls). SQL Files of upg07_sync_update.cmd and upg08_postaction.cmd are called again

get_numvalue.sql > 14_01_get_numvalue.log

set_numvalue.sql > 14_02_set_numvalue.log

getseq.sql > 14_03_getsequences.log

dropseq.sql > 14.04_dropseq.log

creseq.sql > 14_05_creseq.log

cre_rep_edb.sql > 14_06_cre_rep_edb.log

upg15_convert_nvarchar2.cmd Convert all NVARCHAR2 fields of the database into VARCHAR2 fields. convert_nvarchar2.sql > 15_01_convert_nvarchar2_sql.log

convertall.sql > 15_02_convert_nvarchar2_sql.log

upg_env.cmd Common upgrade settings, like Java, JRE, Path, etc. --
xml2drop.cmd Generates ora/ ref_data_tab.par and ora/ref_data_tab_drop.sql files for manually import/export of production tables. You have to configure which tables are relevant for the takeover step before. --
xml2html.cmd Converts generated XML files to HTML format for a module. Example: "xml2html.cmd dtv" Or "xml2html.cmd all" Possible module names ('all' for all modules): dtv edb brw dode lgv wfl chg gdm rmt gtm ase cmg
check_edb_crm_null.sql Reports invalid values in change management columns EXECUTE WA_BUG7107296;

5.2 Configuration Files in /conf/

  • ApplicationParameter.xml - Global application configuration file

  • aseDD.xml - Configuration file for upgrade module ASE (Advanced Structure Editor)

  • brwDD.xml - Configuration file for upgrade module BRW (Explorer)

  • chgDD.xml - Configuration file for upgrade module CHG (Change Management)

  • wflDD.xml - Configuration file for upgrade module WFL (Workflow)

  • dtvDD.xml - Configuration file for upgrade module DTV (DataView Repository)

  • edbDD.xml - Configuration file for upgrade module EDB (Agile PLM configuration)

  • gdmDD.xml - Configuration file for upgrade module GDM (Office integration)

  • gtmDD.xml - Configuration file for upgrade module GTM (Classification)

  • lgvDD.xml - Configuration file for upgrade module LGV (LogiView)

  • rmtDD.xml - Configuration file for upgrade module RMT (Requirement Management)

  • cmgDD.xml - Configuration file for upgrade module CMG (configuration Management)

  • special.xml - Configuration file for the step "Synchronize Repository"

  • specialreplace.xml - A sample configuration file for special replace cases

  • ref_tables.xml - Configuration file for the upgrade step "Takeover production data"

  • wfl_ctl.xml - Configuration file for Workflow mapping

  • insert.xsl, delete.xsl, update.xsl, upgrade.xsl - XSL-stylesheet for converting XML control files to HTML, used by xml2html.cmd script

  • ref_data_tab_drop.xsl - XSL-stylesheet for generating SQL script, which drops production data tables in the customer dump. This stylesheet is used by xml2drop.cmd

  • ref_data_tab_par.xsl - XSL-stylesheet for generating table list clause for oracle EXP command, which can be used alternatively to transfer production data tables from production database. This stylesheet is used by xml2drop.cmd

  • cla_stl.xsl - XSL-stylesheet for configuration file for classification upgrade (Axalant 2000 to PLM5.x), which generates a HTML output of performed mapping operations

  • dtv_dd.dtd - Document type definition file for module control files

5.3 Contents of the Folder "upgrade/conf/template"

  • ApplicationParameterORACLE.xml - Upgrade Tool settings file with standard values for an ORACLE database. Copy this file to upgrade/conf to reset the application settings.

  • ref_tables.xml - This configuration file is used during the takeover phase for read only reasons. Based on settings in this file, a ref_table.xml file is created in the CONF directory during the "Create ref. File" step.

  • special_move.xml - Examples for the special case with table field moving.

  • special_rename.xml - Examples for the special case with table field renaming.

  • Special.xml - Default template.

  • specialreplace.xml - Examples for special replace cases.

5.4 SQL Scripts

Here is a short description of SQL scripts delivered with the Agile upgrade tool. The execution of each script creates a log file in the log/ directory which are named like the script itself with a prefix like 08.

SQL Script Description
ana_lv.sql Analyze LogiView content in the customer dump. Please control the log file of this script as described in the manual.
before_sync.sql This script has to be executed before running the step "Synchronize Repository". It is done by default with the standard upgrade configuration. It prepares the table T_STA_LUT and drops triggers, because otherwise it is impossible to insert rows in the involved tables.
char_check.sql Creates character scan report.
check_edb_crm_null.sql The script checks the consistency of configuration settings and production data and reports any disparities.
cleanup.sql This script cleans up some dump content and is executed automatically after the step "Synchronize Repository".
cleanup_c_id_null.sql This script cleans up some inconsistencies in the customer dump (like rows with negative C_ID values). It must be executed before DTV-upgrade.
compare_lgv.sql Performs LogiView comparison between two different schemas
convert_nvarhar2.sql The script searches for fields of data type nvarchar2 and creates an sql script named convertall.sql which contains necessary commands to convert all NVARCHAR2 fields of the database to VARCHAR2.
convert_to_utf8.sql Convert (VAR)CHAR2 columns from BYTE to CHAR semantic after a dump import
customer_database_tasks.sql This script executes some cleanup statements to get rid of common dump inconsistencies.
cre_plm_tbs.sql Creates missing Oracle table spaces.
cre_plm_usr.sql Create a database user. This script needs 2 parameters: username and password.
cre_rep_edb.sql Creates all schema objects (tables, views, indexes, packages, triggers, sequences, etc.) and insert number server rows, most of them already exist, a lot of errors will be logged after executing this script.
creseq.sql The script will be executed in the production database and generates two files named dropseq.sql and creseq.sql. These files update settings of database sequences in the customer database.
db_defaults.sql Overwrites default constraints on the database level, since they are different from DataView default definitions. It is executed automatically after the step "Synchronize_repository".
del_and_save_lvmodel.sql Delete standard LogiView content and save customized models with a prefix "SAVE-".
drop_obsolete_objects.sql Contains delete statements for all de-supported database objects. Such objects are not deleted by the Upgrade Tool.
dtv406-407.sql Pre-action script has to be executed before DTV-upgrade for customer dump version <= Agile e6.0 LA.
dtv407-430.sql Pre-action script has to be executed before DTV-upgrade for customer dump version <= Agile e6.0 GA.
dtv430-431.sql Pre-action script has to be executed before DTV-upgrade for customer dump version <= Agile e6.0.1.
dtv431-432.sql Pre-action script has to be executed before DTV-upgrade for customer dump version <= Agile e6.1.
dtv432-433.sql Pre-action script has to be executed before DTV-upgrade for customer dump version <= Agile e6.0.3.
dtv433-434.sql Pre-action script has to be executed before DTV-upgrade for customer dump version <= Agile e6.1.1
dtv434-435.sql Pre-action script has to be executed before DTV-upgrade for customer dump version <= Agile e6.1.2.2
dtv6122-6130.sql Pre-action script has to be executed before DTV-upgrade for customer dump version <= Agile e6.1.2.2
dtv6130-6200.sql Pre- action script has to be executed before DTV-upgrade for customer dump version <=Agile e6.1.3.0
edb_explorer.sql Converts DTV explorer to Agile e6 EDB-explorer. This step is executed once after common modules upgrade.
fill_edb_in_contexts.sql Migrates PLM5.x IN_CONTEXT values to EDB_IN_CONTEXTS introduced with Agile e6.0
getoradrop.sql Get script "dropall.sql" which cleans up a complete database schema.
get_compile_all.sql Generates a script to recompile all db objects.
get_numvalue.sql This script is executed in the production database and generates a file named " set_numvalue.sql " after takeover step. This file updates number server values in the customer database.
get_rebuildidx.sql This script generates a file named " rebuildidx.sql " to rebuild all indexes in a right table space of a schema. It has 5 parameters for table spaces: EDB EDB_IDX EDB_LOB EDB_TMP EDB_TMPIDX
grant_dtv.sql grant SELECT rights to DTV tables within the target reference dump
Invalid_objects.sql Lists all objects still invalid in the dump.
levind_in_stalut.sql This script is called automatically after "Synchronize Repository" and converts records in the table T_STA_LUT. It is needed only for upgrades form <= Eigner PLM to >= Agile e6.
lgv_bug_8201546.sql Corrects dump errors or inconsistencies for C_NR conflicts in standard Agile e6 dump.
special602.sql Special data modifications for upgrade to 6.0.2
special_61.sql Special data modifications for upgrade to 6.1.0
takeover_dtv.sql Takeover DataView internal repository from target reference dump
testconnection.sql Dummy SQL script for testing sqlplus connections
trunc_lvtabs.sql Truncate all LogiView tables. This script is executed on reference dumps only!
update_browser.sql This script adds missing French labels for browser.

Executed for dumps <=e6.1.2.2

update_customers_UIC.sql This script has to be executed on the customer dump before proceeding with the upgrade.
upd_t_selection.sql This script is a workaround for incompatible changes for table T_SELECTION in Eigner PLM5.0 This script is already executed on all reference dumps delivered with Agile Upgrade Tool. It will automatically executed IDs that are necessary in the step "preaction-scripts".
update_defartmehr.sql Fills DEFARTMEHR.BVB_ARTIKEL field during the CLEANUP_BVB phase of the step "Postaction".
upg_org_ref_default.sql A sample update script for existing STEP_NO_REF and STEP_ORG_REF values.

5.5 Header SQL Scripts

Header SQL Script Description
convert_nvarchar2.sql This script has to be executed on the customer dump after synchronize repository in the customization upgrade as well as in the takeover production data. The scripts convert all database table columns of the user with data type nvarchar2 to varchar2.
getseq.sql This script is executed in the production database and generates files named "dropseq .sql "and " creseq.sql" after takeover step. These files updates database sequence values in the customer database.

5.6 Directories

Directory Description
cmd Windows shell scripts of the Upgrade Tool.
conf Configuration XML files.
conf\template Some templates of XML configuration files. The Upgrade Tool does not use these files. The only exception is the file ref_tables.xml. It will be read by the tool to recreate /conf/ref_tables.xml.
data This directory contains several subdirectories, each for a module - like BRW, EDB, etc. For each module delete, insert, and update XML files are created. After performing these operations on the customer database, an error XML file is written. Additionally, HTML files generated for a module are saved here. A file customizing.log in this directory contains conflicts caused by customizing of the original dump.
data\dtv DataView upgrade files as described above are stored here. Please read carefully the file customizing.log because it contains userexit conflicts.
data\sync Log files of the synchronize repository upgrade step are stored in this directory.
data\cla Log files of the classification upgrade step are stored in this directory.
doc Upgrade Tool documentation.
dumps Database dumps can be stored here. Dumps, which are imported / exported by shell scripts imp_dmp.cmd and exp_dmp.cmd, have to be stored in this directory.
img Upgrade Tool images.
lib Upgrade tool Java executables.
log Log files of all SQL scripts and common application log files.
ora\sql Oracle SQL scripts.
scripts Unix / Linux shell scripts of the Upgrade Tool.
tmp Temporary files.
unsupported Upgrade Tool files, that are unsupported

5.7 Migration Rules

Standard rules are available for insert, update, and delete and these rules are verified during the comparison of the table contents. They can be overwritten by special definitions.

5.7.1 Standard Rules for Delete

Data records deleted in the standard are also deleted in the customer dump.

Customer-specific dump Source master Target master Action
+
+
- Delete

5.7.2 Standard Rules for Update

Data records existing in the source master dump that were deleted in the customer dump are not re-created. Existing data records are updated. The standard changes overwrite the customer changes. Special rules apply on field level to protect customer-specific changes.

Customer-specific dump Source master Target master Action
+
+
+
Update

5.7.3 Standard Rules for Insert

Data records not existing in source master dump or in the customer dump are added.

Customer-specific dump Source master Target master Action
- - +
Insert

5.7.4 Special Rules

Customer changes that will not be overwritten by standard changes are:

  • Field defaults and check strings.

  • Customizing hints for fields containing userexits.

  • Special handling for mask components.

  • Replacements of strings (-> specialreplace.xml).

5.8 Repeatable Tasks

The following table gives an overview of steps which may be repeated without re-importing the customer dump.

Step Repeatable
run pre-action-scripts YES
DTV-upgrade "Create Files" YES
DTV-upgrade "Perform Insert,Update,Delete" NO
run before-sync-scripts YES
Synchronize_Repository "Analyze" YES
Synchronize_Repository "Synchronize" YES
run after-sync-script NO
run before-common-scripts NO
EDB-upgrade (Configuration) "Create Files" YES
EDB-upgrade (Configuration) "Perform Insert,Update,Delete" NO
BRW-upgrade (Browser) "Create Files" YES
BRW-upgrade (Browser) "Perform Insert,Update,Delete" NO
LGV-upgrade (LogiView) "Create Files" YES
LGV-upgrade (LogiView) "Perform Insert,Update,Delete" NO
WFL-upgrade (Workflow) "Create Files" YES
WFL-upgrade (Workflow) "Perform Insert,Update,Delete" NO
CHG-upgrade (Change Management) "Create Files" YES
CHG-upgrade (Change Management) "Perform Insert,Update,Delete" NO
GTM-upgrade (Classification) "Create Files" YES
GTM-upgrade (Classification) "Perform Insert,Update,Delete" NO
GDM-upgrade (Office Suite) "Create Files" YES
GDM-upgrade (Office Suite) "Perform Insert,Update,Delete" NO
RMT-upgrade (Requirement Management Traceability) "Create Files" YES
RMT-upgrade (Requirement Management Traceability) "Perform Insert,Update,Delete" NO
ASE-upgrade (Advanced Structure Editor) "Create Files" YES
ASE-upgrade (Advanced Structure Editor) "Perform Insert,Update,Delete" NO
CMG-upgrade (Configuration Management) "Create Files" YES
CMG-upgrade (Configuration Management) "Perform Insert,Update,Delete" NO
run after-common-scripts YES
Classification attribute inheritance NO
special replace NO

5.9 Error Messages

5.9.1 File Name: <upg_root>\data\sync\sync_analysis.log

After the step: Synchronize Repository > Analyze

#
Error Action Description
1. DTV field T_ACT_CLA.C_LEN_VIS has the type I10 but its data is incomplete. Do NOT ignore the message. FIS-ID: 10288 > Loaderfile

In T_FIELD, entries for the 3 fields are not correct:

T_ACT_CLA.C_LEN_VIS

T_ACT_CLA.C_LEN_VIR

T_ACT_CLA.C_WID_VIS

2. DTV Field T_CHK_DSP.C_ID is found twice Ignore the message DTV system fields (also in the default dump) as an exception in the DTV repository.

Do not make any changes.

The following are the DTV system fields:

C_ID

C_VERSION

C_LOCK

C_UIC

C_GIC

C_CRE_DAT

C_UPD_DAT

C_ACC_OGW

3. DTV Field V_CHG_OPR_FRM.EDB_EWO_EDB_ID has type I10 but its table does not exist Ignore the message T_FIELD contains required fields without an entry in T_TABLE.

Do not make any changes.

4. DB field T_PTL_DAT.DESCR_GER has misbegotten sibling T_PTL_DAT.DESCR Ignore this message from the Release Agile e6.x onwards Error is in the default dump axalant2000sp3.

Here, the fields DESCR, DESCR_GER, DESCR_ENG and DESCR_FRA exist.

The table belongs to the module WEB-Portal, which is not part of the default anymore from the Release Agile e6.x onwards.

The associated tables are removed during the upgrade procedure

5. DB field V_CHG_OPR_ART.EDB_PARENT is of the type - (CHAR,0,null). Ignore the message View is defined in the database.

View - Fields do not need a TYPE because this is already defined in the master table.

FIS-ID:10289 - FAQ entry - no error.

6. DTV Field C_GRP_USR.C_ACCESS has no type. Ignore the message View in the DTV repository.

View - Fields do not need a TYPE because this is already defined in the master table.

7. DB Field SYS_NC00041$ from index EDB_CLA_IND2 does not exist in table T_CLA_DAT. Ignore the message EDB_CAL_IND2 is a function based index. This has been added to the default dump for the performance reasons from the Release Agile e6.0 onwards.

FIS-ID:10290 - FAQ entry - no error.

8. DB Field BVB_ARTIKEL.PART_NAME_FRA has been added but this field seems to have already been multi-language before. It is empty now. Ignore the message This message is displayed if it is already defined as multi-lingual in the DTV repository, but the fields are not available in the database.
9. Missing standard value for NOT NULL field T_MASTER_DAT.UNIT. Append a field default entry to the special cases file. Do NOT ignore the message This message is displayed if Tabellen.Feld (Table.Field) NOT NULL is created or modified, but no default value is defined in the file <upg_root>/conf/special.xml.

Create missing field default in file spezial.xml.

Example:

<FieldDefault>

<FieldName>T_MASTER_DAT.UNIT</FieldName>

<FieldType>S</FieldType>

<FieldSize>20.0</FieldSize>

<DefaultValue>

<Value>nix-unit</Value>

</DefaultValue>

</FieldDefault>

10. CREATE UNIQUE INDEX EDB_GDM_PRP1 ON T_GDM_PRP (PROPERTY_NAME, PROPERTY_TYPE ) TABLESPACE EDB_IDX ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found. Do NOT ignore the message Error in the PLM5.x dump with Office Suite hotfix4.

The Property_Name "PARAGRAPHCOUNT" exist twice. Delete one of the data records.

Check for possible usage in:

T_GDM_TPL_PRP T_GDM_PRP.C_ID = T_GDM_TPL_PRP.C_ID_2

FIS-ID: 10622 - Dataset can only be deleted via SQL-Plus.

11. It is not supported to change the type of the field T_DTO_FNC.C_DESCRIP_ENG from (S,255,0) to (S,20,0) Ignore the message ONLY for the table T_DTO_FNC FIS-ID:10291 - solved with upg3.0.39 - new plm601upgref dump.

See the error descriptions 12 or 13 for further details.

12. Had no permission to change the type of the field T_CHK_PAR.REC_ID from (I,10,0) to (S,40,0).

OR

Permission OK. Ready to change the type of the field T_CHK_PAR.REC_ID from (I,10,0) to (S,40,0).

Do NOT ignore the message.

Use the upgrade tool: upgtool 3.0.24

At the end of the upgrade the data type has to be correct.

FIS-ID:10152 - solved with upg3.0.34

13. Missing permission to change the type of the field BVB_ARTMEHUFK.NACHMEHR from (S,4,0) to (I,10,0). Do NOT ignore the message.

Use the upgrade tool: upgtool 3.0.38

At the end of the upgrade, the data type has to be correct.

FIS-ID:10276, 10262 - solved with upg3.0.38.

In the course of these FIS-IDs, the file special.xml has been modified.

Change the datatype BVB_Tables to FALSE.

14. Did not delete DB index A_T_ORD_HIS. Ignore the message