I never even thought about creating a user with backup system privilege.
Before I start testing, will it it work if the user has only backup
privs and
most of the database objects are owned by SYSDBA?
( I know I know it's crazy but db is a real mess, dating back to
Interbase days,
and we don't have the resources for rewriting/testing tens of thousands
of lines of code....
a lot of which has SYSDBA user hard coded... etc)
A bit of background, as I have had looked into this same issue:
We run the database on customer owned servers but don't want to give
them access to the database outside
of the application programs so they don't muck things up (cause they
will, and have).
Note for Windows, if you used a command line parameter, the user and
password is visible
in task manager when you view the command line there.... also not so good.
To get around that I wrote a bat file that runs gbak and set and use
ISC_USER and ISC_PASSWORD
The application programs rettrieve and decrypt the user and password
kept in an ini file
But they are in the script if anyone wants to look for it...
This all really just a deterrent