Results 1 to 8 of 8
  1. #1
    Join Date
    Nov 2008
    Posts
    15

    Unanswered: SQL6048N message from DB2 V8.1 on HP-UX 11i

    So, when I try to start our DB2 V8.1 instance, I get this message:

    $ db2start
    SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing.
    $

    When I look at the tail end of db2diag.log, I see a TON of entries like this:

    Code:
    2008-11-11-14.54.48.151514-300 I1670728890C356    LEVEL: Severe
    PID     : 27478                TID  : 1           PROC : db2fm
    INSTANCE: db2inst8             NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
    MESSAGE : DiagData
    DATA #1 : Hexdump, 4 bytes
    0x7F7F95E8 : FFFF E860                                  ...`
    Any ideas on what's going on?

    Thanks in advance for your time!

    Peace...

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Check if the port defined in SVCENAME is not occupied by something else. However, the log entries written right after the db2start command would be more relevant...
    ---
    "It does not work" is not a valid problem statement.

  3. #3
    Join Date
    Nov 2008
    Posts
    15
    Thanks. Where is SVCENAME defined?

    EDIT: I move the old db2diag.log file to a new file name so I could get a new log file created and this is what the new log file has in it after I issue the db2start command:

    Code:
    2008-11-11-16.18.50.557626-300 I1A1265            LEVEL: Event
    PID     : 5241                 TID  : 1           PROC : db2fm
    INSTANCE: db2ins64             NODE : 000
    FUNCTION: DB2 UDB, RAS/PD component, _pdlogInt, probe:120
    START   : New db2diag.log file
    DATA #1 : Build Level, 144 bytes
    Instance "db2ins64" uses "64" bits and DB2 code release "SQL08023"
    with level identifier "03040106".
    Informational tokens are "DB2 v8.1.0.96", "s050811", "U803922", FixPak "10".
    DATA #2 : System Info, 104 bytes
    System: HP-UX usmghuhp B.11.11 U 9000/800
    CPU: total:1 online:1 Threading degree per core:1
    Physical Memory(MB): total:1536 free:1189
    Virtual  Memory(MB): total:4608 free:4261
    Swap     Memory(MB): total:3072 free:3072
    Kernel   Params: msgMaxMessageSize:65535 msgMsgMap:2050 msgMaxQueueIDs:1024
                     msgNumberOfHeaders:2048 msgMaxQueueSize:65535
                     msgMaxSegmentSize:16 shmMax:1073741824 shmMin:1 shmIDs:1000
                     shmSegments:120 semMap:2050 semIDs:2048 semNum:4096
                     semUndo:1024 semNumPerID:2048 semOps:500 semUndoPerProcess:10
                     semUndoSize:104 semMaxVal:32767 semAdjustOnExit:16384
    Information in this record is only valid at the time when this file was
    created (see this record's time stamp)
    
    2008-11-11-16.18.50.469182-300 I1267A364          LEVEL: Severe
    PID     : 5241                 TID  : 1           PROC : db2fm
    INSTANCE: db2ins64             NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
    MESSAGE : DiagData
    DATA #1 : Hexdump, 4 bytes
    0x800003FFFF7F99F0 : FFFF E860                                  ...`
    
    2008-11-11-16.19.03.149849-300 I1632A364          LEVEL: Severe
    PID     : 5305                 TID  : 1           PROC : db2fm
    INSTANCE: db2ins64             NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
    MESSAGE : DiagData
    DATA #1 : Hexdump, 4 bytes
    0x800003FFFF7F99F0 : FFFF E860                                  ...`
    I've got a 32-bit DB2 V8 install and a 64-bit install and I get teh SQL6048N message regardless of running the 32-bit or 64-bit versions.

    Here is the db2diag.log file from the 32-bit instance:
    Code:
    2008-11-11-16.23.48.489059-300 I1C1265            LEVEL: Event
    PID     : 6420                 TID  : 1           PROC : db2fm
    INSTANCE: db2inst8             NODE : 000
    FUNCTION: DB2 UDB, RAS/PD component, _pdlogInt, probe:120
    START   : New db2diag.log file
    DATA #1 : Build Level, 124 bytes
    Instance "db2inst8" uses "32" bits and DB2 code release "SQL08023"
    with level identifier "03040106".
    Informational tokens are "DB2 v8.1.0.96", "s050811", "U803922", FixPak "10".
    DATA #2 : System Info, 100 bytes
    System: HP-UX usmghuhp B.11.11 U 9000/800
    CPU: total:1 online:1 Threading degree per core:1
    Physical Memory(MB): total:1536 free:1196
    Virtual  Memory(MB): total:4608 free:4268
    Swap     Memory(MB): total:3072 free:3072
    Kernel   Params: msgMaxMessageSize:65535 msgMsgMap:2050 msgMaxQueueIDs:1024
                     msgNumberOfHeaders:2048 msgMaxQueueSize:65535
                     msgMaxSegmentSize:16 shmMax:1073741824 shmMin:1 shmIDs:1000
                     shmSegments:120 semMap:2050 semIDs:2048 semNum:4096
                     semUndo:1024 semNumPerID:2048 semOps:500 semUndoPerProcess:10
                     semUndoSize:104 semMaxVal:32767 semAdjustOnExit:16384
    Information in this record is only valid at the time when this file was
    created (see this record's time stamp)
    
    2008-11-11-16.23.48.487708-300 I1267C356          LEVEL: Severe
    PID     : 6420                 TID  : 1           PROC : db2fm
    INSTANCE: db2inst8             NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:32
    MESSAGE : DiagData
    DATA #1 : Hexdump, 4 bytes
    0x7F7F95E8 : FFFF E860                                  ...`
    Thanks!
    Peace...
    Last edited by TomWilliams; 11-11-08 at 17:29.

  4. #4
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by TomWilliams
    Thanks. Where is SVCENAME defined?
    db2 get dbm cfg | grep SVCENAME

    It most likely refers to an entry in /etc/services
    ---
    "It does not work" is not a valid problem statement.

  5. #5
    Join Date
    Nov 2008
    Posts
    15
    Thanks. I found that command out doing a Google search. Unfortunately, when I issue that command I get no output:

    Code:
    $ db2 get dbm cfg | grep SVCENAME
    $ db2 get dbm cfg
    SQL6048N  A communication error occurred during START or STOP DATABASE MANAGER
    processing.
    $

    Something else I've noticed is something continues to write to db2diag.log after the commands I've entered have terminated.

    I'm going to reboot the box now and see which DB2 processes start when the system boots and I'll post that list here.

    Peace...

  6. #6
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Ah. Try ipclean first.

    Edit: not sure what is the similar thing on HP/UX
    ---
    "It does not work" is not a valid problem statement.

  7. #7
    Join Date
    Nov 2008
    Posts
    15
    I see "ipclean" is available for DB2 on AIX and when my system comes back up, I'll see if it's availabe for HP-UX too.

    Thanks!

    Peace...

  8. #8
    Join Date
    Nov 2008
    Posts
    15
    Ok, I got the instance to start!!!!! I found this article:

    http://www.walkernews.net/2007/09/07...r-of-db2start/

    On that page, here is the line that helped the most:

    Ensure that all the host names defined in the db2nodes.cfg file in the sqllib directory are defined on the network and are running.
    The db2nodes.cfg file had the OLD hostname of the system specified and the new hostname wasn't listed. I added the hostname in the db2nodes.cfg file to the local hosts file and the 32-bit V8 instance started just fine!

    Thanks!

    Peace...

Posting Permissions

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