Adding space in a LVM2 managed file system on IBM: Linux on System z
(Doc ID 1074801.1)
Last updated on AUGUST 02, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.5 [Release 10.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Linux on IBM Z
Goal
The goal of this document is to provide the steps to follow when a Database hangs because all the online logfiles require to be archived and the switch log can't be done because the file system is full :
ORA-19502: write error on file "/orp5db/oradata/orp5/control01.ctl", blockno 640 (blocksize=16384)
ORA-27061: waiting for async I/Os failed
Error: 28: No space left on device
Note that the method suggested here needs to execute a shutdown abort which means associated loss of transactions. Oracle Support recommends to administer the system to prevent to reach this situation. However, in case that the file system is full, we suggest first to try to clear space to prevent to execute shutdown abort otherwise go ahead with the steps below.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |