Exadata / RDBMS -- DBCA fails KFOD-00101: LRM error [110] - [DBT-05801] There are no ASM disk groups detected.

This time I will keep it short..

This is for the ones who use RAC or Exadata or ASM or GRID .. Should I keep going ? :)

Well, in a migration project we were using XTTS. The target was Exadata ( actually it is needless to say:) It was a new one though.. An Exadata X8-2M.. (Actually, not so new.. Already started talking about Exadata X9-2) 

Anyways, we were creating the target database using DBCA to do the things by the MAA documents and to make it clean.. DBCA failed with KFOD-00101: LRM error [110] .. 

KFOD-00101: LRM error [110] while parsing command line arguments
SEVERE: Oct 08, 2021 2:02:42 PM oracle.install.commons.util.exception.AbstractErrorAdvisor getDetailedMessage
SEVERE: [FATAL] [DBT-05801] There are no ASM disk groups detected.
CAUSE: ASM may not be configured, or ASM disk groups are not created yet.
ACTION: Create ASM disk groups, or change the storage location to File System.

KFOD 101 error was a well known one but! the LRM "110" error was not so famous, so we did a strace check. strace showed that DBUA was trying to read an unrelated init.ora file which was located in the $GRID_HOME/dbs directory.. 

That init.ora was placed there accidentally by the customer. So we removed it. This action solved the problem.  Okay. I think this post is over :)

However, let me also point out one more thing;

I found this worth sharing with you, because it looked pretty interesting before we found the cause. 

Maybe it still is..!  It shows how fragile the environments, the binaries and the tools are. So we need to keep it clean not only to increase our efficieny but also to avoid unnecessary errors.

So , we should keep the environment clean (including our GRID & Database environment:)