Hi Volker,

I have tried this with dba and here's what I see:

Could not execute statement. Syntax error near 'MUTEX' SQLCODE=-131, ODBC 3 State="42000" Line 1, column 1

CREATE MUTEX protect_my_cr_section SCOPE CONNECTION

select * from sp_displayroles( 'dba', 'expand_down')
where role_name like 'Create any %' or role_name like '%mutex%'
order by 1;

role_name,parent_role_name,grant_type,role_level
'CREATE ANY INDEX','SYS_AUTH_SA_ROLE','ADMIN',3
'CREATE ANY MATERIALIZED VIEW','SYS_AUTH_SA_ROLE','ADMIN',3
'CREATE ANY OBJECT','SYS_AUTH_SA_ROLE','ADMIN',3
'CREATE ANY PROCEDURE','SYS_AUTH_SA_ROLE','ADMIN',3
'CREATE ANY SEQUENCE','SYS_AUTH_SA_ROLE','ADMIN',3
'CREATE ANY SEQUENCE','SYS_AUTH_RESOURCE_ROLE','NO ADMIN',2
'CREATE ANY TABLE','SYS_AUTH_SA_ROLE','ADMIN',3
'CREATE ANY TEXT CONFIGURATION','SYS_AUTH_SA_ROLE','ADMIN',3
'CREATE ANY TRIGGER','SYS_AUTH_SA_ROLE','ADMIN',3
'CREATE ANY TRIGGER','SYS_AUTH_RESOURCE_ROLE','NO ADMIN',2
'CREATE ANY VIEW','SYS_AUTH_SA_ROLE','ADMIN',3

I am starting to wonder if Mutexes are supported in the Developer version of the server! Do you know if this is the case?

Thanks.

Hi Volker,

It looks like I found the problem and it's rather strange. Since everyone suggested that there should be no problem with this (as long as my user has the rights) I tried this with a different database and had no problem. It then occurred to me that the original database I was testing with is the ultimate "legacy" database. This database was originally created for use with the original Watcom server and has gone through numerous updates and upgrades all the way up to now v17. So the good news for me is that I don't have any sort of fundamental problem but the bad news is that something is wrong with user rights and roles in this database (which is compatible with server v17). Here is what we get running with a "new/fresh/v17" database: select * from sp_displayroles( 'dba', 'expand_down') where role_name like 'Create any %' or role_name like '%mutex%' order by 1;

role_name,parent_role_name,grant_type,role_level 'CREATE ANY INDEX','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY MATERIALIZED VIEW','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY MUTEX SEMAPHORE','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY OBJECT','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY PROCEDURE','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY SEQUENCE','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY SEQUENCE','SYS_AUTH_RESOURCE_ROLE','NO ADMIN',2 'CREATE ANY TABLE','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY TEXT CONFIGURATION','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY TRIGGER','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY TRIGGER','SYS_AUTH_RESOURCE_ROLE','NO ADMIN',2 'CREATE ANY VIEW','SYS_AUTH_SA_ROLE','ADMIN',3 'DROP ANY MUTEX SEMAPHORE','SYS_AUTH_SA_ROLE','ADMIN',3 'UPDATE ANY MUTEX SEMAPHORE','SYS_AUTH_SA_ROLE','ADMIN',3

and here's what we get when we run this against the "legacy" database that has been upgraded numerous times over a couple of decades: role_name,parent_role_name,grant_type,role_level 'CREATE ANY INDEX','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY MATERIALIZED VIEW','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY OBJECT','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY PROCEDURE','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY SEQUENCE','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY SEQUENCE','SYS_AUTH_RESOURCE_ROLE','NO ADMIN',2 'CREATE ANY TABLE','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY TEXT CONFIGURATION','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY TRIGGER','SYS_AUTH_SA_ROLE','ADMIN',3 'CREATE ANY TRIGGER','SYS_AUTH_RESOURCE_ROLE','NO ADMIN',2 'CREATE ANY VIEW','SYS_AUTH_SA_ROLE','ADMIN',3

Dropping the common rows we are left with the apparent fact that the following are missing in the "legacy" database: 'CREATE ANY MUTEX SEMAPHORE','SYS_AUTH_SA_ROLE','ADMIN',3 'DROP ANY MUTEX SEMAPHORE','SYS_AUTH_SA_ROLE','ADMIN',3 'UPDATE ANY MUTEX SEMAPHORE','SYS_AUTH_SA_ROLE','ADMIN',3

When I say missing I mean that they are not even listed as being available to be assigned to a user (at least in SQL Central). I'd mentioned in my initial question that "CREATE ANY MUTEX SEMAPHORE" was not available to be assigned.)

Since the latest update of this database was done by exporting all data from a (I believe) v15 database and then importing into a fresh v17 database I'm not sure what I could have done differently to avoid this problem. Do you have any idea how I can salvage this database by getting whatever System tables are messed up straightened out? (Vague question but I have no idea what tables are not correct. All I can see at this point is that there are no MUTEX related roles available for assignment.)

Thank you.