Tungsten
Clustering
Tungsten
Replicator
Tungsten
Dashboard
Contact Us
Get Support
Continuent Documentation
Manual Home
Tungsten Replicator 7.1 Manual
Page in Other Manuals
Tungsten Clustering (for MySQL) 7.1 Manual
Breadcrumbs
>
Tungsten Replicator 7.1 Manual
>
C. Troubleshooting
Chapters
Preface
1. Introduction
2. Deployment Overview
3. Deploying MySQL Extractors
4. Deploying Appliers
5. Deployment: Advanced
6. Deployment: Security
7. Operations Guide
8. Command-line Tools
9. The tpm Deployment Command
10. Tungsten REST API (APIv2)
11. Replication Filters
12. Performance and Tuning
A. Release Notes
B. Prerequisites
C. Troubleshooting
D. Files, Directories, and Environment
E. Terminology Reference
F. Internals
G. Frequently Asked Questions (FAQ)
H. Ecosystem Support
I. Configuration Property Reference
Navigate Up
C. Troubleshooting
Parent Sections
C.1. Contacting Support
C.2. Support Tools
C.3. Error/Cause/Solution
C.4. Known Issues
C.5. Troubleshooting Timeouts
C.6. Troubleshooting Backups
C.7. Running Out of Diskspace
C.8. Troubleshooting SSH and tpm
C.9. Troubleshooting Data Differences
C.10. Comparing Table Data
C.11. Troubleshooting Memory Usage
C.3. Error/Cause/Solution
Prev
^Up
Appendix C. Troubleshooting
Next
C.3. Error/Cause/Solution
C.3.1.
MySQLExtractException: unknown data type 0
C.3.2.
Services requires a reset
C.3.3.
OptimizeUpdatesFilter cannot filter, because column and key count is different. Make sure that it is defined before filters which remove keys (eg. PrimaryKeyFilter)
C.3.4.
Unable to update the configuration of an installed directory
C.3.5.
Too many open processes or files
C.3.6.
There were issues configuring the sandbox MySQL server
C.3.7.
Unexpected failure while extracting event
C.3.8.
Attempt to write new log record with equal or lower fragno: seqno=3 previous stored fragno=32767 attempted new fragno=-32768
C.3.9.
The session variable SQL_MODE when set to include ALLOW_INVALID_DATES does not apply statements correctly on the Replica.
C.3.10.
Replicator runs out of memory