Last updated on MARCH 02, 2009
Applies to:Oracle Communications ASAP Cartridges - Version: 1.0.0 to 1.0.1
This problem can occur on any platform.
In the README for UNICOHIN_1_0_0_R1_0_1.b31.tar, there was a fix for the
QRY_ALL-SERVICES-DETAILS ASDL regarding the parsing of return value/parameters.
When this ASDL operates in b31, a PROV_CARTRIDGE_EXCEPTION is thrown when the cartridge attempts to parse the COUNT value. The value returned from the NE is "1", which is numeric, yet the cartridge states "COUNT is invalid format".
-- Steps To Reproduce:
Run a QRY_ALL-SERVICES-DETAILS ASDL live to the network element and observe the JNEP diag file when the response is returned.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms