Informix Error -706

Reasons / Common Causes

-706 fires when a session that neither owns a procedure nor holds DBA privilege attempts to execute it without having been granted Execute privilege — per the official guidance, this is the specific privilege required.

1. A session calling a procedure it doesn't own and hasn't been granted Execute privilege on — the direct, only cause.
2. A privilege grant that was expected to already exist but was never actually issued, or was revoked since.

Solutions / Resolution

1. Have the procedure's owner (or a DBA-privileged user) grant Execute privilege:

   GRANT EXECUTE ON PROCEDURE update_order TO app_user;
   

2. Confirm the procedure's owner first, if it's not obvious who should grant the privilege:

   SELECT procname, owner FROM sysprocedures WHERE procname = 'update_order';
   

3. Check existing grants to confirm whether Execute privilege genuinely isn't there, versus being granted on a different (similarly-named) routine:

   SELECT a.grantee, a.procauth FROM sysprocauth a, sysprocedures p
   WHERE a.procid = p.procid AND p.procname = 'update_order';
   

Examples

Hitting the restriction

EXECUTE PROCEDURE update_order(42, 'shipped');
-- -706: app_user has no Execute privilege on update_order

Granting it

-- Run by the owner of update_order, or a DBA-privileged user:
GRANT EXECUTE ON PROCEDURE update_order TO app_user;

Diagnostic Checks

1. Query sysprocedures for the procedure's owner and sysprocauth (joined on procid) for existing Execute grants, to confirm the privilege genuinely isn't there.

Related Errors / Related Topics

• -674 — "Routine routine-name cannot be resolved." A related routine-call error — missing execute permission is one of several conditions that error covers, while -706 is specific to the permission check itself.

Confirm the procedure's actual owner via sysprocedures, then have them (or a DBA) grant Execute privilege.