Re[2]: Delete Procedure

Wed, 02 May 2001 11:43:55 -0700

     To all who offered food for thought, my sincere thanks (Bob Edis, 
     Mark, Terrence Burk, Charlie Maloney).  It will be a trial and error 
     to fix this problem.  To re-create the situation in my test 
     environment is very difficult and attempts have been made with no 
     reoccurrence of the partial updating problem.  I shall ponder each of 
     your ideas and try various approaches if the problem happens again. So 
     far, the rarity of the problem allows me the liberty to not be too 
     excited about a solution.

     For those of you who wondered about my environment, it is HP-UX 
     B.11.00 A, Oracle Release 8.0.6.2.0, PowerHouse 8.13.D3.

Regards, Gerry

______________________________ Reply Separator _________________________________
Subject: RE: Delete Procedure  
Author:  "Fry  Mark" <Mark.Fry@COGNOS.com> at RDM-PO1
Date:    05/02/2001 5:23 AM

Hmmm, something else is going on here, I'd guess.  Just a hunch, do you have 
a hard-coded UPDATE procedure?  If so, what does it look like? (ie does it 
contain code that says something like...
FOR TIME_ATTEND
BEGIN
  PUT NOTDELETED TIME_ATTEND
  PUT TIME_ATTEND_2
  PUT TIME_ATTEND_2IN
  PUT TIME_ATTEND_IN
;  PUT TIME_ATTEND
END

Mark Fry
Cognos Limited
email: Mark.Fry@Cognos.com

Cognos Limited
Registered in England, number 1635598.  Registered office:  Westerly Point, 
Market Street, Bracknell, Berkshire, RG12 1QB

This e-mail may contain confidential information and is confidential to the 
user of the e-mail address to which it is addressed.  No-one else may copy 
or forward all or any of this e-mail in any form.  If you receive this 
e-mail in error please destroy this message and notify the sender by return 
e-mail."     

-----Original Message-----
From: GGrimm@pcc-structurals.com [mailto:GGrimm@pcc-structurals.com] 
Sent: 01 May 2001 00:40
To: powerh-l@lists.swau.edu
Subject: Delete Procedure 

     On some situation (yet to be ascertained), a partial update occurs 
     about 5% of the time when updating cached records if record(s), have 
     been deleted with a range of numbers, for example: D-9/10.

     Has anyone an idea what could cause this from the below snippet 
     without having to see the entire code?  The data base is Oracle 8.06. 
     Could changing a field in a deleted record after the delete cause a 
     problem?

     Following is a snippet of the code, primary and three secondary files, 
     no DELETE files, secondary retrieval done in FIND procedure with no 
     records is possible on any of the three secondaries.  The absence of 
     secondary(s) is not the cause of the partial Update that happens.  

     ---------
     FILE TIME_ATTEND  PRIMARY       OCCURS 13       NOITEMS CACHE 255
        ACCESS VIA EMPLOYEENO, SHIFT_DATE, SHIFT_NO, ENTITY_CODE & 
        USING EMPLOYEENO OF EMPLOYEES, T_SHIFT_DATE,             &
              T_SHIFT, TIME_ATTEND_ENTITY                        &
                    ORDERBY EMPLOYEENO, SHIFT_DATE, SEQ_NUM
        ACCESS VIA SHIFT_DATE, DEPT_CODE, SHIFT_NO, ENTITY_CODE     & 
        USING T_SHIFT_DATE, T_REQ_DEPT, T_SHIFT, TIME_ATTEND_ENTITY &
                    ORDERBY EMPLOYEENO, SHIFT_DATE, SEQ_NUM
     FILE TIME_ATTEND_2  SECONDARY  OCCURS WITH TIME_ATTEND  NOITEMS 
     FILE TIME_ATTEND_2  SECONDARY  OCCURS WITH TIME_ATTEND  NOITEMS &
                                          ALIAS TIME_ATTEND_2IN 
     FILE TIME_ATTEND    SECONDARY  OCCURS WITH TIME_ATTEND  NOITEMS &
                                          ALIAS TIME_ATTEND_IN 
     . . . . .
     PROCEDURE DELETE
     BEGIN
          DELETE TIME_ATTEND_2IN
          DELETE TIME_ATTEND_IN
          DELETE TIME_ATTEND_2
          DELETE TIME_ATTEND
     END

= = = = = = = = = = = = = = = = = = = = = = = = = = = = 
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu 
Unsubscribe: "unsubscribe" in message body to 
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.