Restore not finished

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Matt - 29 Mar 2006 17:54 GMT

I have a database restore that hasn't finished because it ran into a
problem with not enough memory to complete the restore utility.
However, I cannot update the db cfg to allow enough memory because I
cannot connect to the database because the restore has not completed.
I'm not sure how I'm supposed to fix the memory issue to complete the
restore if I cannot update it until the restore is complete. Any
suggestion would be greatly appreciated. Stupid mistake on my part.
Thanks. Matt

Reply to this Message

Gert van der Kooij - 29 Mar 2006 17:57 GMT

> I have a database restore that hasn't finished because it ran into a
> problem with not enough memory to complete the restore utility.
[quoted text clipped - 4 lines]
> suggestion would be greatly appreciated. Stupid mistake on my part.
> Thanks. Matt

You don't need to connect to the database to change db cfg parms, an
attach to the node/instance it belongs to should be enough.

Reply to this Message

Matt - 29 Mar 2006 18:05 GMT

I can attach to the instance. Then when I try to run the update db cfg
statement, the response is that a database connection does not exist.
Not sure what else to try.

Reply to this Message

Matt - 29 Mar 2006 18:06 GMT

I can attach to the instance. Then when I try to run the update db cfg
statement, the response is that a database connection does not exist.
Not sure what else to try.

Reply to this Message

Gert van der Kooij - 29 Mar 2006 18:24 GMT

> I can attach to the instance. Then when I try to run the update db cfg
> statement, the response is that a database connection does not exist.
> Not sure what else to try.

You need to specify the DEFERRED option to prevent DB2 from automatic
connecting to the database, check the docs at http://tinyurl.com/h4jby

Reply to this Message

Keith - 29 Mar 2006 19:11 GMT

> > I can attach to the instance. Then when I try to run the update db cfg
> > statement, the response is that a database connection does not exist.
> > Not sure what else to try.
>
> You need to specify the DEFERRED option to prevent DB2 from automatic
> connecting to the database, check the docs at http://tinyurl.com/h4jby

I am not sure your udb version and not knowing your exact "memory"
error during restore, see if this works:
db2set DB2_OVERRIDE_BPF=1000 (and bounce the instance)

If your database gets restored successfully, then you can adjust
bufferpool sizes.

Keith Ponnapalli
IBM Certified Database Administrator - DB2 UDB V8.1 for Linux, UNIX and
Windows
IBM Certified Solutions Expert - DB2 UDB V7.1 Database Administration
for UNIX, Linux, Windows and OS/2
INFORMIX Certified 9.2 Database Administrator/4GL Developer

Reply to this Message

ShengTC@gmail.com - 30 Mar 2006 06:18 GMT

Did you try this?

db2 update db cfg for dbname using xxxx xxxx

To change db cfg, you don't need to connect to a database, you can use
the "for" option.

Reply to this Message