By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,280 Members | 1,693 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,280 IT Pros & Developers. It's quick & easy.

DB2 SQL1084C grief

P: n/a
Hiya everyone.

I'm toying with a little db server.
It's an AMD64 X2, so dual cpu 64 bit.
It's a box with a total of 2GB of memory.

We have a database server with comparable specs.
an AMD64 X2 with 4GB of memory.
This machine has 3 databases running.
I backed up one of those databases and am trying to install it on the
2GB db server.

They are both machines with OpenSuSE 10.1 64bit installed.
The DB2 product installed is DB2 Workgroup Unlimited Server 8.1. (FP 10,
I think).
These are the sysctl settings we've used.

kernel.sem=250 256000 32 1024
kernel.msgmni=1024
kernel.msgmax=4096
kernel.shmmni=2048
kernel.shmmax=2109538304
kernel.shmall=2109538304

We've tried doubling values and halving values. But these are IMO the
most correct values for our system, but then again, I could be wrong.
When I create an empty database, everything is ok... I can connect etc.

But when I restore the backup from the other machine (both 64 bit
instances) I get the following message:

SQL1084C Shared memory segments cannot be allocated. SQLSTATE=57019
Now, what I understand of this message is that we're lacking memory.
But to me it makes no sense, since we have 3 databases of the same size
running on a 4GB machine.

the database heap of the image being restored is 8192 pages.

So, does anyone have any idea on what I'm doing wrong?

Thank you.

-R-
Sep 7 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Hmmm... gaining insight in the matter, thanks to the elaborate reporting
fixpak 13 does on memory issues.

Question:
When restoring a database, how can I influence the database
configuration? Is creating an empty database with its own settings
enough? (ie. does restoring a database image into an existing database
retain the settings of the existing database?)

Because since I'm unable to connect to the database after the restore
(the database has not got enough memory available to fire up, despite
the db2_override_bpf setting) I cannot change those settings with a mere
db2 update db cfg.

Thanks.

-R-

Jurgen Haan wrote:
Hiya everyone.

I'm toying with a little db server.
It's an AMD64 X2, so dual cpu 64 bit.
It's a box with a total of 2GB of memory.

We have a database server with comparable specs.
an AMD64 X2 with 4GB of memory.
This machine has 3 databases running.
I backed up one of those databases and am trying to install it on the
2GB db server.

They are both machines with OpenSuSE 10.1 64bit installed.
The DB2 product installed is DB2 Workgroup Unlimited Server 8.1. (FP 10,
I think).
These are the sysctl settings we've used.

kernel.sem=250 256000 32 1024
kernel.msgmni=1024
kernel.msgmax=4096
kernel.shmmni=2048
kernel.shmmax=2109538304
kernel.shmall=2109538304

We've tried doubling values and halving values. But these are IMO the
most correct values for our system, but then again, I could be wrong.
When I create an empty database, everything is ok... I can connect etc.

But when I restore the backup from the other machine (both 64 bit
instances) I get the following message:

SQL1084C Shared memory segments cannot be allocated. SQLSTATE=57019
Now, what I understand of this message is that we're lacking memory.
But to me it makes no sense, since we have 3 databases of the same size
running on a 4GB machine.

the database heap of the image being restored is 8192 pages.

So, does anyone have any idea on what I'm doing wrong?

Thank you.

-R-
Sep 8 '06 #2

P: n/a
In article <45**********************@news.xs4all.nl>, ju****@fake.dom
says...
Hmmm... gaining insight in the matter, thanks to the elaborate reporting
fixpak 13 does on memory issues.

Question:
When restoring a database, how can I influence the database
configuration? Is creating an empty database with its own settings
enough? (ie. does restoring a database image into an existing database
retain the settings of the existing database?)

Because since I'm unable to connect to the database after the restore
(the database has not got enough memory available to fire up, despite
the db2_override_bpf setting) I cannot change those settings with a mere
db2 update db cfg.

Does it make any difference if you use the DEFERRED option on the update
db cfg command?
Sep 8 '06 #3

P: n/a
Gert van der Kooij wrote:
In article <45**********************@news.xs4all.nl>, ju****@fake.dom
says...
>Hmmm... gaining insight in the matter, thanks to the elaborate reporting
fixpak 13 does on memory issues.

Question:
When restoring a database, how can I influence the database
configuration? Is creating an empty database with its own settings
enough? (ie. does restoring a database image into an existing database
retain the settings of the existing database?)

Because since I'm unable to connect to the database after the restore
(the database has not got enough memory available to fire up, despite
the db2_override_bpf setting) I cannot change those settings with a mere
db2 update db cfg.


Does it make any difference if you use the DEFERRED option on the update
db cfg command?
Can't check atm :P
Decided to just put in more memory. and now it works like a charm.
Still not entirely clear why the database would not run on a 2G setup,
but for now it suffices. I will continue experimenting on a similar machine.
Sep 8 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.