Results 1 to 7 of 7
  1. #1
    Join Date
    Sep 2003
    Location
    Sacramento, CA
    Posts
    28

    Unhappy Unanswered: Problem with CC communicating with Linux Server

    I am new to DB2 and have had such a pain with DB2. I had to manually install and configure my P-series Redhat Linux server with DB2. The gui install froze on us so I had to do everything manually using the IBM Installation and Configuration supplement. Here is where I am: I have installed DB2 on the server, created an instance called db2inst2. I have 3 linux users called db2inst2 (group name db2iadm1), db2fenc1 (group name db2fadm1), and db2as (group name db2asgrp).

    Here is my problem at this point, there may be more to come later I am sure once I get past this point.
    I am able to go into the Control Center on my Windows XP workstation and I can see the Linux Server (name LinuxDB2). I can click the + beside the system and see the instances folder and under that I see DB2LINUX (db2inst2). I had already previously cataloged the TCPIP node using the client command line.
    The port # is the same on both the client and the server (40000). Whenever I try to create a database it asks for a username/password, I put in the instance owner username of db2inst2. It then pops up with an error SQL22204N. I am thinking it is something I have missed in the setup either on the server or client side.

    Here is a listing of my GET DBM CFG for both the server and the client:


    SERVER GET DBM CFG LIST:
    db2 => get dbm cfg

    Database Manager Configuration

    Node type = Enterprise Server Edition with local and remote clients

    Database manager configuration release level = 0x0a00

    CPU speed (millisec/instruction) (CPUSPEED) = 8.147937e-07
    Communications bandwidth (MB/sec) (COMM_BANDWIDTH) = 1.000000e+02

    Max number of concurrently active databases (NUMDB) = 8
    Data Links support (DATALINKS) = NO
    Federated Database System Support (FEDERATED) = NO
    Transaction processor monitor name (TP_MON_NAME) =

    Default charge-back account (DFT_ACCOUNT_STR) =

    Java Development Kit installation path (JDK_PATH) = /opt/IBMJava2-ppc-131

    Diagnostic error capture level (DIAGLEVEL) = 3
    Notify Level (NOTIFYLEVEL) = 3
    Diagnostic data directory path (DIAGPATH) = /home/db2inst2/sqllib/db2dump

    Default database monitor switches
    Buffer pool (DFT_MON_BUFPOOL) = OFF
    Lock (DFT_MON_LOCK) = OFF
    Sort (DFT_MON_SORT) = OFF
    Statement (DFT_MON_STMT) = OFF
    Table (DFT_MON_TABLE) = OFF
    Timestamp (DFT_MON_TIMESTAMP) = ON
    Unit of work (DFT_MON_UOW) = OFF
    Monitor health of instance and databases (HEALTH_MON) = OFF

    SYSADM group name (SYSADM_GROUP) = DB2INST2
    SYSCTRL group name (SYSCTRL_GROUP) =
    SYSMAINT group name (SYSMAINT_GROUP) =
    SYSMON group name (SYSMON_GROUP) =

    Database manager authentication (AUTHENTICATION) = SERVER
    Cataloging allowed without authority (CATALOG_NOAUTH) = NO
    Trust all clients (TRUST_ALLCLNTS) = YES
    Trusted client authentication (TRUST_CLNTAUTH) = CLIENT
    Bypass federated authentication (FED_NOAUTH) = NO

    Default database path (DFTDBPATH) = /home/db2inst2

    Database monitor heap size (4KB) (MON_HEAP_SZ) = 90
    Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048
    Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0
    Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC
    Backup buffer default size (4KB) (BACKBUFSZ) = 1024
    Restore buffer default size (4KB) (RESTBUFSZ) = 1024

    Sort heap threshold (4KB) (SHEAPTHRES) = 20000

    Directory cache support (DIR_CACHE) = YES

    Application support layer heap size (4KB) (ASLHEAPSZ) = 15
    Max requester I/O block size (bytes) (RQRIOBLK) = 32767
    Query heap size (4KB) (QUERY_HEAP_SZ) = 1000
    DRDA services heap size (4KB) (DRDA_HEAP_SZ) = 128

    Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 100

    Priority of agents (AGENTPRI) = SYSTEM
    Max number of existing agents (MAXAGENTS) = 400
    Agent pool size (NUM_POOLAGENTS) = 200(calculated)
    Initial number of agents in pool (NUM_INITAGENTS) = 0
    Max number of coordinating agents (MAX_COORDAGENTS) = (MAXAGENTS - NUM_INITAGENTS)
    Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX_COORDAGENTS
    Max number of client connections (MAX_CONNECTIONS) = MAX_COORDAGENTS

    Keep fenced process (KEEPFENCED) = YES
    Number of pooled fenced processes (FENCED_POOL) = MAX_COORDAGENTS
    Initial number of fenced processes (NUM_INITFENCED) = 0

    Index re-creation time (INDEXREC) = RESTART

    Transaction manager database name (TM_DATABASE) = 1ST_CONN
    Transaction resync interval (sec) (RESYNC_INTERVAL) = 180

    SPM name (SPM_NAME) =
    SPM log size (SPM_LOG_FILE_SZ) = 256
    SPM resync agent limit (SPM_MAX_RESYNC) = 20
    SPM log path (SPM_LOG_PATH) =

    TCP/IP Service name (SVCENAME) = 40000
    Discovery mode (DISCOVER) = SEARCH
    Discover server instance (DISCOVER_INST) = ENABLE

    Maximum query degree of parallelism (MAX_QUERYDEGREE) = ANY
    Enable intra-partition parallelism (INTRA_PARALLEL) = NO

    No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = 4096
    Number of FCM request blocks (FCM_NUM_RQB) = AUTOMATIC
    Number of FCM connection entries (FCM_NUM_CONNECT) = AUTOMATIC
    Number of FCM message anchors (FCM_NUM_ANCHORS) = AUTOMATIC

    Node connection elapse time (sec) (CONN_ELAPSE) = 10
    Max number of node connection retries (MAX_CONNRETRIES) = 5
    Max time difference between nodes (min) (MAX_TIME_DIFF) = 60

    db2start/db2stop timeout (min) (START_STOP_TIME) = 10


    I did notice that my SYSADM, SYSCTRL, SYSMAINT, SYSMON are blank. I don’t know what values these are suppose to be set to. I have the three linux users db2as, db2inst2, and db2fenc1. I have three groups, db2iadm, db2fadm1, and db2asgrp.
    Do I need to set these three sys groups to my linux groups? Do I need to create any new groups? Please tell me which groups the sys groups should be set to.

    I don’t know if setting the sys groups will fix my SQL22204N problem though. Does anyone have an idea what I can do to fix that particular issue?

    Oh Yeah, here is my GET DBM CFG for the client side as well:

    Database Manager Configuration

    Node type = Client

    Database manager configuration release level = 0x0a00

    Federated Database System Support (FEDERATED) = NO
    Transaction processor monitor name (TP_MON_NAME) =

    Default charge-back account (DFT_ACCOUNT_STR) =

    Java Development Kit installation path (JDK_PATH) = C:\Program Files\IBM\
    SQLLIB\java\jdk

    Diagnostic error capture level (DIAGLEVEL) = 3
    Notify Level (NOTIFYLEVEL) = 3
    Diagnostic data directory path (DIAGPATH) =

    SYSADM group name (SYSADM_GROUP) =
    SYSCTRL group name (SYSCTRL_GROUP) =
    SYSMAINT group name (SYSMAINT_GROUP) =
    SYSMON group name (SYSMON_GROUP) =

    Database manager authentication (AUTHENTICATION) = SERVER
    Cataloging allowed without authority (CATALOG_NOAUTH) = YES
    Bypass federated authentication (FED_NOAUTH) = NO

    Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 512
    Directory cache support (DIR_CACHE) = YES

    Max requester I/O block size (bytes) (RQRIOBLK) = 32767
    DOS requester I/O block size (bytes) (DOS_RQRIOBLK) = 4096
    DRDA services heap size (4KB) (DRDA_HEAP_SZ) = 128

    Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 100

    Transaction manager database name (TM_DATABASE) = 1ST_CONN

    NetBIOS Workstation name (NNAME) =

    Discovery mode (DISCOVER) = SEARCH

    db2 =>

    If anyone can help me, it would be much appreciated. I have gotten to this point before and gave up for like 6 months on DB2. The IBM Support worked with me for like 2 weeks and I just gave up. It was too frustrating because it was taking too long to figure out the problem, there was a language barrier with the guy I was working with. I was thinking we should just go with SQL Server because I know its much easier to setup. My company has already decided to stay with DB2 so I need to get this working.

    Thanks,
    David

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    What version and fixpack of DB2 do you have, and what version of RH Linux?
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  3. #3
    Join Date
    Sep 2003
    Location
    Sacramento, CA
    Posts
    28

    versions and fixpacks

    The Administration client is v8.1.0.36. The Redhat is the AS 2.1 (I think that number is right). The DB2 is version 8.1 but I am not sure what the latest fixpack that has been installed. Is there a linux command I can type to find out what the exact fixpack that is running?

    David

  4. #4
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Download and install the latest Java SDK from this site:
    https://www6.software.ibm.com/dl/lxd...03&S_CMP=LXJDK

    Then run the following commands (changing the path statement depending on where the new Java is installed:

    db2 update dbm cfg using jdk_path /opt/IBMJava2-141
    db2 update admin cfg using jdk_path /opt/IBMJava2-141

    The first command should be run by the instance owner and the second command should be run by the Admin Server user id (the default is dasusr1 unless you changed it).

    Then reboot the machine.

    On Linux, both the 1.31 and new Java can co-exist on the machine and you can change which one DB2 uses by running the db2 update command.

    Please let us know how this works out.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  5. #5
    Join Date
    Sep 2003
    Location
    Sacramento, CA
    Posts
    28

    Problem with CC communicating with Linux Server

    Here is what happened. I downloaded the Java SDK. The lastest was 1.42. I FTPed the file over to the Linux Server and installed it using RPM. I then logged into db2inst2 (the instance owner) and executed the db2 update dbm cfg using JDK_PATH /opt/IBMJava2-ppc64-142. That worked fine and it showed the new path when I did a get dbm cfg.

    For the 2nd part where you wanted me to change the admin cfg. I did not have a dasusr1 login. The login id I specified when I created the das was db2as. But just to be consistent with what you were saying, I dropped my das, created a dasusr1 login, and then recreated my das with the dasusr1 login. I then logged into dasusr1. When I tried to execute the db2 update admin cfg command, the db2 command was not recognized. I tried just typing db2 by itself to get into the command line but it was not a reconized command the way it was when I was logged in as db2inst2. By the way I did try it by logged on as my old das user name also before I recreated the das and it still did not recognize the db2 command.

    I am at a loss now. One other thing to mention is the JDK_PATH that was set before I made changes (/opt/Java2-ppc-131) did not exist in the opt folder. the only folder under opt was the IBM folder. I dont know if that was part of my problems to start with. But right now the admin cfg for JDK_PATH still is pointing to the old path and I cannot change it now. What can I do to get the dasusr1 login to recognized the db2 command so I can execute command line instructions?

    I feel like I am so close but so far. I am not even at the point of having a database created yet. That was my next step trying to create it in the Control Center. HELP!

    David

  6. #6
    Join Date
    Sep 2003
    Location
    Sacramento, CA
    Posts
    28

    my current cfg listings

    Here are my current dbm cfg and admin cfg listings

    Admin Server Configuration

    Authentication Type DAS (AUTHENTICATION) = SERVER_ENCRYPT

    DAS Administration Authority Group Name (DASADM_GROUP) = db2asgroup

    DAS Discovery Mode (DISCOVER) = SEARCH
    Name of the DB2 Server System (DB2SYSTEM) = LINUXDB2

    Java Development Kit Installation Path DAS (JDK_PATH) = /opt/IBMJava2-ppc-131
    Java Development Kit Installation Path DAS (JDK_64_PATH) =

    DAS Code Page (DAS_CODEPAGE) = 0
    DAS Territory (DAS_TERRITORY) = 0

    Location of Contact List (CONTACT_HOST) =
    Execute Expired Tasks (EXEC_EXP_TASK) = NO
    Scheduler Mode (SCHED_ENABLE) = OFF
    SMTP Server (SMTP_SERVER) =
    Tools Catalog Database (TOOLSCAT_DB) =
    Tools Catalog Database Instance (TOOLSCAT_INST) =
    Tools Catalog Database Schema (TOOLSCAT_SCHEMA) =
    Scheduler User ID =






    Database Manager Configuration

    Node type = Enterprise Server Edition with local and remote clients

    Database manager configuration release level = 0x0a00

    CPU speed (millisec/instruction) (CPUSPEED) = 8.147937e-07
    Communications bandwidth (MB/sec) (COMM_BANDWIDTH) = 1.000000e+02

    Max number of concurrently active databases (NUMDB) = 8
    Data Links support (DATALINKS) = NO
    Federated Database System Support (FEDERATED) = NO
    Transaction processor monitor name (TP_MON_NAME) =

    Default charge-back account (DFT_ACCOUNT_STR) =

    Java Development Kit installation path (JDK_PATH) = /opt/IBMJava2-ppc64-142

    Diagnostic error capture level (DIAGLEVEL) = 3
    Notify Level (NOTIFYLEVEL) = 3
    Diagnostic data directory path (DIAGPATH) = /home/db2inst2/sqllib/db2dump

    Default database monitor switches
    Buffer pool (DFT_MON_BUFPOOL) = OFF
    Lock (DFT_MON_LOCK) = OFF
    Sort (DFT_MON_SORT) = OFF
    Statement (DFT_MON_STMT) = OFF
    Table (DFT_MON_TABLE) = OFF
    Timestamp (DFT_MON_TIMESTAMP) = ON
    Unit of work (DFT_MON_UOW) = OFF
    Monitor health of instance and databases (HEALTH_MON) = OFF

    SYSADM group name (SYSADM_GROUP) = DB2INST2
    SYSCTRL group name (SYSCTRL_GROUP) =
    SYSMAINT group name (SYSMAINT_GROUP) =
    SYSMON group name (SYSMON_GROUP) =

    Database manager authentication (AUTHENTICATION) = CLIENT
    Cataloging allowed without authority (CATALOG_NOAUTH) = NO
    Trust all clients (TRUST_ALLCLNTS) = YES
    Trusted client authentication (TRUST_CLNTAUTH) = SERVER
    Bypass federated authentication (FED_NOAUTH) = NO

    Default database path (DFTDBPATH) = /home/db2inst2

    Database monitor heap size (4KB) (MON_HEAP_SZ) = 90
    Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048
    Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0
    Size of instance shared memory (4KB) (INSTANCE_MEMORY) = AUTOMATIC
    Backup buffer default size (4KB) (BACKBUFSZ) = 1024
    Restore buffer default size (4KB) (RESTBUFSZ) = 1024

    Sort heap threshold (4KB) (SHEAPTHRES) = 20000

    Directory cache support (DIR_CACHE) = YES

    Application support layer heap size (4KB) (ASLHEAPSZ) = 15
    Max requester I/O block size (bytes) (RQRIOBLK) = 32767
    Query heap size (4KB) (QUERY_HEAP_SZ) = 1000
    DRDA services heap size (4KB) (DRDA_HEAP_SZ) = 128

    Workload impact by throttled utilities(UTIL_IMPACT_LIM) = 100

    Priority of agents (AGENTPRI) = SYSTEM
    Max number of existing agents (MAXAGENTS) = 400
    Agent pool size (NUM_POOLAGENTS) = 200(calculated)
    Initial number of agents in pool (NUM_INITAGENTS) = 0
    Max number of coordinating agents (MAX_COORDAGENTS) = (MAXAGENTS - NUM_INITAGENTS)
    Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX_COORDAGENTS
    Max number of client connections (MAX_CONNECTIONS) = MAX_COORDAGENTS

    Keep fenced process (KEEPFENCED) = YES
    Number of pooled fenced processes (FENCED_POOL) = MAX_COORDAGENTS
    Initial number of fenced processes (NUM_INITFENCED) = 0

    Index re-creation time (INDEXREC) = RESTART

    Transaction manager database name (TM_DATABASE) = 1ST_CONN
    Transaction resync interval (sec) (RESYNC_INTERVAL) = 180

    SPM name (SPM_NAME) =
    SPM log size (SPM_LOG_FILE_SZ) = 256
    SPM resync agent limit (SPM_MAX_RESYNC) = 20
    SPM log path (SPM_LOG_PATH) =

    TCP/IP Service name (SVCENAME) = 40000
    Discovery mode (DISCOVER) = SEARCH
    Discover server instance (DISCOVER_INST) = ENABLE

    Maximum query degree of parallelism (MAX_QUERYDEGREE) = ANY
    Enable intra-partition parallelism (INTRA_PARALLEL) = NO

    No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = 4096
    Number of FCM request blocks (FCM_NUM_RQB) = AUTOMATIC
    Number of FCM connection entries (FCM_NUM_CONNECT) = AUTOMATIC
    Number of FCM message anchors (FCM_NUM_ANCHORS) = AUTOMATIC

    Node connection elapse time (sec) (CONN_ELAPSE) = 10
    Max number of node connection retries (MAX_CONNRETRIES) = 5
    Max time difference between nodes (min) (MAX_TIME_DIFF) = 60

    db2start/db2stop timeout (min) (START_STOP_TIME) = 10

  7. #7
    Join Date
    Sep 2003
    Location
    Sacramento, CA
    Posts
    28

    Red face Getting closer

    I am getting closer to my solution to this problem. I found out that I needed to have an entry in the /etc/services file. Previously I just had SVCENAME set to a port number (40000), same as the client. But I created an entry in the services file called DASPORT 40000/tcp. After that I restarted the server. Once it came back up I was able to create my first database using the Control Center which I was not able to do before. Jumping for joy, I decided to try the next step and create a table. Well the jumping stopped then. I got error SQL30081N protocol specific error "10061". I will have to look this up to give me guidance to troubleshoot it. Any one have any ideas right off hand what I should be looking for with this error?

    Thanks,
    David

Posting Permissions

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