Insufficient Oracle archive space causes imp big data to be suspended

The big data mentioned here is relatively speaking. The data size used in the experiment is 4 GB...

First, describe the situation. First, use vmware workstation 9 to create a virtual machine and install CentOS 6. Then, download the online documentation from the Oracle official website. (In fact, the installation times are too many to understand. Installing oracle is nothing more than doing this: 1. A graphic interface is required. 2. The required packages must be fully installed. 3. Change the kernel parameters. 4. Create users and groups. 5. installation directory authorization) oracle has never had the RHEL6 installation documentation before. Now, I have downloaded the latest oracle Database Installation File (even if the old version cannot be detected ). This is the official document: http://www.oracle.com/technetwork/database/enterprise-edition/documentation/index.html

Here, I found a strange problem. After installing all the dependent packages, I checked that many software packages were not installed when installing the oracle software. I confirmed that 100% was installed, however, it is detected that the software package is not installed (the installed software package is newer than the package that it requires to install). However, the document is clearly written, or laster, which clearly supports the updated version...

If you confirm it, no problem occurs. You can directly ignore all and continue the installation. The installation is smooth and no error is reported ~~

The above just said that the installation was a bit depressing, and the installation on RHEL5 was good, which should be an oracle problem. The following is a problem with data import. When I have installed the database, created a tablespace, and started to import data, everything went well before, and then it was stuck in the dark. I thought that the virtual machine was suspended and greeted vmware several times. However, I found that what I did in the virtual machine was very fast, but it was just half done and I died. It cannot survive or survive. If you use ctrl + c to forcibly terminate a VM at this time, an error will be reported when you turn off the VM and start the VM again. This is a classic error. ORA-03113: communication channel file end (error resolved) This link for everyone to see.

It was later known that the session was forcibly terminated before it was over, so this error would occur. It doesn't matter if the session is forced to end. You can also end the session.

Select sid, serial #, status, server from v $ session where username = 'abc'; ---- ABC is the user ~

Oracle uniquely identifies a session through the system Identifier (SID) and Serial Number (SERIAL Number, Serial. Check the active session and end it.

Alter system kill session '7, 15 ';

For example, terminate a session (SID = 7, SERIAL # = 15 ).

If you end the session, there will be no ORA-03113 error.

Later, I found that the problem with the above phenomena was archiving !!

The archived log space is full, so it keeps stuck there! There are two ways to solve this problem: 1. Increase the archive log space (4 GB after installation by default), 2. delete some archive logs.

I. Increase the size of archive log Space

Select * from v $ recovery_file_dest;

Show parameter db_recovery_file_dest

View the archived Log Size and space usage.

Alter system set db_recovery_file_dest_size = 20G;

Ii. Delete archived logs (the following are copied to network articles)

Log on to the database server as an ORACLE user

Go to ORACLE Data Backup Tool

Rman target/

Or rman target/@ orcl

2. Execute in the Command window

Delete archivelog all completed before 'sysdate-7 ';

Description

SYSDATA-7, indicating the current system time 7 days ago, the before keyword indicates the archived log 7 days ago, and if the flash back function is used, the flash back data is also deleted.

In the same way, you can delete all the logs from the past seven days to the present. However, it is recommended that you back up the database immediately after you delete the logs.

Delete archivelog from time 'sysdate-7 ';