Database Conversion Error after update 11.7.1 to SP3

Report SqlBase bugs and possible workarounds.
mschoelzel
Germany
Posts: 164
Joined: 06 Jun 2017, 13:12
Location: Bad Oeynhausen, Germany

Database Conversion Error after update 11.7.1 to SP3

Post by mschoelzel » 06 Nov 2014, 08:51

I have installed Service Pack 3 for SQLBase 11.7 64Bit, which I got from the Gupta website, over an existing installation with SP1. After this i tried to connect with SQLTalk 64Bit to an existing database, which I'd created under SP1, 64Bit. I get the following error:

00452 Cannot convert this database - Database has been shutdown

At the SQLBase console I see this messages:

3> 3/1: Database File Name HAMM74
3> 3/2: Conversion of DB to Current Version Failed - Error: 354
3> 3/3: Object specified in DROP VIEW is not a view
3> 3/4: Converted to Error: 452
3> 3/5: Cannot convert this database - Database has been shut down
3> err=452 epo=0 rbf=0

Something there is wrong. :(

Matthias

Mike Vandine

Re: Database Conversion Error after update 11.7.1 to SP3

Post by Mike Vandine » 07 Nov 2014, 08:01

Hi Matthias,

This is a known issue. There were some inconsistencies with how views were being stored on the database and one of the internal fixes we made with 11.7 SP3 was to correct this with an automatic conversion if someone just moved the .dbs file. An unload/load works fine.

We had a report of this problem from one customer immediately after we had done the SP3 release and fixed this. The cause of the error was a public synonym that had been created by the customer on a system table. We didn't think that others would have done this, so didn't do a full replacement of the SP.

I have an EMP for the 32-bit version but need to get the 64-bit version downloaded as well and included.

Please contact me at mike.vandine@guptatechnologies.com and I will arrange to get this to you. A couple of workarounds if appropriate:

1. Do an unload of the database on the SP1 version and a load on the SP3 version. That will work (plus has other advantages as well, i.e. a 'clean' database).
2. If you *really* need these synonyms, drop them on the old database, move the .dbs file, then add them back on the SP3 version. If you don't really need them, just drop them from the old database and move the .dbs file.

The Drops:

drop public synonym SYSCOLAUTH;
drop public synonym SYSCOLUMNS;
drop public synonym SYSCOMMANDS;
drop public synonym SYSFKCONSTRAINTS;
drop public synonym SYSINDEXES;
drop public synonym SYSKEYS;
drop public synonym SYSPKCONSTRAINTS;
drop public synonym SYSSYNONYMS;
drop public synonym SYSTABAUTH;
drop public synonym SYSTABCONSTRAINTS;
drop public synonym SYSTABLES;
drop public synonym SYSUSERAUTH;
drop public synonym SYSVIEWS;

The creates:

CREATE PUBLIC SYNONYM SYSCOLAUTH FOR SYSADM.SYSCOLAUTH;
CREATE PUBLIC SYNONYM SYSCOLUMNS FOR SYSADM.SYSCOLUMNS;
CREATE PUBLIC SYNONYM SYSCOMMANDS FOR SYSADM.SYSCOMMANDS;
CREATE PUBLIC SYNONYM SYSFKCONSTRAINTS FOR SYSADM.SYSFKCONSTRAINTS;
CREATE PUBLIC SYNONYM SYSINDEXES FOR SYSADM.SYSINDEXES;
CREATE PUBLIC SYNONYM SYSKEYS FOR SYSADM.SYSKEYS;
CREATE PUBLIC SYNONYM SYSPKCONSTRAINTS FOR SYSADM.SYSPKCONSTRAINTS;
CREATE PUBLIC SYNONYM SYSSYNONYMS FOR SYSADM.SYSSYNONYMS;
CREATE PUBLIC SYNONYM SYSTABAUTH FOR SYSADM.SYSTABAUTH;
CREATE PUBLIC SYNONYM SYSTABCONSTRAINTS FOR SYSADM.SYSTABCONSTRAINTS;
CREATE PUBLIC SYNONYM SYSTABLES FOR SYSADM.SYSTABLES;
CREATE PUBLIC SYNONYM SYSUSERAUTH FOR SYSADM.SYSUSERAUTH;
CREATE PUBLIC SYNONYM SYSVIEWS FOR SYSADM.SYSVIEWS;

Hope this helps!

Best regards,

Mike

Return to “Bug Reports”

Who is online

Users browsing this forum: [Ccbot] and 0 guests