Starting IBM OD DB2 Instance issue

[mani]

Hi,

I am facing trouble while starting the IBMOD DB2 (V9.5) instance in my UAT server ( Sun Solaris 5.10). There are 5 instances of IBMOD available, however at any given point of time, only 1-2 instances can be brought up. while trying to bring more than that, I am getting the below error

arsdb -I <Instance name> -gkv

"Unable to start database <instance name>.  SQLCODE = -1032".

I have Opened a PMR with IBM and they recommended to increase the memory and we did that last week. we are double the memory than what we were earlier, Even after that, we still see the issue persists and not able to bring all 5 instances. max we can bring up is '3' at a given time.

All the instances are in the same machine. if any more specfic detail is required, pls let me know.

Also, is there any other check that I can perform myself before going to IBM again.

Any help is much appreciated.

cheers
Mani

[mani]

Forgot to mention that we are on IBM OD 8.4.1.6 and will be moving to version 9. in about 6-7 months. But we need to get all these instances up and running.


cheers
Mani

[Justin Derrick]

Yeah, arsdb is great, until it doesn't work.  It has a habit of hiding all of the error messages you would normally get.

If you know the names of all your databases, then you should be able to start them 'manually' by logging in as the instance owner, and issuing:

db2 activate database <DB>  (Where <DB> is the name of the database.)

If you get error messages, do some searches and find the most common issues. 

If you don't get anything useful from those error message, look for the 'sqllib' directory in the database instance owner's directory, and inside that directory is another directory called 'db2dump', which is where DB2 puts it's diagnostic info.  Inside the db2dump directory is a file called 'db2diag.log'. Use the 'tail' command to search for the last set of meaningful messages, and go from there...

Good luck!

-JD.

[mani]

Hi JD,

I am getting the below error when tring to activate it

SQL1032N  No start database manager command was issued.  SQLSTATE=57019

Any suggestions on what could be misisng.


cheers
Mani

[mani]

@JD,

here is what I did.

1) db2start
2) db2 activate db <dbname>


and it worked now. I will try bringing multiple instances and keep u posted.

cheers
Mani

[mani]

Hi,

I tried starting the database instance one by one, On starting the 3rd instance I am getting the below error:

"10/14/2014 23:46:02     0   0   SQL1220N  The database manager shared memory set cannot be allocated.
SQL1032N  No start database manager command was issued.  SQLSTATE=57019"

Is there a way to find the database manager shared memory set??

Upon googling for the above error, here is what I could see:

SQL1220N  The database manager shared memory set cannot be allocated.

Explanation:

The database manager could not allocate its shared memory set. The cause
of this error may be insufficient memory resources either for the
database manager or the environment in which its operation is being
attempted. Memory resources that can cause this error include:
*  The number of shared memory identifiers allocated in the system
*  The size of the shared memory segment
*  The amount of paging or swapping space available in the system
*  The amount of physical memory available in the system

User response:

One or more of the following:
*  Validate that sufficient memory resources are available to satisfy
   the database manager's requirements, and those of the other programs
   running on the system.
*  On Linux 32-bit, increase the kernel parameter shmmax to 256 MB. On
   Linux 64-bit, increase the kernel parameter shmmax to 1GB.
*  Reduce database manager's memory requirement for this memory set by
   reducing the database manager configuration parameters which affect
   it. These are: fenced_pool and, numdb.
*  Where appropriate, stop other programs using the system.

[Justin Derrick]

To try and address your specific situation, you should contact your company's DBA team to help you tune DB2.

Managing memory in DB2 is pretty much a task for wizards.  You can enable the Self-Tuning Memory Manager, which allows DB2 to manage it's own memory.  It's actually very good, and in the majority of situations will provide very good results.

Here's an introduction to STMM in DB2 v9 (it was introduced in DB2 9.1):
http://www.ibm.com/developerworks/data/library/techarticle/dm-0606ahuja/index.html

To turn on STMM:
   db2 update db cfg for <database> using self_tuning_mem on 
(Where <database> is the name of your database.)

You'll probably want to do that for each of your databases.

You'll need to change other configuration parameters to 'automatic' in order for STMM to do it's job properly.

Let us know how this works for you.

-JD.

[mani]

@ JD,

Unfortunately we have no DB2 DBA support in my company who can take a look into it. Since its IBM proprietary, they still own it.


Cheers
Mani

[Justin Derrick]

Have you considered opening a PMR to get some assistance with the DB2 issue?

Also, since this is memory related, does your system meet (or exceed) the memory requirements specified in the installation guide?

-JD.