on 07-21-2016 10:21 PM
All,
thank you for reading this question.
I am creating a stored procedure and all or a sudden I hit a road block. I have been creating them just fine and i am not sure why this one would be any different.
I am creating the stored proc on the same package where other sps are created and activated fine.
My stored pro performs a delete / insert / update on a CDS table from a SCHEMA which i have all access INSERT / ALTER / CREATE ANY / DELETE / UPDATE / TRIGGERS / DEBUG you name it.
the stored proc activates fine if i comment out my code.. but that's of no help for me. I have already tried deleting it and recreating it with out any luck. i also created a stored proc with a different name.
on the trace file i see the following error:
error code: 40305, error message: Could not create catalog object: insufficient privilege; Not authorized, object: package ...
as mentioned before, I already have other stored procs on the same package which are working fine.
my stored proc (.hdbprocedure) declaration is as follow (i created it like all others via the wizard):
PROCEDURE "SCHEMA"."path.to::sp"()
LANGUAGE SQLSCRIPT
SQL SECURITY INVOKER
AS
BEGIN
-- logic
END
I am on SP 11 -- 1.0.112.02 .. this just started happening today
very weird - anyone?
Let me give it a try.
Do you have any other CRUD Stored Proc on the same schema? I can guess you have this Schema , as a brand new schema, and _SYS_REPO doesnot have access granted for your schema.
Can you please check that.
Regards,
Chandan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.