proper way to shutdown db2

[Tim B.]

Hello,

I am looking for the proper way to shut down db2 completely so that I
can do a cold back up on all the databases.

Thanks!

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---

[Blair Adamache]

Have a look at the quiesce command. Normally, it should be as simple as:

db2 force applications all
db2 connect to database <<dbname>> in exclusive mode
db2 backup database......

Note that this is at the database level. Quiesce also works at the
instance level if you have multiple databases in an instance.

Tim B. wrote:

Hello,

I am looking for the proper way to shut down db2 completely so that I
can do a cold back up on all the databases.

Thanks!

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000
Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

[Tim B.]

Thanks for your response. This is the script that I will be running.
Does this sound decent:

#!/bin/bash

# The following three lines have been added by UDB DB2.
if [ -f ~/sqllib/db2profile ]; then
. ~/sqllib/db2profile
else
exit 1
fi

# kick out everyone
db2 force applications all

db2 connect to database db1 in exclusive mode
db2 "backup database db1 to /opt/BACKUP"

db2 connect to database db2 in exclusive mode
db2 "backup database db2 online to /opt/BACKUP"

db2 connect to database db3 in exclusive mode
db2 "backup database db3 online to /opt/BACKUP"
What do I have to do to ensure that no one attempts any read/writes to
the database and also, how do I put the database back online?
Blair Adamache wrote:

Have a look at the quiesce command. Normally, it should be as simple as:

db2 force applications all
db2 connect to database <<dbname>> in exclusive mode
db2 backup database......

Note that this is at the database level. Quiesce also works at the
instance level if you have multiple databases in an instance.

Tim B. wrote:

Hello,

I am looking for the proper way to shut down db2 completely so that I
can do a cold back up on all the databases.

Thanks!

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World!

>100,000 Newsgroups

---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---

[Tim B.]

Also, how can I completely shutdown db2 and grab the raw database files
for the backup? In other words, I don't want to backup using db2
commands, I might simply want to tar up the whole thing and go.

Blair Adamache wrote:

Have a look at the quiesce command. Normally, it should be as simple as:

db2 force applications all
db2 connect to database <<dbname>> in exclusive mode
db2 backup database......

Note that this is at the database level. Quiesce also works at the
instance level if you have multiple databases in an instance.

Tim B. wrote:

Hello,

I am looking for the proper way to shut down db2 completely so that I
can do a cold back up on all the databases.

Thanks!

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World!

>100,000 Newsgroups

---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---

[Blair Adamache]

When the backup completes, users can reconnect. You might want to
quiesce each database individually before backing it up - the time from
the start of the first backup to the second allows a large window for
lots of users to reconnect to the 2nd and 3rd databases.

Tim B. wrote:

Thanks for your response. This is the script that I will be running.
Does this sound decent:

#!/bin/bash

# The following three lines have been added by UDB DB2.
if [ -f ~/sqllib/db2profile ]; then
. ~/sqllib/db2profile
else
exit 1
fi

# kick out everyone
db2 force applications all

db2 connect to database db1 in exclusive mode
db2 "backup database db1 to /opt/BACKUP"

db2 connect to database db2 in exclusive mode
db2 "backup database db2 online to /opt/BACKUP"

db2 connect to database db3 in exclusive mode
db2 "backup database db3 online to /opt/BACKUP"
What do I have to do to ensure that no one attempts any read/writes to
the database and also, how do I put the database back online?
Blair Adamache wrote:

Have a look at the quiesce command. Normally, it should be as simple as:

db2 force applications all
db2 connect to database <<dbname>> in exclusive mode
db2 backup database......

Note that this is at the database level. Quiesce also works at the
instance level if you have multiple databases in an instance.

Tim B. wrote:

Hello,

I am looking for the proper way to shut down db2 completely so that I
can do a cold back up on all the databases.

Thanks!

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World!
>100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000
Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

[Blair Adamache]

DB2 does not support that. It can work if the database is truly
inactive, but if you run into a problem, IBM Service and Support may not
be able to help you.

Tim B. wrote:

Also, how can I completely shutdown db2 and grab the raw database files
for the backup? In other words, I don't want to backup using db2
commands, I might simply want to tar up the whole thing and go.

Blair Adamache wrote:

Have a look at the quiesce command. Normally, it should be as simple as:

db2 force applications all
db2 connect to database <<dbname>> in exclusive mode
db2 backup database......

Note that this is at the database level. Quiesce also works at the
instance level if you have multiple databases in an instance.

Tim B. wrote:

Hello,

I am looking for the proper way to shut down db2 completely so that I
can do a cold back up on all the databases.

Thanks!

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World!
>100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000
Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

[Jim]

Could you give me some examples on that quiesce command? Someone took my
damn book and I am having trouble coming up with decent documentation on
it.

Blair Adamache wrote:

When the backup completes, users can reconnect. You might want to
quiesce each database individually before backing it up - the time from
the start of the first backup to the second allows a large window for
lots of users to reconnect to the 2nd and 3rd databases.

Tim B. wrote:

Thanks for your response. This is the script that I will be running.
Does this sound decent:

#!/bin/bash

# The following three lines have been added by UDB DB2.
if [ -f ~/sqllib/db2profile ]; then
. ~/sqllib/db2profile
else
exit 1
fi

# kick out everyone
db2 force applications all

db2 connect to database db1 in exclusive mode
db2 "backup database db1 to /opt/BACKUP"

db2 connect to database db2 in exclusive mode
db2 "backup database db2 online to /opt/BACKUP"

db2 connect to database db3 in exclusive mode
db2 "backup database db3 online to /opt/BACKUP"
What do I have to do to ensure that no one attempts any read/writes to
the database and also, how do I put the database back online?
Blair Adamache wrote:

Have a look at the quiesce command. Normally, it should be as simple as:

db2 force applications all
db2 connect to database <<dbname>> in exclusive mode
db2 backup database......

Note that this is at the database level. Quiesce also works at the
instance level if you have multiple databases in an instance.

Tim B. wrote:

Hello,

I am looking for the proper way to shut down db2 completely so that I
can do a cold back up on all the databases.

Thanks!

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World!
>100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000
Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---

[Jim]

Also,

If I simply wanted to back db2 up at a filesystem level, without running db2
commands, how can I get db2 in a state where this is possible? I know this
requires shutting it completely down, but how?

Thanks!
Blair Adamache wrote:

When the backup completes, users can reconnect. You might want to
quiesce each database individually before backing it up - the time from
the start of the first backup to the second allows a large window for
lots of users to reconnect to the 2nd and 3rd databases.

Tim B. wrote:

Thanks for your response. This is the script that I will be running.
Does this sound decent:

#!/bin/bash

# The following three lines have been added by UDB DB2.
if [ -f ~/sqllib/db2profile ]; then
. ~/sqllib/db2profile
else
exit 1
fi

# kick out everyone
db2 force applications all

db2 connect to database db1 in exclusive mode
db2 "backup database db1 to /opt/BACKUP"

db2 connect to database db2 in exclusive mode
db2 "backup database db2 online to /opt/BACKUP"

db2 connect to database db3 in exclusive mode
db2 "backup database db3 online to /opt/BACKUP"
What do I have to do to ensure that no one attempts any read/writes to
the database and also, how do I put the database back online?
Blair Adamache wrote:

Have a look at the quiesce command. Normally, it should be as simple as:

db2 force applications all
db2 connect to database <<dbname>> in exclusive mode
db2 backup database......

Note that this is at the database level. Quiesce also works at the
instance level if you have multiple databases in an instance.

Tim B. wrote:

Hello,

I am looking for the proper way to shut down db2 completely so that I
can do a cold back up on all the databases.

Thanks!

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World!
>100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000
Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---

[Mark A]

"Jim" <[e-mail]> wrote in message
news:10***************@hive.lunargravity.net...

Could you give me some examples on that quiesce command? Someone took my
damn book and I am having trouble coming up with decent documentation on
it.

Web based manuals
http://publib.boulder.ibm.com/infoce...help/index.jsp

PDF Manuals (can be downloaded):
http://www-3.ibm.com/cgi-bin/db2www/...bs.d2w/en_main
(The above link will wrap) Page down to bottom of screen.

Don't leave home without them.

[Blair Adamache]

db2stop

Jim wrote:

Also,

If I simply wanted to back db2 up at a filesystem level, without running db2
commands, how can I get db2 in a state where this is possible? I know this
requires shutting it completely down, but how?

Thanks!
Blair Adamache wrote:

When the backup completes, users can reconnect. You might want to
quiesce each database individually before backing it up - the time from
the start of the first backup to the second allows a large window for
lots of users to reconnect to the 2nd and 3rd databases.

Tim B. wrote:

Thanks for your response. This is the script that I will be running.
Does this sound decent:

#!/bin/bash

# The following three lines have been added by UDB DB2.
if [ -f ~/sqllib/db2profile ]; then
. ~/sqllib/db2profile
else
exit 1
fi

# kick out everyone
db2 force applications all

db2 connect to database db1 in exclusive mode
db2 "backup database db1 to /opt/BACKUP"

db2 connect to database db2 in exclusive mode
db2 "backup database db2 online to /opt/BACKUP"

db2 connect to database db3 in exclusive mode
db2 "backup database db3 online to /opt/BACKUP"
What do I have to do to ensure that no one attempts any read/writes to
the database and also, how do I put the database back online?
Blair Adamache wrote:
Have a look at the quiesce command. Normally, it should be as simple as:

db2 force applications all
db2 connect to database <<dbname>> in exclusive mode
db2 backup database......

Note that this is at the database level. Quiesce also works at the
instance level if you have multiple databases in an instance.

Tim B. wrote:
>Hello,
>
>I am looking for the proper way to shut down db2 completely so that I
>can do a cold back up on all the databases.
>
>Thanks!
>
>
>
>----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
>News==----
>http://www.newsfeed.com The #1 Newsgroup Service in the World!
>
>>100,000 Newsgroups
>
>---= 19 East/West-Coast Specialized Servers - Total Privacy via
>Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000
Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---

[Jim]

Oh wow....I thought there was more to it than that. I will be able to
restore all of the data by doing:

#!/bin/bash

db2stop
tar czf /backup/foo.tar.gz /home/db2inst1

^ I know this is simplified but then I could simply untar /home/db2inst1 and
have a working database, correct?

I am acting like a moron and asking dumb questions but just crossing my T's
and dotting my I's. I appreciate your patience with my ignorance.

Blair Adamache wrote:

db2stop

Jim wrote:

Also,

If I simply wanted to back db2 up at a filesystem level, without running
db2
commands, how can I get db2 in a state where this is possible? I know
this requires shutting it completely down, but how?

Thanks!
Blair Adamache wrote:

When the backup completes, users can reconnect. You might want to
quiesce each database individually before backing it up - the time from
the start of the first backup to the second allows a large window for
lots of users to reconnect to the 2nd and 3rd databases.

Tim B. wrote:
Thanks for your response. This is the script that I will be running.
Does this sound decent:

#!/bin/bash

# The following three lines have been added by UDB DB2.
if [ -f ~/sqllib/db2profile ]; then
. ~/sqllib/db2profile
else
exit 1
fi

# kick out everyone
db2 force applications all

db2 connect to database db1 in exclusive mode
db2 "backup database db1 to /opt/BACKUP"

db2 connect to database db2 in exclusive mode
db2 "backup database db2 online to /opt/BACKUP"

db2 connect to database db3 in exclusive mode
db2 "backup database db3 online to /opt/BACKUP"
What do I have to do to ensure that no one attempts any read/writes to
the database and also, how do I put the database back online?
Blair Adamache wrote:
>Have a look at the quiesce command. Normally, it should be as simple
>as:
>
>db2 force applications all
>db2 connect to database <<dbname>> in exclusive mode
>db2 backup database......
>
>Note that this is at the database level. Quiesce also works at the
>instance level if you have multiple databases in an instance.
>
>Tim B. wrote:
>
>
>>Hello,
>>
>>I am looking for the proper way to shut down db2 completely so that I
>>can do a cold back up on all the databases.
>>
>>Thanks!
>>
>>
>>
>>----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
>>News==----
>>http://www.newsfeed.com The #1 Newsgroup Service in the World!
>>
>>>100,000 Newsgroups
>>
>>---= 19 East/West-Coast Specialized Servers - Total Privacy via
>>Encryption =---
>
>
>
----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000
Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via
Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==---- http://www.newsfeed.com The #1 Newsgroup Service in the World!

>100,000 Newsgroups ---= 19 East/West-Coast Specialized Servers - Total

Privacy via Encryption =---

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---