How to expand an Informix Database Server.

(Last modified: 08Feb2005)

This document (10075757) is provided subject to the disclaimer at the end of this document.

fact

Telelogic CMSynergy

Unix

Raw Partitions

goal

How to expand an Informix Database Server.

Increase chunk files

symptom

Error: ISAM 131

dbspace is full

cause

Not enough contiguous free disk space is available to complete the
current operation. For C-ISAM programs, if transaction logging is in
use, roll back the current transaction. Make some disk space available,
and run the program again. For SQL products, roll back the current
transaction, if possible. Contact the system administrator about
acquiring more disk space for databases.

If a Continuus/CM operation results in an Informix error message including an Informix error number followed by ISAM 131, the Informix database server most likely lacks adequate space to complete the operation. Either free space by cleaning up the databases on this Informix server, or expand the space allocated to the Informix server.

fix

Before attempting to expand the server, you must ensure a valid backup exists for each database on the database server.

note

The commands that expand or alter the database must be run as the informix user.

fact

For information about a server’s available space, run:
ccmsrv status -s <server_name> -a

Look for the --- dbspace ccm --- section, and notice the free space in relation to the available space. below 10000 kb is considered low.

For information about how much space a database uses, run:
ccmdb_size <database_pathname>

note

It is recommended that this operation be done with two people verifying the commands being used.  This is to ensure that no mistakes are made.

fix

First, identify that there is enough free space available.

su - informix

cd <file path to chunk files>              ie. cd /db4/data   (information from ccmsrv status -all -s cm0s4a, under the dbspace ccm area)

look for space: df -k             (this will tell you in this example that db4 is only 55% full)

ls -l                                (look for the name(s) of previous chunk files, ie. cm0s4a_ccm.dbs     The new name is going to add _2 or _3 etc.)

Second, expand the database server using the ccmsrv expand command.

note

Example:
ccmsrv expand -s <server_name> -size <size_in_kbytes> -p <path_to_chunkfiles> -d <dbspace_name> -o <offset>

ie: ccmsrv expand -s cm0s4a -size 2000000 -p /db4/data/cm0s4a_ccm_2.dbs -d ccm

By default, a Continuus/CM Informix database server consists of four dbspaces (see for example: ccmsrv status -all -s cm0s4a):
the root or 'dbspace rootdbs', 'dbspace temp', 'dbspace log' , and 'dbspace ccm'.  You must specify which one needs to be expanded.  This is done with the -d option as shown above.

-size 2000000 for 2 Gig to create the maximum size for a chunk file

The -o option is only used if a raw disk partition is used in the following manner: Assume a server was created on a single 200 MB raw disk partition such that the server’s 20000 KB root dbspace was located on that partition at offset 0, the 8000 KB log dbspace was located on that same partition at offset 20000, and the 40000 KB first ccm dbspace was located on that same partition at offset 28000.
You decide to expand the ccm dbspace by another 40 MB. ccmsrv status -s <server_name> -a reports that the dbspaces are presently allocated to use 68 MB of the partition. Your system administrator confirms that the entire 200 MB partition is available for the Informix server, and you’ve confirmed that the existing 68 MB started at offset 0 of the partition. More than 40 MB is therefore available for your use. Specify -size 40000, -d ccm, and -o  68000 to the ccmsrv command.

document

Document Title: How to expand an Informix Database Server.
Document ID: 10075757
Solution ID: NOVL83192
Creation Date: 17Oct2002
Modified Date: 08Feb2005
Novell Product Class:Third Party

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.