以下文档摘自metalink doc : 188134.1
Subject: Tracing the Database Configuration Assistant (DBCA)
Doc ID: 188134.1 Type: BULLETIN
Modified Date: 09-OCT-2008 Status: PUBLISHED
Purpose
——-
The Purpose of this document is to assist in debugging DBCA problems.
Scope & Application
——————-
This document is for DBAs and support analysts to troubleshoot DBCA issues.
Tracing the Database Configuration Assistant (DBCA)
—————————————————
To provide verbose output for DBCA, tracing can be enabled to provide additional
output. To turn on tracing from 9i to 10g:
1. Do a copy of the original dbca file in $ORACLE_HOME/bin. For example:
cp $ORACLE_HOME/bin/dbca $ORACLE_HOME/bin/dbca.ori
2. vi the dbca file in the $ORACLE_HOME/bin directory.
3. At the end of the file, look for the following line:
# Run DBCA
$JRE_DIR/bin/jre -DORACLE_HOME=$OH -DJDBC_PROTOCOL=thin -mx64m -classpath
$CLASSPATH oracle.sysman.assistants.dbca.Dbca $ARGUMENTS
4. Add the following just before the -classpath in the ‘$JRE_DIR’ line:
-DTRACING.ENABLED=true -DTRACING.LEVEL=2
5. At the end of the dbca file, the string should now look like this:
# Run DBCA
$JRE_DIR/bin/jre -DORACLE_HOME=$OH -DJDBC_PROTOCOL=thin -mx64m
-DTRACING.ENABLED=true -DTRACING.LEVEL=2 -classpath $CLASSPATH
oracle.sysman.assistants.dbca.Dbca $ARGUMENTS
The -DTRACING.LEVEL was missing a space after the 2 so that it looks
like 2-classpath.
6. To trace run:
[opcbsol1]/u01/home/usupport> dbca > dbca.out &
The output will be written to the dbca.out file.
In 10.2 you can add the -DDEBUG flag so that you get the debug information
given to you interactively
“C:\oracle\product\10.2.0\racdb\jdk\jre\BIN\JAVA” -DDEBUG -DORACLE_HOME=”%OH%” –
DJDBC_PROTOCOL=thin -mx128m oracle.sysman.assistants.dbca.Dbca %*
BUT in 10.2 you should already have the trace information 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/<DBNAME>/trace.log
.
