使用resource_limit及profile限制用户连接(三)

NOTE:

If you are running in a shared server environment, you need to be careful not to accidentally kill your dispatchers and/or shared servers. In Oracle 10.2 (or higher) a dedicated connections V$SESSION + V$PROCESS + OS Process can be cleaned up with

ALTER SYSTEM DISCONNECT SESSION ',' IMMEDIATE

At this point in versions prior to 10.2 and for shared server connections the only solution is to kill the session at the OS level (see Kill and ORAKILL above)

* Windows : use the orakill command .... orakill (see Note 69882.1 for details)

On occasions we see conditions where a database session has a V$SESSION.STATUS = SNIPED ... and the entry never goes away . This condition can be achieved by implementing Database Resource Limits + Profiles without DCD and allow the database session to exceed the limit in the profile

5、小结

a、参数RESOURCE_LIMIT = TRUE用于启用数据库资源配置限制

b、profile用于实现资源配置，创建profile或修改已存在的profile来调整各个具体资源配置

c、将profile指派给那些需要限制的用户

d、一旦被限制的用户超出所设定的阀值将收到资源配置相关的错误提示

e、被限制资源的session状态变成sniped

f、被限制资源的session对应的server process并没有被释放，需要手动释放或结合sqlnet.expire_date来进行释放