Dumb Oracle client install question

Printable View

Show 40 post(s) from this thread on one page

01-13-2005, 12:28 PM
slimdave

Hanky, your confrontational nature just makes it all the more sweet when I tell you to RTFM

:D

http://download-west.oracle.com/docs..._ems.htm#19522

Quote:

Beginning with Oracle 8.0.6 databases and higher, the OEM_MONITOR role is created by the Oracle database creation scripts. This role permits access to database functionality within Enterprise Manager. For example, running events against a database (tablespace full, buffer cache hit ratio) or browsing through the objects in a database via the Console Navigator tree. These types of functionality require database credentials on which to perform these operations. Rather than granting the powerful DBA role to the database credentials, many administrators prefer to provide only the necessary privileges required to do these operations. Granting the OEM_MONITOR role to the database credentials, ensures that the user has the minimum sufficient privileges required for these operations.
Note:

You need to create the OEM_MONITOR role using the SYS account.

If you need to create the OEM_MONITOR role manually, here are the steps you need to perform:

1. Create a role called OEM_MONITOR

drop role OEM_MONITOR;
create role OEM_MONTOR:

2. Grant the 'connect' role to OEM_MONITOR

grant connect to OEM_MONITOR;

3. Grant the system privileges 'Analyze any' & 'Create table' to OEM_MONITOR

grant analyze any to OEM_MONITOR;
grant create table to OEM_MONITOR;

4. Create the SELECT_CATALOG_ROLE role as defined in sc_role.sql .
5. Grant the SELECT_CATALOG_ROLE to the OEM_MONITOR role

grant select_catalog_role to OEM_MONITOR;

You are now ready to grant the OEM_MONITOR role to the database user that will be used as "database preferred credentials" in Enterprise Manager. In addition to granting the OEM_MONITOR role to a user, you must also ensure that the QUOTA for the user account is set to UNLIMITED.

The "Continued Row" event test needs to analyze results into a table so it needs both the "analyze any" and "create table" privileges.
Note:

The "analyze any" privilege is used by the "index rebuild" event to compute statistics.

Now, we can get on with the search for his lost credibility.
01-13-2005, 12:37 PM
DaPi

Quote:

Originally posted by Mr.Hanky
Development is ok huh? Well in my department development boxes should mirror production, how is that going to be possible if any schmuck developer can go in and alter/drop/add/truncate tables and objects whenever they want to?

Not sure what you're saying here Mr.H.

I'm sure the passwords are different between dev & prod! (Please say Yes.)

The job of a developer is to make dev different from prod - it's called development. I expect a developer to create and modify objects as the job requires - but not in prod (see above). Accidents can happen in dev - if too often, you shoot/fire the offender.
01-13-2005, 12:42 PM
slimdave

Quote:

Originally posted by DaPi
Not sure what you're saying here Mr.H.

I'm sure the passwords are different between dev & prod! (Please say Yes.)

The job of a developer is to make dev different from prod - it's called development. I expect a developer to create and modify objects as the job requires - but not in prod (see above). Accidents can happen in dev - if too often, you shoot/fire the offender.

Quite so.

The database that is the same as production is called "Quality Assurance" -- "Development" is for developers.

Of course, Mr Hankey's employer may have a history of making bad hiring decisions, and that might have affected how things are done there. Does that sound possible?
01-13-2005, 12:46 PM
gandolf989

Quote:

Originally posted by slimdave
Quite so.

The database that is the same as production is called "Quality Assurance" -- "Development" is for developers.

Of course, Mr Hankey's employer may have a history of making bad hiring decisions, and that might have affected how things are done there. Does that sound possible?

You might have a point there Dave. :D
01-13-2005, 12:48 PM
DaPi

Quote:

Originally posted by slimdave
Mr Hankey's employer may have a history of making bad hiring decisions . . .

There may have been exceptions ;)
01-13-2005, 12:50 PM
gandolf989

Quote:

Originally posted by Mr.Hanky
While I admire your tenacity I feel it is grossly misplaced.

OEM is a DATABASE MANAGEMENT UTILITY, PERIOD
It is a DBA tool, period.

The use of OEM is dependent on the privileges that the user has. I'm not sure how to make you understand that. It's not like I am advocating giving every developer DBA privs. I understand why there is a separation of responsibilty between DBA's and developers. Just try not to make this discussion about you. You are a little too sensitive to be a good DBA anyway. Perhaps if you had some objectivity, you might see things differently.
01-13-2005, 01:09 PM
Mr.Hanky

I ain't givin up yet, even if the whole world is against me.

"For example, running events against a database (tablespace full, buffer cache hit ratio) or browsing through the objects in a database via the Console Navigator tree"

What does that have to do with tuning SQL?

Too sensitive to be a good DBA, ha. You were not saying that during our political discussions!

Dave, I posted not one or two but three descriptions of OEM from Oracle's documentation describing it as a database management tool.
No where does it mention that it is a nifty SQL tuning tool even in your own post.
01-13-2005, 01:10 PM
Mr.Hanky

I do stand corrected on developement, I was thinking more on production support. We still do not let our developers use DBA privs in development.
01-13-2005, 01:16 PM
Mr.Hanky

Come hard or don't come at all DAVE!!

"To use the Event system, an administrator must have sufficient privileges to access database objects from the Console. Under most circumstances, full DBA privileges are not required, nor would be appropriate to assign full DBA privileges to every administrator. For this reason, the OEM_MONITOR role was created."

Fut the wuk does monitoring events have to do with TUNING SQL!?

C'mon, at least you have to admire my complete lack of abandon in my quest for knowledge.
01-13-2005, 01:17 PM
slimdave

Quote:

"For example, running events against a database (tablespace full, buffer cache hit ratio) or browsing through the objects in a database via the Console Navigator tree"

What does that have to do with tuning SQL?

Viewing indexes, statistics on tables + indexes, partitioning, memory configuration etc., just as examples. "Examples" in the sense used in the quote i posted.

Quote:

Dave, I posted not one or two but three descriptions of OEM from Oracle's documentation describing it as a database management tool.
No where does it mention that it is a nifty SQL tuning tool even in your own post.

Gandolf said "I only want to use the OEM tools to tune PL/SQL code before it gets into production, and before it get system tested."

It's pretty handy as an editor of PL/SQL code in the database ... finding procedures within packages is easy, editing the code and hitting "Compile" .. doesn't get much easier than that. You can pay for other tools if you like, but OEM does the job there.

And it doesn't require DBA privileges, which i think was your first objection.

Show 40 post(s) from this thread on one page