C.3.2. Services requires a reset

C.3.2. Services requires a reset
Prev	^Up	C.3. Error/Cause/Solution	Next

C.3.2. Services requires a reset

Last Updated: 2016-05-18

Condition or Error

The replicator service needs to be reset, for example if your MySQL service has been reconfigured, or when resetting a data warehouse or batch loading service after a significant change to the configuration.

Causes

If the replicator stops replicating effectively, or the configuration and/or schema of a source or target in a datawarehouse loading solution has changed significantly. This will reset the service, starting extraction from the current point, and the target/Replica from the new Primary position. It will also reset all the positions for reading and writing.

Rectifications

To reset a service entirely, without having to perform a re-installation, you should follow these steps. This will reset both the THL, source database binary log reading position and the target THL and starting point.
1. Take the Replica offline:
```
Replica-shell> trepctl offline
```
2. Take the Primary offline:
```
Replica-shell> trepctl offline
```
3. Use trepctl to reset the service on the Primary and Replica. You must use the service name explicitly on the command-line:
```
Primary-shell> trepctl -service alpha reset -y
Replica-shell> trepctl -service alpha reset -y
```
4. Put the Replica online:
```
Replica-shell> trepctl offline
```
5. Put the Primary online:
```
Replica-shell> trepctl offline
```

Prev	Up	Next
C.3.1. MySQLExtractException: unknown data type 0	^Level	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)

Continuent Documentation

C.3.2. Services requires a reset