Arctera

In an IPv6 environment, db2icrt and db2idrop commands return a segmentation fault error during instance creation and instance removal (1602444)

When using IBM DB2 db2icrt command to create a DB2 database instance on a pure IPv6 environment, the db2icrt command returns segmentation fault error message. For example:

$ /opt/ibm/db2/V9.5/instance/db2icrt -a server -u db2fen1 db2inst1
/opt/ibm/db2/V9.5/instance/db2iutil: line 4700: 26182 Segmentation fault
$ {DB2DIR?}/instance/db2isrv -addfcm -i ${INSTNAME?}
<!--NeedCopy-->

The db2idrop command also returns segmentation fault, but the instance is removed successfully after the db2idrop command is issued. For example:

$ /opt/ibm/db2/V9.5/instance/db2idrop db2inst1 
/opt/ibm/db2/V9.5/instance/db2iutil: line 3599:  7350 Segmentation fault      
$ {DB2DIR?}/instance/db2isrv -remove -s DB2_${INSTNAME?} 2> /dev/null

DBI1070I  Program db2idrop completed successfully.
<!--NeedCopy-->

This happens on DB2 9.1, 9.5, and 9.7.

This issue has been identified as an IBM issue. Once IBM has fixed this issue, then IBM will provide a hotfix for this segmentation problem.

At this time, you can communicate in a dual-stack to avoid the segmentation fault error message until IBM provides a hotfix.

To communicate in a dual-stack environment

  1. Add an IPv6 hostname as an IPv4 loopback address to the /etc/hosts file. For example:

    Or

    127.0.0.1 is the IPv4 loopback address.

    swlx20-v6 and swlx20-v6.punipv6.com are the IPv6 hostnames.

   127.0.0.1 swlx20-v6
   <!--NeedCopy-->
   127.0.0.1 swlx20-v6.punipv6.com
   <!--NeedCopy-->
In an IPv6 environment, db2icrt and db2idrop commands return a segmentation fault error during instance creation and instance removal (1602444)

In this article