admin procedures

[kburrows]

Hi everyone,

I am wanting to create a package with several procedures using the execute immediate for user administration. The package would contain: create user, drop user, grant, revoke statements with the variables passed in when executed.

Question:

Who should own a package like this? I would probably run this as SYS, but should I create a package in the SYS schema?

Does or has anyone else done this before? What are the pros and cons of creating as SYS?

Thanks
Kathy

[anandkl]

its better to create under a user who has dba previleges.Not the sys or system user.

cheese
anandkl

[hrishy]

Hi

I suggest you not to craete any objects in the sys schema as it a dangerous to do so from a security perspective.It might bring down your system or corrupt your database.

regards
Hrishy

[Raminder]

Apart from very real danger of damaging SYS owned objects, there is the question of performance. The SYSTEM tablespace already has a lot of I/O activity going on when the database is in use. You don't want to increase the I/O in that tablespace further.

[kris109]

My suggestion is to create separate scripts in a directory such as /dba as opposed to a package in the database. We do like that. When I need to create a new user I just do @create_user. Any DBA with create user privileges can use these scripts.