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.