...
At 11:32 AM 3/21/2005, you wrote:
I had a similar problem at one client's and now begin all RESTORE programs with sirens, noises and TWO dialogs to confirm that they REALLY want to do this - EMERGENCY restore only!!!
David Blocker
[EMAIL PROTECTED]
781-784-1919
Fax: 781-784-1860
Cell: 339-206-0261
----- Original Message -----
From: Dennis Fleming
To: RBG7-L Mailing List
Sent: Monday, March 21, 2005 10:00 AM
Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3table corruption
Good thread on backup, copy, xcopy, save, restore, reload, pack indexes, transaction logging, etc.
But, I didn't realize how confusing this is for my customers until last week when one of them used our Restore routine (Input BKP and LOB files) instead of the Reload routine. They were using last week's data for two days before they realized it was last week's data. I think I'll go back to calling our Reload utility to what it was years ago- "Compress your files".
...
At 07:00 AM 3/21/2005, you wrote:
Claudine
I do a complete back up everynight except Sat and Sun. I also do a
backup of all database every 4 hours even on the weekends just in case.
I'm using Backup Exec 9.x on Netware.
Buddy
-----Original Message-----
From: [email protected] [ mailto:[email protected]] On Behalf Of Claudine
Robbins
Sent: Sunday, March 20, 2005 4:18 PM
To: RBG7-L Mailing List
Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3 table
corruption
Bernie,
In my transportation database, I write/append to an audit file each time
a record is added or edited, but I'm only dealing with one table. I
also have an incremental backup several times during the day from which
I can easily restore. In my invoices database, there are 9 related
tables. Writing the data is simple enough, restoring it might be
complex.
I think I need to take a Backup 101 course. Backup and documentation
always seem last on the to-do list... With the Oracle database -- now
successfully replaced with RBase :) -- we had a sophisticated daily
backup to tape in place along the son/father/grandfather model. Not one
single Oracle dba was ever willing to assure me that any of it could
successfully be restored...
And to my knowledge, it was never even tested!!!
Let's hear it from the list... What's everybody doing for backups?
Claudine
> -----Original Message-----
> From: [email protected] [ mailto:[email protected]] On Behalf Of Bernard
> Lis
> Sent: Sunday, March 20, 2005 2:03 PM
> To: RBG7-L Mailing List
> Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3
> table corruption
>
> Hi Claudine,
> For one of my customers, I have a tracking table.
> Any time an item is added to the item table, or a sale is made, or
> inventory is replenished, a row is added to the tracking table which
> indicates any of the above actions and the date and time it ocurred,
> and WhoDidIt.
> Though we haven't needed to use it for rebuilding purposes, the store
> manager uses it to determine why inventory is not what it is supposed
> to be and if any midnight requisitioning is happening.
>
> Bernie Lis
>
> ----- Original Message -----
> From: "Claudine Robbins" <[EMAIL PROTECTED]>
> To: "RBG7-L Mailing List" <[email protected]>
> Sent: Sunday, March 20, 2005 1:24 PM
> Subject: [RBG7-L] - RE: Access Violation Messages and Sys_Layouts3
> table corruption
>
>
> > Ok gang, here is what I did to mitigate my problem. It's not a
> > complete solution but I believe the surgery was the least invasive
> > for the
> patient.
> >
> > My backup from Thursday night when restored, didn't cause any access
> > violations :). However, it did trip RScope with that minor
> > sys_layouts3 problem which I fixed simply by deleting the two rows
> > causing the
> problem
> > and reloading the only row unloaded from the oldest backup which
> > didn't have that problem. As Ross Perot used to say: "Are you with
> > me?"
> >
> > That left me with having to restore data entered on Friday which I
> > unloaded from the damaged db and reloaded into the corrected db.
> > The only thing
> I
> > don't know how to do is to restore changes made on Friday to
> > existing
> data
> > which I guess will simply have to be re-entered. All in all, it
> > should work.
> >
> > Thank goodness for daily backups. But a question begs, how would
> > you backup/restore changes made to existing data? Some kind of a
trigger?
> I
> > need an education on this subject now that I've had the hard
lesson...
> >
> > Claudine
> >
> >> -----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
> >
> >
--- RBG7-L
=======================3D====================== D=
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]
(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
=======================3D====================== D=
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
=======================3D====================== D=
TO UNSUBSCRIBE:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
=======================3D====================== D=
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body,
place any
text to search for.
=======================3D====================== D=
Dennis Fleming
IISCO
http://www.TheBestCMMS.com
Phone: 570 775-7593
Mobile: 570 351-5290
Dennis Fleming
IISCO
Phone: 570 775-7593
Mobile: 570 351-5290
