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