> Date: Sat, 25 Jan 2003 16:14:26 -0500
> From: Paul Turpin <[EMAIL PROTECTED]>
> Subject: Re: [DB2EUG] DB2 EEE V7 FP8 Crashing

As Christi says EEE is different than DB2 on OS/390.  It has some unique 
challenges
on the UNIX platform, but you rarely share the environment with other 
users as you
do in the OS/390 world.

I'm not sure why you are having to do a full recovery after a crash. 
Normally DB2 would
go into automatic crash recovery after you bring DB2 back up.  That can 
take a few
minutes as DB2 spins through the logs.  I would think that since you are 
in a data
warehouse environment you would have less logging to deal with.  The 
only time I have
seen the need for a real recovery in the EEE environment is when there 
was a data
corruption issue caused by hardware problems.  I do wish that DB2 would 
issue a few
more messages indicating where it is during the recovery process, so I 
can estimate
when it will return to life, but maybe I'll get those in V8.

Fortier, Christi (GTS) wrote:

>I did not say it is difficult to maintain.  It is just a different mindset
>than mainframes.  You need to tune the hardware & if you choose a multiple
>server cluster, you need to manage more servers.  There are some parms that
>are critical in UDB.  There are some things that will be easier on
>mainframes & other things that are easier on UDB (some easier on AIX others
>easier on Win).  Every installation is different. Like any database on any
>platform, you can keep the systems up & performing optimally if they are
>tuned to take advantage of features & allow for current limitations.
>
>If migrating to Regattas still make you uncomfortable, perhaps you should
>evaluate Z-linux to the mainframe?
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>Sent: Friday, January 24, 2003 2:00 PM
>To: Reys, Ellen
>Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Pendlebury-Bowe, Leslie;
>[EMAIL PROTECTED]
>Subject: RE: [DB2EUG] DB2 EEE V7 FP8 Crashing
>
>
>
>Thanks for your feedback.  You have brought out  exactly one of my points.
>Little DB2 seems to be difficult to maintain and has all sorts of issues
>about backward compatibility and stability.  It concerns me greatly.
>Problems take days and sometimes weeks to debug and fix.  How acceptable is
>this with a critical highly visable applicaiton?  In my mind not very.
>
>Frank
>
>
> 
>
>                      "Reys, Ellen"
>
>                      <[EMAIL PROTECTED]        To:
>"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>,
>
>                      m>                        [EMAIL PROTECTED]
>
>                      Sent by:                 cc:       [EMAIL PROTECTED],
>"Pendlebury-Bowe, Leslie"                                 
>                      owner-db2eug@lugw
><[EMAIL PROTECTED]>, [EMAIL PROTECTED]
>
>                      ash.org                  Subject:  RE: [DB2EUG] DB2
>EEE V7 FP8 Crashing                                          
> 
>
> 
>
>                      01/24/2003 12:57
>
>                      PM
>
>                      Please respond to
>
>                      "Reys, Ellen"
>
> 
>
> 
>
>
>
>
>
>Hello Frank,
>
>We have in production a fairly large Warehouse (over 6 TB) on DB2 UDB EEE
>7.2 FP4 for over 8 months, and we had it in UAT prior to that. It performs
>well and is stable. We did not have a chance to do the FP upgrade, as we
>first need to upgrade development and run it for some time. Every time we
>about to upgrade to the latest FP, this FP becomes "problematic" and
>introduces new severe bugs. However, we are still in business :)
>
>Ellen Klebaner-Reys
>Data Management Services
>Inovant - a Visa Solutions Company
>[EMAIL PROTECTED]/650-432-1746  m/s: 3125-1D
>
>
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>Sent: Friday, January 24, 2003 4:04 AM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]; Pendlebury-Bowe, Leslie;
>[EMAIL PROTECTED]
>Subject: [DB2EUG] DB2 EEE V7 FP8 Crashing
>
>
>
>We are about to implement a very large Data Warehouse in DB2 EEE on a
>Regatta machine.  As we have been working with what I call little DB2 (as
>opposed to big DB2 Mainframe OS/390), I am seeing that we have many cases
>where we are forced to recover the entire Database because DB2 crashes for
>various reasons.
>
>The most recent example of what I am talking about is DB2 Tempspace filled
>up and caused DB2 to crash.  This is a known bug according to IBM and they
>have a fix for V7 FP8.  The thing I find very concerning is that we can't
>simply bring DB2 backup.  Rather we are in a position to have to recover
>the entire Database.  Our warehouse is planned to be about 60 TB with
>thousands of tables.  I am concerned about the fact it seems many times
>when DB2  crashes we are in this forced recovery situation.  As the
>database continue to grow this is going to become more and more time
>consuming and fraught with danger.  It also puts us in a negative light
>with the user community and our management.
>
>It appears little DB2 has stability problems and I am becoming concerned
>about the answer we keep getting from IBM to do a full recovery, or that
>seems to be the only solution.  Do other's using DB2 on AIX seem to be
>experiencing this problem or needing to recover the entire DB??   I am
>concerned we are taking a huge step backwards by taking our warehouse off
>the Mainframe as it seems little DB2 is where big DB2 was 15 years ago.
>
>Anyone have any thoughts they would like to share?  I appreciate the
>opportunity to discuss this with others in the real world.
>
>Frank
-
:::  When replying to the list, please use 'Reply-All' and make sure
:::  a copy goes to the list ([EMAIL PROTECTED]).
***  To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
***  For more information, check http://www.db2eug.uni.cc

Reply via email to