Sources of Oracle commits from pc_server

• Article Type: General
• Product: Aleph
• Product Version: 19.01

Description:
Our DBA has discovered that the pc_servers are doing very large numbers of commits in a short amount of time.

For instance, the ABC library pc_server did 20,000 commits on July 22.

Why are there so many commits?

Resolution:
There are various sources of Oracle commits by the pc_server. The main ones are:

hitting Enter (z65)
searching (z05 and z110 result sets)
Acq activity (z68, z601, etc.) and logging (z71)
Circ activity (z36, z35, z36h, z31, etc.) and logging (z309)
Item update (z30 and z30h)

I don't find much Circ activity for abc50 on 20090722, but here are the others:

Each time a staff member hits Enter, the z65_time in the z65 (GUI session) record is updated. This probably accounts for a large part of the Oracle commits originating from the ABC library.

It's hard to know what component of the searching is for abc users but here is what we see so far today (Wed, Aug 5) for all the libraries:

vir01@ALEPH18> select count(*) from z05;
**** Hit return to continue ****

COUNT(*)
----------
8451


vir01@ALEPH18> select count(*) from z110;
**** Hit return to continue ****

COUNT(*)
----------
5307

If 20% of the z05 and z110 commits on 20090722 were for ABC, that would be 2600.


There were 1287 Acq activities logged in the z71:

abc50@ALEPH18> select count(*) from z71 where Z71_OPEN_DATE = '20090722';
**** Hit return to continue ****

COUNT(*)
----------
1287


There were 753 item updates:

abc50@ALEPH18> select count(*) from z30h where Z30H_H_DATE = '20090722';
**** Hit return to continue ****

COUNT(*)
----------
753


I think you can see how we could reach the 20,000 Oracle commits we see for ABC on 20090722.

• Article last edited: 10/8/2013