Re: Tunning & DBA SQLs

Klaus,

Check the use of 'profiles' within Oracle. It can restrict resources to a user. In addition to this you could also use views to restrict the # of rows being returned from a select. Views can also help in avoiding "bad sql". The use of Roles can be used to effectively restrict privileges (or grant them) to specific sets of users.

Hope this helps.

--
Vikram Goel                                 Motorola email: vgoel_at_pts.mot.com
Sr. Oracle DBA - Consultant
Aerotek Inc.                                My email:  vgoel_at_emi.net

Motorola Info:
Mail Stop 39, Room S1014
1500 Gateway Blvd,
Boynton Beach, FL 33426 


In article <316C8EC7.1C7A_at_primenet.com>, Klaus Schnurr <kschnurr_at_primenet.com> writes:


>We are using Oracle Server 7.1 (running under Solaris 2.4) in a 


>semiconductor manufacturing environment. Users are mainly using the 

>database for data analysis purposes which requires intensive data 

>queries. However, deploying the database and the front-end tools within 

>a client-server environment revealed very soon the limitations of the 

>systems. One user can bring system down to its knees by running an 

>extremely complex query which consumes all the system resources. The 

>users are connecting via the Sequelink middleware product from Intersolv 

>to the database. Now, I have the following questions:

>

>1. Is there any way, within Oracle or UNIX, to restrict the available 

>system and oracle resources which are available for a requested 

>instance?

>

>2. Can Oracle restrict the number of rows a query can return to the user 

>(i.e. trapping "run-away" queries)

>

>3. Does anybody know of Oracle SQL statements which would allow to 

>monitor the database performance?

>

>Thanks a lot for your support and help!

>

>Klaus