Timos Failes On Second Pcm_op_tcf_aaa_authorize Call
Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 18.104.22.168.0
This problem can occur on any platform.
Timos can only handle one PCM_OP_TCF_AAA_AUTHORIZE when DataMigrationOnStartup = false.
Setting DataMigrationOnStartup = false was done to reduce the memory usage of timos and speed up
Timos should complete its cache during work, according to the documentation:
"If the data needed to process the request is found in the ROC, TIMOS DM uses the data in the ROC;
otherwise it forwards the request to the database, gets the response, caches the data in the ROC,
and returns the response to the CM."
-- Steps To Reproduce:
1) Run dm_timos with DataMigrationOnStartup = false and connect CM to timos.
2) Call PCM_OP_TCF_AAA_AUTHORIZE for a configured, active account (lets call it X). This ends with success.
3) Call again PCM_OP_TCF_AAA_AUTHORIZE for another configured, active account (lets call it Y).
This step failes with:
<PIN_ERR_BAD_ARG:4> location=<PIN_ERRLOC_FM:5> class=<APPLICATION:4> field
num=<PIN_FLD_MSID:5,745 3> recid=<0> reserved=<0>
The same calls of PCM_OP_TCF_AAA_AUTHORIZE on CM connected directly to DM both ends with success.
Restarting cm and timos and calling the opcode first for Y, then for X gives the result when
second call - this time for X - ends with the same error, demonstrating the error is not depending
on account data.
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