Ovation Database (For Use with Windows 2000)

Section Title Page Section 1. Introduction

1-1. Overview...... 1-1 1-2. Ovation Database Types ...... 1-2 1-3. Relationships with other Database Functions...... 1-4 1-4. Definition of Terms...... 1-5 1-5. Contents of this Document ...... 1-7 1-6. Additional Reference Documentation...... 1-8

Section 2. Population of the Database

2-1. Overview...... 2-1 2-2. Database Initial Definition Tool (DBID) ...... 2-2 2-3. Import (OvPtImport)...... 2-3 2-3.1. Import Format (Ovation 2.x Systems) ...... 2-4 2-3.2. Import Format (for Ovation 1.x Systems) ...... 2-9 2-4. Export (OvPtExport)...... 2-12 2-4.1. Using OvPtExport to Restore the Database...... 2-13 2-5. Oracle Import and Export ...... 2-14

Section 3. Backing Up and Restoring the Database

3-1. Overview...... 3-1 3-2. Backing Up the Database Files...... 3-2 3-2.1. Complete Database Backup (using exp80) ...... 3-3 3-2.2. Partial Database Backup (using OvPtExport) ...... 3-3 3-3. Reloading the Database Files ...... 3-4 3-3.1. Reloading from an Oracle Database Backup...... 3-4 3-3.2. Reloading from an Ovation Export File...... 3-5

Glossary

Index

1/03 1 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C

Section 1. Introduction

1-1. Overview

This manual discusses the Ovation Database that is provided with the Ovation Windows 2000 Operating System. The Ovation system uses the Relational Database Management System (RDBMS) philosophy. This philosophy consists of three major components: • A common mechanism for performing similar actions. • An intimate sharing of data. • Interaction with a shared repository of data. A Relational Database Management System stores information in tables — rows and columns of data — and conducts searches by using data in specified columns of one table to find additional data in another table. In a relational database, the rows of a table represent records (collections of information about separate items) and the columns represent fields (particular attributes of a record). In conducting searches, a relational database matches information from a field in one table with information in a corresponding field of another table to produce a third table that combines requested data from both tables.

Many pieces of information in the Ovation system, including system configuration, control algorithm information, and the process point database are stored in the Ovation Database. The Ovation Database provides the capability to integrate and organize the massive amounts of raw data in the system to create meaningful and valuable information.

All programming tools and user interfaces store their data in the Ovation Database, and then the information is transmitted to the control system. The Ovation Database allows the applications software and the control system to be easily accessed via third party SQL (Structured Query Language) tools. This means that the Ovation process control system data is open and accessible.

The Ovation Database is based on ORACLE8. For computing environments, such as Ovation, that are connected via networks, ORACLE combines the data physically located on different computers into one logical database that can be accessed by non-controller network nodes.

1/03 1-1 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 1-2. Ovation Database Types

1-2. Ovation Database Types

At the heart of the RDBMS is the Ovation Database which consists of a Master Database and is supported by various Distributed Databases.

The Distributed Database contains subsets of information from the Master Database and is stored locally on a drop to allow that drop to operate if the Master Database is unavailable. A Distributed Database is present on each drop in the system and is continually updated as point information changes.

The contents of these subsets depend on the system drops as defined below: • Identification of Plant Mode Point (if applicable). • Information used to retrieve process point data from the Ovation Highway. For Operator Stations, this includes all system points updated via the Load function for originated and explicitly received points and the Distributed Database Propagation software for all other system points. For Controllers, this includes only originated and explicitly received points (updated via the Drop load function). See “Ovation Developer Studio User Guide” (WIN60) for information on the Load function. • Identification of primary/partner drop ID pairings for system drops. For Ovation Operator Stations, this includes all system drops updated via Distributed Database Propagation Software. For Controllers, this means only itself (if redundant) and any redundant drops which it explicitly receives points from (updated via the Load function). • Security Information. This is for Ovation Operator Stations only. It is updated via the Distributed Database Propagation Software. • System Point Directory. This is for Ovation Operator Stations only. It is updated via the Distributed Database Propagation Software. • MMI data for all System Points. This is for Ovation Operator Stations only. It is updated via the Distributed Database Propagation Software. • Global Point Groups. This is for Ovation Operator Stations only. They are updated via the Distributed Database Propagation Software.

The Distributed Database subsets are kept consistent with the contents of the Master Database. Database propagation provides the mechanism whereby the database contents at each distributed location are kept consistent with the contents of the Master Database. The propagation of all database changes is performed by an exchange of messages between a server process (db_xmit_server) which monitors the Master Database and client processes (db_xmit_client) which operate on each distributed station.

WIN15 (Rev 0) 1-2 1/03 Emerson Process Management Proprietary Class 2C 1-2. Ovation Database Types

Changes to the Master Database are performed using system editing functions such as those provided by the Ovation Developer Studio and the Ovation Control Builder. These changes are applied to the database through the business rules API functions. When a point modification is loaded to the originating drop(s) via the Load function, a record of the change is maintained in a table in the Master Database.

Similarly, a change is recorded whenever Ovation Security objects or Point Group objects are changed in the Ovation Developer Studio. The server monitors this table to identify when changes have been loaded to the system.

Each change is identified by a unique sequence number which allows the server to ensure that changes are applied to the Distributed Databases in the same order that they were applied to the Master Database.

As changes are made/loaded, the server performs a multicast broadcast of applicable data for each change in sequence. Mechanisms exist whereby clients can detect if messages have been missed and establish a direct TCP connection with the server to quickly get “up-to-date.” The server also periodically broadcasts (via multicast) the Plant Mode Point Information, primary/partner drop information, drop mismatch information, and the current sequence number. Clients use the current sequence number to determine if they need to explicitly request an update.

1/03 1-3 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 1-3. Relationships with other Database Functions

1-3. Relationships with other Database Functions

The Ovation Database has a relationship with other functions as described below:

Ovation Control Builder — Algorithm and Control Builder default points are created, deleted and modified with the Control Builder. Control program instructions and Boolean program instruction information are created and deleted with the Control Builder. The Load function of the Ovation Developer Studio is used to load the information to the originating drop(s).

Ovation Developer Studio — The Developer Studio provides a package of tools necessary to build and maintain a process control system. Using the tools available, you can build an entire system, import information from a previously created database into the Developer Studio, and edit and update attributes such as network configurations and point information.

WIN15 (Rev 0) 1-4 1/03 Emerson Process Management Proprietary Class 2C 1-4. Definition of Terms

1-4. Definition of Terms

Table 1-1 lists and describes the terms that are used in this manual.

Table 1-1. Definition of Terms Term Definition API Database Application Programming Interface. Used to “talk” or interface to the system Relational Databases: Oracle (Master Database) or Raima (Distributed Database used by Operator Stations and populated from Oracle). Business Rules (Ovation) Layer of software between Ovation applications and the database interface software. Distributed Database Contains a subset of the information stored on the Master Database. A Distributed Database is present on each drop in the system and is continually updated as point information changes. It contains an updatable system point directory and the MMI data fields of the process points (ED, SD, RS, and so forth) as well as the other fields not broadcast as part of a point’s static data. Distributed Database Propagation Continuously running daemon process on the Server drop Software which broadcasts, via multicast address, distributed database information to all system drops. It also supports a mode whereby clients can receive information by TCP connection if they are significantly out of date. Export (OvPtExport) function Ovation utility that is run to copy data from the database to a text file. Import (OvPtImport) function Ovation utility that is run to put data into the database. This is done by means of a text file. Load function on the Ovation Ovation function that is used to transfer data from the Developer Studio Master Database and distribute it to control drops and those drops that originate points. Master Database Contains the entire process database. It is used for creating, modifying, and verifying control strategies and process points. At runtime, it supports queries of the process database, captures changes made to control and point attributes, and propagates those changes to the distributed database. Network Nodes Another term for drops on the Ovation Network.

1/03 1-5 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 1-4. Definition of Terms

Table 1-1. Definition of Terms (Cont’d) Term Definition Oracle import/export function Oracle’s utility that is used to put data into the database and to backup the data in the database. However, this function is used for complete restoration of the entire database (structure and contents) following a catastrophic failure (disk crash, operating system reload, and so forth). This tool is NOT for saving and restoring database contents during an Ovation software upgrade. Working Area Part of the Master Database that is used when working with the system. This is where all interaction with the database takes place. This is the only part of the database that can be edited.

WIN15 (Rev 0) 1-6 1/03 Emerson Process Management Proprietary Class 2C 1-5. Contents of this Document

1-5. Contents of this Document

This document is organized into the following sections:

Section 1. Introduction describes the organization of this manual and provides a description of the Database types, a list of terms, and a list of additional reference documents.

Section 2. Population of the Database describes the utilities used to put data into and take data out of the database.

Section 3. Backing Up and Restoring the Database provides information on backing up and reloading the database.

1/03 1-7 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 1-6. Additional Reference Documentation

1-6. Additional Reference Documentation

Table 1-2 lists additional reference documentation which may be helpful while using this manual.

Table 1-2. Reference Documentation Document Number Title Description WIN60 Ovation Developer Studio Provides information on configuration, creating User Guide points, and security. WIN80 Ovation Control Builder Describes the control logic that is run in the User Guide Ovation NT Controller and how to create that logic. R3-1140 Ovation Record Types Provides information on process points and record Reference Manual fields. R3-1145 Ovation Error Codes and Lists and describes the error codes and messages Messages incorporated in the Ovation system.

In addition to the documents listed in Table 1-2, this manual may refer to “applicable vendor documentation,” which is defined on a project basis. These documents may include: • Operating system (Microsoft Windows 2000TM) manuals. • Peripheral device documentation.

WIN15 (Rev 0) 1-8 1/03 Emerson Process Management Proprietary Class 2C Section 2. Population of the Database

2-1. Overview

This section discusses how information is put into and taken out of the Ovation Database. The following topics are included in this section: • Database Initial Definition Tool (DBID) (Section 2-2). • Import (OvPtImport) (Section 2-3). • Export (OvPtExport) (Section 2-4). • Oracle Import and Export (Section 2-5). Table 2-1 provides brief descriptions of the various database tools used to populate the Ovation database. The following sections provide detailed descriptions of those tools.

Table 2-1. Database Tools Tool Description DBID Microsoft Access graphical interface used to create points in a text (ASCII) file (Emerson Tool) that can then be imported into the Master Database. OvPtImport Imports data from text file (for example, a DBID produced file) into Master (Ovation Tool) Database. Can be used to restore database (using data from a previous OvPtExport file). OvPtExport Exports data from Master Database and produces a text file. This file does not (Ovation Tool) contain SIDs or a point’s network interface information. imp80 Can be used to restore database after a catastrophic failure (such as a disk crash). (Oracle Tool) Operates on the binary file produced by exp80. exp80 Can be used to backup system. Produces a binary file. (Oracle Tool)

1/03 2-1 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 2-2. Database Initial Definition Tool (DBID)

2-2. Database Initial Definition Tool (DBID)

The Database has the potential to be a very large repository of data. A means is provided to perform mass entry as well as importing data defined in a format foreign to the Master Database.

To facilitate the initial population of the Database, the Database Initial Definition Tool (DBID) was created. Like the Ovation Point Building process in the Ovation Developer Studio, DBID provides a graphical user interface for creating, deleting, and modifying point data. The DBID also supports mass data entry and global edit/ replace functions by allowing the user to modify data directly in the point tables. See “Ovation Developer Studio User Guide” (WIN60) for information on the Point Building process.

DBID is based on the Microsoft Access95, 97, and 2000 database products along with other programs for data checking. DBID looks very similar to the Ovation Point Building program, as it contains forms for definitions and configuration of hardware in the system and for entry and editing of the point data.

Data may be entered manually or point data may be loaded from a number of other sources such as DBASE or spreadsheet files, but may require some customer conversion depending on the structure of the external data.

Once information is entered in DBID, processed by Emerson Process Management, and imported into the Master Database, it can be modified through the Ovation Point Building process on a point-by-point basis.

DBID generates a text file that can be imported by Emerson Process Management into the Ovation Database (see Section 2-3).

Note

It is beyond the scope of this manual to further discuss DBID. For more information, refer to the DBID documentation or contact an Emerson representative.

WIN15 (Rev 0) 2-2 1/03 Emerson Process Management Proprietary Class 2C 2-3. Import (OvPtImport)

2-3. Import (OvPtImport)

Once an import file has been generated from the DBID tool (Section 2-2), the Import function (OvPtImport) is used to move data into the Master Database. It works in conjunction with the Export function (OvPtExport) (Section 2-4).

The import process serves three purposes: • Initial creation of the database. • Modification of an existing database. • Restoration of the database to a known state. The Import function supports two different import file formats. The first (version 1), is identical to that produced by the Ovation 1.x Export function and dbid (see Section 2-3.2). The new format (version 2) has been defined to provide improved functionality and performance on the Ovation 2.x systems (see Section 2-3.1).

The OvPtImport utility is located in the C:\Ovation\OvationBase directory. To use OvPtImport, run the following command from a command prompt:

ovptimport -u ptadmin/ptadmin@ptdb -s

where can be any one of the following:

-h = Displays help messages -c = Continue despite errors -f = Full import. Replace existing contents. Note that the use of this option reassigns System IDs (SIDs). Graphics and Control Sheets must be reimported and recompiled following the use of this option. -id = Ignore defaults -n = New objects only -p = Parse the file(s). No database updates -r = Check for presence of all required fields -s = For version 1 import files, specify the system name for a full import or the system to use if an incremental import.

1/03 2-3 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 2-3. Import (OvPtImport)

Once data is imported into the Master Database, it must be loaded into the Controllers and drops that originate points. This is done with the Load function in the Ovation Developer Studio (see “Ovation Developer Studio User Guide” (WIN60) for more information).

Caution

Do NOT use the database import function (OvPtImport) if the Ovation Developer Studio or any Ovation engineering program that is accessed from the Studio (Control Builder, Graphics Builder, or the Holding Register Configuration UI) is in use anywhere in your system. Confirm that these programs are not being used before you perform a database import. The OvPtImport program temporarily disables certain Oracle triggers, which are required for proper operation of the Ovation Engineering Tools. If the OvPtImport program should fail to complete/exit naturally (for example, if the task was manually killed by the user), those triggers will not be restored. If this should occur, in order for the database to function properly, the applicable triggers must be re-enabled either by a subsequent OvPtImport operation (which runs to completion) or manually by using the following command: OvPtImport -u ptadmin/ptadmin@ptdb -Xrc

2-3.1. Import Format (Ovation 2.x Systems)

The format of the Import file for Ovation 2.x systems is structured after the hierarchy defined in the Ovation NT Developer Studio. The hierarchy is described briefly below; however, for more detailed information, see “Ovation Developer Studio User Guide” (WIN60).

The Ovation Developer Studio provides an integrated package that allows you to quickly and easily perform configuration and engineering functions for a Windows 2000 based Ovation System. Using the tools available, you can build an entire system, import information from a previously created database, and edit and update attributes such as network configurations and point information.

WIN15 (Rev 0) 2-4 1/03 Emerson Process Management Proprietary Class 2C 2-3. Import (OvPtImport)

Ovation Developer Studio functions are categorized in a hierarchical file structure or System Tree. Figure 2-1 depicts the Developer Studio System Tree. Ovation configuration information is specified at appropriate levels of the system hierarchy.

Licenses Security Systems Folder Ancillary Point Groups Configuration Graphics Networks

Configuration Graphics Networks Folder Units

Configuration Graphics Units Folder Drops

Configuration Graphics Drops Folder I/O Devices Control Components Control Tasks Holding Registers Points Analog Deluxe Analog Digital Deluxe Digital Points Folder Packed Deluxe Packed Packed Digital Algorithm Drop Module Node Figure 2-1. Ovation Developer Studio System Tree

1/03 2-5 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 2-3. Import (OvPtImport)

The highest level in the System Tree is the System, followed by the Network, Unit, Drop, and Point. Point objects are the lowest level of the system tree and open to reveal point records. Point records store the information that defines the attributes of the point. Ovation configuration settings and attributes changes made at the System level default down through the System tree but can be adjusted at each subsequent level. Figure 2-2 shows the Developer Studio interface.

Figure 2-2. Developer Studio Interface

As described previously, the format of the Import file mirrors the Developer Studio System Tree. Each line of the import file contains a statement of the following form:

(TYPE=“” NAME=“” [ ] )

WIN15 (Rev 0) 2-6 1/03 Emerson Process Management Proprietary Class 2C 2-3. Import (OvPtImport)

Object definitions (optionally followed by attributes) are specified in descending order of the hierarchy and are delimited by parenthesis. Changes to an object’s attributes are delimited by square brackets [ ]. The lack of [ ] indicates that the object is a placeholder to the next level of the hierarchy. No changes are made to this object during import.

WARNING

If square brackets are used in a statement, and nothing is shown inside, “[ ]”, this indicates that the object’s attributes should be deleted (that is, whatever the information was, change it to the default, since nothing is defined inside the square brackets). Use caution when using square brackets.

For points, the list of applicable object attributes is the same as the field names used in version 1.x import files with the exclusion of NETWORK_ID, UNIT_ID, and DROP_ID. These attributes are implied based on the point’s position in the hierarchy.

The following example shows an import file where the system, network, and drop objects are used as placeholders (that is, no changes to existing data). The Unit object is being changed as well as the analog point “LA100”. Note that the first line of the file must be “OVPT_FORMAT=2.x” to specify that this is a version 2.x format import file.

1/03 2-7 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 2-3. Import (OvPtImport)

OVPT_FORMAT=2.1 (TYPE=”System” NAME=”Ovation” (TYPE=”Network” NAME=”NET0” (TYPE=”Unit” NAME=”UNIT1” [UNIT_NAME=”UNIT1” UNIT_VALUE=”1”] (TYPE=”Drop” NAME=”DROP1/DROP51” (TYPE=”AnalogPoint” NAME=”LA100” [DESCRIPTION=”Test Point” BROADCAST_FREQUENCY=”S” OPP_RATE=”S” CHARACTERISTICS=”-----” PERIODIC_SAVE=”0” TAGOUT=”0” UNCOMMISSIONED=”0” INITIAL_VALUE=”0” AUTO_RESET=”0” AUTO_ACKNOWLEDGE=”0” LOW_ALARM_PRIORITY_1=”1” LOW_ALARM_PRIORITY_2=”1” LOW_ALARM_PRIORITY_3=”1” LOW_ALARM_PRIORITY_4=”1” LOW_ALARM_PRIORITY_USER=”1” HIGH_ALARM_PRIORITY_1=”1” HIGH_ALARM_PRIORITY_2=”1” HIGH_ALARM_PRIORITY_3=”1” HIGH_ALARM_PRIORITY_4=”1” HIGH_ALARM_PRIORITY_USER=”1” TOP_OUTPUT_SCALE=”100” BOTTOM_OUTPUT_SCALE=”0” THERMOCOUPLE_UNITS=”F” CONVERSION_TYPE==”0” CONVERSION_COEFF_1=”0” CONVERSION_COEFF_2=”1.234” CONVERSION_COEFF_3=”1.234E+012” CONVERSION_COEFF_4=”0” CONVERSION_COEFF_5=”10000” CONVERSION_COEFF_6=”0” CJC_TEMPERATURE_UNITS=”F” DISPLAY_TYPE=”S”

Figure 2-3. Import File for Ovation 2.x Systems

WIN15 (Rev 0) 2-8 1/03 Emerson Process Management Proprietary Class 2C 2-3. Import (OvPtImport)

SIGNIFICANT_DIGITS=”2” IO_TASK_INDEX=”1” SECURITY_GROUP_1=””1” SECURITY_GROUP_2=”1” SECURITY_GROUP_3=”1” SECURITY_GROUP_4=”1” DEADBAND_ALGORITHM=”STANDARD” COLLECT_ENABLED=”0” EVENT_ENABLED=”0”] ) ) ) ) ) Figure 2-3. Import File for Ovation 2.x Systems (Cont’d)

2-3.2. Import Format (for Ovation 1.x Systems)

For users who are upgrading from Ovation 1.x to Ovation 2.x, the following import formats are applicable. Each line of the import file contains an action statement of the form:

OBJECT=“” ACTION=“” ...

Terms Used

Valid OBJECT_TYPEs are POINT and TABLE. Under each OBJECT_TYPE, different ACTION_TYPEs are valid, as shown below: • POINT — valid ACTION_TYPEs are: — INSERT — used to insert a new point or modify specific fields of an existing point. Note that when importing into the Ovation NT database, this command is handled as RESET/REDEFINE. — DELETE — used to remove a point. This command is not applicable when importing into the Ovation NT database. — RESET (or REDEFINE) — used to assign a null value to every non- required field of an existing point and optionally modify specific fields of that point. An attempt to RESET a non-existent point is treated as an INSERT of that point.

1/03 2-9 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 2-3. Import (OvPtImport)

• TABLE — valid ACTION_TYPES are: — PURGE — results in the contents of the table being deleted. — INSERT — inserts a new row in the table.

Rules

The following rules apply to the format of the import file.

1. OBJECT_TYPE and ACTION_TYPE must be specified for each action line. An action line may be split across multiple physical lines with new lines, but the breaks must occur between keyword pairs.

2. For points, the attributes are specified with the field name and field value separated with an equal sign. Attributes are separated by whitespace. Field values are enclosed in double quotes. For each definition, all required fields must be specified. Any number (including none) of the optional fields may be specified. Case is not significant for the field names, but is for the field values. Integer fields may be specified in base 10 or in base 16 if prefaced with 0x.

3. For tables, the table name is specified with the table attribute, and each of the columns is specified as = “column value”. It is highly recommended that table commands always be preceded by a PURGE, followed by all of the insert statements necessary to populate the table.

4. Comments can be included by prefacing the comment with a “#” character. All text from the # character to the end of the line is ignored. Note that # characters with double quotes are not considered comments.

Examples

The following examples are given to illustrate the import format: • Inserting or modifying a point: OBJECT= “POINT” ACTION= “INSERT” point_name= “LD134INS001” record_type= “LD” network_id= “0” unit_id= “1” drop_id= “134” broadcast_frequency= “S” opp_rate= “S” low_alarm_priority_1= “2” high_alarm_priority_1= “3”

WIN15 (Rev 0) 2-10 1/03 Emerson Process Management Proprietary Class 2C 2-3. Import (OvPtImport)

• Resetting a point and specifying a field: OBJECT= “POINT” ACTION= “RESET” point_name= “LD134INS001” network_id= “0” unit_id= “1” engineering_units= “Volts” • Purging a table: OBJECT= “TABLE” ACTION= “PURGE” table= “drop_io_config” • Inserting into a table: OBJECT= “TABLE” ACTION= “INSERT” table= “drop_io_config” drop_id= “161” network_id= “0” unit_id= “1” pci_slot= “1” io_type= “1”

Special Considerations for Both Formats

The Import function will not support the following operations: • Moving objects from one location to another. • Changing I/O modules (hardware) via version 1 import files.

1/03 2-11 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 2-4. Export (OvPtExport)

2-4. Export (OvPtExport)

The Export function (OvPtExport) is used to pull data out of the Master Database. It works in conjunction with the Import function (OvPtImport) (Section 2-3).

The Export function (OvPtExport) produces a text file which contains the current configuration of the system (drops, hardware, security, and so forth), as well as user- level parameters defined for all points in the system. It does not contain SIDs and network information.

The OvPtExport files can be used for revision control of the database. Since each OvPtExport file represents the user parameters of all objects in the database, they can be saved independently with a user-assigned revision number and used later to restore the database contents (Section 2-4.1).

The OvPtExport utility is located in the C:\Ovation\OvationBase directory. To use OvPtExport, run the following command from a shell tool window:

ovptexport -u ptadmin/ptadmin@ptdb -o [-a -mm -nd -s -h]

where:

-o = Output filename to receive the export -a = Output all attribute definitions -mm = Minimal module definitions -nd = Do not export defaults -s = Specify the system name to export -h = Display help messages

WIN15 (Rev 0) 2-12 1/03 Emerson Process Management Proprietary Class 2C 2-4. Export (OvPtExport)

2-4.1. Using OvPtExport to Restore the Database

A means of restoring the working area of the database is required. This can be accomplished by one of two methods: Restore the entire database using the Oracle import/export utilities (Section 2-5) or apply the contents of a previous OvPtExport.

Depending on the circumstances and the customers needs, either one or both of these methods may be used.

A less disruptive means of doing a restore is to apply the contents of a previous OvPtExport. Since they only affect the user-level parameters of the database, they can be applied (via OvPtImport) without requiring a clear and reload of all the drops in the system.

There is one caution to this process: OvPtImport does not implicitly delete points. If an OvPtExport file were created, and new points were subsequently added to the database, an OvPtImport of the previous file will not remove those new points.

Note

An OvPtExport file does not contain control information. Control sheets must be backed up separately. See “Ovation Control Builder User Guide” (WIN80) for more information. It also does not contain the graphic source files themselves. These files must also be backed up separately and imported into the system from the Ovation Developer Studio after the restoration of the database via OvPtImport. See “Ovation Graphics Builder User Guide” (WIN90).

1/03 2-13 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 2-5. Oracle Import and Export

2-5. Oracle Import and Export

The Oracle utilities imp80 and exp80 are used to create and restore image backups of the entire database. They take a binary snapshot of both the database structure and contents, and can be used for a complete restoration of the entire database following a catastrophic failure (disk crash, operating system reload, and so forth). Following a restoration, the state of the database (structure and contents) is exactly what it was when the export was taken. These tools are not necessary (and typically should not be used) for restoring database contents during an Ovation software upgrade.

For more information on the imp80 and exp80 functions, refer to the applicable Oracle documentation.

WIN15 (Rev 0) 2-14 1/03 Emerson Process Management Proprietary Class 2C Section 3. Backing Up and Restoring the Database

3-1. Overview

At times it may be necessary to backup and reload the database. The following topics are included in this section: • Backing up the database files (Section 3-2). • Reloading the database files (Section 3-3).

1/03 3-1 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 3-2. Backing Up the Database Files

3-2. Backing Up the Database Files

There are two programs available for backing up the database: • Oracle export program (exp80). This tool saves the entire database, all of the structure, and all of the content; alternately, it can also be used to save selected portions. Existing point SIDs and network addressing assignments are retained. Following a restoration, the state of the database (structure and contents) is exactly what it was when the export was taken.

This tool should be used to back up the database so that it could be completely restored in case there is a system disruption such as disk crash or operating system reload.

This type of backup is generally not portable from one Ovation job to the next. It should not be used to copy a database between a Master Database and an External Database.

To use the Oracle export program, refer to the Oracle documentation that was supplied with your system. • Ovation Export program (OvPtExport). This tool saves all of the database configuration and point information into an ASCII file. None of the database structure is saved.

This tool should be used when an Ovation software upgrade of the server requires a complete reload of that drop.

If necessary, the database schema is changed during a software upgrade procedure and no restore operations are needed.

However, if for any reason the Database Server is completely reloaded, the database must be populated with the export file, re-execution of Control Builder scripts (to load control sheet information into the database), and a re-import of all the custom diagrams.

WIN15 (Rev 0) 3-2 1/03 Emerson Process Management Proprietary Class 2C 3-2. Backing Up the Database Files

3-2.1. Complete Database Backup (using exp80)

Use the following procedure to backup the database structure and content:

1. Export the contents of the Oracle database with the following command:

exp80 USERID=system/wdpf FILE= FULL=Y COMPRESS=N LOG=

(where is the user-defined filename for the backup file) This will create a file named .

(where is the user-defined filename for the log file) This will create a file named .

2. Compress the file using any of the various compress programs available on Windows (such as WinZip or another third-party package may be used). See applicable operating system documentation.

3. Save the backup file using some type of backup medium (tape, CD, and so forth). See applicable operating system documentation.

3-2.2. Partial Database Backup (using OvPtExport)

Use the following procedure to backup the database point information:

1. Run the OvPtExport program:

OvPtExport -u ptadmin\ptadmin@ptdb -o (where is the user-defined filename for the backup file)

This will create a file named .

2. Compress the file using any of the various compress programs available on Windows (such as WinZip or another third-party package may be used). See applicable operating system documentation.

3. Save the backup file using some type of backup medium (tape, CD, and so forth). See applicable operating system documentation.

1/03 3-3 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C 3-3. Reloading the Database Files

3-3. Reloading the Database Files

3-3.1. Reloading from an Oracle Database Backup

Use the following procedure to reload the complete database (including structure) from the backup created in Section 3-2.1. An example of when this would be necessary include recovery from a catastrophic failure (such as a hard disk failure).

1. If the Software Server functions must be reloaded, refer to “Ovation Software Load Kit” (WIN10). Procedures are dependent on individual systems and cannot all be described in this manual.

2. Enter the following commands to restore the backup:

3. svrmgr30 SVRMGR> connect internal; password: wdpf SVRMGR> shutdown immediate; SVRMGR> startup restrict pfile=D:\orant\database\ptdb\ pfile\initptdb.ora;(this is all one line) SVRMGR> drop user ptadmin cascade; SVRMGR> exit;

imp80 USERID=system/wdpf FILE= FULL=Y LOG= IGNORE=Y (where is the filename of the backup file) (where is the filename of the log file)

4. Reboot the Database Server drop.

5. Using the Ovation Developer Studio, import custom graphic files and Control Builder sheets. See “Ovation Graphics Builder User Guide” (WIN90) and “Ovation Control Builder User Guide” (WIN80) respectively.

WIN15 (Rev 0) 3-4 1/03 Emerson Process Management Proprietary Class 2C 3-3. Reloading the Database Files

3-3.2. Reloading from an Ovation Export File

Use the following procedure to reload the partial database (none of the structure) from the backup created in Section 3-2.2.

1. If the Software Server functions must be reloaded, refer to “Ovation Software Load Kit” (WIN10). Procedures are dependent on individual systems and cannot all be described in this manual.

2. Run the import program:

OvPtImport -u ptadmin\ptadmin@ptdb -f

3. Restore the custom graphic files and Control Builder sheets via the Import function on the Ovation NT Developer Studio. See “Ovation Graphics Builder User Guide” (WIN90) and “Ovation Control Builder User Guide” (WIN80) respectively on how the Import function is used with graphics and control builder sheets.

4. Clear and reload each drop in the system with the Load function. A clear and reload of each drop in the system is required when the -f option is used in the import operation (see Step #2). If the -f option is not used, simply reload each drop.

See “Ovation Developer Studio User Guide” (WIN60) for more information on the Load function.

1/03 3-5 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C

Index

A L API 1-5 Load function (Developer Studio) 1-2, 1-4, 1- 5, 2-4, 3-5 B Backing up Database files 3-2 M complete, using exp80 3-3 Master Database 1-2, 1-5 partial, using OvPtExport 3-3 Business Rules (Ovation) 1-5 N Network Nodes 1-5 C Complete backup of Database 3-3 O Control Builder (relationship to Database) 1-4 Oracle import/export function 1-6, 2-14 Ovation Database D Distributed Database 1-2 Database Initial Definition Tool (DBID) 2-2 Master Database 1-2 See also Import function OvPtExport function 1-5, 2-12, 3-2 db_xmit_client 1-2 partial backup 3-3 db_xmit_server 1-2 restore database 2-13 definition of terms 1-5 OvPtImport function 1-5, 2-3 Developer Studio (relationship to Database) 1- file format (Ovation 1.x) 2-9 4 file format (Ovation 2.x) 2-4 Distributed Database 1-2, 1-5 db_xmit_client 1-2 P db_xmit_server 1-2 Partial backup of Database 3-3 Distributed Database Propagation Software 1- Population of the Database 2-1 5 Database Tools 2-1 DBID 2-2 E exp80 2-14 exp80 (Oracle export) 2-14, 3-2 imp80 2-14 Export function (OvPtExport) 1-5, 2-12 OvPtExport 2-12 restore database 2-13 OvPtImport 2-3 See also Import function R I reference documents 1-8 imp80 (Oracle import) 2-14 Relational Database Management System 1-1 Import file format (Ovation 1.x) 2-9 relationship with other Database functions 1-4 examples 2-10 Reloading Database files 3-4 rules 2-10 from Oracle Database backup 3-4 special considerations 2-11 from Ovation Export file 3-5 terms used 2-9 Restore Database using OvPtExport 2-13 Import file format (Ovation 2.x) 2-4 sample file 2-8 S special considerations 2-11 SQL (Structured Query Language) tools 1-1 Import function (OvPtImport) 1-5, 2-3 System Tree (Developer Studio) 2-5 file format (Ovation 1.x) 2-9 file format (Ovation 2.x) 2-4 W See also Database Initial Definition Tool. Working Area 1-6

1/03 Index-1 WIN15 (Rev 0) Emerson Process Management Proprietary Class 2C