Yes, permissions are very important. I ran into a similar problem because I didn't have the correct permissions. Make sure the user has the following permissions:
CREATE ANY TABLE
ALTER ANY TABLE
DROP ANY TABLE
CREATE ANY PROCEDURE
EXECUTE ANY PROCEDURE
DROP ANY PROCEDURE
Also, make sure there is enough space in the default tablespace of that user.
HTH
~Suvesh
I set these permissions in the DataBase properties. I checked all db_owner, db_rightaccess....etc.
But, still the same...
also made Method=direct instead of Cursor, but of no use.
Should I need to run any grant permission script or alter the script and create the Database object again?
I haven't checked the tablespace yet...
G
Its possible that the proxy user (the username you use to connect the repository to the database instance) does not own the database tables--in this case, the "object" table is simply the first. The "attribute" table would be next, then "userobj", "userattr" and so forth.
You might need to create views to act as synonyms/aliases.