Results 1 to 7 of 7
  1. #1
    Join Date
    Jun 2007
    Posts
    12

    Unanswered: v8 instance creation hangs on solaris 10

    I'm trying to create a v8 instance on a Solaris 10 container, and the creation process is halting while db2flacc is being run. I've let db2flacc run for 48 hours, but it never does any more than sitting there soaking up cpu cycles.
    Has anyone seen anything similar, or know if there's a solution to this?
    I've ensured that passwords and permissions are correct, and I've been able to create v7 instances on the same container.
    Following advice I've found online, I've also reset permissions as follws

    chmod g+s db2flacc
    chmod u+s db2aud

    then su to root and do:

    chmod ug+s db2ckpw

    but this didn't help.
    I would appreciate any suggestions anyone has to offer.
    I'm running V8 FP13 on Solaris 10 update 3

  2. #2
    Join Date
    Jan 2008
    Posts
    88
    not to sure but what is the command you are firing...
    and which edition of db2 u using...is there any error message in diag log

  3. #3
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    I would suggest to undo any changes to the permissions on DB2 executables. If you're in doubt whether the permissions have been tempered with, re-install the FixPak.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  4. #4
    Join Date
    Jun 2007
    Posts
    12
    I am running DB2 UDB2 V8.2, and the command is ./db2icrt -u db2inst3 db2inst3
    There are no errors in db2diag.log, since no instance is ever created.

    I have reinstalled DB2 and the fixpak twice. The current installation has had no modifications made to permissions.

    I have been digging further and discovered the following in an instance creation log file:
    --------------------------------------------------------------

    Program name = db2idbm
    Instance home dir = /oanda/db2inst3, Sysadm group = db2inst1
    Instance type = 1, Auth type = SERVER

    SQL1042C An unexpected system error occurred. SQLSTATE=58004
    Update DBM cfg SYSADM_GROUP errcode = 4
    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 problem determination. Resolve the
    problem and try the command again. If the problem persists,
    please contact IBM Support.
    ------------------------------------------------

    This is leading to new avenues of investigation which I am now pursuing.

  5. #5
    Join Date
    Jun 2007
    Posts
    12
    problem resolved - the machine name in /etc/hosts was not fully qualified.
    How's that for an intuitive error message?
    But thanks to everyone who gave this some thought.

  6. #6
    Join Date
    Jan 2008
    Posts
    88
    I didnt get what the /etc/hosts file has to do with instance creation

  7. #7
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    I could imagine that DB2 tries to initialize the db2nodes.cfg file by referring to /etc/hosts. Maybe it tries to look up the host names in there for some purposes, and without a matching /etc/resolv.conf or fully qualified names, the name resolution fails, resulting in the "internal error".

    p.s: Surely not a helpful error message at all...
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

Posting Permissions

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