Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / September 2003

Tip: Looking for answers? Try searching our database.

FP3 on 8.1 broke my database

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Frank - 30 Sep 2003 20:13 GMT
My UDB database was ok when I installed FP3 to test things out.  After
installing FP3 the database gives me this message when I try to
connect to it for the first time:

$ db2 connect to c814db
SQL1084C  Shared memory segments cannot be allocated.  SQLSTATE=57019

Since installing FP3 I have backed it out (back to FP2), but the
problem remained.  I've also backed out FP2 with no luck.  This box is
low on RAM but has nothing else running and was working OK.

Please help!

Below is a section of the db2diag.log that might be useful.

Thanks,
Frank

SQL8017W  The number of processors on this machine exceeds the defined
entitlement of "1" for the product "DB2 Enterprise Server Edition".
The
number of processors on this machine is "2".  You should purchase
additional
processor based entitlements from your IBM representative or
authorized dealer
and update your license using the License Center or the db2licm
command line
utility. For more information on updating processor based licenses,
refer to
the Quick Beginnings manual for your platform.  For more information
on the
db2licm utility, refer to the DB2 Command Reference.

2003-09-30-15.09.01.394896 pid:1891 tid:1 level:3
Common - Generic Registry - GlobalReg::ValidateRecord() probe:30
impact 0x90000228 Invalid Global Registry missing field mask


2003-09-30-15.09.03.360739   Instance:db2c81   Node:000
PID:1886(db2star2)   TID:1   Appid:none
base sys utilities  startdbm Probe:911

ADM7513W  Database manager has started.

2003-09-30-15.09.12.159216   Instance:db2c81   Node:000
PID:1931(db2agent (C814DB) 0)   TID:1  
Appid:*LOCAL.db2c81.007910190911
base sys utilities  sqleFirstConnect Probe:15

DIA8305C Memory allocation failure occurred.
ZRC=0x850F0005

2003-09-30-15.09.12.222687   Instance:db2c81   Node:000
PID:1931(db2agent (C814DB) 0)   TID:1  
Appid:*LOCAL.db2c81.007910190911
base sys utilities  sqleFirstConnect Probe:16

DiagData
0000 0e28                                     ...(
Larry Edelstein - 30 Sep 2003 20:35 GMT
Frank,

What platform are you running on? What version/release level? Are you
using DB2 UDB with or without the DPF?

Your best bet is to open up a PMR with IBM support. It might be a new bug,
but it can also be orphaned IPC processes that weren't cleaned up when DB2
was last started. There may be other causes also.

Larry Edelstein

> My UDB database was ok when I installed FP3 to test things out.  After
> installing FP3 the database gives me this message when I try to
[quoted text clipped - 54 lines]
> DiagData
> 0000 0e28                                     ...(
Sean McKeough - 30 Sep 2003 20:58 GMT
If this is Linux/Windows your dbheap is trying to allocate @670MB of
space...you'll need to look at decreasing num agents, bufferpool sizes
etc (there can be some creep in underlying db2 usage of this heap on new
release boundaries).

If this is non linux unix, then your dbheap is mighty tiny and you
should make sure your box is clean as Larry suggests (ipclean -a).

> My UDB database was ok when I installed FP3 to test things out.  After
> installing FP3 the database gives me this message when I try to
[quoted text clipped - 55 lines]
> DiagData
> 0000 0e28                                     ...(
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.