當點擊完 finish按鈕後，dbca 或者dbua hang住
來源於：
DBCA/DBUA APPEARS TO HANG AFTER CLICKING FINISH BUTTON (文檔 ID 727290.1)
適用於：
Oracle Database Configuration Assistant - Version 10.2.0.1 to 11.2.0.1 [Release 10.2 to 11.2]
Information in this document applies to any platform.
症狀：
Trying to create a database using the DBCA.
After configuring all options successfully, clicking finish does nothing.
This can also happen when using DBUA to upgrade a database.
There is no progress, and no errors are returned.
Looking at the dbca trace.log does not show any errors, just the following: [AWT-EventQueue-0] [11:20:29:828] [DBCAWizard.onFinish:1139] m_bFinishClicked: true [AWT-EventQueue-0] [11:20:30:2] [DBCAWizard.onFinish:1139] m_bFinishClicked: true [AWT-EventQueue-0] [11:20:35:126] [SQLEngine.done:1958] Done called
In 10.2 trace information should be written automatically to the following location
$ORACLE_HOME/cfgtoollogs/dbca/trace.log
In 11g, the location of trace.log has changed to:
$ORACLE_BASE/cfgtoollogs/dbca/
原因：
In most cases, it appears that an X client is being used to run the DBCA, like Xming.
When using Xming, this behaviour can occur if some Xming fonts are missing as discussed in unpublished Bug 6714527 (closed at status 'Not a Bug').
In case several Xwindows clients are tested to fail, the problem could also be caused by the next environment variable when using a recent Oracle release, e.g. 11gR2 :
ORA_NLS10=/nls/data/9idata
In this case, you may also encounter an error:
ORA-12705: Cannot access NLS data files or invalid environment specified
解決方案：
To use Xming, you have to install the complete font package.
Updating Xming to a newer version has also been known to resolve the issue.
Optionally, run DBCA locally from the console, using a different X client or using VNC.
Reflections X and Exceed are also known to work.
However, problems have been reported with Exceed version 13.0.0 which seems not compatible with Oracle 11g. Exceed version 14.0.0 is reported to work, so please use that version when using Exceed.
If the environment variable
ORA_NLS10=/nls/data/9idata
is set, unset it and retry.
