How to solve the error caused by IQ migrating object

This article mainly explains how to solve the error caused by IQ migration object. The explanation in the article is simple and clear, easy to learn and understand. Please follow the editor's train of thought to study and learn how to solve the error caused by IQ migration object.

9. The second node has down dropped, so we delete the transaction log log file and run the following statement to synchronize catalog db from the coordinator node.

Dbbackup-y-d-c "uid=dba;pwd=sql;links=tcpip {10.x.2.2 cross portals 10000}; eng=iqdm_s01" / data01/iqdm

Set the log path:

Dblog-r-t iqdm.log iqdm.db

10. The coordinator node looks at the cluster status, and sp_iqmpxinfo checks to see if the node is in included or excluded status. If it is included, then you can directly open these nodes (start_iq). If the node state is excluded, then the state needs to be modified at the orchestrating node.

Alter multiplex server iqdm_s02 status included

Check the coordinator node to see if sp_iqmpxinfo has been joined, and if the status is included, run the following statement to synchronize catalog db from the coordinator node.

Dbbackup-y-d-c "uid=dba;pwd=sql;links=tcpip {10.x.2.2 cross portals 10000}; eng=iqdm_s01" / data01/iqdm

Mv iqdm.log iqdm.log.bak

Dblog-r-t iqdm.log iqdm.db

Start_iq is on.

11. Finally, open other nodes in the same way.

Thank you for reading, the above is the content of "how to solve the error caused by IQ migration object". After the study of this article, I believe you have a deeper understanding of how to solve this problem caused by IQ migration object. The specific use of the situation also needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!