[firebird-support] Re: gbak trigger(3) error
Thanks for your response, but this doesn't appear to be relevant as we do not know what ODS is, have never used it, and created the database brand new under Firebird 2.5. --- In firebird-support@yahoogroups.com, Norman Dunbar Norman@... wrote: On 08/08/13 19:27, jack.mason58 wrote: gbak: ERROR:table/procedure has non-SQL security class defined From http://sourceforge.net/mailarchive/forum.php?thread_name=5106F9F2.4040200%40ibphoenix.comforum_name=firebird-devel At 01:07 a.m. 29/01/2013, Dmitry Yemanov wrote: AFAIR, this is a known issue. ODS 11.2 databases cannot be restored on older FB versions because it has other conventions to name security classes (SQL$number instead of SQL$tablename, this was done to fix the old security issue with longer than 27 chars metadata names) and these new names, after being backed up successfully, are not accepted by older FB versions due to their system triggers expecting the name in the old format (SQL$tablename). I don't know about any solution other than migrating via a script. Might be helpful? Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: 27a Lidget Hill Pudsey West Yorkshire United Kingdom LS28 7LG Company Number: 05132767
[firebird-support] Re: gbak trigger(3) error
Thanks for your response. The version of gbak is 2.52 right off the Firebirdsql.com website yesterday. The database was backed up successfully using that version of gbak, but would not restore without the indicated error. gbak has another problem (will not reliably backup one of our databases) so we would use another backup agent if we could. --- In firebird-support@yahoogroups.com, Mark Rotteveel mark@... wrote: On Fri, 09 Aug 2013 07:41:27 +0100, Norman Dunbar Norman@... wrote: On 08/08/13 19:27, jack.mason58 wrote: gbak: ERROR:table/procedure has non-SQL security class defined From http://sourceforge.net/mailarchive/forum.php?thread_name=5106F9F2.4040200%40ibphoenix.comforum_name=firebird-devel At 01:07 a.m. 29/01/2013, Dmitry Yemanov wrote: AFAIR, this is a known issue. ODS 11.2 databases cannot be restored on older FB versions because it has other conventions to name security classes (SQL$number instead of SQL$tablename, this was done to fix the old security issue with longer than 27 chars metadata names) and these new names, after being backed up successfully, are not accepted by older FB versions due to their system triggers expecting the name in the old format (SQL$tablename). I don't know about any solution other than migrating via a script. Might be helpful? This might indicate that the gbak version used is from an older version of Firebird. Mark
[firebird-support] Re: gbak trigger(3) error
Thanks for your response. We are not downgrading a database; quite the opposite. Interbase 6.0 is about 10 years old and since we upgraded our server from Windows 7 to Linux Mint, we wanted to upgrade our database server to one currently supported, and since the Interbase format is supported by Firebird --- In firebird-support@yahoogroups.com, Norman Dunbar Norman@... wrote: It seems as if you are attempting to downgrade a database - at least, that's what my Google-fu turns up - but I don't have a very high Google-fu rating! ;-) There's a tracker on this very matter at http://tracker.firebirdsql.org/browse/CORE-2949. Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: 27a Lidget Hill Pudsey West Yorkshire United Kingdom LS28 7LG Company Number: 05132767
Re: [firebird-support] Re: gbak trigger(3) error
... and since the Interbase format is supported by Firebird I think I have an idea on why you have problems. From where and when is the information that Interbase format is supported by Firebird?
[firebird-support] Re: gbak trigger(3) error
Firebird was developed to be a better Interbase and has improved on Interbase over the years. We have applications that run identically and equally well whether connected to an Interbase server or a Firebird server. In none of the cases is it Firebird to Firebird. It is gbak that has the problems, not Firebird. --- In firebird-support@yahoogroups.com, André Knappstein Knappstein@... wrote: ... and since the Interbase format is supported by Firebird I think I have an idea on why you have problems. From where and when is the information that Interbase format is supported by Firebird?
Re: [firebird-support] Re: gbak trigger(3) error
On Fri, 09 Aug 2013 15:10:31 -, jack.mason58 jack.maso...@yahoo.com wrote: Where do I find fbstat? It is not included in the 2.5.2 download I pulled yesterday from firebirdsql.com. It is not in the bin directory nor the top directory. 03/19/2013 11:23 AM 241,664 gstat.exe ODS is On Disc Structure. If you run a gstat -h database_name (or fbstat -h database on Linux Mint!) then it will display something like the following: You need gstat, it is just called fbstat on Linux Mint. Mark
Re: [firebird-support] Re: gbak trigger(3) error
Hi ! Em 9/8/2013 12:10, jack.mason58 escreveu: Where do I find fbstat? It is not included in the 2.5.2 download I pulled yesterday from firebirdsql.com. It is not in the bin directory nor the top directory. It's GSTAT It's a long long time that I used Interbase... But I think you should use gbak from Interbase to produce the back-up and restore it using gbak from firebird. I don't know if the back-up produced by IB 6 gbak will be compatible with FB 2.5 gbak. when I migrate from IB 6 it was to FB 0.9... If FB 2.5 gbak could not understand IB 6 gbak back-up, you could try a two step migration IB 6 - FB 1 - FB 2.5 or a 3 step migration IB 6 - FB 1 - FB 1.5 - FB 2.5 As far as I know gbak will be retro compatible, but IB 6 is very old version, don't know how long the retro compatibility is preserved. Another option is to extract SQL Metadata using IB isql (-X option), then create a new FB 2.5 database, run the generated script, and pump the data from the IB server to FB server. see you !
