Thank you, Helen:

I thought the same, then I tried a few things and found the following:

1. Yes, both DBs used SYSDBA to attempt the system table UPDATE.

2. The difference turned out to be that for one there was actually some
source code in the fields. While the other that threw an error message,
already had NULL fields in all records.

3. When limiting the UPDATE to a specific record rather than the entire
table and even then setting RDB$Procedure_Source = NULL only when there
is some source code to null, then it works fine.

Chuck Belanger


On 5/31/2018 7:43 PM, Helen Borrie helebor@...
[firebird-support] wrote:

>> 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
>
>
>
> ------------------------------------
> Posted by: Helen Borrie <helebor@...>
> ------------------------------------
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Documentation item
> on the main (top) menu. Try FAQ and other links from the left-side menu there.
>
> Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ------------------------------------
>
> Yahoo Groups Links
>
>
>
>

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus