This content has been marked as final. Show 3 replies
As a workaround, try using a synonym so as to avoid having to prefix the type name with USER1
e.g. as user2: create or replace synonym blab for user1.blablabla;
I'm not sure why its not working - the "" in the error message does seem strange.
One other thing you could do is post some SQL (e.g. simplified test case) for the creation of the type, granting permission and show that it can be used OK from user2 in SQL - this would help isolate it as an OCCI problem rather than just a general SQL/Types problem