COMUNICACIONES ORALES / COMUNICAÇÕES ORALS

The Data options on the main menu are Change Management, Inter DB Macros and Extract Database Control.

16.12.1

Change Management

The Data > Change Management option is used to Merge Changes and Backtrack Changes in the AVEVA Hull and Outfitting sessions.

16.12.1.1 Merging Sessions

AVEVA Hull and Outfitting 12.1.SPx sessions enable recording a history of changes to the database. When a new session is made, changed data is appended at the end of the database file. Appending updated data to database files increases the disk space requirements. If the history information is not required, in order to save disk space, database(s) can be compacted by merging sessions. It can be specified that the changes before or after a given date or session number will be merged.

i.e. If there is a session, which corresponds to a project milestone that needs to be kept, the administrator can merge the sessions around this. In other cases, it may be that all sessions before a given date or within a given week need to be merged. Merging the database sessions has no effect on any database references into that database from other databases.

To merge sessions select Data > Change

Management > Merge Changes from the main Admin menu. The Merge Changes form will be displayed. It is possible to merge the changes to All Project databases, the System databases, or the Single database selected in the list.

AVEVA Marine (12.1) System Administration (Basic) TM-2120

If All Project databases option is selected, changes can be merged for the period before or after a given time, date or session number.

If System Database option is selected, changes before or after a given time, date or session number can be merged.

If Single database option is selected, a database from the list is to be selected. Log into the ADMIN as system user

in the MTP project. Select Single Database

HULLDRAFTFWD/HULLFWDPADD1 from the list.

The Database Sessions button is now available. Click the Database Sessions button. The Database Sessions form appears displaying all sessions which have not been merged.

Click the Dismiss button to leave the form.

From the Merge changes form click the Apply button, and then click the Database Sessions button again. As shown, all the sessions have been merged and the database size will have been reduced.

Normal procedure is to do database merge after creating a project archive.

The Command window can be opened during the merging of sessions to give additional information regarding the results of merging.

The Rebuild list button is used to update the list of databases. I.e. if a new database has been created while the form is displayed, the list will not be updated until the form is closed and re- displayed, or the Rebuild list button is clicked.

www.aveva.com

16.12.1.2 Backtrack Sessions.

A database can be returned to the state it was in at a previous session using the Data > Change

Management > Backtrack Changes option on the main Admin menu. The Backtrack Changes form will be displayed.

Select the database from the list. Backtrack changes can be executed by specifying a time, date or session number.

Subsequent sessions will be lost, and so you may wish to copy the database before backtracking. You can backtrack to the date or session number required.

Note that if a database has been upgraded after the nominated session it will be necessary to upgrade the database again.

The Rebuild list button is used to update the list of databases. I.e. if a new database has been created while the form is displayed, the list will not be updated until the form is closed and re-displayed, or the Rebuild list button is clicked.

From the Backtrack Changes form select the Database

DRAFT/MIDPADD. An example can be seen in the screen shot showing the database is up to Session Number 23. Changes can be backtracked to any session above Session Number 2 because Session Number 2 is required as this is the Database Creation Session. Click More button to see the session details.

The DB Session number may differ from those shown in the screen shots due to previous merging of sessions.

The Session Number field is used to set the session to backtrack to, 18. Click the Apply button. As shown on the Database Session Form, a new Session, session 24 has been created which is a copy of session 18.

AVEVA Marine (12.1) System Administration (Basic) TM-2120

The GUI does not actually do a physical backtrack. It performs revert i.e. the latest session is a copy of a previous session.

To illustrate this we will now enter AVEVA Hull and Outfitting 12.1.SPx in the Training project as user DHULL in the STRUCDESIGN mdb, using the HullDesign application. Display the Draft Explorer (View > Explorers > Draft Explorer). Create a new drawing named BACKTRACK. Save the drawing then Save and Unclaim and exit. Log into Admin, backtrack the database

HULLDRAFTFWD/HULLFWDDPADD1 to the previous session. Then log in to the project again and view the drawing list. The drawings can be retrieved by Backtracking the database back to the previous session.

Backtrack changes can be done by specifying a time, date or session number

16.12.2

Backtracking the Databases (Command Window)

As previously stated, the AVEVA Hull and Outfitting 12.1.SPx GUI performs revert and not a physical backtrack. The only way of performing physical backtrack is to use the command Window.

The administrator should not use the Backtrack Command as data will be deleted; this command will be used during the Reconfigure Same ref process which is discussed later

Example backtracks on the Command Window. BACKTRACK PIPEF/DESIGN SESS 2

16.12.3

Inter-DB Macros

Inter-DB macros can be displayed by selecting Data > Inter-db Macros from the main Admin menu. The Inter-Database Macros form will be displayed.

To delete a macro, select the macro in the scrolling list and click Delete button. This allows deleting any macros, not just the macros for the current team.

Inter-DB macros are created in the following situations:

A user in design application attempts to make a connection to an element in a design database to which the user does not have write access to;

A user in design application attempts to make a connection to an element in a multiwrite design database to which the user has write access, but the element is claimed by another user; A user in isodraft updates revision and detail attributes which need to be stored in the design database, to which the user has no access to;

The administrator would normally check with the project users before deleting Inter-DB macros.

Normal procedure is that the designers run and delete their own macros so the last situation stated above is not the usual way of handling inter - DB macros.

www.aveva.com

16.12.4

Inter-DB Macros

Data > Extract Database Control option displays the Extract Database Control form, which allows user to see the extract hierarchy in the project, and to refresh, release, issue and drop changes to extract databases.

Database Extracts are covered in System Admin (Advanced) training course.