DM backup job reported pipe connection failure error problem

We often encounter this error when we back up the database regularly during the Dameng database job:

[description] when a backup job chooses to back up the database based on the backup set, there is a high probability that it will encounter a backup job failure report pipe connection failure error.

How can we solve this kind of problem?

There are two ways.

If the dmap service exists, restart the AP service and still report connection failure. Delete the relevant files in the bin directory and restart again.

2 check for the existence of the ap service and restart the ap service.

Treatment method

Treatment method 1:

Summary description

Use the ps-ef | grep dmap command to check whether the ap service exists. If not, go to the DM server viewer to start the service, and the startup service still reports a connection failure error. Delete the relevant files in the bin directory, and then restart the service to regenerate the two files.

Additional details: this operation is not a database factor, abnormal shutdown of the server (power loss, storage loss, etc.).

Treatment method 2:

Summary description

At present, this problem has only been encountered in a pure domestic environment, which is a probabilistic problem.

Using one of the troubleshooting methods, it is found that the AP service exists, the restart of the AP service does not report an error and the backup job returns to normal.

Additional details: to avoid this probabilistic problem without being discovered, using timing scripts to restart ap services at intervals is the best way, which is difficult to reproduce.

The script is as follows:

Restart at 06:30 every week

[root@localhost~] crontab-e

30 6 * * 0 / tydata/dmdbms/bin/DmAPService restart

The time can be determined according to the individual situation, the above is for reference only.