BUG098 errors

[derbydave]

Hi.

Can anyone give me any details about this error message?
Is it something we should be concerned about?
They used to crop up only occasionally, but we have had 84 in the last 24 hours!!

We have an Opt.11 rel. 25.4B.
Valid routes are 100,110,120.
Obviously from the error description its trying to pass route 1022 which is of course invalid.

Details posted below, for information.

Many thanks

Dave.



BUG0098 C R
"The route number (RNO) passed into Procedure $SET_ROUTE_PTRS is out of
range.

C = Customer Number
R = Route Number"
Action: Investigate possible data corruption.
Severity: Minor
% BUG098
% BUG098 : 0 1022
% BUG098 + 1067E808 107548C8 10522166 10521650 1051ED44
% BUG98 + 1051E5C0 1051DA82 10516E18 10510EC4 1050F5E8
% BUG098 + 1050F12C 1050E1CE 1050DFCC 108C6076 108C5D32
% BUG98 + 108C565E 108C4FB2 108C3FEA 1051773A 1051755E
% BUG098 + 10510ED8 1050F5E8 1050F12C 1050E1CE 1050DFCC
% BUG98 + 108223EA 10DC37C6 10DC1DF0 10DC1AF4 10E6D46C
% BUG098 + 10E6D32E 10E67CCE 10E63062
%
% BUG098
% BUG098 : 0 1022
% BUG098 + 1067E808 107548C8 105220EC 1052163E 1051ED44
% BUG98 + 1051E5C0 1051DA82 10516E18 10510EC4 1050F5E8
% BUG098 + 1050F12C 1050E1CE 1050DFCC 107D848C 107D78C8
% BUG98 + 10647C62 10644D66 10D09B02 107C3E66 20E3D9C6
% BUG098 + 107C2282 10E6D3F2 10E6D32E 10E6CC76 10E67DC8
% BUG98 + 10E63062

 

[chaosnla]

bug codes are generally selfcorrecting but they do deliver good info. if your bug codes are intermit, its ok,
if bug codes are blasting your termial making it hard to login or whatnot, you'll need to do something about them.
hope this helps

 

[chaosnla]

if you have corruption like the msg kinda indicates,since you dont have that rt. you may want to back that system up and them reloadit. . whata you think.

 

[derbydave]

Its worth a try, backup + reload.
I'll look into it.
Thanks.

 

[NTOldTimer]

Print all of the RLB info. LD 86
REQ PRT
CUST 0
TYPE RLB
RLI (Carrage Return with no answer)
The whole Route List Block will print.

Go through it all carefully and see if one of the entries has your invalid Route 1022 entered by mistake.

If you don't find it there then I'd open a ticket with your vendor and have them check for any possible patches that may be needed.

 

[NTOldTimer]

I scanned this message too quickly. Open mouth insert...

Although a quick look at the RLB wouldn't hurt anything. If you save it to file or you are using ProComm and your scroll back history is big enough then you can search for the 1022 route and make a quick determination.

The reference to corruption is most likely not wrong. Pay close attention and save to text file any messages during the data dump and your sysload. Chaosnla has posted the best course of action.

 

[derbydave]

Checked LD86 - no invalid route 1022 in there by mistake.
Is the data dump part of the midnight routines?

Dave.

 

[NTOldTimer]

Is a data dump part of the midnight routines?

If 43 is in the configuration DROL (print OVLY in LD 22)
then a data dump will be run every day during the midnight routines. If 43 is not in the DROL then a data dump will be performed during the midnight routines if you do any software changes.

We always involk a data dump (LD 43 EDD) before performing a sysload.

At this point it seems that a sysload might help your COW (Option 11s are sometimes referred to COWSs Corruption On the Wall because of their tendancy towards data corruption.)

 

[derbydave]

Yes.
DROL=30,38,43,44,135
so will check log tomorrow morning for any errors.

 

[derbydave]

NtOldTimer, yes there is an error in LD43 of the mids.

EDD016 NO GO. BAD DATA

Things do seem to be pointing to corruption.
How do I do a sysload - is it just a case of hitting the reset button on the card in the main cab?

Dave.

 

[chaosnla]

gonna need to "EDD CLR" then what ever is corrupt will get kicked out.

 

[chaosnla]

oops din't finish edd clr before the sysload

 

[derbydave]

Cheers guys.
Will give it a try.

 

[derbydave]

Hi all.

Problem now fixed, but we had to get British Telecom in to do it.
It took them nearly 3 hours!!!

Basically, "EDD CLR" didn't work - gave a load more error messages, they tried to apply a couple of patches but couldn't get them to go onto the system.

From what they said, it turns out there was an 8MB file filling up the flash memory card that shouldn't have been there, they reckon created in error every night, increasing in size. This was causing the datadump errors + stopping any patches being applied as there was no room left.

They deleted it, applied the patches, the BUG098's have stopped + datadump worked OK last night.

Thanks all for your comments + suggestions.

Dave.