My Oracle Support Banner

Invalid DBWS classes After Upgrading Database From 10g to 11gR2 (Doc ID 1497322.1)

Last updated on AUGUST 24, 2020

Applies to:

Web Services - Version 10.1.3.1.0 and later
Information in this document applies to any platform.

Goal

After upgrading a database instance from 10.2 to 11.2, several web services callout (UTL_DBWS) related java classes are now invalid.

The following INVALID objects were noticed in testing:

HTTPClient/OracleSSL*
HTTPClient/OracleSSL$1
HTTPClient/OracleSSL$2
HTTPClient/OracleSSL$3
HTTPClient/OracleSSL$4

but other classes beyond these could be shown as invalid depending on the database environment.

In the original 10.2 instance, the callout jars were installed in the SYS schema.

What steps are necessary to restore the web services callout functionality?

a) Is it possible to "fix" the migrated database without reloading the JVM, and if so how?
b) What is the recommended approach as far as upgrading the database goes with regards to the web services callout functionality?
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.