Summary of the content on the page No. 1
NN10031-111
Succession Multimedia Communications Portfolio
MCP Database Module
Basics
Standard MCP 1.1 FP1 (02.02) April 2003
Summary of the content on the page No. 2
Summary of the content on the page No. 3
Nortel Networks Confidential 3 Overview The Database Module uses the Oracle Enterprise Manager to configure, administer, and monitor provisioned subscriber and configuration data. How this guide is organized This document provides an overview of Database Module architecture, including data replication and data transfer concepts. The following principal tasks performed with the Database Module are also documented. • Configuring the Oracle Enterprise Manger to perform backups, observer acc
Summary of the content on the page No. 4
4 Overview Nortel Networks Confidential Architecture As shown in Figure 1, the Database Module consists of Oracle Servers having a primary database and a replicated secondary database managed from the Oracle Enterprise Manager (OEM) Console. The Oracle databases operate in replicated mode and applications and components normally send and receive data directly to and from the primary database. Monitoring logs, alarms, and operational measurements, OEM login, and maintenance updates are
Summary of the content on the page No. 5
Nortel Networks Confidential Overview 5 For information about the communication protocols and interactions between the Database Module and network components, see Figure 2, “SQL over JDBC,” on page 11. Each database includes replicated objects and non-replicated objects. Tables are the only objects that are replicated. Non-replicated objects include stored procedures, functions, and views. Minimal, redundant, and variable server configurations are supported in enterprise deployments. Re
Summary of the content on the page No. 6
6 Overview Nortel Networks Confidential while the secondary database operates in a limited write state at all times. Table 1 Database operational states Database states Description Normal Fully writable for applications. Inserts, (Primary database) updates, or deletions are permitted to the primary database. The Oracle Server continuously transfers changed data to the secondary database. Limited write Read only for applications with the (Secondary exception of registrations (inserts, u
Summary of the content on the page No. 7
Nortel Networks Confidential Overview 7 Data transfer When data transactions occur, updates to the primary database are queued for transfer to the secondary database. Similarly, changes made to the secondary database are queued for transfer to the primary database. See “Database failover” on page 19. The data transfer process between the primary and secondary databases is managed by push and purge jobs, described as follows: Push jobs: When push jobs execute, they reassign all transactio
Summary of the content on the page No. 8
8 Overview Nortel Networks Confidential Database recovery Recovery restores a database to its original state after a failure. See “Database recovery” on page 84. Manage replication transaction errors The OEM Console provides tools for resolving replication errors, should they occur. Replication errors can result from a lack of available space in a table targeted for an update or other unresolved replication conflicts. For additional information, see “Resolving replication errors” on pag
Summary of the content on the page No. 9
Nortel Networks Confidential Overview 9 Events: Database events are processed by the Oracle Enterprise Manager and alerts are generated when specified error thresholds are reached. Monitor events as required and respond to alerts as appropriate. See “Event monitoring” on page 23. Alert logs and trace files: When an Oracle process detects an internal error, it dumps information about the error into a trace file. Each Database Module also has an alert file. The alert file is a chronolog
Summary of the content on the page No. 10
10 Overview Nortel Networks Confidential MCP hardware The Database Module is deployed on a pair of Sun Netra t1400/1405s servers configured in an Oracle master-master replication mode for redundancy. Hardware Details Primary and Secondary Sun Netra t 1400 or Sun Netra t 1405 Database servers with the following hardware features: - 4 440 Mhz CPUs - 4 GB RAM - 4 36.4-GB hard disks - 10x Internal DVD-ROM drive - 20-GB 4mm DDS-4 Internal tape drive - 1 Quad Fast Ethernet (QFE) PCI card - 1400
Summary of the content on the page No. 11
Nortel Networks Confidential Overview 11 Network interfaces and protocols User interfaces which access the Database Module are: SQL over JDBC: The Database Module communicates with network components using Structured Query Language (SQL) over Java Database Connection (JDBC). See Figure 2, “SQL over JDBC,” on page 11 and Figure 1, “Database Module architecture normal operation,” on page 4. As shown in Figure 2, all communication between applications and the Database is by SQL over JDBC
Summary of the content on the page No. 12
12 Overview Nortel Networks Confidential the System Management Console. The OracleMonitor extracts (using SNMP gets and SQL queries) information concerning the health of the database. This information is then transformed into alarms/logs/OMs, allowing the data to be viewed from the System Management Console Alarm/Log/OM browsers. OAM&P strategy Offline data migration between releases and maintenance updates are supported. See “Upgrades” on page 13. Database backup, recovery, and resynch
Summary of the content on the page No. 13
Nortel Networks Confidential 13 Upgrades Strategy The following deployment tasks related to the Database Module are performed by your next level of support: Adds and configures the server(s) hosting the Database Module Installs Oracle Deploys the Database Module software onto the server(s) Offline migration Off-line migration of data between releases enables upgrading the Database Module from one release to the next without loss of data. Once the Database Module is upgraded to a new re
Summary of the content on the page No. 14
14 Upgrades Nortel Networks Confidential Tools and utilities Database Module maintenance updates are deployed from the System Management Console. For details, see MCP System Management Console Basics. Database Module updates Database Module maintenance updates include database schema files, stored procedures, and backup and recovery scripts. Full upgrades are done by your next level of support. Maintenance updates can be done as explained in the following procedure. Updating a Database
Summary of the content on the page No. 15
Nortel Networks Confidential Upgrades 15 Reverting to a previous version of the database If you want to revert to a previous version of the database, you must redeploy a previous version of the database over the current database. In such a scenario, the user is first prompted to confirm that they want to revert to a previous version of the database. The user is then warned that doing so removes data gathered since the previous update. An older version of the database is then restored. See
Summary of the content on the page No. 16
16 Upgrades Nortel Networks Confidential NN10031-111 Standard MCP 1.1 FP1 (02.02) April 2003 Copyright © 2003, Nortel Networks
Summary of the content on the page No. 17
Nortel Networks Confidential 17 Fault management Strategy Database Module fault management consists of monitoring and responding to logs and alarms from the Oracle Enterprise Manager (OEM) Console and the System Management Console. See MCP System Management Console Basics. The Database Module is built on an Oracle database and provides high availability using Oracle Replication to a secondary database on a separate server. As updates are applied to the primary database, they are transferre
Summary of the content on the page No. 18
18 Fault management Nortel Networks Confidential Task flows Table 3 outlines Database Module performance management tasks. Table 3 Performance management task flows Topic Subtopic Procedure Database Backups “Monitoring backups” monitoring on page 20 Events “Monitoring events” on page 24 Replication “Monitoring replication” on page 28 “Monitoring registration deletions” on page 31 Alert logs and trace “Monitoring alert logs files and trace files” on page 35 Disk usage “Monitoring disk
Summary of the content on the page No. 19
Nortel Networks Confidential Fault management 19 Tools and utilities Use the following tools to perform Database Module fault monitoring tasks: Oracle Enterprise Manager (OEM) Console: Used by the database administrator for backup and recovery and database fault management. For details, see “Security and Administration” on page 69. System Management Console: Launches the OEM Console and Oracle Monitoring Application. Provides log and alarm information. For details, see MCP System Mana
Summary of the content on the page No. 20
20 Fault management Nortel Networks Confidential Database monitoring from the Oracle Enterprise Manager Console To launch the OEM Console, see “Logging in to the OEM Console” on page 45. Monitoring backups When a database backup starts, an email is sent to the administrator. Another email is sent when the job completes. The status of completion of the job is included in that email. In addition to email notification, the administrator can view the output log of the backup job, as explain
