Message: EDD016 NO GO. BAD DATA ??? 2

[gonzo99]

when trying to backup, I get the following message:
EDD000
.edd

EDD016 NO GO. BAD DATA

tried a EDD CLR:

ESN 00
CHECKING
EDD005 ***** INCOMPLETE DATA STRUCTURE *****

EDD005 ***** ESN DATA *****
TEMU048 Database disk volume is full

EDD005 ***** DO NOT REDUMP *****
EDD005 ***** REFER TO NTP *****

The NTP says: call Nortel ;-(

I use DSC's for networking (currently 4000 DSC administered).

ESN Setting:
ld 86

MEM AVAIL: (U/P): 1022759 USED U P: 219484 134012 TOT: 1376255
DISK RECS AVAIL: 394
REQ prt
CUST 0
FEAT esn

MXLC 100
MXSD 5
MXIX 5
MXDM 100
MXRL 100
MXFC 5
MXFS 10
MXSC 5000
NCDP 4
AC1 9
AC2 0
DLTN NO
ERWT YES



directory listing in PDT:
pdt>
ll

Directory of 'c:/u/db':

SIZE DATE TIME NAME
---------- ----------- -------- ------------
1024 Feb-04-1996 11:37:26 . <DIR>
1024 Feb-04-1996 11:37:26 .. <DIR>
1024 Feb-04-1996 11:37:26 INV <DIR>
396 Jan-09-2004 15:06:06 IPREM.DB
126976 Mar-17-2004 14:57:00 DATABASE.BAK
178176 Feb-12-2004 01:02:06 DATABASE.REC
396 Dec-09-2002 17:51:16 IPREM.BAK
48 Oct-21-2003 13:03:04 SURV.BAK
333008 Mar-17-2004 14:58:40 AAL.DAT
698 Feb-12-2004 07:22:02 VIEWCFG.TMP
1024 Feb-04-1996 11:55:12 ITG_DNLD <DIR>
32 Jan-15-2004 09:37:22 PASSWD.REC
238 Jan-09-2004 15:06:02 INET.DB
1024 Mar-17-2004 14:57:00 CONFIG.BAK
1024 Feb-12-2004 01:02:06 CONFIG.REC
3013 Feb-04-2004 12:03:16 CPDIR0.CSV
55 Feb-12-2004 01:02:02 EPTFLAG.DB
0 Feb-12-2004 01:02:02 EPTDELTA.DB
25 Jan-09-2004 15:06:04 ESET1.DB
25 Jan-09-2004 15:06:06 ESET2.DB
0 Feb-11-2004 01:01:46 SMPSERV.BAK
45 Feb-12-2004 01:02:00 SMPCONF.DB
85 Feb-12-2004 01:02:04 ZONE.DB
7107 Aug-26-2003 09:17:34 QOSLOG.BK
4546 Feb-19-2004 17:42:24 QOSLOG.TXT
238 Nov-13-2003 13:07:00 INET.BAK
85 Feb-11-2004 01:01:48 ZONE.BAK
48 Jan-09-2004 15:06:06 SURV.DB
45 Feb-11-2004 01:01:44 SMPCONF.BAK
0 Feb-12-2004 01:02:02 SMPSERV.DB

pdt>

No additional DSC's where administered since the last succesful backup.

Any suggestions?

 

[unkalary]

Ya call NORTEL

 

[one234]

Hi,

Go in to PDT and type chkdsk this will show you the free diskspace.

I do not know which release 11C you have, but you should at least have 1.5 Mb free...

If you do, do a EDD CLR and see if that works




Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...

 

[JJhere]

You have corrupt data, do not do EDD CLR. You need to have vendor or ETAS at nortel fix the problem.

 

[geirendre]

If you just added some new equipment to your
switch, like a MIRAN-card, then it's normal
to get a NO GO BAD DATA.
If that's the case,then it's safe to do a
EDD CLR.
But if you didn't, then I suggest you contact
Nortel..

 

[one234]

@Geirendre

If it's normal for you the get a NO GO DAD DATA when you install a MIRAN, you really must have a look at your install procedure.

It's absolutely NOT normal to get a NO GO BAD DATA when you install a card (Doesn't what card)

The only time I get a NO GO BACK DATA is when I'm playing around with the database in PDT




Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...

 

[wolfi24]

Yes , I agree with one234

Wolfi

 

[NTOldTimer]

Before I went to Nortel I would sysload and check out anything that prints a TN or DN or anything unusual during the reload. If a TN shows up then delete it, data dump EDD CLR if you have to, and sysload again.

 

[gonzo99]

to NTOldTimer:

should I press down the INI-Button or power down the whole cabinet 0 ?

 

[geirendre]

I agree with you 0ne234,
it's NOT normal to get a NO GO BAD DATA.
But twise I have comed across an Opt11 with this
problem, and in both cases we were able to trace
the problem back to a MIRAN-card that someone had
installed a few weeks earlyer.
A call to Nortel verified that it could
happend, and that it was safe to do a EDD CLR.
Both switches are working fine today,
more than a year later...

Another reminder to us all of how important
an up to date BACKUP is !!!

 

[gonzo99]

I've checked the Disk space:

pdt>
chkdsk
Volume in drive 'c:' has no label
0 bytes free on 'c:'
pdt>


I assume, the Disk space is left because of the CDR Data.
SAM Win is'nt able to retrieve the CDR Data through FTP.
Where can I delete the CDR-Data in PDT?

 

[gonzo99]

OK, got it!

pdt> ll

Directory of 'c:/u/smp_db':

SIZE DATE TIME NAME
---------- ----------- -------- ------------
1024 Feb-04-1996 11:37:26 . <DIR>
1024 Feb-04-1996 11:37:26 .. <DIR>
3 Feb-12-2004 07:22:26 DBA.INI
23842 Nov-17-2003 00:00:36 11171352.CDR
8218906 Feb-13-2004 08:22:44 02171259.CDR

!!!

did a "del 02171259.CDR"
(at current time, the CDR Data are not important!)

followed by a EDD CLR in LD 43

after that, a "normal" EDD works.

Now I have to determine, why "SAM Win" was'nt able to retrieve the CDR-Data.

Thank for your help!

 

[NTOldTimer]

Great thread Gonzo!