If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > SQL1220N The database manager shared memory set cannot be allocated

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-11-03, 01:32
gemini95117 gemini95117 is offline
Registered User
 
Join Date: Dec 2002
Location: PUNE, INDIA
Posts: 25
Post SQL1220N The database manager shared memory set cannot be allocated

Hi guys,

I have a DB2 7.1 on AIX. I have a requirement where-in i have to install DB2 8 also on the same machine. I was able to install the DB2 8 and also create a new db2inst8 db2 8.x instance.

I got the following messages when i did the db2icrt.
I could make out just that its referring to the das of db2 7.x version for sure with the /home/db2as directory something....
Any ideas if this is a error or just a warning ..

---------------------------------
# ./db2icrt -a server -u db2fenc8 db2inst8
exec(): 0509-036 Cannot load program /home/db2inst8/sqllib/bin/db2ftok because of the following errors:
0509-130 Symbol resolution failed for db2ftok because:
0509-136 Symbol sqloGetInstancePath (number 19) is not exported from
dependent module /home/db2as/sqllib/lib/libdb2.a(shr.o).
0509-136 Symbol sqloclose (number 20) is not exported from
dependent module /home/db2as/sqllib/lib/libdb2.a(shr.o).
0509-136 Symbol sqlogins (number 21) is not exported from
dependent module /home/db2as/sqllib/lib/libdb2.a(shr.o).
0509-136 Symbol sqlogmt2 (number 22) is not exported from
dependent module /home/db2as/sqllib/lib/libdb2.a(shr.o).
0509-192 Examine .loader section symbols with the
'dump -Tv' command.
DBI1070I Program db2icrt completed successfully.
------------------------------------

Also, when i tried to start the new db2 8 instance with db2start.
It gives me a message
------------------------------------
$ db2start
12-11-2003 11:50:11 0 0 SQL1220N The database manager shared memory set cannot be allocated.
SQL1032N No start database manager command was issued. SQLSTATE=57019
------------------------------------
Any ideas where i am going wrong with the installation or if there is any setting which i have missed.

--RAHool
Reply With Quote
  #2 (permalink)  
Old 12-11-03, 01:43
nitingm nitingm is offline
Registered User
 
Join Date: Jul 2003
Location: Austin, TX, USA
Posts: 278
Memory Limitations

Hi,

I am not sure, but under the 32 bit operating systems there is a memory limit for roughly around 2.5 GB per instance. We have faced the same problems and realised that if we limit the memory usage to approx 1.7 GB then it works fine.

What is suggest is based on your physical memory in the server try to resize your parameters and ensure that the memory is split across all instances.

Please refer to the admin-performance guide that's a great starting point.

Cheers

nitin.
Reply With Quote
  #3 (permalink)  
Old 12-11-03, 08:19
GertK GertK is offline
Registered User
 
Join Date: Nov 2003
Location: Netherlands
Posts: 96
Re: SQL1220N The database manager shared memory set cannot be allocated

Quote:
Originally posted by gemini95117
Hi guys,

I have a DB2 7.1 on AIX. I have a requirement where-in i have to install DB2 8 also on the same machine. I was able to install the DB2 8 and also create a new db2inst8 db2 8.x instance.

I got the following messages when i did the db2icrt.
I could make out just that its referring to the das of db2 7.x version for sure with the /home/db2as directory something....
Any ideas if this is a error or just a warning ..


I searched for db2ftok on the IBM Technical Support site and found a technote which could solve your problem.

Hope this helps.

Copied from that technote:

========================================

The problem here is that the DB2 V8 binary is trying to use the DB2 V7 library.

db2iexec runs db2ftok as the instance owner which gets the environment from the instance owner's .profile and then from the db2profile. As per the db2profile, it will pickup correct migrated path for all binaries and libraries. However, many times a manual update in .profile might create an unwanted problem. In this case the following were entered in .profile:

---------------------------------
LIBPATH=$LIBPATH:/usr/lib:/usr/lpp/db2_07_01/lib
export LIBPATH
---------------------------------

So, in .profile of the instance owner, there should not be any DB2 libpath entry.

Similar problems also might be faced if following are done:

Unwanted DB2 references are manually entered in .profile of root user.
Links to DB2 libraries are created from /usr/lib either accidentally or by some tools.
db2profile is manually updated to make quick fix of path problems.
/lib does not point to /usr/lib

========================================
Reply With Quote
  #4 (permalink)  
Old 12-11-03, 09:21
gemini95117 gemini95117 is offline
Registered User
 
Join Date: Dec 2002
Location: PUNE, INDIA
Posts: 25
Thumbs up Resolved

YES,

This LIBPATH thing changes worked.


Thank you all for your help

--RAHool
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On