You should check the elements called =16402/22665, =16402/22666 and =16402/22667 as from your jpeg images. DB number 18 (16402-8192-8192=18)
Could they be SPEC selectors elements?
In the past I had problem with SELE elements with no members.
Try to delete them. (quick report filter: MCOUNT EQ 0)
Project GBU
Database DESEMFPVP/PVP Filename /%GBU000%/gbu4001_0001
DB number 4001
Extract number 1
DB type DESI
DB size 17589 Pages
(36.022 Million bytes)
Maximum size 2000 Million Pages
DB is 0.0009% full
Page size 2048 bytes
Last Session Number: 960
Last Session Date: 11:36 5 May 2011
Last Session User: umodibbo
Last Session Description: Default session comment
Options requested STATISTICS OFF
CHECK CLAIM LIST
FULL CHECK
They are not virus my friend!
It normally happens when you modify piping specs.
You move SPCOs from one place to another or you delete/remove them.
How is life in Lagos?
I have been there a couple of weeks around ten years ago. Good memories....
First Aveva trainer to go to Nigeria!!!!
[QUOTE=corrado;50931]You should check the elements called =16402/22665, =16402/22666 and =16402/22667 as from your jpeg images. DB number 18 (16402-8192-8192=18)
Could they be SPEC selectors elements?
In the past I had problem with SELE elements with no members.
Try to delete them. (quick report filter: MCOUNT EQ 0)
Corrado,
thanks it works fine with deletion of =16402/22665, =16402/22666. they are selectors with null setting and spec. they must be virus or what can I call them?
[QUOTE=corrado;50934]They are not virus my friend!
It normally happens when you modify piping specs.
You move SPCOs from one place to another or you delete/remove them.
How is life in Lagos?
I have been there a couple of weeks around ten years ago. Good memories....
First Aveva trainer to go to Nigeria!!!!
That is great! I might have met you if you were at NETCO, though I was not pert of that class.
Corrado, thank you for your input and insight. I guess those were the maximum runtimes we had in design module on the only PDMS project we had if my memory serves right. You have also marked this on another thread as a possible reason to give stackoverflow error.
Soon, we will be having a new project on v12 (yet to start). Personally, I do not have any Cats & Specs experience. Will it be wise then to make this part an action item that Cats & Spec guy will have to perform at the end of any spec update (as good practice kind of stuff)?
[QUOTE=Shrivallabha;51021]Corrado, thank you for your input and insight. I guess those were the maximum runtimes we had in design module on the only PDMS project we had if my memory serves right. You have also marked this on another thread as a possible reason to give stackoverflow error.
Soon, we will be having a new project on v12 (yet to start). Personally, I do not have any Cats & Specs experience. Will it be wise then to make this part an action item that Cats & Spec guy will have to perform at the end of any spec update (as good practice kind of stuff)?
This is the first time I am experiencing this particular run time error, I do not thing it happens on every spec update.
