When loading a schema fails, investigate the DDWLog file. This file is located at [Installation Directory]\Log\DDWLog.txt. This log file contains
The message that DDW sends to the Agent.
The message that DDW receives from the Agent.
The status and progress of the schema loading operation.
Enterprise Database Server Schema
To enable debug logging for Enterprise Database Server schema loading, turn on trace by executing the MARC command
NA DATAEXCHSERVICE TRACE ON.
RDMS Schema
To enable debug logging for the RDMS schema loading operation, edit the runstream SYS$LIB*DEXCH$RUN.DEXCXTRCTRUN to add a D option and then execute @TPF.SCHEMASERVER,TD
Each schema extractor creates new file cycles of DIAG$SXnn$m, LOG$SXnn$m, and BRKPT$SXnn$m
where
nn is the Application Group number
m is an instance number.
Inspect the LOG$SXnn$m file for detailed tracing of RDMS catalog processing within the Agent.
For more information, refer to Host Files Created by Data Exchange (Default qualifier will be DEXCH$DEXCH)
Edit the UREP*UTILITY.RDMS-CATPRIV runstream to be Application Group specific and run it.
For more information, refer to Updating the RDMS Catalog and Configuring User ID for the Director.
SQL Server Schema
DDW uses the ADO.NET technology to connect to the SQL Server database and retrieve the schema information. This data is then stored in the DDW Repository. Status and error information is written to [Installation Directory]\Log\DDWLog.txt.
Oracle Schema
DDW uses the Managed Data Access technology to connect to the Oracle database and retrieve the schema information. This data is then stored in the DDW Repository. Status and error information is written to [Installation Directory]\Log\DDWLog.txt.