Table of Contents
- Title and Copyright Information
- About This Content
- 1 Overview of TimesTen Replication
- 2 Getting Started
-
3
Defining an Active Standby Pair Replication Scheme
- Overview of Master Database States
- Restrictions on Active Standby Pairs
- Defining the DSNs for the Databases
- Table Requirements for Active Standby Pairs
- Defining an Active Standby Pair Replication Scheme
- Identifying the Databases in the Active Standby Pair
- Using a Return Service for an Active Standby Pair
- Setting STORE Attributes for an Active Standby Pair
- Configuring Network Operations for an Active Standby Pair
- Using Automatic Client Failover for an Active Standby Pair
- Including or Excluding Database Objects From Replication
- Replicating Tables With Foreign Key Relationships in an Active Standby Pair
- Replicating Cache Groups in an Active Standby Pair
- Materialized Views in an Active Standby Pair
- Replicating Sequences in an Active Standby Pair
- Duplicating a Database
-
4
Defining Attributes and Options for a Replication Scheme
- Connection Attributes for Replicated Databases
- Configuring Parallel Replication
- Managing the Transaction Log on a Replicated Database
-
Using a Return Service
- RETURN RECEIPT
- RETURN RECEIPT BY REQUEST
- RETURN TWOSAFE
- RETURN TWOSAFE BY REQUEST
- NO RETURN
- Specifying a Different Return Service for Each Subscriber in a Classic Replication Scheme
- Setting the Return Service Timeout Period
- Disabling Return Service Blocking Manually
- Establishing Return Service Failure and Recovery Policies
- Setting STORE Attributes
- Configuring the Network
-
5
Administering an Active Standby Pair Without
Cache Groups
- Setting Up an Active Standby Pair With No Cache Groups
- Recovering From a Failure of the Active Database
- Recovering From a Failure of the Standby Database
- Recovering After a Dual Failure of Both Active and Standby Databases
- Recovering From the Failure of a Subscriber Database
- Reversing the Roles of the Active and Standby Databases
- Detection of Dual Active Databases
-
6
Administering an Active Standby Pair With
Cache Groups
- Replicating Cache Groups Within Active Standby Pairs
- Changing User Names or Passwords Used by Replication
- Recovering From a Failure of the Active Database
- Recovering From a Failure of the Standby Database
- Recovering After a Dual Failure of Both Active and Standby Databases
- Recovering From the Failure of a Subscriber Database
- Reversing the Roles of the Active and Standby Databases
- Detecting Dual Active Databases
- Using a Disaster Recovery Subscriber in an Active Standby Pair
-
7
Altering an Active Standby Pair
-
Making DDL Changes in an Active Standby
Pair
- Controlling Replication of Objects to All Databases in an Active Standby Pair
- DDL Statements That Can Be Automatically Replicated
- Creating a New PL/SQL Object in an Existing Active Standby Pair
- Restrictions on Making DDL Changes in an Active Standby Pair
- Examples Showing How to Making DDL changes in an Active Standby Pair
- Making Other Changes to an Active Standby Pair
-
Making DDL Changes in an Active Standby
Pair
-
8
Using Oracle Clusterware to Manage Active Standby Pairs
- Overview of How Oracle Clusterware Can Manage TimesTen
- Requirements, Considerations, and Installation for Your Cluster
- Restricted Commands and SQL Statements
-
Creating and Initializing a Cluster
- Start the TimesTen Cluster Agent
- Create and Populate a TimesTen Database on One Host
- Create System DSN Files on Other Hosts
- Create a cluster.oracle.ini File
- Create the Oracle Clusterware Resources to Manage Virtual IP Addresses
- Create an Active Standby Pair Replication Scheme
- Start the Active Standby Pair and the Applications
- Load Cache Groups
- Include More Than One Active Standby Pair in a Cluster
- Configure an Oracle Database as a Disaster Recovery Subscriber
- Configure a Read-Only Subscriber That Is Not Managed by Oracle Clusterware
- Configuring Oracle Clusterware Management With the cluster.oracle.ini File
- Monitoring Cluster Status
- Shutting Down a Cluster
-
Recovering From Failures
- How TimesTen Performs Recovery When Oracle Clusterware is Configured
- When an Active Database or Its Host Fails
- When a Standby Database or Its Host Fails
- When Read-Only Subscribers or Their Hosts Fail
- When Failures Occur on Both Master Nodes
- When More Than Two Master Hosts Fail
- Perform a Forced Switchover After Failure of the Active Database or Host
-
Clusterware Management
- Changing User Names or Passwords When Using Oracle Clusterware
- Managing Hosts in the Cluster
- Managing Active Standby Pairs in a Cluster
- Managing Read-Only Subscribers in the Active Standby Pair
- Reversing the Roles of the Master Databases
- Modifying Connection Attribute Values
- Managing the TimesTen Database RAM Policy
- Changing the Schema
- Making Schema Changes to Cache Groups
- Moving a Database to a Different Host
- Performing a Rolling Upgrade of Oracle Clusterware Software
- Upgrading TimesTen when Using Oracle Clusterware
- Performing Host or Network Maintenance
-
9
Defining Classic Replication Schemes
- Designing a Highly Available System
- Defining a Classic Replication Scheme
- Restrictions and Table Requirements for Classic Replication Schemes
- Establishing the Databases
- Duplicating a Master Database to a Subscriber
- Restrictions for Classic Replication Schemes Involving Multiple Masters
- Defining Replication Elements
- Checking for Replication Conflicts on Table Elements
- Setting Transmit Durability on DATASTORE Element
- Using a Return Service in a Classic Replication Scheme
- Setting STORE Attributes in a Classic Replication Scheme
- Configuring Network Operations for a Classic Replication Scheme
- Classic Replication Scheme Syntax Examples
- Applying a Classic Replication Scheme to a Database
- Creating Classic Replication Schemes With Scripts
-
10
Altering a Classic Replication Scheme
-
Altering a Classic Replication Scheme
- Adding a Table or Sequence to an Existing Classic Replication Scheme
- Adding a PL/SQL Object to an Existing Classic Replication Scheme
- Adding a DATASTORE Element to an Existing Classic Replication Scheme
- Dropping a Table or Sequence From a Classic Replication Scheme
- Creating and Adding a Subscriber Database to a Classic Replication Scheme
- Dropping a Subscriber Database From a Classic Replication Scheme
- Changing a TABLE or SEQUENCE Element Name in a Classic Replication Scheme
- Replacing a Master Database in a Classic Replication Scheme
- Eliminating Conflict Detection in a Classic Replication Scheme
- Eliminating the Return Receipt Service in a Classic Replication Scheme
- Changing the Port Number for a Classic Replication Scheme
- Changing the Replication Route
- Changing the Log Failure Threshold
- Altering a Replicated Table in a Classic Replication Scheme
- Truncating a Replicated Table in a Classic Replication Scheme
- Dropping a Classic Replication Scheme
-
Altering a Classic Replication Scheme
-
11
Managing Replication
- Show State of Replication Agents
- Replication of Statistics
- Set the Replication State of Subscribers
- Show Master Database Information
- Show Subscriber Database Information
- Show the Configuration of Replicated Databases
- Show Replicated Log Records
- Use ttRepAdmin to Show Replication Status
- Check the Status of Return Service Transactions
- Analyze Outstanding Transactions in the Replication Log
- 12 Resolving Replication Conflicts
- 13 Improving Replication Performance
- 14 Managing Database Failover and Recovery
- A TimesTen Configuration Attributes for Oracle Clusterware