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

The main content of this article is to explain "how to solve the problem of DG hanging MRP0 due to insufficient library disk." interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Next let the editor to take you to learn "how to solve DG due to lack of library disk guide MRP0 hang up" bar!

At the customer site, the MRP0 process of the slave database was terminated when the alarm message was received. Log in to the slave database to check that the mrp0 process indeed hung up. Check the alert log and found that the error was caused by the inability to create a table space. After inquiry, the customer learned that the customer added 40G table space in the main database, while the slave database data disk group only had 17G, which caused mrp0 to hang up because it was unable to create a table space of the same size.

How to handle it:

First, the original idea is to delete that tablespace directly in the main database, and see if the standby database can also delete the tablespace, but consider that the standby database has not successfully created the tablespace, let alone synchronously apply the delete tablespace command of the master database, not to mention that the master database is a production library. You can't delete tablespaces at will.

Second, I consulted my colleagues and said that it is possible to create a table space with the same name in the repository, but the size can be changed to a little smaller. (not implemented, possibility to be tested)

Third, create a tablespace of the same size as the main library and place it in a place to store enough disk groups. (the following is the actual operation)

1. Shut down the database, start both in mount, and create a tablespace of the same size as the main database (it should also be OK in open. Later test it).

2. Create tablespaces to other directories (note the parameter standby_file_management)

3. Start the log synchronization application and track down the files

4. Turn off synchronization

5. Open the database

6. Reopen the synchronization application

This question needs to be tested and studied more deeply, and record the question and process briefly for the time before. the experience is that any operation in the future should be checked in advance and considered more comprehensively, even if it is as simple as adding a table space or data file.

At this point, I believe you have a deeper understanding of "how to solve the problem of DG MRP0 hanging due to insufficient library disk". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

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.