Results 1 to 2 of 2
  1. #1
    Join Date
    Aug 2009
    Posts
    12

    Unanswered: problem in creating instance

    Hi Guys,
    I am having problems while creating a Db2 instance.
    I have installed Db2 on linux but when I try to create an instance I get below error. Need your help in resolving the same. Error has something to do with entries in /etc/services or .rhosts or db2nodes.cfg file.
    I always thought that entires for db2instance automatically comes in /etc/services files when we create instance. :-(

    [root@aaaaaaaaa instance]# ./db2icrt -u db2fenc1 db2inst1
    /opt/ibm/db2/V9.5/instance/db2iutil: line 4700: 30757 Segmentation fault ${DB2DIR?}/instance/db2isrv -addfcm -i ${INSTNAME?}

    2009-09-16-07.27.52.452148+120 I1G1284 LEVEL: Event
    PID : 31149 TID : 3047933632 PROC : db2bp
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
    START : New Diagnostic Log file
    DATA #1 : Build Level, 128 bytes
    Instance "db2inst1" uses "32" bits and DB2 code release "SQL09050"
    with level identifier "03010107".
    Informational tokens are "DB2 v9.5.0.0", "s071001", "LINUXIA3295", Fix Pack "0".
    DATA #2 : System Info, 436 bytes
    System: Linux aaaaaaaaa.vpndev.local 6 2 i686
    CPU: total:4 online:4 Cores per socket:1 Threading degree per core:2
    Physical Memory(MB): total:3043 free:119
    Virtual Memory(MB): total:8099 free:5175
    Swap Memory(MB): total:5056 free:5056
    Kernel Params: msgMaxMessageSize:65536 msgMsgMap:65536 msgMaxQueueIDs:16
    msgNumberOfHeaders:65536 msgMaxQueueSize:65536
    msgMaxSegmentSize:16 shmMax:4294967295 shmMin:1 shmIDs:4096
    shmSegments:4096 semMap:32000 semIDs:128 semNum:32000
    semUndo:32000 semNumPerID:250 semOps:32 semUndoSize:20
    semMaxVal:32767 semAdjustOnExit:32767
    Information in this record is only valid at the time when this file was
    created (see this record's time stamp)

    2009-09-16-07.27.52.451692+120 I1286G699 LEVEL: Severe
    PID : 31149 TID : 3047933632 PROC : db2bp
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
    MESSAGE : ZRC=0xFFFFE860=-6048
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6048 sqlerrml: 0
    sqlerrmc:
    sqlerrp : SQLFRCFG
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

    2009-09-16-07.27.52.454187+120 I1986G319 LEVEL: Severe
    PID : 31149 TID : 3047933632 PROC : db2bp
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, command line process, clp_bp_main, probe:2
    DATA #1 : Hexdump, 4 bytes
    0xBFB303A8 : 60E8 FFFF `...

    2009-09-16-07.28.00.501378+120 I2306G699 LEVEL: Severe
    PID : 31158 TID : 3086612688 PROC : db2fm
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
    MESSAGE : ZRC=0xFFFFE860=-6048
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6048 sqlerrml: 0
    sqlerrmc:
    sqlerrp : SQLFRCFG
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

    2009-09-16-07.28.10.699152+120 I3006G699 LEVEL: Severe
    PID : 31260 TID : 3086543056 PROC : db2fm
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
    MESSAGE : ZRC=0xFFFFE860=-6048
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6048 sqlerrml: 0
    sqlerrmc:
    sqlerrp : SQLFRCFG
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

    2009-09-16-07.28.20.879750+120 I3706G699 LEVEL: Severe
    PID : 31361 TID : 3086579920 PROC : db2fm
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
    MESSAGE : ZRC=0xFFFFE860=-6048
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6048 sqlerrml: 0
    sqlerrmc:
    sqlerrp : SQLFRCFG
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

    2009-09-16-07.28.31.072693+120 I4406G699 LEVEL: Severe
    PID : 31462 TID : 3086010576 PROC : db2fm
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
    MESSAGE : ZRC=0xFFFFE860=-6048
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6048 sqlerrml: 0
    sqlerrmc:
    sqlerrp : SQLFRCFG
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

    2009-09-16-07.28.41.258161+120 I5106G699 LEVEL: Severe
    PID : 31565 TID : 3085899984 PROC : db2fm
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
    MESSAGE : ZRC=0xFFFFE860=-6048
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6048 sqlerrml: 0
    sqlerrmc:
    sqlerrp : SQLFRCFG
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

    2009-09-16-07.28.51.430147+120 I5806G699 LEVEL: Severe
    PID : 31666 TID : 3086641360 PROC : db2fm
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
    MESSAGE : ZRC=0xFFFFE860=-6048
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6048 sqlerrml: 0
    sqlerrmc:
    sqlerrp : SQLFRCFG
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

    2009-09-16-07.28.52.481313+120 I6506G375 LEVEL: Error
    PID : 31147 TID : 2019152 PROC : db2
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, command line process, clp_start_bp, probe:3
    MESSAGE : CLP frontend unable to get REQUEST queue handle
    DATA #1 : Hexdump, 4 bytes
    0xBF8AD2C8 : 4200 0F87 B...
    DBI1281E The database manager configuration file could not be
    initialized.

    Explanation:

    An error occurred when attempting to initialize the database manager
    configuration file. A DB2 instance could not be created or migrated.

    User response:

    Refer to the log file for troubleshooting. Resolve the problem and try
    the command again. If the problem persists, please contact IBM Support.




    DBI1079I Output is saved in the log file /tmp/db2icrt.log.30106.

    Explanation:

    All processed and failed operations have been saved into this log file.

    User response:

    Do not modify this file in any way. This file is for IBM Technical
    Support reference.

    ================================================== ======================

    [root@aaaaaaaaa instance]# cat /tmp/db2icrt.log.30106
    Program name = db2idbm
    Instance home dir = /db2home/db2inst1, Sysadm group = db2iadm1
    Instance type = 1, Auth type = SERVER

    SQL6048N A communication error occurred during START or STOP DATABASE MANAGER
    processing.
    Update DBM cfg SYSADM_GROUP errcode = 8
    DBI1281E The database manager configuration file could not be
    initialized.

    Explanation:

    An error occurred when attempting to initialize the database manager
    configuration file. A DB2 instance could not be created or migrated.

    User response:

    Refer to the log file for troubleshooting. Resolve the problem and try
    the command again. If the problem persists, please contact IBM Support.




    DBI1079I Output is saved in the log file /tmp/db2icrt.log.30106.

    Explanation:

    All processed and failed operations have been saved into this log file.

    User response:

    Do not modify this file in any way. This file is for IBM Technical
    Support reference.

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Just curious as to the following:

    1. Do you really want 32-bit Linux?
    2. Why didn't you specify the port in the db2icrt command (-p option)?
    3. Why are you installing Fix Pack 0? You can install the latest fixpack and then just apply the license from the original media you have.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •