NSP CCM Apply on IXP or IMF is failing with ERROR: IDB_LIMIT: Exceeded maximum operations for transaction IdbTransOpsMax=10000

Asset ID:	1-72-2004289.1
Update Date:	2017-02-07
Keywords:

Solution Type Problem Resolution Sure

Solution 2004289.1 : NSP CCM Apply on IXP or IMF is failing with ERROR: IDB_LIMIT: Exceeded maximum operations for transaction IdbTransOpsMax=10000

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 9.0.0 to 10.1.5.1 [Release 9.0 to 10.0]
Information in this document applies to any platform.

Symptoms

In NSM CCM, apply on IMF or IXP is failing with following error message:

IDB Error writing to table ERROR: IDB_LIMIT: Exceeded maximum operations for transaction [IdbView.Cxx:2180] ^^ IdbParam::IdbtransOpsMax=10000

Same log can be found in dbreplicator.log and jmxAgent log.

Changes

System has been reinstalled, clobbered or upgraded.

Cause

Apply is failing because amount of changes to push to server is too big.

Solution

Easiest solution consists of temporarily increasing the limit of possible changes to 50000.

Connect as cfguser on the master server of the subsystem.
Increase the IDB parameter:

ivi IdbParamDef
Change the value of "IdbTransOpsMax" parameter to 50000.
Restart the JMX agent. As cfguser:
$ pm.set off JmxAgent

$ pm.set on JmxAgent
In NSP CCM, apply the configuration.
Rollback the "IdbTransOpsMax" parameter value to previous value.

If it is still failing with 50000, it can be increased to 500000.

References

<BUG:20980866> - APPLY ON IMF IS FAILING ERROR: IDB_LIMIT: EXCEEDED MAXIMUM OPERATIONS FOR TRANSA
<BUG:19108248> - [232286]DURING UPGRADE, APPLY ON IXP IS FAILING AFTER BUILDER PACKAGE ASSOCIATIO
<NOTE:1908657.1> - Datafeed Export not Working after System Upgrade or IXP Clobber

Attachments

This solution has no attachment