There is another problem in the test data verification, but the card owner is still in the process of importing. Then I look at the logs and find that a large number of archive logs are generated during the import of impdp, so the storage and archive space is full, so it gets stuck
Tail / u01 / APP / Oracle / diag / RDBMS / zhanky / zhanky / trace / Alert [zhanky.log (the main errors are 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's a test environment, it just turns on archiving and nothing else is set. Therefore, by default, the storage location is loaded in DB? Recovery? File? Dest? Size, which is 4G by default.
In fact, the solution is simple, just remember that I haven't written a blog for a long time, so record it. The main archive is full. We can set the limit size or delete the archive log. But because there is not much testing space in my side, I use the second method to delete the archived logs.
Open a new terminal first, run the following command from rman target /.
[oracle@source ~]$ rman target / Recovery Manager: Release 11.2.0.4.0 - Production on Tue May 7 20:48:26 2019 Copyright (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_1 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=1163 device type=DISK List of Archived Log Copies for database with db_unique_name ZHANKY ===================================================================== Key Thrd Seq S Low Time ------- ---- ------- - --------- 97 1 100 A 07-MAY-19 . . . . Name: /u01/app/oracle/fast_recovery_area/ZHANKY/archivelog/2019_05_07/o1_mf_1_100_gf3079ns_.arc 140 1 144 A 07-MAY-19 Name: /u01/app/oracle/fast_recovery_area/ZHANKY/archivelog/2019_05_07/o1_mf_1_144_gf30osyo_.arc Do you really want to delete the above objects (enter YES or NO)? yes deleted archived log archived log file name=/u01/app/oracle/fast_recovery_area/ZHANKY/archivelog/2019_05_07/o1_mf_1_100_gf3079ns_.arc RECID=97 STAMP=1007672299 deleted 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=1007672763 Deleted 45 objects RMAN> exit
It's back 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.log Tue May 07 21:06:03 2019 Archived Log entry 140 added for thread 1 sequence 144 ID 0x9c4b270e dest 1: Tue May 07 21:06:12 2019 Thread 1 advanced to log sequence 146 (LGWR switch) Current log# 2 seq# 146 mem# 0: /u01/app/oracle/oradata/zhanky/redo02.log Tue May 07 21:06:13 2019 Archived Log entry 141 added for thread 1 sequence 145 ID 0x9c4b270e dest 1: