Hi Mike, The minor surge occurred at the office Friday morning. The database operations continued unabated with no errors for a couple of hours. Then the Access Violation errors started and no work could be performed.
I tested the database through my terminal services connection and it took several minutes before I also received the Access Violation errors which locked up my server. I then retrieved the backup and ran the file on my local (at home) workstation. I have experienced the same problem here since then... Claudine > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of MikeB > Sent: Saturday, March 19, 2005 2:27 PM > To: RBG7-L Mailing List > Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3 table > corruption > > Is the access violation from more than one computer?... If you had an > outage / > electrical event, there is the possibility that it is an RBase Program > file > corrupted and not the DB. > > If this is so, then continued work on the DB from a "BAD" condition won't > necessarily yield a good result. > > I cannot imagine a condition in which you can break the DB into is least > significant parts (Unload Data / Structure Separately [Bernie]) then > reassemble > it and find corruption of the DB. > > > ----- Original Message ----- > From: "Claudine Robbins" <[EMAIL PROTECTED]> > To: "RBG7-L Mailing List" <[email protected]> > Sent: Saturday, March 19, 2005 3:09 PM > Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3 table > corruption > > > > Sami, Javier, Bernie, > > > > The very first backup I did on January 12 doesn't have a corrupted > > sys_layouts3 table. I unloaded that data and reloaded it into my > current > > database. Although RScope now reports no errors, I still have the > Access > > Violation problem. > > > > Interestingly, Sami, I had already found this routine you posted some > time > > back and had copied it to a notepad file. Unfortunately, I have made > many > > changes to the structure since that January 12 backup... But maybe, I > might > > find a more recent backup that would work. It'll take time since I do > that > > backup every day, sometimes several times a day. > > > > I have to run a couple of errands right now but I'm getting back to it > later > > until I find the answer, by gosh by golly... Luckily, it happened on a > > weekend... > > > > Thanks for all your help. > > > > > -----Original Message----- > > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Sami > Aaron > > > Sent: Saturday, March 19, 2005 1:43 PM > > > To: RBG7-L Mailing List > > > Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3 > table > > > corruption > > > > > > Claudine - > > > > > > There are a couple more options: > > > > > > 1. Find a backup copy of the rb1 file from before the corruption > > > occurred. > > > (NOTE: this will not work if you have made any structural changes to > the > > > database since the date/time on the rb1 file.) Copy the rb1 file into > > > your > > > working folder, replacing the existing rb1 file. Now, do a reload on > the > > > database and see if that helps. > > > > > > 2. Unload all for each of your database tables separately like: > > > SET NULL -0- > > > OUTPUT IHopeThisWorks.str > > > UNLOAD str > > > OUTPUT SCREEN > > > OUTPUT IHopeThisWorks.dta > > > UNLOAD DATA > > > OUTPUT SCREEN > > > > > > Then, RBEDIT IHopeThisWorks.str and search for "CREATE VIEW". > > > Split this file into two files - everything ABOVE the first CREATE > VIEW > > > statement into IHopeThisWorks1.str, and everything from the first > CREATE > > > VIEW to the end of the file as IHopeThisWorks2.str. > > > > > > Then, RBEDIT IHopeThisWorks.dta and search for SYS_Layouts and delete > the > > > whole LOAD section for that table. > > > > > > Then, get rid of the original database or rename it to something else. > > > > > > SET MESS ON > > > SET ERROR MESS ON > > > TRACE IHopeThisWorks1.str > > > --If no errors then > > > RUN IHopeThisWorks.dta > > > --If no errors then > > > TRACE IHopeThisWorks2.str > > > > > > If that still doesn't work, then I still have one more way up my > sleeve so > > > post another question here.... > > > > > > > > > Good luck! > > > Sami > > > > > > > > > > > > -----Original Message----- > > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Claudine > > > Robbins > > > Sent: Saturday, March 19, 2005 1:15 PM > > > To: RBG7-L Mailing List > > > Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3 > table > > > corruption > > > > > > Javier and Bernie, > > > > > > I have now reloaded the last 4 complete backup files created with > unload > > > all > > > and every single one reports the 'data' error in RScope for the > > > sys_layouts3 > > > table. > > > > > > I also tried deleting both records in sys_layouts3 and RScope reports > no > > > corruption. However, Access Violation messages continue and db is > > > unusable. > > > > > > (how do you spell seperately?) separately. And that's a good idea. > I'm > > > going to do that now... > > > > > > Claudine > > > > > > > > > > > > > -----Original Message----- > > > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Javier > > > > Valencia > > > > Sent: Saturday, March 19, 2005 1:03 PM > > > > To: RBG7-L Mailing List > > > > Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3 > table > > > > corruption > > > > > > > > You could try doing a RELOAD or an UNLOAD of the structure and data > and > > > > then > > > > reconstructing the database. TTBOMK the SYS_LAYOUTS3 table stores > only > > > the > > > > layouts of tables of views and it is not critical, if the data is > > > deleted > > > > it > > > > should just display the tables/views in the default format. > > > > Javier, > > > > > > > > Javier Valencia, PE > > > > President > > > > Valencia Technology Group, L.L.C. > > > > 14315 S. Twilight Ln, Suite #14 > > > > Olathe, Kansas 66062-4578 > > > > Office (913)829-0888 > > > > Fax (913)649-2904 > > > > Cell (913)915-3137 > > > > ================================================ > > > > Attention: > > > > The information contained in this message and or attachments is > intended > > > > only for the person or entity to which it is addressed and may > contain > > > > confidential and/or privileged material. Any review, > retransmission, > > > > dissemination or other use of, or taking of any action in reliance > upon, > > > > this information by persons or entities other than the intended > > > recipient > > > > is prohibited. If you received this in error, please contact the > sender > > > > and > > > > delete the material from all system and destroy all copies. > > > > ====================================================== > > > > > > > > -----Original Message----- > > > > From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of > Claudine > > > > Robbins > > > > Sent: Saturday, March 19, 2005 12:36 PM > > > > To: RBG7-L Mailing List > > > > Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3 > table > > > > corruption > > > > > > > > Hi Javier, > > > > > > > > I'm working with a copy. I've tried deleting both rows and even > though > > > > RScope no longer reports the problem, the Access Violation Messages > > > > continue... > > > > > > > > Claudine > > > > > > > > > -----Original Message----- > > > > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of > Javier > > > > > Valencia > > > > > Sent: Saturday, March 19, 2005 12:33 PM > > > > > To: RBG7-L Mailing List > > > > > Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3 > > > table > > > > > corruption > > > > > > > > > > Hi Claudine: > > > > > Whatever you do...backup first!!! > > > > > Then you can try deleting the offending items and see if that > fixes > > > the > > > > > problem; if it does not, you still have the original... > > > > > Javier, > > > > > > > > > > Javier Valencia, PE > > > > > President > > > > > Valencia Technology Group, L.L.C. > > > > > 14315 S. Twilight Ln, Suite #14 > > > > > Olathe, Kansas 66062-4578 > > > > > Office (913)829-0888 > > > > > Fax (913)649-2904 > > > > > Cell (913)915-3137 > > > > > ================================================ > > > > > Attention: > > > > > The information contained in this message and or attachments is > > > intended > > > > > only for the person or entity to which it is addressed and may > contain > > > > > confidential and/or privileged material. Any review, > retransmission, > > > > > dissemination or other use of, or taking of any action in reliance > > > upon, > > > > > this information by persons or entities other than the intended > > > > recipient > > > > > is prohibited. If you received this in error, please contact the > > > sender > > > > > and > > > > > delete the material from all system and destroy all copies. > > > > > ====================================================== > > > > > > > > > > -----Original Message----- > > > > > From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of > Claudine > > > > > Robbins > > > > > Sent: Saturday, March 19, 2005 12:24 PM > > > > > To: RBG7-L Mailing List > > > > > Subject: [RBG7-L] - Access Violation Messages and Sys_Layouts3 > table > > > > > corruption > > > > > > > > > > Hi all, > > > > > > > > > > We had a small surge at the office yesterday and one of my db's is > now > > > > > constantly giving off access violation messages which cannot be > > > > resolved. > > > > > > > > > > Upon running RScope 7.5, I find that there is an error in my > > > > sys_layouts3 > > > > > table which cannot automatically be fixed because it contains a > note > > > > > field. > > > > > This table has two rows, one for an existing 'important' table, > the > > > > other > > > > > for a view which I can easily delete and recreate. > > > > > > > > > > What should I do? > > > > > > > > > > Claudine > >
