LSH: OWB Hits The Platform Service Is Not Available; ORA-29532 Java.lang.ExceptionInInitializerError
(Doc ID 2215249.1)
Last updated on APRIL 15, 2022
Applies to:
Oracle Life Sciences Data Hub - Version 2.2.3 and laterInformation in this document applies to any platform.
Symptoms
OWB service is hitting below errors when trying to execute @service_doctor.sql. As consequence, all the jobs are failing .
ERROR
--------------
>>>>>> There are errors in one or more PL/SQL packages and functions
Platform properties have been loaded correctly
Platform location has been seeded correctly
NLS messages have been loaded correctly
>>>>>> The platform service is not available
Service script is accessible to the database server
>>>>>> There is a problem with the repository connection information used to start the service
>>>>>> Here is the detailed error message which contains the connection information passed to the service:-
>>>>>> Cannot access the repository owner password from within the database server
>>>>>> Please verify that this information is accurate
>>>>>> If this information is correct, then please use the
'set_repository_password.sql' script to reset the stored password
The start_owb.sql also results on below error:
Not Available
Diagnostics:
service startup failure reason ORA-29532: Java call terminated by uncaught Java exception: java.lang.ExceptionInInitializerError. Please invoke <OWB_HOME>/owb/rtp/sql/service_doctor.sql for more information.
STEPS TO REPRODUCE
-----------------------------------
Execute the script:
Changes
No changes were done at database level or in the OS server level. Got pings from end users that the Work Area installations started failing. Decided to restart OWB services and then, trying to start them up hit this issue and OWB is not longer starting up.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |