[DB2-L] Multiple DB2 subsystems on the same LPAR

Joseph Fatula

[DB2-L] Multiple DB2 subsystems on the same LPAR
Not good news--perhaps CPU upgrade time or application diet time.
Another thing which might help depending upon the application, the
data, and the number of old records is record archiving. Not a popular
solution but "any port in a storm" as they say.

Joe Fatula

----- Forwarded by Joseph Fatula/PHEAA on 01/05/05 01:40 PM -----

Joel Goldstein -
Responsive
Systems To
<[login to unmask email] [login to unmask email]
ystems.com> cc
Sent by: DB2 Data
Base Discussion Subject
List Re: [DB2-L] Multiple DB2 subsystems
<[login to unmask email] on the same LPAR
ORG>


01/05/05 01:35 PM


Please respond to
Joel Goldstein -
Responsive
Systems
<[login to unmask email]
ystems.com>







Pete,

I think the key phrase is what you wrote
is  "  1 very busy production DB2 subsystem on a very busy LPAR."
If your LPAR is already very busy, you probably can't afford to run a
second DB2 there, even if you were thinking
that the cpu consumption might be split 50/50.  It will cost you more cpu
to do this, and as others mentioned, there are  a lot
of other additional resource impacts as well.

Regards,
Joel
----- Original Message -----
From: Cavan, Peter
Newsgroups: bit.listserv.db2-l
To: [login to unmask email]
Sent: Wednesday, January 05, 2005 10:19 AM
Subject: [DB2-L] Multiple DB2 subsystems on the same LPAR

We are running Z/OS V1.4, DB2 V7.1. We are running 1 very busy production
DB2 subsystem on a very busy LPAR.

Would it be beneficial to split the work into 2 separate DB2 subsystems on
the same LPAR?

Any comments from someone already running multiple production subsystems on
the same LPAR?



Pete Cavan




This message and its contents (to include attachments) are the property of
Kmart Corporation (Kmart) and may contain confidential and proprietary
information. You are hereby notified that any disclosure, copying, or
distribution of this message, or the taking of any action based on
information contained herein is strictly prohibited. Unauthorized use of
information contained herein may subject you to civil and criminal
prosecution and penalties. If you are not the intended recipient, you
should delete this message immediately.
---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm
---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Tom Moulder

Re: Multiple DB2 subsystems on the same LPAR
(in response to Joseph Fatula)
So, have you thought about SQL tuning? One approach is described in an
article published in z/Journal last year. You can download at --> HYPERLINK
"http://www.zjournal.com/Article.asp?ArticleID=842"http://www.zjournal.com/A
rticle.asp?ArticleID=842.

Tom Moulder
TREX Associates, Inc.
9728 Delmonico
Keller, TX. 76248-9559
+1 817-741-5549 Office
+1 817-741-5548 Fax
+1 832-858-4279 Mobile
HYPERLINK "http://www.t-rex-associates.com/"www.t-rex-associates.com Web
Site

_____

From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf
Of Joel Goldstein - Responsive Systems
Sent: Wednesday, January 05, 2005 12:35 PM
To: [login to unmask email]
Subject: Re: [DB2-L] Multiple DB2 subsystems on the same LPAR


Pete,

I think the key phrase is what you wrote
is " 1 very busy production DB2 subsystem on a very busy LPAR."
If your LPAR is already very busy, you probably can't afford to run a second
DB2 there, even if you were thinking
that the cpu consumption might be split 50/50. It will cost you more cpu to
do this, and as others mentioned, there are a lot
of other additional resource impacts as well.

Regards,
Joel

----- Original Message -----
From: HYPERLINK "mailto:[login to unmask email]"Cavan, Peter
Newsgroups: bit.listserv.db2-l
To: HYPERLINK "mailto:[login to unmask email]"[login to unmask email]
Sent: Wednesday, January 05, 2005 10:19 AM
Subject: [DB2-L] Multiple DB2 subsystems on the same LPAR


We are running Z/OS V1.4, DB2 V7.1. We are running 1 very busy production
DB2 subsystem on a very busy LPAR.

Would it be beneficial to split the work into 2 separate DB2 subsystems on
the same LPAR?

Any comments from someone already running multiple production subsystems on
the same LPAR?



Pete Cavan





_____




This message and its contents (to include attachments) are the property of
Kmart Corporation (Kmart) and may contain confidential and proprietary
information. You are hereby notified that any disclosure, copying, or
distribution of this message, or the taking of any action based on
information contained herein is strictly prohibited. Unauthorized use of
information contained herein may subject you to civil and criminal
prosecution and penalties. If you are not the intended recipient, you should
delete this message immediately.

----------------------------------------------------------------------------
----- Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm

----------------------------------------------------------------------------
----- Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm


--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.6.8 - Release Date: 1/3/2005



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.6.8 - Release Date: 1/3/2005


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm