RE: [U2] SB Problem - Urgent

[kafsat taiyus]

Thank you Susan,   I have fixed the problem and still trying to understand what actually caused the problem.   Thank you for your help.   Regards Kafsat         -----Original Message----- From: Susan Lynch [mailto:[EMAIL PROTECTED] Sent: Monday, 3 May 2004 1:04 PM To: [EMAIL PROTECTED] Subject: Re: [U2] SB Problem - Urgent   In response to a message from: kafsat taiyus   First, the problem looks like data corruption, given the error messages shown.   Second, how to fix it:   - Make sure all the users are logged off.   - Go to the SB directory and run       guide_51 DMCONT       This will produce a guide_errors file that will show you the             errors and will allow the fixfile command to repair them:   - Run the fixfile command       fixfile -dDummyfile -f       where Dummyfile is a file name that is not used in your                     application - it will hold some output from the fixfile command     when finished.   - Run another guide_51 DMCONT, and check the guide_errors file     to be sure that there are no errors this time.   -  Repeat fixfile and guide_51 if errors occur again.  Users can get on after  you stop seeing errors in the guide_errors file.   Third, what causes data structure errors?  There are a number of possible causes, including, but not limited to, system crashes, hardware and power problems, someone using a DOS or Windows or Unix text editor to change something in a UniData file without understanding the underlying file and record structure issues, a static file hitting the 2 gig limit, a file being restored from a damaged backup medium, etc.  Given that it is DMCONT, and not likely to be maintained by your application programs, I suspect that some of the other possible causes can be ruled out, like users updating the file without proper locking, one user doing a clear-file while someone else was updating the file.     Good luck getting the system back up for your users! Hi,   No body can log in to SB+ error                                                                                   Current UniData home is /usr/ud52/.                                             Current working directory is /data1/rtime/SBPlus/SB.                            2:blk check error in U_post_read for file 'DMCONT', key 'SB.ACCOUNTS', number=33                                                                                  1:block check error in modify_record for file 'DMCONT', key 'SB.ACCOUNTS', numbe r=34816                                                                         1:block check error in U_append_strtuple for file 'DMCONT', key 'SB.ACCOUNTS', n umber=33                                                                        Fatal error: WRITE error          Any idea why this is happening and how to fix it?   Regards Kafsat This email and any attachments are confidential and intended solely for the use of the person or entity to whom they are addressed. If you are not the intended recipient, please do not disclose, store, copy or take any action in reliance on it or them. If you have received this message in error, please tell us by reply email (or telephone + 61 (0) 3 9274 9100) and delete all copies on your system. Any opinion, advice or information in this email is not necessarily that of the owners or officers of this company. Please advise us immediately if you or your employer do not consent to email for messages of this type. Retail Decisions has taken reasonable precautions to ensure that any attachment to this email has been swept for viruses. However, we cannot accept any liability for any damage sustained as a result of software viruses, and would advise that you carry out your own virus checks before opening any attachment. Please note that communications sent by or to any person through our computer system may be viewed by other Retail Decisions employees or officers strictly in accordance with law.