Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "how to solve the errors caused by IQ migrating object". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Keywords

"sp_mpxprocesstlvlog exception", "cannot maintain catalog sync"

Because the file of 1T Size is restored to the new host, the raw device of each LUN on the new host is 1.5T, resulting in the unreasonable use of 500g of space. We use to add a 1.5T RAW DEVICE, and then put the original file

Read only, then transfer the data to the new raw device through sp_iqemptyfile, and finally delete the previous file. However, when there is a problem in deleting the file, all the nodes outside the coordination node are down down.

1. Create a new dbspace file.

Alter dbspace msgdw add file msgdw_16399'/ data01/iqdm/data/iq_msgdw_11.iq'

two。 Set the dbspace file of the original exception to read-only

Alter dbspace msgdw alter file msgdw_16391 readonly

3.sp_iqfile msgdw to see if the file becomes RO, and if so, commit immediately

Then run sp_iqfile msgdw again, and if the file status is still RO, make sure that the file is indeed RO.

4.sp_iqemptyfile migrates the original write exception objects to a read / write dbspace file, and then clears it.

Sp_iqemptyfile msgdw_16391

5. Check to see if the file set to readonly can be drop.

Sp_iqfile msgdw

-this should show that OkToDrop column for the problem dbfile msgdw_16391 should change from N to Y

If the status is Y, COMMIT immediately, check the sp_iqfile msgdw again, and if you confirm OkToDrop=Y, you can take the next step.

6. Delete the read-only dbspace file.

Alter dbspace msgdw drop file msgdw_16391

7. The deletion succeeded, but it was found that all the nodes other than the orchestration node were down. Look at the iqmsg log and find the following statement:

Sp_mpxprocesstlvlog exception, SQLSTATE=QSA44 [An IO error was encountered while reading a

Database page in INVALID_DBSPACE DBSpace.

Many of these cases are found in the SAP Support query:

2491497-Random secondary node crash with "Secondary server cannot maintain catalog sync" error

2147434-DROP and CREATE USER causes "Secondary server cannot maintain catalog sync."

This is the end of the content of "how to solve the errors caused by IQ migrating object". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.