titel: dadi–ma administration manual -...

Dokument Typ:

Titel:

Lieferbedingungs-Nr.:

Produktgruppe:

Schlagwörter:

Klassifikations Nr.:

Konfigurationsteil-Nr.:

Produktklassifizierungs-Nr.:

Freigabe Ordnungs-Nr.:

Bearbeitet:

Geprüft:

Abteilung: Firma:

Document Type:

Title:

DRL/DRD No.:

Product Group:

Headings:

Classification No.:

Configuration Item No.:

Classifying Product Code:

Release Order No.:

Prepared by:

Agreed by:

Department: Company:Genehmigt:Approved by:

Abteilung: Firma:Department: Company:

Genehmigt:Approved by:



Manual

DADI–MA Administration Manual

N/A

MDA – Team RIO 62 DASA RI

PR 1216401

N/A

N/A

1216401

8–QABA

N/A

I. Lenz RIO 62 DASA RI

P. Athmann RIO 63 DASA RI

Raumfahrt-Infrastruktur

DaimlerChrysler A erospaceDok.Nr./Doc. No.:AusgabeÜberarbtg. Datum

/Issue:/Rev.: /Date:

Datum/Date: 01.09.1997 31.03.2000

COL–RIBRE–MA–0036–00 4 A

FORM 0019.1/3 Daimler–Benz Aerospace, Bremen – All Rights Reserved – Copyright per DIN 34

ivRaumfahrt-Infrastruktur

COL–RIBRE–MA–0036–004 01.09.1997A 31.03.2000ii

DaimlerChrysler A erospaceDok.Nr./Doc. No.:AusgabeÜberarbtg.Seite

Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:

FORM 0672.0V.7 Daimler–Benz Aerospace AG,D–28199 Bremen – All Rights Reserved – Copyright per DIN 34

DOCUMENT CHANGE RECORD

Issue / Rev. Issue date Pages / Section affected

Remarks

1/– 18.07.94 all initial version

2/– 01.12.95 3.1.5 New section for Printer Installation

2/A 01.02.96 3.1.2.33.1.33.1.4,3.1.5,3.2.1,3.2.23.1.63.1.7

Update cshrc fileTar file options changedUpdate administration scriptsNew section User Defined Data Structure DefinitionNew section copying

3/– 04.04.97 2.13.1.2.23.1.3.2

ICD reference updatedOracle Version 7.3.2.1User and Group Creation

4/– 01.09.97 3 User definable tablespace names for aggregates andindexes

4/A 31.03.2000 3.1.5 You must not use the ’–’ sign for printer names.


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.2000iii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


1 INTRODUCTION 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 Identification and Scope 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Purpose 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 APPLICABLE AND REFERENCE DOCUMENTS 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 Applicable Documents 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2 Reference Documents 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 DADI–MA INSTALLATION AND DEINSTALLATION 3. . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 DADI–MA Installation 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1 Installation conventions and prerequisites 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.1.1 Procedure conventions 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1.2 System Administrator 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.2 Installation Environment 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2.1 User and Group Creation 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2.2 Creation of ORACLE user DADIMA and Tablespace TS_DADI 7. . . . . .

3.1.3 Setup DADI–MA Oracle Objects 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.4 Upgrade DADI–MA Data from previous DADI–MA Version 11. . . . . . . . . . . . . . . 3.1.5 Printer Installation 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 DADI–MA Deinstallation 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 Deinstall DADI–MA User 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2 Deinstall DADI–MA Files 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 MDB PRE–INSTALLATION ACTIVITIES 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.1 Copying the DADI–MA Export Files (MDB installation files) 15. . . . . . . . . . . . . . 3.3.2 User defined Data Structure Upgrade (Adapt MDB upgrade file: ’parfile.lst2’) 15.


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.2000iv


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


This page is intentionally left blank.

17Raumfahrt-Infrastruktur

COL–RIBRE–MA–0036–004 01.09.1997A 31.03.20001


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


1 INTRODUCTION

1.1 Identification and Scope

This document is the Administration Part of the Users and Operations Manual for the MDA – DataDictionary Maintenance Application.

1.2 Purpose

With the administration part of the User’s and Operations Manual the purchaser of DADI–MA will be ableto install the software and all of its necessary environment on a Sun Sparc server machine. It covers theinstallation and deinstallation of the DADI–MA software itself.

It is prerequisited that different software products are present on the workstation. This product list ismentioned in the chapter ’Installation Environment’.If they are not installed, please perform the installation according the chapter ’MDA Administration Manual’of the MDA Users and Operations Manual.


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.20002


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


2 APPLICABLE AND REFERENCE DOCUMENTS

Document No. Issue / Revision

Document Title

___________________________________________________________________________

2.1 Applicable Documents

2.1.1 SPE 1216 401 002 2/C 05.11.1993

MDA Requirements Specification

2.1.2 COL–RIBRE–ICD–0015–00 3/– 28.02.97

System to MDA Interfaces

2.2 Reference Documents

none


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.20003


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3 DADI–MA INSTALLATION AND DEINSTALLATION

This chapter describes how to install the DADI–MA software into its operating environment, including thedetailed manual steps to be followed, and how to deinstall the DADI–MA software.

There are a few prerequisites to both the system administrator who installs the software and to the systemenvironment where the software is installed. This prerequisites are described in the first section of thischapter.

The second section describes the installation of the software, and the final section describes the deinstallationof the DADI–MA software.

3.1 DADI–MA Installation

Check whether all you need is delivered. That is one tape with the DADI–MA distribution usually togetherwith the complete MDA installation software, the release notes, the installation and users manual. Thefollowing short overview will sketch all actions to be performed to complete the installation:

• Installation Conventions and PrerequisitesA short introduction for what is expected from the administrator who install the softwareand some hints on the understanding of the installation procedure

• Installation EnvironmentThis includes all preconditions of the necessary hardware, full installation of SunOS andOracle. Also the environment has to be set up as required. Moreover, the DADI–MA user has to be created.

• Install DADI–MA


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.20004


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3.1.1 Installation conventions and prerequisites

3.1.1.1 Procedure conventions

The installation script will maintain the following conventions:

Every machine interaction will be shown in a gray box, as depicted in the following paragraph. Machineprompts and messages will be kept in plain courier font:

Machine prompt>

Inputs of the user will be in bold courier font:

Machine prompt> User‘s input<Return>

Generic entries which have to be filled out or replaced by the user will be in bold italic courier font:

disk description

Comments within the machine interaction boxes, which will not be present on the screen, will be in italiccourier font:

(Lots of output here)

If there is a lot of output between two user commands, and that output is not important for understandingthe procedure, it is suppressed and replaced by three dots in a column, occasionally with a comment aboutthe time it will last or some errors which could be ignored.

.

. (Ignore error messages)

.

If OpenWindows is started after login as a user, the machine interaction cannot be described as a plainsequence of commands. Instead the interaction will be continued in the shelltool window of theOpenWindows desktop. To logout simply exit from OpenWindows.

Always before the user has to interact with the system, all actions to be performed will be described in detail.

Within some programs, two different kinds of user input are used:

· enterThe keyboard input has to be finished with the <Return> –key.

· typeThe keyboard input (a single keystroke) is processed as soon as you type a character.

Single keys with a special meaning are surrounded by the up– and down–sign (< and >, respectively). Specialkeys, which have to be pressed simultaneously, will be included in one pair of up– and down–signsconcatenated with a hyphen. Simultaneously means, that the keys have to be pressed in the sequence theyappear from left to right, but that every key has to be kept down during the complete operation.


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.20005


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Special keys which have to be pressed in a sequence will be included in a couple of up– and down–signs eachand then be concatenated by hyphens externally. Sequentially means the key has to be pushed down and thenreleased before the next key is pressed down. Examples:

Keys with a special meaning:<Return><Tab>

Keys to be pressed simultaneously<Shift–Return><Control–Backspace>

Keys to be pressed sequentially<Escape>–<a><Pause>–<o>–<”>

3.1.1.2 System Administrator

The administrator who installs DADI–MA is expected to have a basic knowledge of UNIX, i. e. commands,shells, editors, etc. As far as the software is installed from scratch, there cannot be done any harm to thesystem in case of an error, besides of the loss of time. If you would like to modify an existing system alreadyset up, be sure to have a most recent complete backup of your system, because acting as root may causedamage of the installed system in case of an error, even if taking the most rigid precaution.

The administrator needs access to the root account to perform some of the necessary actions. One UNIX userhas to be created. If there are standard procedures for that, they shall be used. Otherwise, look in the SunOSmanuals how to create user accounts in a Sun UNIX networked environment.

The environment for the user has to be adapted to the needs of DADI–MA. That is done by introducing somealias and setenv commends in the .cshrc and .login files. There will be a listing of the suggested changes.If some of the suggestions are already implemented in your .cshrc or .login files, ignore them.

If in doubt, the SunOS system and network administrator shall be asked. In case of a conflict betweenfollowing suggestions and the already installed environment, the DADI–MA suggestions shall be preferred,because otherwise the software will not work properly.


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.20006


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3.1.2 Installation Environment

To install the DADIMA–Tool the same H/W and S/W environment preconditions are to be met as for MDA.Since MDA is supposed to be already installed you need not take care for any environment preconditions.If MDA was not yet installed refer to MDA installation manual for more information.

Before starting DADIMA–Tool installation be sure that the MDA delivery tape was loaded asdescribed in the MDA installation manual.

3.1.2.1 User and Group Creation

• Add the group mda to the system.

• Add the mps user to the system.

Create a .login file for the user mps and place it in the home directory. This .login file should contain thefollowing lines:

This is the login add–on for a DADI–MA user

set path = ($ORACLE_HOME/bin $path)

setenv TWO_TASK Your_Actual_TWO_TASK_Value

setenv OPENWINHOME /usr/openwinsetenv ORACLE_HOME Your_Oracle_Homae_Directorysetenv ORACLE_SID Your_Oracle_SIDsetenv LD_LIBRARY_PATH $ORACLE_HOME/lib: $OPENWINHOME/libsetenv XAPPLRESDIR $OPENWINHOME/lib/app–defaults

setenv MDA_HOME Your_Specific_MDA_Directory (depending on the installation)


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.20007


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3.1.2.2 Creation of ORACLE user DADIMA and Tablespace TS_DADI

ORACLE has its own user administration, and each user who would like to use the database and DADI–MA,has to have an ORACLE account besides of a UNIX account. If the user is not present in oracle, you haveto create him. If the user is present, but do not have the right privileges and the correct table spaces, you canfollow the same procedure as described below.

The user needs the connect and resource privileges.

Perform the following steps to create the tablespace TS_DADI and the user DADIMA.

Note: In case you already have an DADI–MA–Tool installed and you want to keep the old installation inparallel in order to perform the data upgrade from the old installation into the new one (see section 3.1.4)you have to take another tablespace name (e.g. TS_DADI_NEW) and user name (e.g. DADIMA_NEW),in case the tablespace name and user name are already used for the old installation.

Login: oracle<Return>Password: YourPassword <Return>machine# sqlplus<Return>Enter user–name: system<Return>Enter password: YourPassword <Return>

SQL> create tablespace TS_DADI datafile ’ YourDatabaseDirectory /dbs/TS_DADI’ <Re-turn> 2 size 50M default storage (<Return> 3 initial 5K next 5K minextents 1 maxextents 99<Return> 4 pctincrease 50) online;<Return>

Tablespace createdSQL> grant connect, resource to DADIMA identified by DADIMA;<Return>SQL> alter user DADIMA default tablespace TS_DADI temporary tablespace TEMP;<Return>SQL> alter user DADIMA quota unlimited on TS_DADI; <Return>SQL> exit<Return>


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.20008


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3.1.3 Setup DADI–MA Oracle Objects

The install_dadi script performs the installation of the DADI–MA oracle objects.

At the beginning of the script a dialogue asks the user to specify the tablespace names for the database objectsthat are generated by this tool during the ’export to MDB’ function. Thus the user is able to define differenttablespaces for the aggregates and indexes. The default is always TS_MPS and can be overwritten by a validtablespace name.

machine% cd $MDA_HOME/util/dadi/scripts <Return>machine% install_dadi <Return>_____________________________________________________________________________________ This procedure installs the DADIMA Tool. _____________________________________________________________________________________ Do you want to install DADIMA ? [y] ___________________________________________________________________________ The logging–file stores all display outputs during the script execution. The file will be stored in the user HOME directory: [/mbf_home/mps] Enter logging–file name (default: install_dadi.log) :


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.20009


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


_______________________________________________________________

___________________________________________________________________________

Enter OWNER NAME of the DADIMA account [DADIMA] : Enter OWNER PASSWORD of the DADIMA account [DADIMA] :

Parameters for the ’create table’ statement generation process:_______________________________________________________________

The following dialog allows you to define separate tablespaces for:

1. Aggregates containing no LONG or LONG RAW data types 2. Aggregates containing LONG or LONG RAW data types

3. Indexes of aggregates containing no LONG or LONG RAW data types 4. Indexes of aggregates containing LONG or LONG RAW data types

5. Storage clause for LONG and LONG RAW data types

Note: The default value for all tablespaces is TS_MPS. The defaults for storage clause of LONG and LONG RAW data types are INITIAL 300K, NEXT 300K.

For all parameters enter only valid data to ensure that the create table statement process generates valid create table statements.

Tablespace for aggregates containing no LONG or LONG RAW data types [TS_MPS]: Tablespace for aggregates containing LONG and LONG RAW data types [TS_MPS]: Tablespace for indexes of aggregates containing no LONG and LONG RAW data types[TS_MPS]: Tablespace for indexes of aggregates containing LONG and LONG RAW data types[TS_MPS]: Storage clause for LONG and LONG RAW data types INITIAL [300K]: Storage clause for LONG and LONG RAW data types NEXT [300K]:

_________________________________________________________________


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.200010


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The actual values are:

Tablespace for aggregates containing no LONG or LONG RAW data types is [TS_MPS]Tablespace for aggregates containing LONG and LONG RAW data types is [TS_MPS]

Tablespace for indexes of aggregates containing no LONG and LONG RAW data types is[TS_MPS]Tablespace for indexes of aggregates containing LONG and LONG RAW data types is[TS_MPS]

Storage clause for LONG and LONG RAW data types INITIAL is [300K]Storage clause for LONG and LONG RAW data types NEXT is [300K]

_______________________________________________________________________________________________________

Everything correct [Y/N]? y___________________________________________________________________________Start DADIMA Installation.

... lots of messages

Disconnected from Oracle7 Server Release 7.3.2.1.0 – Production ReleasePL/SQL Release 2.3.2.0.0 – Production___________________________________________________________________________ DADIMA Installation finished.___________________________________________________________________________

In case the standard CGS end item types and aggregates shall be loaded in order to define the mapping ofthe user defined end item types to the CGS standard end item types the following script has to be started:

machine% cd $MDA_HOME/util/dadi/scripts<Return>machine% load_cgs_standard_agg <Return>machine% Enter DADIMA account name[DADIMA]: <Return>machine% Enter DADIMA account password [DADIMA]: <Return>machine%machine%


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.200011


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3.1.4 Upgrade DADI–MA Data from previous DADI–MA Version

It is prerequisite, that the new DADI–MA version contains new tables due to new functions, e.g. compositeaggregate definitions. To use the DADI–MA data definitions, performed in the old DADI–MA installationversion, also in the new DADI–MA version, an upgrade is necessary. The upgrade transfers the datadefinitions from the old DADI–MA data table structure into the new DADI–MA data table structure.

The following scripts are valid for the DADI–MA upgrade from the version 2 to version 3. If there is a newDADI–MA version in the future, new scripts will be supplied by the DADI–MA supplier.

machine% cd $MDA_HOME/util/dadi/upgrade <Return>machine% sqlplus <old dadima account>/<password> <Return>machine% start exp_dadi_from_v212_or_v300_for_v4_1_0<Return>machine% sqlplus <new dadima account>/<password> <Return>machine% start upgraded_v4_1_0_data <Return>machine%

This finishes the DADI–MA software installation.


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.200012


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3.1.5 Printer Installation

DADI–MA uses the standard Oracle report function for report printing. Within the report handlerpre–defined printers can be choosen from a selection list. The selection list displays the different printerswhich have been pre–defined in the uiprint.txt file. The file has to be modified to the specific needs with atexteditor.

machine% cd $ORACLE_HOME/guicommon2/tk23/admin<Return>machine% vi uiprint.txt<Return>

## This is the printer configuration files# Format is# <OSName>:<Type>:<Version>:<Long Name>:<Description File>:## The first field is the name of the printer. It is the name you give# to lpq.## The second field is the type of driver to be used for the printer.# Currently, ”PostScript” and ”ASCII” are the only types of driver for# printers supported for now. But in future we may be supporting# drivers for other printer types.# # The third field is the version of the type of printer driver. It’s 1# or 2 for all PostScript printers; or 1 for ASCII printers.## The fourth field is a long description of the printer.## The fifth field is the printer description file to be used. For# PostScript printers it is the PPD file of the printer. (This field is# currently unused for ASCII printers.)## You don’t have to update this file to use any printer. The printer# chooser interface let’s you select a printer at run time as well as# associate a printer description file to the printer## Note the trailing ’:’ is significant. Also all the fields need to be# filled in. You can use default.ppd if you don’t have a PPD file for# the printer, but it’s best to use the correct PPD file for the# printer.## The next four lines contain printer definition exampleslp:PostScript:1:lw printer on mps:default.ppd:lw_mps_s:PostScript:1:lw_mps_s printer on mps2s:default.ppd:lw2_gsags:PostScript:1:lw2_gsags printer on gsafs:default.ppd:lw_mps2s:PostScript:1:lw_mps2s printer on mps2s:default.ppd:add your printer definitions here## Define the printers, save the changes and exit the texteditor#machine%


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.200013


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


This finishes the DADI–MA software installation.

Please note that you must not use the ’–’ sign for printernames. Allowed are all alphanumeric characters and underscorecharacter.


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.200014


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3.2 DADI–MA Deinstallation

The following text describes how to deinstall and remove all installations which have been made during theDADI–MA software installation. It is important to perform the steps in the right sequence because otherwisethere could be problems to execute a certain deinstallation step. The deinstallation is performed in a reversesequence to the installation procedure.

The following actions are necessary to remove DADI–MA from the operational environment:

• Deinstall DADI–MA User

• Deinstall DADI–MA

3.2.1 Deinstall DADI–MA User

To deinstall the DADI–MA user you have to login as mps and to use the drop_dadi script in$MDA_HOME/util/dadi/scripts. Perform the following instructions:

machine% cd $MDA_HOME/util/dadi/scripts <Return>machine% drop_dadi <Return>...... (some messages and user input for logging file name)...Enter OWNER NAME of the DADIMA account [DADIMA] : TheOwnerName<Return>Enter OWNER PASSWORD of the DADIMA account [DADIMA] : ThePassword <Return>___________________________________________________________________Start DADIMA De–Installation....... (a lot of installation messages)...___________________________________________________________________DADIMA De–Installation finished.___________________________________________________________________machine%

This finishes the deinstallation of the DADI–MA user.

3.2.2 Deinstall DADI–MA Files

To deinstall the DADI–MA files from disk you have to login as mps and perform the following instructions:

machine%

machine% \rm –r –f $MDA_HOME/util/dadi<Return>


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.200015


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3.3 MDB PRE–INSTALLATION ACTIVITIES

Once the user has installed the DADI–MA Tool has has defined his own MDB Version with this tool, thenext step is the installation of the MDB Version (refer to MDA Administration Manual). Prior to theinstallation three steps have to be done:

• Export MDB Version / generate MDB installation files

• Copy MDB installation files into the MDB installation environment

• Adapt MDB upgrade file ’parfile.lst2’

3.3.1 Copying the DADI–MA Export Files (MDB installation files)

When a user has performed the ”Export to MDB” in DADI–MA, all generated files are stored in the

$MDA_HOME/MDA/util/dadi/dadi_export

directory.

The export files have to be copied from the DADI–MA scope into the MDB Installation scope, before theMDB can be installed with these data. The MDB installation scripts access the information from the

$MDA_HOME/MDA/config/mdb/install

directory.

To transfer the generated export files from the DADI–MA scope into the MDB installation scope, thefollowing steps have to be performed:

machine% ( Move to the MDB installation directory )

machine% cd $MDA_HOME/config/mdb/install<Return>( Remove the old export files )

machine% \rm –r dadi_export<Return>

( Copy the export files into the MDB installation directory)machine% \cp –r $MDA_HOME/util/dadi/dadi_export .<Return>

3.3.2 User defined Data Structure Upgrade (Adapt MDB upgrade file: ’parfile.lst2’)

If a user modifies existing MDB data structure definitions with DADI–MA, an upgrade becomes necessaryin order to transfer the data from the old MDB version into the new one.

It is always recommended to keep the new MDB version upward–compatible to the old MDB version. Thismeans not to delete or modify any existing aggregates or attributes, only add new once.

If the new MDB version contains additional data structures, the following parameter file has to be modified.

$MDA_HOME/MDA/config/mdb/upgrade/parfile.lst2<mdb version name>

This file includes the CGS standard aggregate names and the user defined aggregate names. It has to bemaintained by the DADI–MA Tool user (data structure engineer). Normally this file is filled with the CGSstandard aggregate names.

If new user defined aggregates are defined with DADI–MA, these aggregates have to be included into thisfile.


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.200016


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The parfile.lst2 has to contain only aggregates that are compatible between the new and the old MDB version.In case the file contains aggregates which are not compatible with the old MDB version, error messages willoccur when executing the import of the old MDB version and the import fails for the non compatibleaggregates.


COL–RIBRE–MA–0036–004 01.09.1997A 31.03.200017


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


This page is intentionally left blank.