Applicable to the CMS and gateways
To improve database performance, for example when importing large volumes of captured emails, we recommend that you reconfigure the value of the initrans property to enable multiple concurrent block connections.
When Oracle performs row level locking (an enqueue), it creates a ‘slot’ entry in the relevant block header. By default, there is one slot per block. This can become a contention point if multiple connections try to concurrently modify the same block. For this reason, we recommend that you increase the number of available slots for database tables associated with captured events. You also need to increase the slots in the respective table indexes.
What is a Suitable Setting for Initrans?
This depends on your CA DataMinder deployment. For example, if you are running extensive Event Import jobs, our experience in the field indicates that you should set initrans to be ‘the number of Event Import instances plus two’. For further guidance, please contact CA Support at http://ca.com/support.
Which Tables and Indexes?
Table |
Index |
Wgn3Event |
IX_WGN3EVENT_EXTERNALID IX_WGN3EVENT_EVENTTIMESTAMP IX_WGN3EVENT_UPDATETIMESTAMP PK_WGN3EVENT UK_WGN3EVENT_SEQIDM |
Wgn3EA |
IX_WGN3EA_TYPE PK_WGN3EA |
Wgn3EventParticipant |
IX_WGN3EVENTPARTY_ADDRID IX_WGN3EVENTPARTY_LOGINID IX_WGN3EVENTPARTY_TIMESTAMP PK_WGN3EVENTPARTICIPANT |
Copyright © 2014 CA.
All rights reserved.
|
|