Re: 11.5.9 Application grows hugely in prev two weeks

There are not many rows in the FND_ENV_CONTEXT table, only 113086.
However, below is the list of top ten segments order by Num-of-rows.

    Top ten segments by num of rows     Owner Segment Name Num of Rows Size
BOM CST_ELEMENTAL_COSTS 14,361,580.00 1.18 MRP MRP_ATP_DETAILS_TEMP
14,344,690.00 3.72 APPLSYS FND_CONCURRENT_DEBUG_INFO 13,168,040.00 2.71
APPLSYS FND_LOG_TRANSACTION_CONTEXT 12,065,450.00 0.76 IRTA
IRTA_DWH_INVENTORY 10,223,133.00 2.06 INV MTL_TRANSACTION_ACCOUNTS
8,797,420.00 1.46 BOM CST_STANDARD_COSTS 7,690,960.00 0.76 INV
MTL_CST_ACTUAL_COST_DETAILS 4,912,340.00 0.61 APPLSYS FND_LOG_MESSAGES
3,550,620.00 0.71 INV MTL_MATERIAL_TRANSACTIONS 3,044,640.00 1.39

And top-ten segments by size:

    Top ten segments by size  Owner Segment Name Size Num of Rows MRP
MRP_ATP_DETAILS_TEMP 3.72 14,344,690.00 ASO ASO_ORDER_FEEDBACK_T 3.01
843,100.00 APPLSYS FND_CONCURRENT_DEBUG_INFO 2.71 13,168,040.00 IRTA
IRTA_DWH_INVENTORY 2.06 10,223,133.00 IRTA IRTA_DWH_TEST2 1.93 0.00 INV
MTL_TRANSACTION_ACCOUNTS 1.46 8,797,420.00 INV MTL_MATERIAL_TRANSACTIONS
1.39 3,044,640.00 BOM CST_ELEMENTAL_COSTS 1.18 14,361,580.00 WSH
WSH_DELIVERY_DETAILS 1.12 2,278,480.00 IRTA IRTA_DWH_TEST 0.99 2,456,180.00

  -Vikram

On Tue, Oct 7, 2008 at 12:11 PM, James Morrow <morrow.james@xxxxxxxxx>
wrote:
> Check the size of FND_ENV_CONTEXT (Note:  158751.1).  If it is
> unusually large, it's likely that you've hit this (common) bug in
> 11.5.9.
>
> -- James
> ----------------------------------------------------------------------
> James J. Morrow | Senior Oracle Applications DBA
> morrow.james <at> gmail <dot> com
>
>
>
>
> On Tue, Oct 7, 2008 at 11:05 AM, vikram singh <vikramsingh120@xxxxxxxxx>
wrote:
>> Hi All,
>>
>> My Client's 11.5.9 instance has been growing hugely in the last two
>> weeks. All i know so far is that the Client is not running any
>> programs that he thinks could cause the huge db growth.
>> I was looking for any new concurrent programs that might be running of
>> late that wasnt running earlier and which could cause the growth. No
>> success so far.
>>
>> How can i narrow down to the culprit cause?
>>
>> Thanks,
>> -Vikram
>>
>>
>
>

Other related posts: