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

Description:
We are very tight on space in our /exlibris filesystem. Can we install the ue kit on a different mountpoint besides /exlibris so that if the pump maxes out, aleph will not be compromised?

Resolution:
Yes, the UE kit can be installed in a different filesystem than /exlibris -- in which case the ./upgrade_express_2001_2101/data/ output would be written to that other filesystem rather than /exlibris.

Also, if necessary, you could export the v19 data one library at a time. You would specify in the Upgrade Express --> Upgrade Parameters --> upgrade libraries parameter just one library (or two). Then you would do Export Customer Data (using the Data Pump), transfer the zipped file to the v21 server, and run Install Customer Data on v21.

util a/17/11/1 ("Check Space Utilization of Oracle Tables") in abc01, which produces the abc01 $data_scratch/count_rep.lst output, shows that the total space for abc01 is 165 gig (20 million BLOCKS) and that 9.5 gig of this is z69:

6 SEGMENT TABLESPACE

7 SEGMENT NAME TYPE NAME BYTES (K) BLOCKS EXTENTS

8 --------------- ---------- ---------- ---------- ---------- ----------
... .......
102 Z69 TABLE TS2D 6348800 793600 620

103 Z69_ID INDEX TS2X 2027520 253440 198

104 Z69_ID1 INDEX TS1 1229824 153728 257

... .......
... .......
127 sum 165252456 20656557



The following SQL shows the counts by year for the z69 (OPAC log) table. The z69 is used for producing OPAC statistics. Aleph has no OPAC statistics reports, but your ARC does. If/when you are done producing statistics for past years you could delete the z69's for those years (-- first saving them to tape).

abc01@DALEPH> select substr(Z69_TIME_STAMP,1,4), count(*) from z69 group by substr(Z69_TIME_STAMP,1,4);
**** Hit return to continue ****

SUBSTR(Z69_T COUNT(*)
------------ ----------
2005 3224742
2008 5912045
2010 7236060
2012 61435
2009 6789781
2006 6259474
2011 4183939
2007 6151251

• Article last edited: 10/8/2013