Test Data Import with Optimistic Locking turned ON

Per Kate, no longer blocked by UIDATIMP-997
Also no longer blocked until Prokopovych confirms that Optimistic Locking changes have been merged

Once unblocked:

1. Have PTF test Data Import performance with OL turned off (current PTF env is Juniper, so they will need to upgrade their env to include the latest version of MODINV and MODINVSTO) UIDATIMP-995
2. Have PTF test Data Import performance with OL turned on UIDATIMP-996

Scenarios:

1. Run an update import with OL turned on. Compare the job time to the same job without OL turned on.
2. As a user, open a holdings and/or item in edit mode. Then run an update job that will affect the same holdings and/or item. One import is done, edit a couple things on the holdings/item, and try to save it. (should trigger the OL message)
3. See if you can trigger a scenario where Data Import is the second user trying to update a holdings or item (maybe run a manual edit to an item in a loop?)

To turn OL off:

• ALTER TABLE instance DISABLE TRIGGER set_instance_ol_version_trigger;
• ALTER TABLE holdings_record DISABLE TRIGGER set_holdings_record_ol_version_trigger;
• ALTER TABLE item DISABLE TRIGGER set_item_ol_version_trigger;

To turn OL on:

• ALTER TABLE instance ENABLE TRIGGER set_instance_ol_version_trigger;
• ALTER TABLE holdings_record ENABLE TRIGGER set_holdings_record_ol_version_trigger;
• ALTER TABLE item ENABLE TRIGGER set_item_ol_version_trigger;