Skip to main content

Posts

Showing posts from April, 2015

Profiles and resource management

Benefits of Profile You can enforce a limit on resource utilization using resource limit parameters. Also you can maintain database security by using password management feature. Resource Parameters • SESSIONS_PER_USER Specify the number of concurrent sessions to which you want to limit the user. • CPU_PER_SESSION Specify the CPU time limit for a session, expressed in hundredth of seconds. • CPU_PER_CALL Specify the CPU time limit for a call (a parse, execute, or fetch), expressed in hundredths of seconds. • CONNECT_TIME Specify the total elapsed time limit for a session, expressed in minutes. • IDLE_TIME Specify the permitted periods of continuous inactive time during a session, expressed in minutes. Long-running queries and other operations are not subject to this limit. • LOGICAL_READS_PER_SESSION Specify the permitted number of data blocks read in a session, including blocks read from memory and disk. • LOGICAL_READS_PER_CALL Specify the permitted th...

Proxy User and Connect Through

Proxy User and Connect Through Since Oracle 9i Release 2 it has been possible to create proxy users, allowing you to access a schema via a different username/password combination. This is done by using the GRANT CONNECT THROUGH clause on the destination user. Assuming we have a user called SCOTT and we want to create a proxy user to allow someone to connect to SCOTT without knowing the password, we could do the following. CONN / AS SYSDBA CREATE USER test_user IDENTIFIED BY test_user; ALTER USER scott GRANT CONNECT THROUGH test_user; We can now connect to the SCOTT user, using the credentials of the proxy user. SQL> CONN test_user[scott]/test_user SQL> SHOW USER USER is "SCOTT" SQL> Proxy users can be identified using the PROXY_USERS view. SELECT * FROM proxy_users; PROXY CLIENT AUT FLAGS ------------------------------ ------------------------------ --- ----------------------------------- TEST_USER ...