I'm now loging all my db backup results with the -Y switch from my scheduler. I just ran it on all my databases. One is a DOCUMENT SERVER DATABASE all it has is three tables. I ran the scheduled backup procedure on it and got this result.

gbak: ERROR:invalid request BLR at offset 13
gbak: ERROR: table id 171 is not defined
gbak: ERROR:gds_$compile_request failed
gbak:Exiting before completion due to errors

I then ran a backup manually and it worked just fine no errors doing the backup. The manual backup was doing using IBConsole. The scheduled one was done using a windows service that shells out to windows to run the commands I sent earlier.

What is going on??

--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:
>
> At 10:44 AM 13/03/2009, you wrote:
> >here is another error that I get sometimes on a restore of the noon backup. Again, I have never had this problem with the backup when there is noone on the system.
> >
> >gbak: ERROR:attempt to store duplicate value (visible to active transactions) in unique index "RDB$INDEX_11"
> >gbak:Exiting before completion due to errors
>
> This during a **backup** ?? gbak -b ??? That smells like a batch script or scheduler entry that has the wrong switch. Eeeew! Check 'im!
>
> RDB$INDEX_11 is the unique index on the generator name in RDB$GENERATORS. Now, a *restore* would be pumping data into that table so it's slightly feasible that this error could occur during a *restore*...though it would suggest that someone has been meddling with that system table unless at some point a partially restored database was put into production use.
>
> gbak -b doesn't write to the database at all. However (unless flagged otherwise with the -g switch) its select * queries on all tables triggers garbage collection, which writes to disk at a much lower level than DDL and certainly doesn't create, alter or drop records in the system tables.
>
> ./heLen
>