Ora-00257:archiver error. Connect internal only, until freed.

Error
Environment: winxp+oracle9.2.0.1 Client
win2003+oracle9.2.0.5 Service Side
First, the error process:
Execute the following statement on the client:
Conn SCOTT/TIGER@PGJT
Declare
I number;
Begin
Select S.nextval into I-dual;
While i<1000
Loop
Insert into B values (i);
End Loop;
End
An error occurred, the client is a fake panic phenomenon.
Open a new window:
Sql> Conn SCOTT/TIGER@PGJT
is connected.
Sql> select Sid,serial#,username from V$session;

SID serial# USERNAME
--------- --------- ------------------------------
1 1
2 1
3 1
4 1
5 1
6 1
7 1
8 1
9 1
10 1
11 1
12 14
5 SCOTT
SCOTT
15 4
16 1
17 1
18 1
19 1
4 Nccwgs

20 rows have been selected.

Time used: 00:00:00.01
Sql> alter system kill session ' 13,5 ';

The system has changed.

Time used: 00:00:00.00
Sql>

Repeat the above steps about 3 times,
Sql> Conn SCOTT/TIGER@PGJT
ERROR:
Ora-00257:archiver error. Connect internal only, until freed.

Unable to connect to the database.

Second, Problem Description-------------------

The database is running in Archive log mode and automatic archiving turned on.  When the archive log destination diskspace becomes full automatic archiving'll stop.  This is expected to happen. At the "point a" should appear on the screen:oracle Instance v816-can not allocate log, archival required whe  n All of the online redo logs are filled up, the database would be on a hang state.  After freeing up diskspace the online redo logs are still not archiving. In most cases it is the correct behaviour.

If you are attempt to manually archive the files for you receive the following errors:

Svrmgr> Archive Log Next Ora-16014:log 1 sequence# 199 not archived, no available destinations Ora-00312:online log 1 Thread 1: ' C:oracleoradatav816redo01. LOG '

Svrmgr> Archive log all ora-16020:less destinations available than specified by log_archive_min_succeed_dest

Solution Description--------------------

Some of the possible ways to fix this problem:

1. Use the command:

Alter system archive log all to ' c:oracleoradatav816archive '; *note:you must specify a location ref-ora-16014

2. Shutdown and restart the database. It May is necessary to do a Shutdown abort.

3. Use the REOPEN attribute of the Log_archive_dest_n Init.ora parameter.

Log_archive_dest_n= '
Reopen=30 ' Or run the following comand:

alter system set Log_archive_dest_n = ' Reopen '

4. Use the commands:

Alter system archive log stop; Alter system archive log start;

Explanation-----------

The error ora-16014 is the real clue for this problem.  Once the archive destination becomes full the location also becomes. Normally Oracle does does a recheck to the if space has been made.

1. Using The Command:alter System archive log all to ' c:oracleoradatav816archive ';  Gives Oracle a valid location for the archive logs.  Even after using this archive log destination parameter are still invalid and automatic achive not does.  This solution is the best for systems, does not archive regularly but cannot are shutdown. You can also a Shutdown immediate instead of Shutdown of allow.

2. Shutdown and restart of the database resets the archive log destinstation parameter to be valid. Don't forget to make disk space available before starting the database.

3. Use the REOPEN the "Log_archive_dest_n parameter to determine whether and" ARCn attempts to re-archive  To a failed destination following a error.   REOPEN applies to all errors, not just OPEN errors.  Reopen=n sets the minimum number of seconds before ARCn should try to REOPEN a failed destination.  The default value for n is seconds. A value of 0 is the same as turning out the REOPEN option, in other words, ARCn'll not attempt to archive after a failu  Re.  If you don't specify the REOPEN keyword, ARCn'll never REOPEN a destination following an error. The Server administration Guide has more information on REOPEN.

References----------

[bug:1271752] AUTOMATIC archiving has not resumed after spaces are freed up Server administration Guide:chapter 7

[note:74324.1] Auto Archive stopped-8i log_archive_dest_n Issues.

3, Problem solving
The archive log uses a full disk space. Delete some old disk archives
sql> shutdown abort;
ORACLE instance shut down.
Sql> Startup
ORACLE instance started.

Total System Global area 542712360 bytes
Fixed Size 455208 bytes
Variable Size 427819008 bytes
Database buffers 109051904 bytes
Redo buffers 5386240 bytes
Database mounted.
Database opened.
Sql> Conn Scott/tiger
Connected.
Sql>