PIN_ERR_NO_MEM and High Water Mark Errors during Online Index Rebuilding
(Doc ID 2673151.1)
Last updated on MAY 26, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
The customer had increased the memory parameters for Data Manager (DM) to avoid PIN_ERR_NO_MEM errors in Production as the followings:
The customer performs index rebuilding activity of all indexes on a monthly basis and observes the PIN_ERR_NO_MEM errors in Connection Manager (CM) logs and high watermark errors in dm_oracle logs around 1-2 hours after the activity. The index rebuilding activity is performed as an online activity during off-peak hours.
Occasionally, PIN_ERR_NO_MEM errors occurred for a few minutes and then dm_oracle was able to recover by itself.
Is there any necessity to restart the CM and DM after the index rebuild activity?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document