[Home] [Help]
1723:
1724: --Update the last_update_login back to null to ensure accurate archival
1725: --when exceptions are generated in the next round
1726:
1727: update msc_item_exceptions ex
1728: set ex.last_update_login = null,
1729: ex.last_update_date = sysdate
1730: where ex.plan_id = MSC_X_NETTING_PKG.G_PLAN_ID
1731: and ex.version = 0
1732: and exception_type in (9, 10, 29, 30)
1733: and nvl(ex.last_update_login,-1) = MSC_X_NETTING_PKG.G_MAGIC_NUMBER;
1734:
1735: --update the if the count is 0 to older version
1736: update msc_item_exceptions ex
1737: set ex.version = version + 1,
1738: ex.last_update_date = sysdate
1739: where ex.plan_id = MSC_X_NETTING_PKG.G_PLAN_ID
1740: and ex.version = 0
1742: and ex.exception_count = 0;
1743:
1744: -- In prior release, we have kept a history of all the exceptions
1745: -- occuring during netting for intelligent analysis use such as
1746: -- exception convergence; overtime or latency of a plan in msc_item_exceptions
1747: -- table. The current usage is using the latest version of the data and
1748: -- not all the history data. If the table is maintaining all the history
1749: -- data, in the rolling of the netting engine run for a period of time,
1750: -- the table will grow quickly and create a performance problem. Therefore,
1750: -- the table will grow quickly and create a performance problem. Therefore,
1751: -- the table is arhived based on the user defined profile option and only keep
1752: -- certain number of version. Default verion = 20
1753:
1754: delete msc_item_exceptions ex
1755: where plan_id = MSC_X_NETTING_PKG.G_PLAN_ID
1756: and exception_type in (9, 10, 29, 30)
1757: and version > 20;
1758:
1756: and exception_type in (9, 10, 29, 30)
1757: and version > 20;
1758:
1759: /***
1760: delete msc_item_exceptions
1761: where plan_id = G_PLAN_ID
1762: and version = 0
1763: and exception_count = 0;
1764: