Invalidated Procedure?

[Former Member]

My previously working procedures have suddenly become unusable. Each of their object icon in the Navigator now has a small gray box. Calling any of the procedure gives the following error message. Also, all the action buttons (Execute, Refresh) in the Definition view are grayed out. So Hana really thinks the procedures are not valid.

Could not execute 'call SCHEMA.PROC_NAME()'

SAP DBTech JDBC: [430]: invalidated procedure: PROC_NAME: line 1 col 24 (at pos 23)

What's the meaning of "Invalidated Procedure"? I can't find a "validate" feature for procedures. BTW, these are RLang procedures.

Thanks,

Ming

[former_member621066]

Hello,

we also had the problem, that we could not call a procedure anymore which had been working fine until that point. Error message was 430 (invalidated procedure). We then dropped the procedure and tried to re-create it with the same query, but it would still run into the 430 error. Is there anyhing else we can do about it? one more info: We had a hana update a few days before

[Former Member · Accepted solution]

Hi Ming,

Usually the message indicates that you don't have read permissions for one or more of the tables/schemas referenced in the procedure. Make sure you grant all required authorizations to the user that owns (if procedure was defined with SECURITY DEFINER) or runs (if defined with SECURITY INVOKER) the stored procedure.

Stored Procedures are explained in detail in the SQL Script Guide...

--juergen

[Former Member · Accepted solution]

It's interesting to see how proactive Hana is at ensuring dependency integrity between related objects. I'm used to run something, get error messages back and then realized something is wrong. In this case, Hana has done that determination for me a head of time, as Juergen has suggested. Pretty cool, except that it'll be much more helpful if it could bubble up the root cause to the GUI. It shouldn't be hard to implement but will be of great value. (Feature request, unless there is a way of drilling into the error message and call stack of procedure calls, like that for job runs.)

Anyway, in this case, after some dependent views was redeployed, the procedures ran without a problem. BTW, the little "blue (not grey) box" on the procedure icon doesn't indicate invalidation. It's just part of the icon.