Transaction Configuration Center - AFP Calibration - Load AFP calibration results - Error - TCC is establishing a connection with the wrong server
Description
This page is for providing you with an explanation of why TCC is establishing a connection with the wrong server, and will give you the steps to fix this:
Observed in CAST AIP
| Release | Yes/No |
|---|---|
| 8.3.x | ✅ |
Observed on RDBMS
| RDBMS | Yes/No |
|---|---|
| CSS | ✅ |
Step by Step Scenario
Below is the step-by-step scenario leading to the problem
- Back up the triplet from one server.
- Restore the triplet on a second server.
- Created a connection profile pointing to the second server.
- Open TCC.
- Click on TCC results.
Impact of the Problem
The impact of the problem on the analysis or the dashboard is: Results of TCC are from the wrong db’s
Action Plan
The reason why TCC is establishing a connection with the wrong server from where you restored the schemas to the local system is because, the new host is not updated in schema and the triplets are not connected to each other on the new host.
To fix the problem,
- Refer to the following page Tools - How to synchronize CAST databases triplet
Impact of the Solution
The impact of the problem on the analysis or the dashboard is: Results of TCC are from the wrong db’s
Notes/comments
Ticket # 5946
Related Pages