osdWsdlRegenerator does not Recover from Database Disconnections
(Doc ID 2804770.1)
Last updated on OCTOBER 25, 2024
Applies to:
Oracle Communications Network Charging and Control - Version 4.3.0 to 12.0.4.0.0 [Release 4.3 to 12.0.0]Oracle Communications Convergent Charging Controller - Version 6.0.0 to 12.0.4.0.0 [Release 6.0 to 12.0.0]
Information in this document applies to any platform.
Symptoms
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) up to and including 12.0.4.0, the osdWsdlRegenerator process on the Service Management Server (SMS) does not recover from database connection interruptions.
The osdWsdlRegenerator process is responsible for regenerating Web Services Description Language (WSDL) files after changes have been made to the Open Services Development (OSD) configuration (as opposed to the libwsdlGenerator.so acsCompilerDaemon plugin which regenerates the WSDL files when changes are made in the Control Plans (CPs).
The only way to tell if the osdWsdlRegenerator connection to the database was interrupted is if the process starts throwing the following error:
This ORA error corresponds to"ORA-01002: fetch out of sequence tips" and essentially means an attempt was made to access an invalid cursor.
As it never recovers, the osdWsdlRegenerator just sits in an endless loop, unable to fetch data from the database to rebuild the WSDL files so changes made via the OSD screens never take effect.
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 |
| Cause |
| Solution |
| References |