Primavera Data Warehouse writes detailed process information to the log files. The logs contain information about installation and each run of the STARETL process. If an error occurs, the log files may include diagnostic information. Analyzing these files can help lead you to the resolution or to the file or process that caused the error.
Oracle Database Gateway 11.2 Reporting Incorrect Column Size
If the Oracle Database Gateway 11.2 reports incorrect column size, and the extract fails, ensure that the following are set in the initdg4msql.ora file:
- HS_NLS_LENGTH_SEMANTICS=CHAR
- HS_FDS_CHARACTER_SEMANTICS=TRUE
- HS_KEEP_REMOTE_COLUMN_SIZE=ALL
Primavera Data Warehouse Configuration Utility does not Launch During Installation
If you are installing Primavera Data Warehouse and the Configuration Utility never launches, the location of the JRE may be incorrect. To correct this issue, complete the following steps:
- Go to <download>\operating system\P_R<release level>_DW\STAR\Disk1\install, where <download> is the location where you downloaded Primavera Data Warehouse.
- Run setup.exe (with Windows) or runInstaller (with UNIX or Linux).
Ensure that you specify the correct location for your Java Runtime Environment (JRE). The installer shows an example of the correct path. See Installing Primavera Data Warehouse Software for details.
Workaround to Drop the ODI Master/Work Repo and Create a Master/Work Repo
To drop the odi master/work repo and create a master/work repo:
- Stop the ODI javaee agent server to close database connection to ODI repo.
- Go to <ORACLE_HOME>/oracle_common/bin folder.
- Run the rcu.
- Select Drop Repository, and drop Oracle Data Integrator / Master and Work Repository only.
- Uncheck all other schemas under AS Common Schemas.
- Run the rcu again.
- Select "Create Repository / System Load and Product Load".
- In the Schemas page, select Select existing prefix and then check "Oracle Data Integrator / Master and Work Repository.
- After completing the rcu, run removeOdiObjects and odiImport.
- Use ODI studio to provide the password for each data server.
- Restart the ODI javaee agent server.
- Sign in to the web app to start the real time load plans.
Scheduled daily runs should run as scheduled.
Workarounds for Solaris Installations
For Solaris installations, use the following workarounds:
- To resolve the error when running the script from \config\odi folder as part of the configuration process:
- Open /config/setenv.sh in a text editor
- Find the line export CONFIG_HOME="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
- Replace that with below code
export CONFIG_HOME="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
if echo "$CONFIG_HOME" | grep -q "/config/odi" ; then
export CONFIG_HOME=$CONFIG_HOME/..
fi
- If you are unable to launch ODI studio in Solaris:
- Open the odi.sh in a text editor
- Find the line sh ./odi
- Change that to bash ./odi and save.
- Llaunch and run the ./odi.sh from bash.