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

When you open the database, you can start to mount status, to open Times 03113 error, there are too many archived logs, resulting in insufficient space, just increase the archived log space.

Solution:

Enter the path and view the alert_oracle.log. You can see that the file record error is as follows:

# error message and suggested solution #

Errors in file / u01/app/oracle/diag/rdbms/orcl11g/orcl11g/trace/alert_orcl11g.log:-locate the error and view the trc file specifically

ORA-19815: warning: db_recovery_file_dest_size bytes (a total of 4102029312 bytes) have been used by 100.00%, and there are still 0 bytes available.

*

You have following choices to free up space from recovery area:

1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard

Then consider changing RMAN ARCHIVELOG DELETION POLICY.

2. Back up files to tertiary device such as tape using RMAN

BACKUP RECOVERY AREA command.

3. Add disk space and increase db_recovery_file_dest_size parameter to

Reflect the new space.

4. Delete unnecessary files using RMAN DELETE command. If an operating

System command was used to delete files, then use RMAN CROSSCHECK and

DELETE EXPIRED commands.

Sys@ORCL > show parameter db_recovery_file_dest;-View

Select * from flashworthy recovery area usage;-View the utilization of the flashback recovery area

--

Through the command window:

-set the size of the archive log space

01.sqlplus / as sysdba

02.shutdown abort-close the process

03.startup mount-load the database

04.select * from vault recovery fileholders destinations;-query archive logs

05.alter system set db_recovery_file_dest_size=10737418240;-set the archive log space to 10G

06.Exit-the space size has been set up here

-

-Delete archive log

[sql] view plaincopy

01.rmantarget /-enter the rman tool window

02.RMAN > crosscheckarchivelog all;-- run this command to mark the archivelog of the invalid expired.

03.RMAN > deletenoprompt archivelog until time "sysdate-3";-delete archived logs from 3 days ago

04.

At this point, you will be thoroughly ok. Next, reopen the database: normal use.

One thing to note in deleting archived files is that the command window shows that the archived files are all under E:\ app\ kang\ flash_recovery_area\ oracle\ ARCHIVELOG, but we cannot delete these files directly in the operating system by hand, because the relevant information about each archivelog is recorded in controlfile, and when we delete these files in OS, we still record these archivelog information in our controlfile. Therefore, these logs will also exist in the OEM manager of Oracle. Because when we manually erase the files in the archive directory, these records are not erased from the controlfile, that is, oracle does not know that these files no longer exist. So you still have to execute the command to delete these files through the command window.

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.