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

The test pilot data validates another problem, but it stays stuck when it is suddenly imported. Then I looked at the log and found that a large number of archive logs were generated during the impdp import process, and the storage space for the archive was full, so it got stuck.

Tail / u01/app/oracle/diag/rdbms/zhanky/zhanky/trace/alert_zhanky.log (the main error is as follows)

[root@source ~] # tail / u01/app/oracle/diag/rdbms/zhanky/zhanky/trace/alert_zhanky.log.... * ARC3: Error 19809 Creating archive log file to'/ u01/app / oracle/fast_recovery_area/ZHANKY/archivelog/2019_05_07/o1_mf_1_100_%u_.arc'Errors in file / u01/app/oracle/diag/rdbms/zhanky/zhanky/trace/zhanky_arc0_2423.trc:ORA-19815: WARNING: db_recovery_file_dest_size of 4385144832 bytes is 100.00% used And has 0 remaining 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.****...

Because it is a test environment, archiving is only enabled and nothing else is set, so the default storage location is db_recovery_file_dest_size, which is also 4G by default.

In fact, the solution is also simple, but remember that I haven't written a blog for a long time, so record it. The main archive is full, which can be solved by setting the size of the limit or deleting the archive log. But because I don't have much test space here, I use the second method to delete the archive log.

First open a new terminal, rman target / run the following command.

[oracle@source] $rman target / Recovery Manager: Release 11.2.0.4.0-Production on Tue May 7 20:48:26 2019Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.connected to target database: ZHANKY (DBID=2622149390) RMAN > RMAN > delete archivelog all; released channel: ORA_DISK_1allocated channel: ORA_DISK_1channel ORA_DISK_1: SID=1163 device type=DISKList of Archived Log Copies for database with db_unique_name ZHANKY====Key Thrd Seq S Low Time-97 1 100 A 07 Mayfair 19. Name: / u01/app/oracle/fast_recovery_area/ZHANKY/archivelog/2019_05_07/o1_mf_1_100_gf3079ns_.arc140 1 144A 07-MAY-19 Name: / u01/app/oracle/fast_recovery_area/ZHANKY/archivelog/2019_05_07/o1_mf_1_144_gf30osyo_.arcDo you really want to delete the above objects (enter YES or NO)? Yesdeleted archived logarchived log file name=/u01/app/oracle/fast_recovery_area/ZHANKY/archivelog/2019_05_07/o1_mf_1_100_gf3079ns_.arc RECID=97 STAMP=1007672299deleted archived log....archived log file name=/u01/app/oracle/fast_recovery_area/ZHANKY/archivelog/2019_05_07/o1_mf_1_144_gf30osyo_.arc RECID=140 STAMP=1007672763Deleted 45 objectsRMAN > exit

After driving, it will return to normal.

[root@source] # tail / u01/app/oracle/diag/rdbms/zhanky/zhanky/trace/alert_zhanky.log Archived Log entry 139 added for thread 1 sequence 143 ID 0x9c4b270e dest 1:Thread 1 advanced to log sequence 145 (LGWR switch) Current log# 1 seq# 145 mem# 0: / u01/app/oracle/oradata/zhanky/redo01.logTue May 07 21:06:03 2019Archived Log entry 140 added for thread 1 sequence 14414 ID 0x9c4b270e dest 1:Tue May 07 21:06:12 2019Thread 1 advanced to log sequence 146i (LGWR switch) Current log# 2 seq# 146mem# 0: / u01/app/oracle/oradata/zhanky/redo02.logTue May 07 21:06:13 2019Archived Log entry 141 added for thread 1 sequence 145 ID 0x9c4b270e dest 1:

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.