Shulou(Shulou.com)06/01 Report--

First, the impact of the problem

If the database archive does not set the archive deletion policy or the archive explosion leads to full archive space, the database will not be able to provide service.

You can't even shut down the database. Because shutting down the database will start to write the log, you cannot write to the day when the space is full.

The log in turn causes the database to fail to start. The business system will not be available.

2. The ways of archiving and storage are as follows:

1. Local file system storage

2. The local file system is stored in the flash zone

3. Store in ASM storage

4. ASM is stored and placed in the flash zone.

III. Handling methods

1. If the archive log is stored in the file system or ASM storage, but not in the fast flash area, you can use the

You need to migrate the archived files in the file system directory or ASM storage to another space, or you can return the

File logs are backed up by RMAN to free up space for archival storage.

2. If it is placed in the flashback area of the file system or ASM storage, the database cannot recognize the files after manual migration

Space release; because the fast flashback area is managed by the Oracle database itself, it needs to be identified by the database

For this phenomenon, see title 4.

Fourth, the solution of filing full in fast flashback area.

If the archive in the flash zone is full, the database will not be able to operate or even close; at this point, the solution

The method is to close an instance in the database through shutdown abort; (shutdown abort

Do not check the consistency of the data file and do not write the data in memory to the data file, just like a forced power outage

So the operation is prudent) (if there is an OGG, you need to shut down the OGG process associated with the host ahead of time, and change the way to OGG.

Process hangs and prevents loss of archives)

After the database is closed, start the database to mount state by startup mount; at this point, you can communicate with the

Check the usage of fast flashback area (mainly based on the current fast production): select * from vastly recoveryfilewise destinations

Capacity size of flashback zone)

If the ASM storage or file system has no capacity to expand, first expand the space for the ASM or file system; then

By alter system set db_recovery_file_dest_size = 100g (expand the previous size by tens of gigabytes, here only

For reference). After expansion, the database will return to normal use.

Log in to RMAN through rman target / method, and perform crosscheck archivelog all; detection database return

Validity of the file

By executing delete noprompt archivelog until time "sysdate-3" in RMAN; (this command indicates that

Delete the archive log, keep it until 3 days ago, and keep it for a few days. According to the business, the number of days is for reference only)

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.