Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
After ASM disk operations, rebalance operation may end with ORA-15041 error. This error means there is not free space.
When we check the ASM operations, we can see the error.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 | SQL> select * from gv$asm_operation; INST_ID GROUP_NUMBER OPERA STAT POWER ACTUAL SOFAR EST_WORK ---------- ------------ ----- ---- ---------- ---------- ---------- ---------- EST_RATE EST_MINUTES ERROR_CODE ---------- ----------- -------------------------------------------- 1 1 REBAL ERRS 1 ORA-15041 2 1 REBAL ERRS 1 ORA-15041 3 1 REBAL ERRS 1 ORA-15041 |
In this case, the only process is to create free space on the disk group. This error will not occur when we create enough space in the disk group with operations like datafile resize, tablespace drop, and so on.
If enough free space has been created in the disk group after the error is received, we can increase the POWER value of the corresponding disk group to restart the rebalance process.
You can find the details in the article named “How To Increase ASM Rebalance Processing Speed”
When you increase the value of POWER again, we will see that the operations continue in 10 parallel and completed succesfuly.
1 2 3 4 5 6 7 8 9 | SQL> select * from gv$asm_operation; INST_ID GROUP_NUMBER OPERA STAT POWER ACTUAL SOFAR EST_WORK ---------- ------------ ----- ---- ---------- ---------- ---------- ---------- EST_RATE EST_MINUTES ERROR_CODE ---------- ----------- -------------------------------------------- 2 1 REBAL WAIT 10 1 1 REBAL WAIT 10 3 1 REBAL RUN 10 10 2 1448119 |
