Subject | Re: gfix: "unavailable database" returned |
---|---|
Author | jegazarco |
Post date | 2010-01-02T14:51:43Z |
--- In firebird-support@yahoogroups.com, Dimitry Sibiryakov <sd@...> wrote:
In anyway i have the metadata in dialect 1.
Now i will try using gfix to move to dialect 3 and extract metadata from dialect 3, and once extracted, recreate a database with dialect 3, but i don't understand what are the problems to use gfix to move one database to dialect 3, and i don't find where are explained.
>I have tables with more than 150 million records, and my server is quadcore 4Gb RAM 2008 server. The last time i tried to migrate it i spend more that 2 days, because all data can not be moved automatically in one step. 1 day is still a lot.
> > Not so simply in a database of 30Gb, that takes 2 days to move data.
>
> 2 days for 30gb? Are your servers 10 years old? My mini-notebook can
> do it twice faster.
>
> > All databases i have in my customers are dialect 1, and i was thinking to use gfix to move to dialect 3.I have near 1500 stored proc and 3000 triggers. From scratch is writing them again?. I have tried to extract metadata from dialect 1, create a database with dialect 3, and connect with dialect 1 to create database from extracted metadata. FB reported a lot of errors.
>
> After that backup-restore is required anyway to convert data and you
> still may have problems with stored objects (procedures and triggers).
>
> The only reliable way to migrate database is recreate it from scratch.
>
In anyway i have the metadata in dialect 1.
Now i will try using gfix to move to dialect 3 and extract metadata from dialect 3, and once extracted, recreate a database with dialect 3, but i don't understand what are the problems to use gfix to move one database to dialect 3, and i don't find where are explained.
> SY, SD.
>