Hi Jason,

When this happens to us we normally still have the good gdb lying
around (we make a backup copy of it before the backup/restore process).
If you have this good gdb then you can simply alter your existing stored
procedures/triggers that call this sp (and have the correct parameters)
and basically blank them out, then change the parameters of the
sp_dhseng_daterules procedure to match what it used to be. That will
allow you to change the sp(s) that is giving the BLR error so you can
blank that one out also. Then you can put the new parameters back on
sp_dhseng_daterules and then put all of the code back (with the new
parameters) into the blanked out procedures and triggers. Make sense?
But if you only have the gbk then I am not sure what you can do.

-steve

On Mon, 2005-06-27 at 10:40 +0000, jasonryan_nis wrote:

> Hi,
>
> I'm restoring a database and I get the following error:
>
> IBE: Invalid token.
> invalid request BLR at offset 212.
> parameter mismatch for procedure SP_DHSENG_DATERULES.
>
> Which in turn means my procedures are not being restored.
>
> I think its because a particular store procedure that calls
> the "sp_dhseng_daterules" was backed up before it was changed to add
> another parameter to the call. Is there anyway of restoring this
> database and the procedures?
>
> Cheers,
> Jason
>
>
>
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>
>


[Non-text portions of this message have been removed]