C.2. Error/Cause/Solution

Continuent Documentation

Search:

Manual Home

Tungsten Replicator 5.3 Manual

Page in Other Manuals

Tungsten Clustering (for MySQL) 5.3 Manual

Breadcrumbs

» Tungsten Replicator 5.3 Manual

» C. Troubleshooting

Navigate Up

C. Troubleshooting

Parent Sections

C.1. Contacting Support

C.2. Error/Cause/Solution

C.3. Known Issues

C.4. Troubleshooting Timeouts

C.5. Troubleshooting Backups

C.6. Running Out of Diskspace

C.7. Troubleshooting SSH and tpm

C.8. Troubleshooting Data Differences

C.9. Comparing Table Data

C.10. Troubleshooting Memory Usage

C.2. Error/Cause/Solution
Prev	Appendix C. Troubleshooting	Next

C.2. Error/Cause/Solution

C.2.1. OptimizeUpdatesFilter cannot filter, because column and key count is different. Make sure that it is defined before filters which remove keys (eg. PrimaryKeyFilter)
C.2.2. Replicator runs out of memory
C.2.3. Unable to update the configuration of an installed directory
C.2.4. 'subscription exists' when setting up CDC on Oracle
C.2.5. Too many open processes or files
C.2.6. There were issues configuring the sandbox MySQL server
C.2.7. MySQLExtractException: unknown data type 0
C.2.8. Services requires a reset
C.2.9. ORA-00257: ARCHIVER ERROR. CONNECT INTERNAL ONLY, UNTIL FREED
C.2.10. Attempt to write new log record with equal or lower fragno: seqno=3 previous stored fragno=32767 attempted new fragno=-32768
C.2.11. The session variable SQL_MODE when set to include ALLOW_INVALID_DATES does not apply statements correctly on the slave.

Prev	Up	Next
C.1. Contacting Support	Home	C.2.1. OptimizeUpdatesFilter cannot filter, because column and key count is different. Make sure that it is defined before filters which remove keys (eg. PrimaryKeyFilter)