免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 4905 | 回复: 6
打印 上一主题 下一主题

Oracle 如何能自动及时 Kill 掉已经断线的 SESSION? [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2003-01-14 14:46 |只看该作者 |倒序浏览
对于远程拨号连接到Oracle数据库的用户,由于断线或其它原因,实际上客户端与数据库的连接已经断开,Oracle如何能及时发现,并删除其会话?

论坛徽章:
1
荣誉版主
日期:2011-11-23 16:44:17
2 [报告]
发表于 2003-01-14 15:29 |只看该作者

Oracle 如何能自动及时 Kill 掉已经断线的 SESSION?

PMON进程就是干这个的吧?

论坛徽章:
0
3 [报告]
发表于 2003-01-14 15:30 |只看该作者

Oracle 如何能自动及时 Kill 掉已经断线的 SESSION?

没错,oracle会自动处理:)

论坛徽章:
0
4 [报告]
发表于 2003-01-14 17:52 |只看该作者

Oracle 如何能自动及时 Kill 掉已经断线的 SESSION?

用一下dead connection detection.

论坛徽章:
0
5 [报告]
发表于 2003-01-15 18:56 |只看该作者

Oracle 如何能自动及时 Kill 掉已经断线的 SESSION?

chaoping,能否解释一下如何使用?
谢谢!

论坛徽章:
0
6 [报告]
发表于 2003-01-28 10:31 |只看该作者

Oracle 如何能自动及时 Kill 掉已经断线的 SESSION?

pMON进程会自动地处理:首先假设该进程的标志有效,然后删除掉所有的该用户的所有占用资源,然后段掉该用户与数据库的连接。

论坛徽章:
0
7 [报告]
发表于 2003-01-28 14:41 |只看该作者

Oracle 如何能自动及时 Kill 掉已经断线的 SESSION?

不要使用缺省的PROFILE,给你的用户定义个受限制的PROFILE就可以了。

具体的参数含义如下:
Profile: General Page

Name

Name of the new profile.

Details

These fields determine the amount of time allocated to the CPU per Session, CPU per
Call, Connect Time, and Idle Time for this profile. The fields are:

CPU/Session: Total amount of CPU time allowed in a session. The limit is expressed in
seconds.

CPU/Call : Maximum amount of CPU time allowed for a call (a parse, execute, or fetch).
The limit is expressed in seconds.

Connect Time: Maximum elapsed time allowed for a session. The limit is expressed in
minutes.

Idle Time: Maximum idle time allowed in a session. Idle time is a continuous period of
inactive time during a session. Long-running queries and other operations are not
subject to this limit. The limit is expressed in minutes.

Database Services

These fields determine the database services allocated to this profile. The fields are:

Concurrent Sessions: Maximum number of concurrent sessions allowed for a user.

Reads/Session: Total number of data block reads allowed in a session. The limit includes
blocks read from memory and disk.

Reads/Call: Maximum number of data block reads allowed for a call (a parse, execute, or
fetch) to process a SQL statement.

Private SGA: Maximum amount of private space a session can allocate in the shared pool
of the System Global Area (SGA). The Private SGA limit applies only if you are using the
multi-threaded server architecture. The limit is expressed in kilobytes (Kbytes).

Composite Limit: Total resource cost for a session. The resource cost for a session is the
weighted sum of the CPU time used in the session, the connect time, the number of
reads made in the session, and the amount of private SGA space allocated.

Entering Values

You can enter a value in a field or choose from the drop-down list adjacent to the field.
Click on the down-arrow to display the list. The drop-down list provides the following
choices:

Default: Use the limit specified for this resource in the DEFAULT profile.

Unlimited: The user's access to this resource is unlimited.

Values: Select one of the existing values. The default values vary by field and are common
values for the field. If you have entered a value in the field, that value appears in the drop
-down list.

Attention: In the SQL Worksheet, you can use the SQL command ALTER RESOURCE
COST to specify the weights for the resources in the Composite Limit. For information
about the ALTER RESOURCE COST command, see the Oracle Server SQL Reference for
your release.
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP