Fix Oracle 19c Database Creation Stuck at 15% 36% 46%

I encountered a small case yesterday and wanted to write it down for reference.

I was creating a new database on a test server today. This test machine already had three instances running, and I planned to add three more. However, the DBCA (Database Configuration Assistant) kept getting stuck at 36% (in CDB mode). If it were a non-CDB setup, it would get stuck at 46%.

Oracle 19c DBCA log screenshot when stuck at 46% progress.

Why Does Oracle 19c Database Creation Get Stuck at 15%, 36%, 46%?

When running DBCA (Database Configuration Assistant) in Oracle 19c, many administrators report the setup freezing at 15% progress. This is usually caused by:

Missing or misconfigured environment variables (ORACLE_HOME, ORACLE_SID)
Insufficient memory or disk space on the host system
Listener configuration issues are preventing service registration
Incorrect database character set or parameters
Permission problems on Oracle directories

Checking the trace logs, I found that the process halted during the execution of datapatch.

 
executing datapatch /orabin/product/19.3.0/OPatch/datapatch

The alert log and other logs didn't provide any useful information. After checking MOS (My Oracle Support), I realized the issue was caused by my previous modification to the glogin.sql file—I had altered it to display the current database name and other information upon local login. I had essentially dug my own grave.

 
vi $ORACLE_HOME/sqlplus/admin/glogin.sql
Add the following parameters
-- Display current database name at login
SELECT 'Connected to database: ' || GLOBAL_NAME AS "Database Name"
FROM GLOBAL_NAME
WHERE ROWNUM = 1
/
-- set prompt to username@SID
SET SQLPROMPT "_USER'@'&_CONNECT_IDENTIFIER> "
-- line break
SET TERMOUT ON

Step-by-Step Fix for Oracle 19c DBCA Stuck

1. The solution was to revert glogin.sql to its original state by deleting or commenting out all manually added content.

2. After making that change, I reran DBCA, and it worked fine.

Note: Modifying glogin.sql can affect patching operations, and it doesn't throw an error—it just gets stuck. So remember this, otherwise you might spend a long time troubleshooting without finding the root cause.

Best Practices for Oracle 19c Installation

Always run pre-install checks before DB creation.
Ensure swap memory is properly configured.
Use AL32UTF8 character set for broader compatibility.
Keep Oracle patches updated to avoid known bugs.

Mobile Menu