ChannelDB2

DB2 DAS problem and also DB2 Memory problem solved Successfully

This is an article regarding the 2 problems mixed DB2 DAS problem and also the Memory problem

Initially I got the problem in db2diag.log file that

The main problem is while creating the new table. we are creating the table in sms table space which will take the memory from unix space for "TS_RECH_0901" tablespace. The buffer bool ares is very less and it is not able to overcome .

Db2 diaglog error msg:

2009-03-25-15.13.04.967324+240 E38891981C723 LEVEL: Warning

PID : 487514 TID : 1 PROC : db2agent (OM_DW_11) 0

INSTANCE: db2inst2 NODE : 000 DB : OM_DW_11

APPHDL : 0-1114 APPID: *LOCAL.db2inst2.090325111301

FUNCTION: DB2 UDB, buffer pool services, sqlbStartPools, probe:2 MESSAGE : ADM6073W The table space "TS_RECH_0901" (ID "88") is configured to

use buffer pool ID "1", but this buffer pool is not active at this

time. In the interim the table space will use buffer pool ID "4096".

The inactive buffer pool should become available at next database

startup provided that the required memory is available.

Then I try to connect to the DB2 database from db2 clinet installed in my laptop. it was not connecting. I was getting some communication error. Then finally found that DAS was not running in the server due to which I cannot get db2 client connection to the control center. So try to start the DAS but DSA was not starting. i was getting the below error.

$ db2admin start

SQL4401C The DB2 Administration Server encountered an error during

startup.

$ db2admin start

SQL4401C The DB2 Administration Server encountered an error during

startup.

$ db2admin stop

SQL4410W The DB2 Administration Server is not active.

Then I check the db2 admin command as below and got the DSA user.

1. What does db2admin command show?

$ db2admin

dasusr1

so from db2diag.log i found that we have memory lack problems on this

kwr-om-bkr-07 machine:

error

2009-03-24-18.21.42.335887+240 E38566654C721 LEVEL: Warning

PID : 708724 TID : 1 PROC : db2agent

(OM_DW_11) 0

INSTANCE: db2inst2 NODE : 000 DB : OM_DW_11

APPHDL : 0-685 APPID: *LOCAL.db2inst2.090324142143

FUNCTION: DB2 UDB, buffer pool services, sqlbStartPools, probe:2

MESSAGE : ADM6073W The table space "SYSCATSPACE" (ID "0") is configured to

use

buffer pool ID "1", but this buffer pool is not active at this

time.

In the interim the table space will use buffer pool ID "4096".

The

inactive buffer pool should become available at next database

startup

provided that the required memory is available.

this says that there lack of free memory occured. Due to this problem by default I just increased Num_estore_segs parameter to 1600 without calculation But again the same memory problem came.

Extended storage segments size (4KB) (ESTORE_SEG_SZ) = 16000

Number of extended storage segments (NUM_ESTORE_SEGS) = 16000

After that I check in Google for IBM information for DB2.I got the below default parameters .

estore_seg_sz - Extended storage memory segment size configuration

parameter

Configuration Type

Database

Parameter Type

Configurable

Default [Range]

9 16 000 [0 - 1 048 575] 9 9

On Windows operating systems, the maximum size is 16 777 216.

Unit of Measure

Pages (4 KB)

so 16000*4Kb=64Mb ok? So, now 64 Mb*16000=1024000 Mb=1 024 Gb so it's

really too big.

Also it may be a reason for not starting DAS.

Then immediately reduced the size to 75 as per the calculation

$ db2 update db cfg for OM_DW_11 using NUM_ESTORE_SEGS 75

DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.

SQL1363W One or more of the parameters submitted for immediate modification were not changed dynamically. For these configuration parameters, all applications must disconnect from this database before the changes become effective.

Now after changing to 75.It is started normal.

But still db2admin is not starting.

$ db2admin start

SQL4401C The DB2 Administration Server encountered an error during startup.

$

Then followed the next steps to drop & create DAS:

Creating a DB2 administration server (DAS)

The DB2® administration server (DAS) provides support services for DB2

tools such as the Control Center and the Configuration Assistant.

To create a DAS, you must have root authority on UNIX® platforms or using

an account that has the correct authorization to create a service. On

Windows®, if a specific user is to be identified, create a user with local

Administrator authority. Enter db2admin create. If a specific user account

is desired, you must use "/USER:" and "/PASSWORD:" when issuing db2admin

create.

You can only have one DAS in a database server. If one is already created,

you need to drop it by issuing db2admin drop.

Typically, the setup program creates a DAS on the instance-owning computer

during DB2 installation. If, however, the setup program failed to create

it, you can manually create a DAS.

As an overview of what occurs during the installation process as it relates

to DAS, consider the following:

On Windows platforms: Log on to the computer you want to create the

DAS on using an account that has the correct authorization to create

a service.

When creating the DAS, you can optionally provide a user account name

and a user password. If valid, the user account name and password

will identify the owner of the DAS. Do not use the user ID or account

name created for the DAS as a User Account. Set the password for the

account name to "Password Never Expires". After you create the DAS,

you can establish or modify its ownership by providing a user account

name and user password with the db2admin setid command.

On UNIX platforms:

1. Ensure that you have root authority.

2. At a command prompt, issue the following command from the

instance subdirectory in the DB2 install path:

dascrt -u ,

is the user name of the DAS user you created when you

were creating users and groups for the DB2 database.

On AIX(R):

/usr/opt/:installdir/instance/

dascrt -u

On HP-UX, Solaris operating system, or Linux(TM): R

/opt/IBM/db2/installdir/instance/

dascrt -u

http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.admin.doc/doc/t0004960.htm

Removing the DB2 administration server (DAS)

Procedure

To remove the DAS:

On Windows(R) operating systems:

1. Log on to the computer using an account or user ID that has the

correct authorization to remove a service.

2. Stop the DAS, using db2admin stop.

3. Backup (if needed) all the files in the db2das00 subdirectory

under the sqllib subdirectory.

Note:

This example assumes db2das00 is the name of the DAS to be

removed. It is possible to have a DAS with a name other than

DB2DAS00 if a user has created a DB2(R) database instance that

has the name DB2DAS00. In this case, the DAS will be named

DB2DAS01 (or, if that is taken, DB2DAS02 and so forth). You

should look for the service with the "DB2DAS" prefix to

identify the specific DAS from the list of several DAS that

might exist. You can use the db2admin command without any

options to list all DAS..

4. Drop the DAS, using db2admin drop.

On UNIX(R) operating systems:

1. Login as a user with DASADM authority.

2. Run the startup script using one of the following:

. DASHOME/das/dasprofile (for Bourne or Korn shell)

source DASHOME/das/dascshrc (for C shell)

where DASHOME is the home directory of the DAS owner.

3. Stop the DAS using the db2admin command as follows:

db2admin stop

4. Back up (if needed) all the files in the das subdirectory under

the home directory of the DAS.

5. Log off.

6. Log in as root and remove the DAS using the dasdrop command as

follows:

dasdrop

The dasdrop command is found in the instance subdirectory under

the subdirectory specific to the installed DB2 database manager

version and release.

Note:

The dasdrop command removes the das subdirectory under the home

directory of the DB2 administration server (DAS).

http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/t0005177.htm

fallowed the below steps to drop and re-create the DAS.

1.Login as db2inst2 to 83 sserver

2. since I am not able to stop the DAS...db2admin stop...i skip this

3. dasdrop

4.login root

5.rm -r dasusr2--since it is not used may be it is effecting the dasusr1.

6.rm -r dasusr1

7.login as db2inst2

8. dascrt -u dasusr1

9.login dasusr1

10.db2admin start

Then finally both the problem is solved.

1.Number of extended storage segments (NUM_ESTORE_SEGS) = 75

2.The droped the DAS and re-created it and also sucessfully db2 admin started.

$ db2admin start
SQL4409W The DB2 Administration Server is already active.

3.Before this as i told you i have dropped the "TS_RECH_0901 " tables itself from which i got 100Gb free space in the unix before it was 100Gb free..now it is 200Gb free

/dev/fslv02 600.00 211.96 65% 4139 1% /database

4. Now I am able to login to control center and also i have created new Tablespace "TS_FACT_DAT" with boffer pool 1000 MB.so that from now onwards we will use DBMS tablespace.

Views: 4436

Comment

You need to be a member of ChannelDB2 to add comments!

Join ChannelDB2

Featured Downloads

Try BLU Acceleration on Cloud

© 2019   Created by channeldb2.   Powered by

Badges  |  Report an Issue  |  Terms of Service