Page 1 of 2 12 LastLast
Results 1 to 15 of 20
  1. #1
    Join Date
    Nov 2010
    Posts
    10

    Unanswered: DB2 Administrator Priviledges in Windows 7

    Hello,

    I tried to install Websphere Message Broker v 6.1 on Windows 7 Professional, I am able to install WMB 6.1, WMQ, DB2 8.2 individually, but when I tried to do default configuration of database, it gave me error saying,
    ------------------------------------------------------------------------
    Task: Creating the database [DEFBKD61] for the default broker. failed
    If you can manually fix the issues that caused this task to fail, do so and then click Yes.
    If you click Yes, the wizard starts the task again.

    If you click No, the wizard rolls back all completed tasks, if roll-back is possible.

    To establish why the task failed, examine this wizard's log file which can be found in the workspace
    directory [C:\Users\****\IBM\wmbt61\workspace\.metadata].
    -------------------------------------------------------------------------
    I also tried to create default database, but was declined by the user permission, I have already added user in Administration perspective in all domains.

    I also tried to use "db2 drop database DEFBKD61, but this command is also giving me error SQL1092N, "User does not have the authority to perform the requested command.

    I also used db2set DB2_GRP_LOOKUP = TOKEN and TOKENLOCAL, but still getting the same error.

    So, could you please let me know how to set DB2 admin properties of user, so that the user can be able to create the default database? (my user name is default "db2admin" which is added in "DB2ADMNS" and "DB2USERS" groups).

    I appreciate your time and solution. Thank You.

  2. #2
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    have you updated dbm cfg for sysadmin group with DB2ADMNS
    once this is done you are sysadmin
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified
    http://www.infocura.be

  3. #3
    Join Date
    Nov 2010
    Posts
    10
    Thank you przytula_guy for reply. But, I do not know how to update dbm cfg for sysadmin group with DB2ADMNS. I am kind of a new bee, and do not know much in details, sorry about that. Could you please let me know how I can update dbm cfg for sysadmin group with DB2ADMNS?

  4. #4
    Join Date
    Nov 2010
    Posts
    10

    neffes tivation

    Hi przytula_guy,

    I tried following commands but got error while performing the commands.

    I issued,

    db2stop - gave me error saying
    "SQL1025N the database manager was not stopped because databases are still active."

    I still ran the command

    db2 update DBM CFG USING SYSADM_GROUP DB2ADMNS

    the command completed successfully,

    and then I tried

    db2start and it gave me error saying
    "sql1042c no start database manager command was issues. SQLSTATE = 57019"

    I restarted the computer and tried to do the same thing it is giving me same error.

    I also tried to go to Administrative Tools -> Services and tried to start DB2 - DB2-0 but it also gives me error saying "Windows could not start the DB2 - DB2-0 on Local Computer.For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code - 1042."

    So, could you please help me identify the issue. What are the next steps I need to follow?

    Thank You.

  5. #5
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Check what is in the DB2 diagnostic log. For example, perform these steps
    - rotate the log by running "db2diag -A"
    - try "db2start"
    - after the failure run "db2diag" without any parameters and check what it says about the error.

    What login ID is used to run the DB2 service?

  6. #6
    Join Date
    Nov 2010
    Posts
    10
    Hello n_i,

    please see the snapshot of the error description. It is something like this

    --------------------------------------------------------------------------
    2010-11-17-16.17.36.700000-300 E9364H396 LEVEL: Error (OS)
    PID : 3360 TID : 3716 PROC : db2fmp.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
    CALLED : OS, -, unspecified_system_function OSERR: 6
    RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
    Invalid parameter

    db2diag invoked with the default set of filtering/formatting options
    on file "C:\PROGRA~1\IBM\SQLLIB\DB2\db2diag.log".
    Enter "db2diag -h" to get a short description of all available options.
    --------------------------------------------------------------------------

    What should I do now?

    The userId used is "db2admin" created by default with the installation of DB2.
    Attached Thumbnails Attached Thumbnails ScreenHunter_01 Nov. 17 16.18.gif  

  7. #7
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    "Something like" doesn't help much. If you are unable to figure out what is the root cause of the error you will need to post the db2diag.log contents from the very moment db2start is issued.

  8. #8
    Join Date
    Nov 2010
    Posts
    10
    It is exactly what I posted
    shows this error

    --------------------------------------------------------------------------
    2010-11-17-16.17.36.700000-300 E9364H396 LEVEL: Error (OS)
    PID : 3360 TID : 3716 PROC : db2fmp.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
    CALLED : OS, -, unspecified_system_function OSERR: 6
    RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
    Invalid parameter

    db2diag invoked with the default set of filtering/formatting options
    on file "C:\PROGRA~1\IBM\SQLLIB\DB2\db2diag.log".
    Enter "db2diag -h" to get a short description of all available options.
    --------------------------------------------------------------------------

    unable to figure out what is the cause for this.

  9. #9
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by aj2307 View Post
    It is exactly what I posted
    No it is not. It should look more like this (note the db2start command):
    Code:
    2010-11-17-13.36.07.859000-300 I1H950             LEVEL: Event
    PID     : 6844                 TID  : 7776        PROC : db2diag.exe
    INSTANCE: DB2                  NODE : 000
    EDUID   : 7776
    FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
    START   : New Diagnostic Log file
    DATA #1 : Build Level, 128 bytes
    Instance "DB2" uses "32" bits and DB2 code release "SQL09073"
    with level identifier "08040107".
    Informational tokens are "DB2 v9.7.300.270", "s100811", "IP23093", Fix Pack "3".
    DATA #2 : System Info, 1564 bytes
    System: WIN32_NT XXXX Service Pack 3 5.1 x86 Family 6, model 23, stepping 10
    CPU: total:2 online:2 Cores per socket:2 Threading degree per core:1
    Physical Memory(MB): total:3002 free:1311 available:1311
    Virtual  Memory(MB): total:4889 free:3106
    Swap     Memory(MB): total:1887 free:1795
    Information in this record is only valid at the time when this file was
    created (see this record's time stamp)
    
    2010-11-17-13.58.45.171000-300 I1371H327          LEVEL: Event
    PID     : 704                  TID  : 7448        PROC : db2start.exe
    INSTANCE: DB2                  NODE : 000
    EDUID   : 7448
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:21
    DATA #1 : <preformatted>
    Single node instance [0] is starting
    
    2010-11-17-13.58.45.234000-300 I1700H1553         LEVEL: Event
    PID     : 704                  TID  : 7448        PROC : db2start.exe
    INSTANCE: DB2                  NODE : 000
    EDUID   : 7448
    FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
    DATA #1 : String, 39 bytes
    C:\PROGRA~1\IBM\SQLLIB\bin\DB2STAR2.EXE
    DATA #2 : Hexdump, 256 bytes
    0x00137624 : 433A 5C50 524F 4752 417E 315C 4942 4D5C    C:\PROGRA~1\IBM\
    0x00137634 : 5351 4C4C 4942 5C62 696E 5C44 4232 5354    SQLLIB\bin\DB2ST
    0x00137644 : 4152 322E 4558 4500 4E4F 4D53 4700 0000    AR2.EXE.NOMSG...
    0x00137654 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
    0x00137664 : 0000 0000 0000 0000 0000 0000 0000 0000    ................

  10. #10
    Join Date
    Nov 2010
    Posts
    10
    Sorry, I got it now, it is as below:

    2010-11-17-16.08.06.997000-300 I1H848 LEVEL: Event
    PID : 5544 TID : 5156 PROC : db2stop.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, RAS/PD component, _pdlogInt, probe:120
    START : New db2diag.log file
    DATA #1 : Build Level, 124 bytes
    Instance "DB2" uses "32" bits and DB2 code release "SQL08020"
    with level identifier "03010106".
    Informational tokens are "DB2 v8.1.7.445", "s040812", "WR21342", FixPak "7".
    DATA #2 : System Info, 1304 bytes
    System: WIN32_NT AJAY-PC 6.1 x86 Family 6, model 23, stepping 10
    CPU: total:2 online:2
    Physical Memory: total:3033 free:1904 available:1904
    Virtual Memory: total:6065 free:4778
    Swap Memory: total:3032 free:2874
    Information in this record is only valid at the time when this file was
    created (see this record's time stamp)

    2010-11-17-16.08.06.994000-300 I852H294 LEVEL: Error
    PID : 5544 TID : 5156 PROC : db2stop.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqlePrintFinalMessage, probe:10
    RETCODE : ZRC=0x00000000=0=PSM_OK "Unknown"

    2010-11-17-16.08.13.988000-300 I1148H320 LEVEL: Event
    PID : 2828 TID : 5704 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
    CHANGE : CFG DBM: "Instance_Memory" <automatic> From: "6504" To: "6504"

    2010-11-17-16.08.14.101000-300 E1470H937 LEVEL: Warning
    PID : 2828 TID : 5704 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, LicCheckProcessors, probe:20
    MESSAGE : ADM12017E The number of processors on this machine exceeds the
    defined entitlement of "1" for the product "DB2 Enterprise Server
    Edition". The number of processors on this machine is "2". You should
    purchase additional processor based entitlements from your IBM
    representative or authorized dealer and update your license using the
    License Center or the db2licm command line utility. For more
    information on updating processor based licenses, refer to the Quick
    Beginnings manual for your platform. For more information on the
    db2licm utility, refer to the DB2 Command Reference.

    2010-11-17-16.08.36.654000-300 E2409H396 LEVEL: Error (OS)
    PID : 3360 TID : 3716 PROC : db2fmp.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
    CALLED : OS, -, unspecified_system_function OSERR: 6
    RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
    Invalid parameter

    2010-11-17-16.08.36.661000-300 E2807H396 LEVEL: Error (OS)
    PID : 3360 TID : 3716 PROC : db2fmp.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
    CALLED : OS, -, unspecified_system_function OSERR: 6
    RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
    Invalid parameter

    2010-11-17-16.09.54.842000-300 I3205H683 LEVEL: Severe
    PID : 2828 TID : 4068 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerInitFmpHeap, probe:60
    MESSAGE : Failed to create the memory segment used for communication with
    fenced routines. If re-starting db2, ensure no db2fmp processes were
    on the instance prior to start. Otherwise, you can ajust this value
    through DB2_FMP_COMM_HEAPSZ db2set value, or by decreasing your
    ASLHEAPSZ setting.
    DATA #1 : Hexdump, 4 bytes
    0x00BBFAA0 : 8084 5E01 ..^.

    2010-11-17-16.09.54.846000-300 E3890H678 LEVEL: Error
    PID : 2828 TID : 4068 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerInitFmpHeap, probe:60
    MESSAGE : ADM11003E DB2 failed to create the memory segment used for
    communication with fenced routines. If restarting DB2, ensure that no
    db2fmp processes are active on the instance prior to start. Otherwise,
    you can adjust the value through the DB2_FMP_COMM_HEAPSZ registry
    variable, or you can decrease the value of ASLHEAPSZ in the database
    manager configuration.

    2010-11-17-16.09.54.860000-300 I4570H357 LEVEL: Severe
    PID : 2828 TID : 4068 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloRunInstance, probe:80
    MESSAGE : DiagData
    DATA #1 : Hexdump, 4 bytes
    0x00BBFB88 : EEFB FFFF ....

    2010-11-17-16.09.54.876000-300 I4929H348 LEVEL: Severe
    PID : 2828 TID : 4068 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:115
    MESSAGE : DiagData
    DATA #1 : Hexdump, 4 bytes
    0x00BBFDE8 : EEFB FFFF ....

    2010-11-17-16.09.54.902000-300 I5279H359 LEVEL: Severe
    PID : 2828 TID : 5412 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleCleanupResources, probe:5
    MESSAGE : DiagData
    DATA #1 : Hexdump, 4 bytes
    0x0006FDA0 : 0000 0000 ....

    2010-11-17-16.09.54.904000-300 I5640H435 LEVEL: Severe
    PID : 2828 TID : 5412 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleCleanupResources, probe:10
    MESSAGE : DiagData
    DATA #1 : Hexdump, 20 bytes
    0x00415AFC : 496E 7374 616E 6365 206E 6F74 2061 6374 Instance not act
    0x00415B0C : 6976 6500 ive.

    2010-11-17-16.09.54.915000-300 I6077H635 LEVEL: Error
    PID : 4588 TID : 4548 PROC : db2start.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloStartDB2Service, probe:50
    DATA #1 : Hexdump, 66 bytes
    0x00129ED8 : 4442 322D 3020 3A20 5468 6520 7365 7276 DB2-0 : The serv
    0x00129EE8 : 6963 6520 6861 7320 7265 7475 726E 6564 ice has returned
    0x00129EF8 : 2061 2073 6572 7669 6365 2D73 7065 6369 a service-speci
    0x00129F08 : 6669 6320 6572 726F 7220 636F 6465 2E0D fic error code..
    0x00129F18 : 0A0A ..

    2010-11-17-16.09.54.925000-300 I6714H658 LEVEL: Severe
    PID : 4588 TID : 4548 PROC : db2start.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:70
    MESSAGE : DiagData
    DATA #1 : Hexdump, 66 bytes
    0x0012A53C : 4442 322D 3020 3A20 5468 6520 7365 7276 DB2-0 : The serv
    0x0012A54C : 6963 6520 6861 7320 7265 7475 726E 6564 ice has returned
    0x0012A55C : 2061 2073 6572 7669 6365 2D73 7065 6369 a service-speci
    0x0012A56C : 6669 6320 6572 726F 7220 636F 6465 2E0D fic error code..
    0x0012A57C : 0A0A ..

    2010-11-17-16.11.36.677000-300 E7374H396 LEVEL: Error (OS)
    PID : 3360 TID : 3716 PROC : db2fmp.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
    CALLED : OS, -, unspecified_system_function OSERR: 6
    RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
    Invalid parameter

    2010-11-17-16.11.36.681000-300 E7772H396 LEVEL: Error (OS)
    PID : 3360 TID : 3716 PROC : db2fmp.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
    CALLED : OS, -, unspecified_system_function OSERR: 6
    RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
    Invalid parameter

    2010-11-17-16.13.36.688000-300 E8170H396 LEVEL: Error (OS)
    PID : 3360 TID : 3716 PROC : db2fmp.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
    CALLED : OS, -, unspecified_system_function OSERR: 6
    RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
    Invalid parameter

    2010-11-17-16.13.36.691000-300 E8568H396 LEVEL: Error (OS)
    PID : 3360 TID : 3716 PROC : db2fmp.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
    CALLED : OS, -, unspecified_system_function OSERR: 6
    RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
    Invalid parameter

    2010-11-17-16.17.36.697000-300 E8966H396 LEVEL: Error (OS)
    PID : 3360 TID : 3716 PROC : db2fmp.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
    CALLED : OS, -, unspecified_system_function OSERR: 6
    RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
    Invalid parameter

  11. #11
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    The first thing you should do is upgrade to the latest fixpack for DB2 8; I believe it's 17 or something.

  12. #12
    Join Date
    Nov 2010
    Posts
    10
    I updated the fix pack to v 18, now I am not getting error in running db2stop,
    db2 update DBM CFG USING SYSADM_GROUP DB2ADMNS, and db2start.

    But, while updating to fixpack, I got an error saying "Windows Installer" is running, close and retry, it had the process id with it, I tried to close that process using task manager and command console both, even I tried to kill the process using /F option, but despite of forced kill, it did not close and I continued the installation without stopping the process.

    I am still getting the same error while doing the default configuration for broker, and even it is not allowing me to create default database DEFBKD61 using DB2 command console.

  13. #13
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by aj2307 View Post
    even it is not allowing me to create default database DEFBKD61 using DB2 command console.
    Please copy and paste there the output of "echo %username%", "db2set -all" and "net user db2admin", as well as the entire command line session where you attempt to create a database.

  14. #14
    Join Date
    Nov 2010
    Posts
    10
    MQSI command
    --------------------------------------------------------------------------

    MQSI 6.1.0.5
    C:\Program Files\IBM\MQSI\6.1


    C:\Program Files\IBM\MQSI\6.1>mqsicreatedb
    BIP9819I: Creates a database for use with a Broker
    Syntax:
    mqsicreatedb databaseName [-i serviceUserID -a servicePassword] [-p portNumber]
    [-e dbType] [-u dbUserID]]

    Command options:
    'databaseName' the name of the database to be created
    Optional:
    '-i serviceUserID' the user ID that the DatabaseInstanceMgr should run under
    '-a servicePassword' the password for the DatabaseInstanceMgr user ID
    '-p portNumber' the port number the DatabaseInstanceMgr should use (default=152
    7)
    '-e dbType' the database type to use, currently supported: 'DB2' or 'Derby'
    '-u dbUserID' (DB2 only) grant database access to this user ID.

    BIP8007E: Mandatory argument missing.
    When using this command interface the user should supply the mandatory argument.

    Correct and reissue the command.

    C:\Program Files\IBM\MQSI\6.1>mqsicreatedb DEFBKD61 -i db2admin -a db2admin
    BIP9816I: Multiple Database types detected, defaulting to 'DB2'.
    BIP9809I: Creating DB2 Database 'DEFBKD61', this may take a while.
    BIP9835E: The DB2 batch command failed with the error code SQLSTATE=42705.
    BIP9835E: The DB2 batch command failed with the error code SQLSTATE=42705.
    The database 'DEFBKD61' could not be created/deleted. The error code SQLSTATE=42
    705 was returned from the DB2 batch command. All preceding steps have been rolle
    d back.
    Fix the problem indicated by the SQLSTATE code and reissue the command.

    C:\Program Files\IBM\MQSI\6.1>

    --------------------------------------------------------------------------



    DB2 Commands
    ************************************************** **********************************************
    C:\Windows\system32>echo %username%
    db2admin

    C:\Windows\system32>db2set -all
    [e] DB2PATH=C:\Program Files\IBM\SQLLIB
    [i] DB2ACCOUNTNAME=Ajay-PC\db2admin
    [i] DB2INSTOWNER=AJAY-PC
    [i] DB2PORTRANGE=60000:60003
    [i] DB2INSTPROF=C:\PROGRA~1\IBM\SQLLIB
    [i] DB2COMM=TCPIP
    [g] DB2_EXTSECURITY=YES
    [g] DB2SYSTEM=AJAY-PC
    [g] DB2PATH=C:\Program Files\IBM\SQLLIB
    [g] DB2INSTDEF=DB2
    [g] DB2ADMINSERVER=DB2DAS00

    C:\Windows\system32>net user db2admin
    User name db2admin
    Full Name db2admin
    Comment
    User's comment
    Country code 000 (System Default)
    Account active Yes
    Account expires Never

    Password last set 11/11/2010 4:44:40 PM
    Password expires Never
    Password changeable 11/11/2010 4:44:40 PM
    Password required Yes
    User may change password Yes

    Workstations allowed All
    Logon script
    User profile
    Home directory
    Last logon 11/19/2010 9:50:39 AM

    Logon hours allowed All

    Local Group Memberships *Administrators *DB2ADMNS
    *DB2USERS *HomeUsers
    *mqbrkrs *mqm
    Global Group memberships *None
    The command completed successfully.


    C:\Windows\system32>

    ************************************************** *******

  15. #15
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    I thought you said you were using the DB2 CREATE DATABASE command and it failed. Can you create the database in this manner?

    SQLSTATE values (e.g. 42705) often correspond to multiple SQLCODE values; you will need to determine the specific SQLCODE to properly diagnose the problem.

Posting Permissions

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