Archibald J. Cox

I've seen a couple of posts on some other sites that have a few things to try. Do a Google Search for "NO GO BAD DATA"

One of the solutions was related to having no space left on the HDD due to an overly large CDR file.

HCJes

You may want to try and attended backup. This will let you know if a particular file is having problems.

LD 143
ABKO

korvettekarl

LD 143 worked however I am still unable to use 43 as standard backup procedure. Do I need to swap CPUs and CMDUs and use 143 again?

korvettekarl

Tried switching to CORE 0 and envoking LD 143. Says everthing is OK and database backup complete. Still cannot use ld 43. Says NO GO BAD DATA.

HCJes

I am guessing there is no corruption issues since ABKO worked fine.

Try clearing the error flag in LD 43
Type EDD CLR
This will clear the last error flag.
See if EDD completes without errors.

Some user on Google stated that a SYS LOAD cleared the problem. I would try this if the error continues since ABKO completed OK.

You will need to contact Nortel certified vendor if the error continues.

korvettekarl

Thanks, I had considered that since it was able to do a backup in ld 143 to both sides but was a scardie cat. Just gave it a shot and it worked. I appreciate everyones help and support.

sengong

As HCJes mentioned go to Ld 43 and perform EDD CLR. Then you have to reboot your system . I am sure It will work after that.

M1tech

If this does not work, you have system corruption. You will need to get your distributor to open up a ticket with GNTS and have them dial in to remove the Corruption. I guess the only other question is if there are any SYS errors in the history or event log.