Re: Company thought DB2 will be better than Oracle.
"Larry Edelstein" <lsedels@us.ibm.com> wrote in message news:3F6F3671.3E92F3D5@us.ibm.com... > Peter, > > I'm not even sure what you're trying to say. > > No one ever said anything about consultants. When you have a problem ... especially a serious one like the one you > describe ... you open up a case with IBM and find out what it takes to fix it! > > Peter ... several people on this newsgroup have offered to help get this escalated for you ... but you have not > provided any additional information. Please don't make it sound like IBM has not listened to you or isn't willing to > do anything about this. > > I am very sorry ... but as I said ... I am going to have to assume that this didn't really happen. This will be my > last post responding to you, unless you can provide some more details and/or more information. > > Larry Edelstein > > Peter wrote: > > > Hi Larry! > > > > There is a difference between in-house DBA and seeing the response of every > > select Statement on production and being highly paid IBM on-call consultant. > > No company will contact IBM consultant for db2start. > > > > I wish you should have taken it like Bill Gates took new Windows release crash > > in a big conference. He immediately admitted developers have to fix the code. > > > > Peter > > > > Larry Edelstein <lsedels@us.ibm.com> wrote in message news:<3F6C831C.F45A9D85@us.ibm.com>... > > > Peter ... I have worked with many customers for more than two years who have never experienced this problem. > > > > > > You are still not providing any specifics or details on this. What are you afraid of? At this point, I must > > > assume that this never happened. I'm sorry. It doesn't take much to provide evidence. > > > > > > Larry Edelstein > > > > > > Peter wrote: > > > > > > > Hi Larry! > > > > > > > > Regarding your comment on continue to trash DB2, I wish you should not > > > > take it in negative way. I find same problem in DB2 as in OS/2. > > > > > > > > I have worked on OS/2 and technically it is far superior than Microsoft > > > > Windows. It did have same issue of all of sudden crashed problem that was > > > > resolved in few years. Unfortunately MS already had the market before that. > > > > > > > > If you find my info is incorrect, I am just asking you to work on one > > > > install of DB2 for 2 years. You will see instance disappearance and when > > > > you type db2start; it starts as if nothing has happened. It simply forgets > > > > and forgives it. I have never seen database starting like that and forgetting > > > > why it crashed all of sudden in production. It is good and bad both. As > > > > a DBA you have to start instance again only and blame poor developers > > > > for wrong SQL statements. Poor guy only did select on a table with > > > > a simple where clause. I have been asked to give query details; there is > > > > nothing in the query other than select on one table with one condition > > > > on where clause. Simply blame the DB2 developers as a workaround. > > > > > > > > Peter > > > > > > > > "Neil Truby" <neil.truby@ardenta.com> wrote in message news:<bkhah6$1qke9$1@ID-162943.news.uni-berlin.de>... > > > > > "Daniel Morgan" <damorgan@x.washington.edu> wrote in message > > > > > news:1064018434.923612@yasure... > > > > > > Larry Edelstein wrote: > > > > > > > > > Is this really going to change anyone's mind? Do you really believe what > > > > > > someone uses as a reference platform is going to make the CFO of a > > > > > > company write a big check? Change their infrastructure? Migrate their > > > > > > existing applications? Get a major university to start offering courses? > > > > > > Maybe they use it as a reference platform because they were cut a > > > > > > sweetheart deal? How can anyone possibly know what decision was made on > > > > > > the 17th hole after a few martinis and a pair of tickets to the World > > > > > > Series or the SuperBowl? > > > > > > > > > > How terribly cynical of you, Daniel! > Larry, While Peter's problem might be a canard(probably is), maybe he does not understand what you mean. Peter, What Larry is trying to say is that you need to provide more information. If you went to a medical Dr and said I have pain and did not give any further information, such as location, then the Dr. would not be able to do much for you. So can you tell us what select statement crashes DB2 in your environment. Could you also tell us what Operating System DB2 is running on and if possible the version of DB2? What would be very nice is what steps you have to perform to cause this crash. If you can't even tell us these things then it calls into question your integrity. Jim
I work for a big financial company and I can understand Larry and you. To give you the select statement and DB2 release number and platforms detail will violate my employment agreement. They are moving the critical DB2/UNIX application to OS/390. I have seen it twice once on AIX and second time on LINUX system. Let us start using DB2 UDB as in-house DBA and you will see yourself disappearance of DB2 instance. It is not developers fault but as work around you have to blame development group. Peter "Jim Kennedy" <kennedy-down_with_spammers@no_spam.comcast.net> wrote in message news:<aPNbb.548237$YN5.371362@sccrnsc01>... > "Larry Edelstein" <lsedels@us.ibm.com> wrote in message > news:3F6F3671.3E92F3D5@us.ibm.com... > > Peter, > > > > I'm not even sure what you're trying to say. > > > > No one ever said anything about consultants. When you have a problem ... > especially a serious one like the one you > > describe ... you open up a case with IBM and find out what it takes to fix > it! > > > > Peter ... several people on this newsgroup have offered to help get this > escalated for you ... but you have not > > provided any additional information. Please don't make it sound like IBM > has not listened to you or isn't willing to > > do anything about this. > > > > I am very sorry ... but as I said ... I am going to have to assume that > this didn't really happen. This will be my > > last post responding to you, unless you can provide some more details > and/or more information. > > > > Larry Edelstein > > > > Peter wrote: > > > > > Hi Larry! > > > > > > There is a difference between in-house DBA and seeing the response of > every > > > select Statement on production and being highly paid IBM on-call > consultant. > > > No company will contact IBM consultant for db2start. > > > > > > I wish you should have taken it like Bill Gates took new Windows release > crash > > > in a big conference. He immediately admitted developers have to fix the > code. > > > > > > Peter > > > > > > Larry Edelstein <lsedels@us.ibm.com> wrote in message > news:<3F6C831C.F45A9D85@us.ibm.com>... > > > > Peter ... I have worked with many customers for more than two years > who have never experienced this problem. > > > > > > > > You are still not providing any specifics or details on this. What are > you afraid of? At this point, I must > > > > assume that this never happened. I'm sorry. It doesn't take much to > provide evidence. > > > > > > > > Larry Edelstein > > > > > > > > Peter wrote: > > > > > > > > > Hi Larry! > > > > > > > > > > Regarding your comment on continue to trash DB2, I wish you should > not > > > > > take it in negative way. I find same problem in DB2 as in OS/2. > > > > > > > > > > I have worked on OS/2 and technically it is far superior than > Microsoft > > > > > Windows. It did have same issue of all of sudden crashed problem > that was > > > > > resolved in few years. Unfortunately MS already had the market > before that. > > > > > > > > > > If you find my info is incorrect, I am just asking you to work on > one > > > > > install of DB2 for 2 years. You will see instance disappearance and > when > > > > > you type db2start; it starts as if nothing has happened. It simply > forgets > > > > > and forgives it. I have never seen database starting like that and > forgetting > > > > > why it crashed all of sudden in production. It is good and bad both. > As > > > > > a DBA you have to start instance again only and blame poor > developers > > > > > for wrong SQL statements. Poor guy only did select on a table with > > > > > a simple where clause. I have been asked to give query details; > there is > > > > > nothing in the query other than select on one table with one > condition > > > > > on where clause. Simply blame the DB2 developers as a workaround. > > > > > > > > > > Peter > > > > > > > > > > "Neil Truby" <neil.truby@ardenta.com> wrote in message > news:<bkhah6$1qke9$1@ID-162943.news.uni-berlin.de>... > > > > > > "Daniel Morgan" <damorgan@x.washington.edu> wrote in message > > > > > > news:1064018434.923612@yasure... > > > > > > > Larry Edelstein wrote: > > > > > > > > Is this really going to change anyone's mind? Do you really > believe what > > > > > > > someone uses as a reference platform is going to make the CFO of > a > > > > > > > company write a big check? Change their infrastructure? Migrate > their > > > > > > > existing applications? Get a major university to start offering > courses? > > > > > > > Maybe they use it as a reference platform because they were cut > a > > > > > > > sweetheart deal? How can anyone possibly know what decision was > made on > > > > > > > the 17th hole after a few martinis and a pair of tickets to the > World > > > > > > > Series or the SuperBowl? > > > > > > > > > > > > How terribly cynical of you, Daniel! > > > > Larry, > While Peter's problem might be a canard(probably is), maybe he does not > understand what you mean. > > Peter, > What Larry is trying to say is that you need to provide more information. > If you went to a medical Dr and said I have pain and did not give any > further information, such as location, then the Dr. would not be able to do > much for you. So can you tell us what select statement crashes DB2 in your > environment. Could you also tell us what Operating System DB2 is running on > and if possible the version of DB2? What would be very nice is what steps > you have to perform to cause this crash. If you can't even tell us these > things then it calls into question your integrity. > Jim
Surely a big financial company would open a problem record with IBM for such a problem? Can you post the problem (PMR) number or send it to me in an e-mail? I agree that a SELECT statement should not crash the instance - but I have seen this happen. Of the 17 original TPC-D queries, one could crash SQL Server (don't remember if it was Microsoft or Sybase SQL Server) on Windows at the 1 GB scale factor. Peter wrote: > I work for a big financial company and I can understand Larry and you. > To give you the select statement and DB2 release number and platforms > detail will violate my employment agreement. They are moving the > critical DB2/UNIX application to OS/390. > > I have seen it twice once on AIX and second time on LINUX system. > Let us start using DB2 UDB as in-house DBA and you will see yourself > disappearance of DB2 instance. It is not developers fault but > as work around you have to blame development group. > > > > Peter > > > > > "Jim Kennedy" <kennedy-down_with_spammers@no_spam.comcast.net> wrote in message news:<aPNbb.548237$YN5.371362@sccrnsc01>... > >>"Larry Edelstein" <lsedels@us.ibm.com> wrote in message >>news:3F6F3671.3E92F3D5@us.ibm.com... >> >>>Peter, >>> >>>I'm not even sure what you're trying to say. >>> >>>No one ever said anything about consultants. When you have a problem ... >> >> especially a serious one like the one you >> >>>describe ... you open up a case with IBM and find out what it takes to fix >> >> it! >> >>>Peter ... several people on this newsgroup have offered to help get this >> >> escalated for you ... but you have not >> >>>provided any additional information. Please don't make it sound like IBM >> >> has not listened to you or isn't willing to >> >>>do anything about this. >>> >>>I am very sorry ... but as I said ... I am going to have to assume that >> >> this didn't really happen. This will be my >> >>>last post responding to you, unless you can provide some more details >> >> and/or more information. >> >>>Larry Edelstein >>> >>>Peter wrote: >>> >>> >>>>Hi Larry! >>>> >>>>There is a difference between in-house DBA and seeing the response of >> >> every >> >>>>select Statement on production and being highly paid IBM on-call >> >> consultant. >> >>>>No company will contact IBM consultant for db2start. >>>> >>>>I wish you should have taken it like Bill Gates took new Windows release >> >> crash >> >>>>in a big conference. He immediately admitted developers have to fix the >> >> code. >> >>>>Peter >>>> >>>>Larry Edelstein <lsedels@us.ibm.com> wrote in message >> >> news:<3F6C831C.F45A9D85@us.ibm.com>... >> >>>>>Peter ... I have worked with many customers for more than two years >> >> who have never experienced this problem. >> >>>>>You are still not providing any specifics or details on this. What are >> >> you afraid of? At this point, I must >> >>>>>assume that this never happened. I'm sorry. It doesn't take much to >> >> provide evidence. >> >>>>>Larry Edelstein >>>>> >>>>>Peter wrote: >>>>> >>>>> >>>>>>Hi Larry! >>>>>> >>>>>>Regarding your comment on continue to trash DB2, I wish you should >> >> not >> >>>>>>take it in negative way. I find same problem in DB2 as in OS/2. >>>>>> >>>>>>I have worked on OS/2 and technically it is far superior than >> >> Microsoft >> >>>>>>Windows. It did have same issue of all of sudden crashed problem >> >> that was >> >>>>>>resolved in few years. Unfortunately MS already had the market >> >> before that. >> >>>>>>If you find my info is incorrect, I am just asking you to work on >> >> one >> >>>>>>install of DB2 for 2 years. You will see instance disappearance and >> >> when >> >>>>>>you type db2start; it starts as if nothing has happened. It simply >> >> forgets >> >>>>>>and forgives it. I have never seen database starting like that and >> >> forgetting >> >>>>>>why it crashed all of sudden in production. It is good and bad both. >> >> As >> >>>>>>a DBA you have to start instance again only and blame poor >> >> developers >> >>>>>>for wrong SQL statements. Poor guy only did select on a table with >>>>>>a simple where clause. I have been asked to give query details; >> >> there is >> >>>>>>nothing in the query other than select on one table with one >> >> condition >> >>>>>>on where clause. Simply blame the DB2 developers as a workaround. >>>>>> >>>>>>Peter >>>>>> >>>>>>"Neil Truby" <neil.truby@ardenta.com> wrote in message >> >> news:<bkhah6$1qke9$1@ID-162943.news.uni-berlin.de>... >> >>>>>>>"Daniel Morgan" <damorgan@x.washington.edu> wrote in message >>>>>>>news:1064018434.923612@yasure... >>>>>>> >>>>>>>>Larry Edelstein wrote: >> >> >> >>>>>>>>Is this really going to change anyone's mind? Do you really >> >> believe what >> >>>>>>>>someone uses as a reference platform is going to make the CFO of >> >> a >> >>>>>>>>company write a big check? Change their infrastructure? Migrate >> >> their >> >>>>>>>>existing applications? Get a major university to start offering >> >> courses? >> >>>>>>>>Maybe they use it as a reference platform because they were cut >> >> a >> >>>>>>>>sweetheart deal? How can anyone possibly know what decision was >> >> made on >> >>>>>>>>the 17th hole after a few martinis and a pair of tickets to the >> >> World >> >>>>>>>>Series or the SuperBowl? >>>>>>> >>>>>>>How terribly cynical of you, Daniel! >>> >>Larry, >>While Peter's problem might be a canard(probably is), maybe he does not >>understand what you mean. >> >>Peter, >>What Larry is trying to say is that you need to provide more information. >>If you went to a medical Dr and said I have pain and did not give any >>further information, such as location, then the Dr. would not be able to do >>much for you. So can you tell us what select statement crashes DB2 in your >>environment. Could you also tell us what Operating System DB2 is running on >>and if possible the version of DB2? What would be very nice is what steps >>you have to perform to cause this crash. If you can't even tell us these >>things then it calls into question your integrity. >>Jim