Re: 5.02 Bug?

In article ocg@emory.mathcs.emory.edu, kmart!jregep@uunet.uu.net () writes: > Debbie Shelton writes: > > > We currently have a problem with our stored procedures. We are running 5.02 > >OnLine > >and have been told that we have to upgrade to 6.0 for the bug fix. Moving from > >5.02 to 6.0 is a VERY BIG step for the DBA.Therefore saying you have to move to > >6.0 when the company isn't prepared to make that big change, in my mind, isn't > What kind of bug? I am VERY interested. > There is a 5.03 out, it this an option? > > || ======= **** **T* ======= ||John Regep > || **** **** ||Store Systems Developement > || **** *R** ||Kmart Corporation > || =========== ********* =========== ||3100 West Big Beaver > || ***A* **** ||Troy, MI 48084 > || **** **** ||(810) 643-5078 > ||=============== *M** **** ===============||uunet!kmart!jregep > We are encountering corruption in our stored procedures. 5.03 is out, but the bug isn't fixed in 5.03. One person suggested that we create a dumb stored procedure that did nothing. We did this and then called it right before we called the stored procedure that was having the problems, but didn't see the problem of the corruption go away. This is a weird situation because we don't always get the messages of corruption in the stored procedures. We get the corruption messages with only one stored procedure, but not every time we run the particular stored procedure. We have MANY stored procedures. It's a weird situation that I can't explain. -debbie shelton dba mccaw cellular communication debbie.shelton@mccaw.com