There's no doubt that the DBCA can make the creation of a database significantly simpler. However, for our purposes as DBAs, there is a downside to using it. Although we've walked through the individual configuration steps, we don't know how DBCA actually did it. For instance, we mentioned earlier that DBCA created the physical files needed to store the database. However, we don't know the commands that were actually used.
Since it is important for us to understand steps like these, we need to dig deeper into the actual process. In truth, DBCA is only a frontend application that builds a set of scripts—the same ones we generated at the end of our DBCA session. Those scripts are then run, and the database is created. To see how DBCA created the database, we need to look at the scripts it generated.
The scripts themselves are located in the directory specified on the last step before the database creation runs. The default for this location is $ORACLE_BASE...