LSW 2.4.X: How To Configure OWB When DB Is On RAC And/Or Exadata

(Doc ID 2379823.1)

Last updated on APRIL 23, 2018

Applies to:

Oracle Health Sciences Data Management Workbench - Version 2.4.6 and later
Oracle Life Sciences Data Hub - Version 2.4.6 and later
Information in this document applies to any platform.

Goal

LSH/DMW 2.4 Installation: How to verify if OWB is Configured Correctly when the Database is on RAC and/or Exadata.

When OWB is incorrectly configured for RAC or Exadata, you may hit unexpected LSH or DMW issues. A known issue is Work Area installation  log may display:

Deploying AUX_CDR_W520_28AB6F46_0_$CREATE_11
Unit Name=AUX_CDR_W520_28AB6F46_0_$CREATE_11
RPE-01003: An infrastructure condition prevented the request from completing.
Unit Name=AUX_CDR_W520_28AB6F46_0_$CREATE_11
ORA-29532: Java call terminated by uncaught Java exception: java.lang.NullPointerException
ORA-06512: at "OWBSYS.WB_RTI_UTIL", line 86
ORA-06512: at "OWBSYS.WB_RTI_UTIL", line 315

 and similar errors will be in the OWB logs, too.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms