关于SQL*NET client trace

netbanker

we got the similar issues in our environment due the PCI setting for firewall ( default they use 2hrs)

Just wonder how are we going to set SQLNET.EXPIRE_TIME ?  We set it to 30 but seems too low...

[ 本帖最后由 netbanker 于 2010-10-20 05:22 编辑 ]

Yong Huang

netbanker,

What is PCI in your message? If you're sure the firewall idle connection timeout is 2 hours, why do you think 30 minutes is too low? You observed too much network overhead? According to Oracle, any setting below 1 hour in your case should be OK.

Yong Huang

netbanker

SOX compliance


Yong, do you have experience of encountering  big performance issue when turnning on the client trace?

Yong Huang

> big performance issue when turnning on the client trace

Absolutely. Whenever I need SQL*Net trace, I set the level to 16 or admin. That adds a lot of overhead to SQL*Net.

But DCD of (say) 10 minute expire_time addds very little overhead to SQL*Net even when you have hundreds of sessions.

Yong Huang

zhangmazi

原来是这个问题啊，困扰大家好久了。看来是防火墙在捣鬼，没错了。