Post in waiting state due to "Error: 12035 - OCISessionBegin failed with ORA-257" (58427)

The Post process is in waiting state and no transactions are applied when show post detail is issued while the status shows that it is running:

Host : hostname
Source : o.SID Queue : queue_name

Operations
Target Status Posted Since Total Backlog
---------- --------------- ---------- ------------------ ---------- ----------
o.SID1 Running 0 27-Oct-09 18:54:30 0 0

Last operation posted:
Redo log: 0 Log offset: 0
INTERNAL OPERATION

Post state : Waiting
Activation Id : 0
Current transaction Id : 0
ID of blocking transaction : 0
Number of open transactions : 0
Number of messages read released : 9147874

Number of threads : 0

The following errors are observed in event_log:

10/27/09 18:54 Logging user command: oracle start post queue queue_name
10/27/09 18:54 Process launched: sp_opst_mt (for o.SID-o.SID1 queue queue_name) [pid = 553136]
[1] 10/27/09 18:54 Notice: Oracle env - assa:/oracle/app/oracle/10.2.0 [sp_opst_mt(pdb)/553136]
[1] 10/27/09 18:54 Error: 12035 - OCISessionBegin failed with ORA-257. [sp_opst_mt(osp)/553136]
[1] 10/27/09 18:54 Error: 12035 - OCISessionBegin failed with ORA-257. [sp_opst_mt(osp)/553136]
[1] 10/27/09 18:54 Notice: Waiting for oracle to become available [sp_opst_mt (for o.SID-o.SID1 queue queue_name)/553136]

The file system housing the LOG_ARCHIVE_DEST directory is full.

More space needs to be added to the device housing the archive logs and then the Post needs to be restarted. This problem can also trigger another space problem when the Post queue gets backlogged as no transactions are applied to the target database, as this results in post queue files retained for a longer period in the rim directory.

The following is the description of ORA-257:

Error:ORA-257: archiver is stuck. CONNECT INTERNAL only, until freed
Cause:While trying to archive a redo log file, the ARCH process encountered an error.
Action:The options to resolve this Oracle error are:
1.This error can be caused when the destination device does not have enough storage space to store the redo log file.
2.Check that the initialization parameter ARCHIVE_LOG_DEST in the initialization file is set correctly.
It may be helpful to check the archiver trace file for more details on the problem.
Note: If this problem is not resolved, Oracle will stop executing transactions.