Thanks for that pointer David. There was, indeed, a trigger on the table which called a function raising an exception. I just have never seen that prior to this database.
On Mon, Apr 24, 2017 at 11:21 AM, John Scalia <jayknowsunix@xxxxxxxxx> wrote:
Ah,, I hadn't considered a trigger that could be blocking it. I'll look for it.On Mon, Apr 24, 2017 at 11:13 AM, David G. Johnston <david.g.johnston@xxxxxxxxx> wrote:ERROR: Permission denied: UPDATE is not allowed on rhnpackageevrThat doesn't look like a system generated message (and grep on the source tree turns up no results) - which means you should be looking for a trigger that is blocking you.David J.