Option 61C - EDD016 NO GO. BAD DATA

[sromero]

I hope that someone may be able to guide me with a situation that I've encounter with my option 61C.

I've noticed that LD 43 on the mid night routines is not running, the routine is ending with an EDD016 No Go. Bad Data error, worse yet I can't load any maintenace loads.
When I try load 43 all I get is a dot propmt and when I try LD 135 it just sits there doing nothing.
I've INI the switch but it didn't help, i just lost the MAC's that have not been saved because I can't do a data dump.
Sorry ! I'm just babbling away... must be my frustration.

Any ideas or comments will be appreciated. Thank you

 

[tekice]

you will probally need a full reload on both cores,if u have tried a ini

good luck

 

[janchundia]

Manually enter
ld 43
edd clr
In the next day check if the backuo routine fail again


Javier

 

[johnpoole]

edd clear usually works, but it writes bad data to a disk. i would ini before i tried the edd clr command. it can cause worse problems

john poole
bellsouth business
columbia,sc

 

[Jaccodo]

Just give a ini is a workaround. Then you don't know why the bad data is there.

I would do a more detailed investication before clearing the EDD or do a ini.

This error isn't there for nothing so if I was you I would contact my vendor.

Grtz,
Jacco.

 

[johnpoole]

the error is usually there do to a bad checksum, fastest way to get one of those is a change on an acd phone. you've got files build on the p(data) side that do not have files listed in the get file field of a recent change. with pdt passwords, nortel could tell you that they found the problem and fixed it. they can also tell you that an ini would have fixed it. if that happened on my switch i would do an off hour ini and call nortel if it happens again. i do not perform a edd clr, because if i remember right, it backs up all data, checksum ignored. i've worked with people that use that command and haven't found corruption due to the clear, but had a nortel eng explain why they perfer a ini before a clr. there 1st choice is a call to their tech support, and a invoice number to cover the cost. 90 percent of what little i know about this switch i learned by makeing mistakes, so that is just my 2 cents.

john poole
bellsouth business
columbia,sc

 

[mluckie1]

Corruption. Reboot system.

 

[acewarlock]

Just remember the switch hasn't done a backup since you have been getting that error code, so depending on how many changes you have done, you could be doing those changes again if you INI or Sysload. I would do the CLR and hope for the best.

 

[RS528]

With a INI the PABX is not loading his database thats only with a sysload.
Contact your vendor. He can can make a copy of your database.rec and config.rec in the PDT before doing anything.

Ronald

 

[johnpoole]

the ini blows away any changes since the last edd, the same as your tech support is about to do, they may be a little more selective. i've seen the problem 3 or 4 times in the past 20 years and even with pdt access, i usually ini instead of cleaning up the data base, it's your call. just letting you know how i handle that problem. worse possible thing it to let it go unchecked.

john poole
bellsouth business
columbia,sc

 

[RS528]

No, the INI is not blow away any changes, because with the INI the database is not loaded from disk it's still using the database in his memory.

Ronald

 

[johnpoole]

well we have to disagree on that, i've had a tech make 100 bad changes on a new install and i ini'ed instead of correcting them,and it did blow them away. and i've done that more then once

john poole
bellsouth business
columbia,sc

 

[mluckie1]

Sometimes when you hit the INI the switch will sysload because it sees the bad data. With the EDD106 error LD 43 completes the backup but will not save the data for the TN specified.

 

[sromero]

I want to thank all of you for your help and valuable input.

Yesterday I did an INI on the switch, but the EDD016 error was still there. By the way INI did blowout my recent MAC's.

johnpoole reply caught my eye because I did have 2 acd test phones. I removed the acd phones and I was able to to do successful EDD but I still could not get to any of the maintenance loads(LD35, LD39, LD40, LD135 or LD137)

This morning I did a cold boot everything seem to come up OK, but I still can't get to any maintenance loads. Tomorrow morning I'll check the AHST and see what SYS errors are popping up.

 

[ArchTelecom]

Best thing to keep good doscumentation on all sets...in case this happens again.

If you can't get yo maint loads, check ADAN in CDR to make sure that TTY is configured for MTC & SCH. Maybe someone reconfigured it on you?

 

[acewarlock]

Quote "If you can't get yo maint loads, check ADAN in CDR to make sure that TTY is configured for MTC & SCH. Maybe someone reconfigured it on you?"

You don't need anything programmed to an ADAN to do and maint on the system, the only thing you won't get is system error message on that port but it won't stop yu from loging in and making changes. I have 2 tty ports with nothing set as user ie MTC, SCH and I can login fine and make changes.