pajama

An assertion failure occurs when the database server cannot continue normal processing and must shut down. You can correct some of the problems that cause assertion failures, such as disk issues. For other problems that cause assertion failures, you must contact IBM® Software Support.

To correct an assertion failure:

1. Look at the online log for the assertion failure message.
   The location of the online log is specified by the MSGPATH configuration parameter. Default:

   • UNIX: $INFORMIXDIR/tmp/online.log
   • Windows: %INFORMIXDIR%\online.log
2. Perform any action mentioned in the assertion failure message. For example, you might need to run an oncheck command or increase the size of the physical or logical log buffer.
   The following table lists the common types of assertion failures and what you can do to correct the underlying problems.

   Table 1. Common types of assertion failures.

   Error	Cause	Solutions
   bfcheck	Corrupted data page, index, or partition page	Run the oncheck command in the assertion failure message. If an index is corrupted, drop and recreate the index. If a partition page is corrupted, you might need to restore the data.
   I/O write chunk	Not enough shared memory or a hardware problem	Look at your operating system logs for hardware problems or problems with other software. Sometimes other software can trigger an Informix® assertion failure. Fix any hardware or other software problems. Free up or increase shared memory for the database server.
   No exception handler	Memory corruption	Look at your operating system logs for hardware problems or problems with other software. Fix any hardware or other software problems.
   sigkill	The oninit daemon was stopped.	Restart the database server.
   segv sigbus	Memory corruption An ill-behaved C user-defined routine A defect in the database server	Look at your operating system logs for hardware problems or problems with other software. Fix any hardware or other software problems. If you use C user-defined routines, check your code for problems. Make sure that your user-defined routines follow the guidelines for well-behaved routines. If you are not running the latest Informix fix pack, check the latest Fixed and known defects file to see whether this issue is fixed. Upgrade to the latest Informix fix pack.

3. Restart the database server. Some assertion failures can be solved by the database server during startup.
4. If the database server does not start or the problem recurs, collect the following files for IBM Software Support in addition to the standard list of information to gather.

   Table 2. Files for support.

   File	Location
   assertion failure files: af.xxx, where xxx is the hexadecimal number associated with the failure	Specified by the DUMPDIR configuration parameter. Default: UNIX: $INFORMIXDIR/tmp Windows: %INFORMIXDIR%\tmp
   sqlhosts file	Specified by the INFORMIXSQLHOSTS environment variable. Default: UNIX: $INFORMIXDIR/etc Windows: registry
   onconfig file	Specified by the ONCONFIG environment variable. Default: UNIX: $INFORMIXDIR/etc Windows: %INFORMIXDIR%\etc
   online log file	Specified by the MSGPATH configuration parameter. Default: UNIX: $INFORMIXDIR/tmp/online.log Windows: %INFORMIXDIR%\online.log
   shared memory dump files:shmem.xxx, where xxx is the hexadecimal number associated with the failure	Specified by the DUMPDIR configuration parameter. Default: UNIX: $INFORMIXDIR/tmp Windows: %INFORMIXDIR%\tmp Generated only if the DUMPSHMEM configuration parameter is set to 1 or 2.

5. Contact IBM Software Support.

1. Ensure that an ODBC driver manager is installed and that each user that will use ODBC has access to it. DB2 does not install an ODBC driver manager, so you must use the ODBC driver manager that was supplied with your ODBC client application or ODBC SDK in order to access DB2 data using that application.
2. Set up .odbc.ini, the end-user's data source configuration. Each user ID has a separate copy of this file in their home directory. Note that the file starts with a dot. Although necessary files are usually updated automatically by the tools on most platforms, users of ODBC on UNIX platforms will have to edit them manually.

   Using an ASCII editor, update the file to reflect the appropriate data source configuration information. To register a DB2 database as an ODBC data source there must be one stanza (section) for each DB2 database.

   The .odbc.ini file must contain the following lines (examples refer to configuration of the SAMPLE database data source):

   • in the [ODBC Data Source] stanza:

        SAMPLE=IBM DB2 ODBC DRIVER

     which indicates that there is a data source called SAMPLE that uses the IBM® DB2 ODBC DRIVER;
   • in the [SAMPLE] stanza:
     on AIX®, for example,

        [SAMPLE]
        Driver=/u/thisuser/sqllib/lib/libdb2.a
        Description=Sample DB2 ODBC Database

     on the Solaris operating system, for example,

        [SAMPLE]
        Driver=/u/thisuser/sqllib/lib/libdb2.so
        Description=Sample DB2 ODBC Database

     which indicates that the SAMPLE database is part of the DB2 instance located in the directory/u/thisuser.

     With the introduction of the 64-bit development environment, there have been a number of inconsistencies among vendors regarding the interpretation of the sizes of certain parameters. For example, the 64-bit Microsoft ODBC Driver Manager treats SQLHANDLE and SQLLEN as both 64-bits in length, whereas Data Direct Connect and open source ODBC driver managers treat SQLHANDLE as 64-bit, but SQLLEN as 32-bit. The developer must therefore pay careful attention to which version of the DB2 driver is required. Specify the appropriate DB2 driver in the data source stanza, according to the following information:

     Type of application	DB2 driver to specify
     32-bit CLI	libdb2.*
     32-bit ODBC Driver Manager	libdb2.*
     64-bit CLI	libdb2.*
     64-bit ODBC Driver Manager	libdb2o.* (db2o.o for AIX)

     Note: The file extension of the DB2 driver to specify depends on the operating system. The extensions are as follows:

     • .a - AIX
     • .so - Linux, Solaris, HP-IPF
     • .sl - HP-PA
3. Ensure that the application execution environment has reference to the ODBC driver manager by including the corresponding shared library in the environment variable for the library path. The following table indicates the library name by operating system

   Operating system	Environment variable	Library name
   AIX	LIBPATH	libodbc.a
   HP-UX, Linux, and Solaris	LD_LIBRARY_PATH	libodbc.so

4. Enable a system-wide .odbc.ini file to be used by setting the ODBCINI environment variable to the fully qualified pathname of the .ini file. Some ODBC driver managers support this feature which allows for centralized control. The following examples show how to set ODBCINI:
   in the C shell,

      setenv ODBCINI /opt/odbc/system_odbc.ini

   in the Bourne or Korn shell,

      ODBCINI=/opt/odbc/system_odbc.ini;export ODBCINI

5. Once the .odbc.ini file is set up, you can run your ODBC application and access DB2 databases. Refer to the documentation that comes with your ODBC application for additional help and information.

To set up the unixODBC Driver Manager for use with CLI and ODBC applications:

1. Download the latest unixODBC source code from http://www.unixodbc.org.
2. Untar the source files. For example:

   gzip -d unixODBC-2.2.11.tar.gz
   tar xf unixODBC-2.2.11.tar

3. For AIX® only: Configure the C compiler to be thread-enabled:

   export CC=xlc_r
   export CCC=xlC_r

4. To compile a 64-bit version of the driver manager using the xlc_r compilers, set the environment variablesOBJECT_MODE and CFLAGS:

   export OBJECT_MODE=64
   export CFLAGS=-q64 -DBUILD_REAL_64_BIT_MODE

5. Install the driver manager in either your home directory or the default /usr/local prefix:
   • (Home directory) Issue the following command in the directory where you untarred the source files:

     ./configure --prefix=$HOME -DBUILD_REAL_64_BIT_MODE --enable-gui=no 
                                        --enable-drivers=no

   • (/usr/local as root) Issue the following command:

     ./configure --enable-gui=no --enable-drivers=no

     (prefix 옵션을 생략하면 /usr/local 디렉토리를 사용한다)

6. Optional: Examine all configuration options by issuing the following command:

   ./configure --help

7. Build and install the driver manager:

   make
   make install

   Libraries will be copied to the [prefix]/lib directory, and executables will be copied to the [prefix]/bindirectory.
8. For AIX only: Extract the shared library from the ODBC driver for DB2® to yield shr.o on 32-bit operating systems and shr_64.o on 64-bit operating systems. To avoid confusion, rename the files db2.o and db2_64.o, respectively. These steps are necessary on AIX because the unixODBC Driver Manager loads the driver dynamically.
   • On 32-bit operating systems, issue the following commands:

     cd INSTHOME/sqllib/lib
     ar -x libdb2.a
     mv shr.o db2.o

     where INSTHOME is the home directory of the instance owner.
   • On 64-bit operating systems, issue the following commands:

     cd INSTHOME/sqllib/lib
     ar -x -X 64 libdb2.a
     mv shr_64.o db2_64.o

     where INSTHOME is the home directory of the instance owner.
   Ensure that your INI file references the correct library.
9. Optional: For AIX only: Extract libodbc.a, libodbcinst.a, and libodbccr.a if you will be dynamically loading the driver manager: (명령을 수행하기 전에 OBJECT_MODE 환경변수가 설정되어 있는지 확인한다)

   ar -x libodbc.a
   ar -x libodbcinst.a
   ar -x libodbccr.a 

   This produces libodbc.so.1, libodbcinst.so.1, and libodbccr.so.1 respectively in the [prefix]/lib/so directory. (파일확장자는 unixODBC 버전에 따라 달라질 수 있다)
10. Build the application and ensure it is linked to the unixODBC Driver Manager by including the -L[prefix]/lib -lodbc option in the compile and link command.
11. Specify the paths for at least the user INI file (odbc.ini) or the system INI file (odbcinst.ini), and set the ODBCHOME environment variable to the directory where the system INI file was created.
    Important: Provide absolute paths when specifying the paths of the user and system INI files. Do not use relative paths or environment variables.
    Note: If compiling 64-bit applications for the ODBC Driver, use the -DODBC64 option to enable the 64-bit definitions in the driver manager.