Subject | Re: Unsuccessful MetaData Update |
---|---|
Author | Adam |
Post date | 2006-01-18T04:31:29Z |
--- In firebird-support@yahoogroups.com, "Craig" <cstevens@d...>
wrote:
Does the backup fail process, or is it the restore of the backup
file? If it is the restore process, are you able to restore that file
on the machine you took the backup from? If not, I suspect it is a a
stored procedure call from within another stored procedure, where the
calling parameters have been changed since the BLR was compiled.
(Happenned once). Restoring with the -v switch, you should be able to
identify which stored procedure is giving you grief, then look for
other procedures where it is called from. Fix the stored procedures
so they are compiled with the correct parameters, and try again.
Of course I may be totally on the wrong track.
Adam
wrote:
>production
> --- In firebird-support@yahoogroups.com, Alexandre Benson Smith
> <iblist@t...> wrote:
> >
> > Craig wrote:
> >
> > >Hi Anyone who could help?
> > >
> > >I have a production database which will restore only on the
> > >machine and the original design machine, but not to two otherwilling
> > >development machines. Each time its comes up with unsuccessful
> > >metadata update. I have a 9k metadata only backup i would be
> > >to send to anyone who would like to attempt to restore thisfile.
> > >Craig,
> > >Thanks
> > >Craig
> > >cstevens@d...
> > >
> > >
> > Craig,
> >
> > What errors did you get ?
> >
> > Maybe some missing UDF ???
> >
> > see you !
> >
> > --
> > Alexandre Benson Smith
> > Development
> > THOR Software e Comercial Ltda
> > Santo Andre - Sao Paulo - Brazil
> > www.thorsoftware.com.br
> >
Does the backup fail process, or is it the restore of the backup
file? If it is the restore process, are you able to restore that file
on the machine you took the backup from? If not, I suspect it is a a
stored procedure call from within another stored procedure, where the
calling parameters have been changed since the BLR was compiled.
(Happenned once). Restoring with the -v switch, you should be able to
identify which stored procedure is giving you grief, then look for
other procedures where it is called from. Fix the stored procedures
so they are compiled with the correct parameters, and try again.
Of course I may be totally on the wrong track.
Adam