> Also, apparently, this is not a blanket restriction, since I can
> successfully run the UPDATE RDB$PROCEDURES on at least 1 other
> converted DB (that is essentially the same as the DB I cannot run this UPDATE on).

Smells like a privileges problem. The updater has to be SYSDBA,
rdb$owner_name or (on POSIX) root. Could also be a regular user that
has been granted and is logged in under the RDB$ADMIN role, or one that
has been granted metadata privs on procedures through user name or
role.

HB


---
This email has been checked for viruses by AVG.
https://www.avg.com