• Product: Aleph
• Product Version: 20, 21, 22, 23
• Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

Question    
How can one determine if the space allocated to each filesystem of a new Aleph instance is adequate?

Answer    
The space occupied by a new Aleph instance is usually similar to the space occupied by the old instance: it's almost never less, and usually just slightly more. (In Aleph 20-up, there have not been any big changes in space requirements. The only exception is if the site has not been doing Publishing and is planning to start with the new version; the z00p LOBSEGMENT can be *very* large.) 

Assuming that the Ex Libris Sizing Manager has approved the configuration it should be adequate. But there could be the issue of allocation between filesystems.... 

Do "df -h" to get the big picture. /exlibris is the central, critical Aleph filesystem. In many cases it will be the only filesystem needing to be considered. (Other filesystems, such as root, boot, tmpfs, etc., are handled by the Unix system administrator.) 

If the server has /exlibris1, /exlibris2, /oradata, etc., filesystems, those need to be considered in conjunction with /exlibris. 

Ex Libris recommends that Aleph tablespace datafiles be defined as AUTOEXTENSIBLE. In this case, Oracle will add to the tablespace as necessary and the main consideration is whether the filesystem(s) the Oracle data resides in have enough space for Oracle to define new or larger extents in. See the link in Additional Information below for SQL to determine if tablespace files are extensible. 

If /exlibris1, /exlibris2, etc., or a separate /oradata filesystem exists, then make sure that the allocations for these filesystems on the new server are at least as great as those on the old server. If the new Aleph instance is on an existing server, make certain that the above mentioned filesystems containing Oracle data have no more than 50% of their space occupied by Oracle data for the old version.

• Article last edited: 02-Mar-2016