Re: Extend db question

2007-06-18 Thread חנה דרזי
Hello,

You can upload and load the db in order to free space.
It is good for performance too.
The all process of reorgenize the database is is the admin book.

Good Luck,
Hana

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Allan Mills
Sent: Thursday, June 14, 2007 3:44 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Extend db question

sure does

Allan Mills | AIX and TSM Administrator
Business  Technology Services | New South Wales Police

8835 9286 (internal 29286)
Mob: 0408 860 046



Paul Dudley [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
14/06/2007 11:35
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] Extend db question







OK - when I run a q db the available space in MB is 32,768, the
assigned capacity in MB is 32,768 and the maximum extension in MB is 0.

I assume that this means that I have to run def dbvol to create
another database volume file before I can run extend db?

Regards
Paul


 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
 Behalf Of David Longo
 Sent: Thursday, 14 June 2007 10:56 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: [ADSM-L] Extend db question

 That note in manual means the size of an individual DB Volume,
 not the DB as a whole.  There are more automatic extensions
 of disks, filesystems, etc. these days - and more to come.

 After you have formatted a DB volume with TSM, you shouldn't monkey
 with it at the OS level.

 Extend DB is what you want.  Generally use size of DB volumes.
 As say you have (6) 4 GB dbvols defined, to use one you would
 enter: extend db 4000.  The value is in MB.

 This is if you have already use def dbvol to create the vol of
course.

 David Longo

  Paul Dudley [EMAIL PROTECTED] 6/13/2007 7:55 PM 
 This morning we received a TSM alert:

 The database utilization is too high. Condition (85.1  85)
 Recommendation: Consider a database space trigger or increase the size
 of the database.

 Going back through my daily TSM reports I have seen that the database
 utilization has increased from 60% to 85% over the past few months.
This
 is to be expected as we are performing more backups than previously.

 Is it correct that I should use the extend db command to do this?

 The q db command shows that the database is 32 Gb in size. On the
server
 I have 24 Gb of free space so I have room to extend the size of the
 database.

 The one thing that confuses me is this statement in the help extend db
 command:

 Attention: You cannot change the size of an allocated database volume
 after
 it has been defined to Tivoli Storage Manager. If you do, Tivoli
Storage
 Manager may not initialize correctly and data could be lost.

 Can someone clarify this statement for me and confirm that using the
 extend db command is the correct way to do this.

 Thanks
 Paul



 Paul Dudley
 ANL IT Operations Dept.
 ANL Container Line
 [EMAIL PROTECTED]





 ANL - CELEBRATING 50 YEARS

 ANL DISCLAIMER
 This e-mail and any file attached is confidential, and intended solely
to the
 named addressees. Any unauthorised dissemination or use is strictly
 prohibited. If you received this e-mail in error, please immediately
notify the
 sender by return e-mail from your system. Please do not copy, use or
make
 reference to it for any purpose, or disclose its contents to any
person.




ANL - CELEBRATING 50 YEARS

ANL DISCLAIMER
This e-mail and any file attached is confidential, and intended solely to
the named addressees. Any unauthorised dissemination or use is strictly
prohibited. If you received this e-mail in error, please immediately
notify the sender by return e-mail from your system. Please do not copy,
use or make reference to it for any purpose, or disclose its contents to
any person.

All mail is subject to content scanning for possible violation of New
South Wales Police
electronic Mail Policy. All persons are required to familiarise themselves
with the
content of the policy located on the NSWP Intranet BULLETIN BOARD.




This message and any attachment is confidential and may
be privileged or otherwise protected from disclosure. If you
have received it by mistake, please let us know by reply
and then delete it from your system; you should not copy
the message or disclose its contents to anyone.


Re: Extend db question

2007-06-18 Thread Richard Sims

On Jun 18, 2007, at 4:04 AM, חנה דרזי wrote:


You can upload and load the db in order to free space.
It is good for performance too.
The all process of reorgenize the database is is the admin book.


I strongly recommend against doing this.  The outage is prolonged,  
there is no documentation on what to do if anything goes wrong, and  
overall the risks are not worth the short-lived performance gain.   
Don't play with fire.


   Richard Sims


Re: Extend db question

2007-06-13 Thread David Longo
That note in manual means the size of an individual DB Volume,
not the DB as a whole.  There are more automatic extensions
of disks, filesystems, etc. these days - and more to come.

After you have formatted a DB volume with TSM, you shouldn't monkey
with it at the OS level.

Extend DB is what you want.  Generally use size of DB volumes.
As say you have (6) 4 GB dbvols defined, to use one you would
enter: extend db 4000.  The value is in MB.

This is if you have already use def dbvol to create the vol of course.

David Longo

 Paul Dudley [EMAIL PROTECTED] 6/13/2007 7:55 PM 
This morning we received a TSM alert:

The database utilization is too high. Condition (85.1  85)
Recommendation: Consider a database space trigger or increase the size
of the database.

Going back through my daily TSM reports I have seen that the database
utilization has increased from 60% to 85% over the past few months. This
is to be expected as we are performing more backups than previously.

Is it correct that I should use the extend db command to do this?

The q db command shows that the database is 32 Gb in size. On the server
I have 24 Gb of free space so I have room to extend the size of the
database.

The one thing that confuses me is this statement in the help extend db
command:

Attention: You cannot change the size of an allocated database volume
after
it has been defined to Tivoli Storage Manager. If you do, Tivoli Storage
Manager may not initialize correctly and data could be lost.

Can someone clarify this statement for me and confirm that using the
extend db command is the correct way to do this.

Thanks
Paul


 
Paul Dudley
ANL IT Operations Dept.
ANL Container Line
[EMAIL PROTECTED] 





ANL - CELEBRATING 50 YEARS

ANL DISCLAIMER
This e-mail and any file attached is confidential, and intended solely to the 
named addressees. Any unauthorised dissemination or use is strictly prohibited. 
If you received this e-mail in error, please immediately notify the sender by 
return e-mail from your system. Please do not copy, use or make reference to it 
for any purpose, or disclose its contents to any person.


Re: Extend db question

2007-06-13 Thread Paul Dudley
OK - when I run a q db the available space in MB is 32,768, the
assigned capacity in MB is 32,768 and the maximum extension in MB is 0.

I assume that this means that I have to run def dbvol to create
another database volume file before I can run extend db?

Regards
Paul


 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
 Behalf Of David Longo
 Sent: Thursday, 14 June 2007 10:56 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: [ADSM-L] Extend db question

 That note in manual means the size of an individual DB Volume,
 not the DB as a whole.  There are more automatic extensions
 of disks, filesystems, etc. these days - and more to come.

 After you have formatted a DB volume with TSM, you shouldn't monkey
 with it at the OS level.

 Extend DB is what you want.  Generally use size of DB volumes.
 As say you have (6) 4 GB dbvols defined, to use one you would
 enter: extend db 4000.  The value is in MB.

 This is if you have already use def dbvol to create the vol of
course.

 David Longo

  Paul Dudley [EMAIL PROTECTED] 6/13/2007 7:55 PM 
 This morning we received a TSM alert:

 The database utilization is too high. Condition (85.1  85)
 Recommendation: Consider a database space trigger or increase the size
 of the database.

 Going back through my daily TSM reports I have seen that the database
 utilization has increased from 60% to 85% over the past few months.
This
 is to be expected as we are performing more backups than previously.

 Is it correct that I should use the extend db command to do this?

 The q db command shows that the database is 32 Gb in size. On the
server
 I have 24 Gb of free space so I have room to extend the size of the
 database.

 The one thing that confuses me is this statement in the help extend db
 command:

 Attention: You cannot change the size of an allocated database volume
 after
 it has been defined to Tivoli Storage Manager. If you do, Tivoli
Storage
 Manager may not initialize correctly and data could be lost.

 Can someone clarify this statement for me and confirm that using the
 extend db command is the correct way to do this.

 Thanks
 Paul



 Paul Dudley
 ANL IT Operations Dept.
 ANL Container Line
 [EMAIL PROTECTED]





 ANL - CELEBRATING 50 YEARS

 ANL DISCLAIMER
 This e-mail and any file attached is confidential, and intended solely
to the
 named addressees. Any unauthorised dissemination or use is strictly
 prohibited. If you received this e-mail in error, please immediately
notify the
 sender by return e-mail from your system. Please do not copy, use or
make
 reference to it for any purpose, or disclose its contents to any
person.




ANL - CELEBRATING 50 YEARS

ANL DISCLAIMER
This e-mail and any file attached is confidential, and intended solely to the 
named addressees. Any unauthorised dissemination or use is strictly prohibited. 
If you received this e-mail in error, please immediately notify the sender by 
return e-mail from your system. Please do not copy, use or make reference to it 
for any purpose, or disclose its contents to any person.


Re: Extend db question

2007-06-13 Thread Allan Mills
sure does

Allan Mills | AIX and TSM Administrator
Business  Technology Services | New South Wales Police

8835 9286 (internal 29286)
Mob: 0408 860 046



Paul Dudley [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
14/06/2007 11:35
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] Extend db question







OK - when I run a q db the available space in MB is 32,768, the
assigned capacity in MB is 32,768 and the maximum extension in MB is 0.

I assume that this means that I have to run def dbvol to create
another database volume file before I can run extend db?

Regards
Paul


 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
 Behalf Of David Longo
 Sent: Thursday, 14 June 2007 10:56 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: [ADSM-L] Extend db question

 That note in manual means the size of an individual DB Volume,
 not the DB as a whole.  There are more automatic extensions
 of disks, filesystems, etc. these days - and more to come.

 After you have formatted a DB volume with TSM, you shouldn't monkey
 with it at the OS level.

 Extend DB is what you want.  Generally use size of DB volumes.
 As say you have (6) 4 GB dbvols defined, to use one you would
 enter: extend db 4000.  The value is in MB.

 This is if you have already use def dbvol to create the vol of
course.

 David Longo

  Paul Dudley [EMAIL PROTECTED] 6/13/2007 7:55 PM 
 This morning we received a TSM alert:

 The database utilization is too high. Condition (85.1  85)
 Recommendation: Consider a database space trigger or increase the size
 of the database.

 Going back through my daily TSM reports I have seen that the database
 utilization has increased from 60% to 85% over the past few months.
This
 is to be expected as we are performing more backups than previously.

 Is it correct that I should use the extend db command to do this?

 The q db command shows that the database is 32 Gb in size. On the
server
 I have 24 Gb of free space so I have room to extend the size of the
 database.

 The one thing that confuses me is this statement in the help extend db
 command:

 Attention: You cannot change the size of an allocated database volume
 after
 it has been defined to Tivoli Storage Manager. If you do, Tivoli
Storage
 Manager may not initialize correctly and data could be lost.

 Can someone clarify this statement for me and confirm that using the
 extend db command is the correct way to do this.

 Thanks
 Paul



 Paul Dudley
 ANL IT Operations Dept.
 ANL Container Line
 [EMAIL PROTECTED]





 ANL - CELEBRATING 50 YEARS

 ANL DISCLAIMER
 This e-mail and any file attached is confidential, and intended solely
to the
 named addressees. Any unauthorised dissemination or use is strictly
 prohibited. If you received this e-mail in error, please immediately
notify the
 sender by return e-mail from your system. Please do not copy, use or
make
 reference to it for any purpose, or disclose its contents to any
person.




ANL - CELEBRATING 50 YEARS

ANL DISCLAIMER
This e-mail and any file attached is confidential, and intended solely to
the named addressees. Any unauthorised dissemination or use is strictly
prohibited. If you received this e-mail in error, please immediately
notify the sender by return e-mail from your system. Please do not copy,
use or make reference to it for any purpose, or disclose its contents to
any person.

All mail is subject to content scanning for possible violation of New
South Wales Police
electronic Mail Policy. All persons are required to familiarise themselves
with the
content of the policy located on the NSWP Intranet BULLETIN BOARD.




This message and any attachment is confidential and may
be privileged or otherwise protected from disclosure. If you
have received it by mistake, please let us know by reply
and then delete it from your system; you should not copy
the message or disclose its contents to anyone.