ORA-19504, oolong Processing

I was woken up by phone at last night. My colleagues at night shift said that the production line could not be used. Open the computer and use toad to directly connect to the database. view the log, saying that archive log cannot be written. view hard disk space, GB available. Select * from V $ lock, which does not run in one minute. Cancel is dropped. The night shift staff called again, and simply restarted, and did not look for the root cause. As a result, the shutdown immediate command does not respond within two minutes. When waiting for the database to shut down, I checked the hard disk again. Oh, there is only MB left. I didn't wake up just now. I thought it was GB and deleted some archive logs, the database was shut down very quickly, and then started up again.
Because I had to take a long vacation and hand over the database to other colleagues for management, he did not clean up the archive log for a week, and I did not check it either. Today, I am not at work. Below are logs.

Errors in file D: \ CIM \ dump \ bdump \ cim_arc1_3068.trc:
ORA-19504: failed to create file "D: \ CIM \ archive \ arc00385062599653342989.arc"
ORA-27044: unable to write the header block of File
OSD-04008: writefile () failure, unable to write to file
O/s-error: (OS 112) there is not enough space on the disk.

Arc1: Error 19504 creating archive log file to 'd: \ CIM \ archive \ arc00385062599653342989.arc'
Arch: archival stopped, error occurred. Will Continue retrying
Mon Oct 26 03:42:51 2009
Errors in file D: \ CIM \ dump \ bdump \ cim_arc1_3068.trc:
ORA-16038: log 3 sequence #142989 cannot be archived
ORA-19504: failed to create file ""
ORA-00312: Online log 3 thread 1: 'd: \ CIM \ redo \ redo3.log'