Billing and Revenue Management (MOSC)

MOSC Banner

Strange DB number coming in the billinfo poid

edited Mar 28, 2017 5:01AM in Billing and Revenue Management (MOSC) 1 commentAnswered

     Hi All

We are upgraded to 7.5PS16 recently and encountering below errors in cm.pinlog while running regression suite.

Below billinfo poid is having a different DB number , where original DB is 0.0.0.1. As a result, opcode call is failing.

Had someone faced below issue, could you please throw some light ?

0 PIN_FLD_POID           POID [0] 0.0.2432.21368 /billinfo 2159262031 0

D Sat Jan 15 06:35:05 2022  XXXX  cm:27026  cm_child.c(132):5207 2:XXXX:testnap:27024:-142910816:20309:1484223386:1:root.0.0.0.1:::

        opcode db: 159404920(0.0.128.120), context db: 1(0.0.0.1), trans_state: 2, opcode: 4

E Sat Jan 15 06:35:05 2022  XXXX  cm:27026  cm_child.c(132):5262 2:XXXX:testnap:27024:-142910816:20309:1484223386:1:root.0.0.0.1:::

        bad cm_change_dm_connection, new db=159404920(0.0.128.120), current db=1(0.0.0.1), err=37(PIN_ERR_TRANS_ALREADY_OPEN), errno=11(Resource temporarily unavailable)

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center