TimesTen TT16225 Errors in an Active/Standby Configuration
(Doc ID 763438.1)
Last updated on APRIL 14, 2022
Applies to:
Oracle TimesTen In-Memory Database - Version 6.0.0 to 7.0.5.0.0 [Release 6.0 to 7.0]Information in this document applies to any platform.
This docNote applies to a problem which could develop in any TimesTen Active/Standby replication configuration.
Add *** ***
***Checked for relevance on 29-02-2012***
Symptoms
- Transaction commit performance in the active/standby pair declines significantly
- The ttmesg.log and tterror.log files show repeated error messages similar to the following:
Changes
The problem is triggered when user makes some kind of DDL or change to the replication configuration itself is made in the active DSN without duplicating that change to the standby DSN. Reversing the change; deleting the newly defined object or resetting the original replication configuration does not solve the problem: once the change has been introduced it cannot be rolled back.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |