Sybase account creation help

[nyck]

Our main sybase server decided to die the other day, so I created a new sybase server along with the databases etc. I then loaded the database dumps into the new database and now one of my users is having the following error message whilst running a script against one of the new databases:-

start
libarbor_db/database_clib.c(7676): ex_servermsg_cb - ERROR, server -
Message number = 10330
Severity = 14
State = 1
Line = 4
Server = 'TSS125'
Procedure = 'check_proc_status'
Message String = EXECUTE permission denied on object check_proc_status, database EUSK11_CUST, owner dbo

Can someone tell me how I reosolve this?

It works fine as the sa user but not as the arbor user which does exist!

 

[level2programmer]

You must give execute permission on stored procedures before a user can execute them. It is very similar to giving permission on tables. If a user does not have permission to do things on the table, SYBSASE will refuse to allow them to access it. Stored procedures are the same.

GRANT EXECUTE ON dbo.TABLE_NAME TO user_name

 

[nyck]

cheers for the response, as you can probably tell I'm a bit rusty with sybase. I also have another server that has got a couple of sybase servers that I need to migrate. So on the new server I have installed sybase and built the two new servers, created data devices etc. How do I go about listing all the users etc on the original sybase servers so that I can create them in preperation for the migration to the new server?

Also the way I'm perfroming the database dumps is as follows:-

use master
go
dump database <DB_NAME> to "/tmp/db_name.dump"

is this ok?

 

[level2programmer]

Yes, that is fine for dumping. It looks like you are using Linux/Unix. Be careful about leaving the dumps on /tmp. Linux has some, which I'm not sure what it is, model for cleaning the /tmp directory. I'm assuming you are logging in as the sybase account, so you can make a directory under /opt/sybase specifically for dumps. Only allow sybase user access to the directory to protect the dumps. Additionally, remember you may want to dump the database creation scripts (or DDL) because any 'ALTER DATABASE...' commands must be done when restoring the database. In otherwords the restore works on the same creation model that was used with the dump. If you have troubles with that, you can do BCP dumps to text files and then import the data back again to a different size database.

Regards.