Filter
Top Products
Overview 7
Copyright © 2003, Nortel Networks MCP Database Module Basics
Nortel Networks Confidential
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 transactions
in the queue to the other master site. Push jobs are scheduled every
30 seconds.
• Purge jobs: When purge jobs execute, they purge or delete all
transactions in the queue that have been transferred to the other
master site. Purge jobs are scheduled every 10 minutes.
Note: The frequency of push and purge jobs is based on optimal
values established during testing.
Oracle Enterprise Manager configuration
Oracle Enterprise Manager (OEM) configuration is done from the OEM
Console. Tasks include OEM Console login, configuring the databases
for backups, configuring the SYSMAN user to receive email
notifications, and configuring OBSERVER accounts. See
“Configuration management” on page 43.
Configuration is performed during installation after the Database
Module has been deployed. See “Application database connection
configuration” on page 57.
Database administration
Database Module administration consists of backup, recovery,
resynchronization, and disk space management. See “Security and
Administration” on page 69.
Database backups
In addition to the redundancy provided by Oracle replication explained
earlier in this chapter, the Database Module supports taking backups
using the OEM Console.
The export backup method is recommended over Recovery Manager
(RMAN) backups.
For details, see “Database backups” on page 71.