Datafeed Export not Working after System Upgrade or IXP Clobber

Asset ID:	1-72-1908657.1
Update Date:	2017-10-30
Keywords:

Solution Type Problem Resolution Sure

Solution 1908657.1 : Datafeed Export not Working after System Upgrade or IXP Clobber

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 9.0.3 and later
Information in this document applies to any platform.

Symptoms

Newly created DataFeeds after system upgrade (or clobber on IXP subsystem) are not exporting data. Under the NSP DataFeed application, concerned feeds are getting "Unknown" status.

Cause

The new DataFeed configuration built after the system upgrade (or clobber on IXP subsystem) is not applied on the IXP side due to some database replication issues between the NSP and the concerned IXPs. In fact, the number of rows that need to be updated under the IXP IDB database is exceeding the limit defined under IdbParamDef IXP table. This is a known issue handled by bug 19114443.
When activating/deactivating a datafeed or when applying changes from DataFeed application, an error message is displayed on JMX logs of the IXP master server:

Result value: [OK, DETrqLineFilterDe, IDB Error writing to table
ERROR: IDB_LIMIT: Exceeded maximum operations for transaction [IdbView.cxx:2180]
^^ IdbParam::IdbTransOpsMax=10000 [IdbView.cxx:2181]
^^ IdbView::storeUpdate() [IdbView.cxx:2182]
^^ IdbViewIter::storeUpdate() [IdbViewIter.cxx:339]
^^ IdbIter::addRecSelect(void *xRec) [IdbIter.cxx:2467]
^^ write_row failed on table DETrqLineFilterDe [ha_idb.cc:2169]

Solution

Connect as cfguser on the master server of the subsystem where the DataFeed is running
Increase the IDB parameter:

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

$ pm.set on JmxAgent
Activate or deactivate one of the DataFeeds running on the concerned subsystem in order to apply the configuration on the IXP.
Rollback the "IdbTransOpsMax" parameter value to 10000.
Retry to activate/deactivate feed

This will not be required for subsequent action done on DataFeed as next database replication will have few updates and 10000 limit will not be reached.

Attachments

This solution has no attachment