Call Management System (CMS) R21 - Add Disk does not allocate disk properly

Description:
In CMS R21 when adding new disks using /opt/informix/bin/dbinit.sh add_disks the new disks appear to be added but are not allocated properly to Informix.

Related Articles:

PSN006319u - https://support.avaya.com/css/public/documents/101091283

Problem Clarification:

Command appears to work correctly.

New disk not allocated properly and not available to CMS.

(cmsr21)-(root)=# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 570M 0 part /boot
├─sda2 8:2 0 10G 0 part /
├─sda3 8:3 0 10G 0 part /cms
├─sda4 8:4 0 1K 0 part
├─sda5 8:5 0 8G 0 part [SWAP]
├─sda6 8:6 0 87.9G 0 part /storage
├─sda7 8:7 0 32G 0 part /export/home
├─sda8 8:8 0 3G 0 part /var
├─sda9 8:9 0 2G 0 part /var/tmp
├─sda10 8:10 0 2G 0 part /var/log
├─sda11 8:11 0 10G 0 part /var/log/audit
├─sda12 8:12 0 16G 0 part /tmp
├─sda13 8:13 0 12G 0 part /opt
└─sda14 8:14 0 606.6G 0 part
sr0 11:0 1 1.6G 0 rom

(cmsr21)-(root)=# onstat -d

HCL Informix Dynamic Server Version 14.10.FC10W2 -- On-Line -- Up 02:10:19 -- 17076588 Kbytes
2024-11-21 14:40:44

Dbspaces
address number flags fchunk nchunks pgsize flags owner name
454cf028 1 0x4030001 1 1 2048 N BA informix rootdbs
454d0c50 2 0x4030001 2 1 2048 N BA informix physdbs
447f4d028 3 0x4020001 3 1 2048 N BA informix logdbs
447f4d270 4 0x4020001 4 1 8192 N BA informix dbtemp
447f4d4b8 5 0x4020001 5 1 8192 N BA informix cmsdbs
5 active, 2047 maximum

Chunks
address chunk/dbs offset size free bpages flags pathname
454cf270 1 1 0 128000 107070 PO-B-- /cmsdisk
447f4e028 2 2 128000 327680 0 PO-B-- /cmsdisk
447f4f028 3 3 455680 65536 0 PO-B-- /cmsdisk
447f50028 4 4 521216 655360 655307 PO-B-- /cmsdisk
447f51028 5 5 3142656 78593280 77555028 PO-B-- /cmsdisk
5 active, 32766 maximum

Cause:

This problem is caused by a defect in the R21 version of dbinit.sh utility (add_disks function). The defect results in a small chunk being added, leaving the rest of the disk unused.

Solution:

**Baseload Procedures should be followed. CMS and IDS should be turned off before installing patch.

As a short term solution, until this issue is resolved in the next CMS R21 update, copy the provided file to the R21 CMS servers where you need to do add_disks and run it as root, e.g., assuming you copied it to /tmp

• (cmsr21)-(root)=# sh /tmp/CMS-8923.patch

The patch script contains one file: /opt/informix/bin/dbinit.sh.

After applying the patch, please verify the MD5 sum of dbinit.sh, ie,

• (cmsr21)-(root)=# md5sum /opt/informix/bin/dbinit.sh It should be: ca7732496df25aa07b85a4636a3e4620

NOTE: the installation of this CMS patch does not requires a restart of CMS.

The patch script is available here: - CMS R21 CMS-8923 Patch (CMS-8923.patch)

Manufacturer Release notes:

PSN006319u - https://support.avaya.com/css/public/documents/101091283

Disclaimer: intlx Solutions Knowledge Base

The information contained in this knowledge base ("Content") is provided for informational purposes only and is intended to be a general resource. intlx Solutions does not guarantee the accuracy, completeness, or timeliness of the Content.

Use at Your Own Risk: By accessing and using the Content, you agree that you do so at your own risk. intlx Solutions assumes no responsibility for any errors or omissions in the Content, nor for any damages or losses you may suffer arising out of or related to the use of the Content.

Current Customers: If you are a current intlx Solutions customer and have questions or require further clarification on any information presented here, please do not hesitate to contact our support team directly. They are available to assist you and ensure you have the most up-to-date information specific to your needs.

Not a Customer? If you are not currently an intlx Solutions customer but are interested in learning more about our solutions and how we can help your business, please click here. We look forward to the opportunity to discuss your needs and explore how a partnership with intlx Solutions can benefit you.

Thank you for your understanding.

This article contains data that is aimed at helping fix an issue with a product. Please use this information at your own risk as intlx Solutions is not responsible for actions taken by the steps or procedures shown in these articles.