UDR Cache

I try: onstat -g prc OUTPUT: UDR Cache: Number of lists : 1021 PC_POOLSIZE : 2048 UDR Cache Entries: list# id ref_cnt dropped? heap_ptr udr name -------------------------------------------------------------- 444 48180 0 0 700000fb1486c38 progr@serwer:.prap_ddo_dom 445 1715 0 0 700000f8864b038 progr@serwer:.prap_23_1 446 34479 1 1 700000f52aa2c38 progr@serwer:.rap3910 448 229 26 0 700000fc586a038 progr@serwer:.idjorgget 448 229 79 1 700000f90024c38 progr@serwer:.idjorgget 448 229 14 1 700000f8d4b5038 progr@serwer:.idjorgget 448 229 14 1 700000f6d3f9838 progr@serwer:.idjorgget 448 229 16 1 700000fb1e30838 progr@serwer:.idjorgget 448 229 15 1 700000f9e299c38 progr@serwer:.idjorgget 448 229 3 1 700000f93aec038 progr@serwer:.idjorgget 448 229 17 1 700000f65f66438 progr@serwer:.idjorgget 448 229 21 1 700000faad27438 progr@serwer:.idjorgget 448 229 14 1 700000fb6da3038 progr@serwer:.idjorgget 448 229 19 1 700000f7fdedc38 progr@serwer:.idjorgget 448 229 29 1 700000fa73a4038 progr@serwer:.idjorgget 448 229 3 1 700000f9bf74c38 progr@serwer:.idjorgget Total number of udr entries: 352. Number of entries in use : 137 I don't understand what happen with procedure idjorgget ?

piootrj@gazeta.pl wrote: I sit possible that procedure idjorgget() a) has multiple versions with different argument lists? Or b) was modified a few times but some sessions still have the old versions attached in prepared statements? Art S. Kagel > I try: > > onstat -g prc> > OUTPUT: > > UDR Cache: > Number of lists : 1021 > PC_POOLSIZE : 2048> > UDR Cache Entries: > > list# id ref_cnt dropped? heap_ptr udr name > -------------------------------------------------------------- > 444 48180 0 0 700000fb1486c38 > progr@serwer:.prap_ddo_dom > 445 1715 0 0 700000f8864b038 > progr@serwer:.prap_23_1 > 446 34479 1 1 700000f52aa2c38 > progr@serwer:.rap3910 > 448 229 26 0 700000fc586a038 > progr@serwer:.idjorgget > 448 229 79 1 700000f90024c38 > progr@serwer:.idjorgget > 448 229 14 1 700000f8d4b5038 > progr@serwer:.idjorgget > 448 229 14 1 700000f6d3f9838 > progr@serwer:.idjorgget > 448 229 16 1 700000fb1e30838 > progr@serwer:.idjorgget > 448 229 15 1 700000f9e299c38 > progr@serwer:.idjorgget > 448 229 3 1 700000f93aec038 > progr@serwer:.idjorgget > 448 229 17 1 700000f65f66438 > progr@serwer:.idjorgget > 448 229 21 1 700000faad27438 > progr@serwer:.idjorgget > 448 229 14 1 700000fb6da3038 > progr@serwer:.idjorgget > 448 229 19 1 700000f7fdedc38 > progr@serwer:.idjorgget > 448 229 29 1 700000fa73a4038 > progr@serwer:.idjorgget > 448 229 3 1 700000f9bf74c38 > progr@serwer:.idjorgget > > Total number of udr entries: 352. > Number of entries in use : 137 > > I don't understand what happen with procedure idjorgget ? >

On 6 Mar, 23:45, "Art S. Kagel" <k...@bloomberg.net> wrote: > pioo...@gazeta.pl wrote: > > I sit possible that procedure idjorgget() a) has multiple versions with > different argument lists? Or b) was modified a few times but some sessions > still have the old versions attached in prepared statements? > > Art S. Kagel > > > I try: > > > onstat -g prc> > > OUTPUT: > > > UDR Cache: > > Number of lists : 1021 > > PC_POOLSIZE : 2048> > > UDR Cache Entries: > > > list# id ref_cnt dropped? heap_ptr udr name > > -------------------------------------------------------------- > > 444 48180 0 0 700000fb1486c38 > > progr@serwer:.prap_ddo_dom > > 445 1715 0 0 700000f8864b038 > > progr@serwer:.prap_23_1 > > 446 34479 1 1 700000f52aa2c38 > > progr@serwer:.rap3910 > > 448 229 26 0 700000fc586a038 > > progr@serwer:.idjorgget > > 448 229 79 1 700000f90024c38 > > progr@serwer:.idjorgget > > 448 229 14 1 700000f8d4b5038 > > progr@serwer:.idjorgget > > 448 229 14 1 700000f6d3f9838 > > progr@serwer:.idjorgget > > 448 229 16 1 700000fb1e30838 > > progr@serwer:.idjorgget > > 448 229 15 1 700000f9e299c38 > > progr@serwer:.idjorgget > > 448 229 3 1 700000f93aec038 > > progr@serwer:.idjorgget > > 448 229 17 1 700000f65f66438 > > progr@serwer:.idjorgget > > 448 229 21 1 700000faad27438 > > progr@serwer:.idjorgget > > 448 229 14 1 700000fb6da3038 > > progr@serwer:.idjorgget > > 448 229 19 1 700000f7fdedc38 > > progr@serwer:.idjorgget > > 448 229 29 1 700000fa73a4038 > > progr@serwer:.idjorgget > > 448 229 3 1 700000f9bf74c38 > > progr@serwer:.idjorgget > > > Total number of udr entries: 352. > > Number of entries in use : 137 > > > I don't understand what happen with procedure idjorgget ? This problem is not related whit bad configuration "PC_HASHSIZE" and "PC_POOLSIZE" ? I heard that is to small PC_POOLSIZE but i'm not sure.