Inactive session after 2 hours of SQL

Experts -

I've a "tableau" reporting session comes from a Window Server to Oracle Linux. It's executing an SQL which runs around 2 hours and then the session is marked as "INACTIVE". The client is getting ORA errors like ORA-00028 and ORA-01013.

The SAME sql was running/completing fine in 2 hours from other workstations.

What could be the issue?

Thanks,
Sve.
LVL 18
sventhanAsked:
Who is Participating?
 
slightwv (䄆 Netminder)Connect With a Mentor Commented:
I would look at the network first.  If the 'bad' workstation and good workstations are on the same subnet/switch/???, look at a configuration, cable or NIC in the 'bad' workstation.
0
 
DavidConnect With a Mentor Senior Oracle Database AdministratorCommented:
http://ora-00028.ora-code.com/ is pretty clear:


ORA-00028:
your session has been killed
Cause:      A privileged user has killed your session and you are no longer logged on to the database.
Action:      Login again if you wish to continue working.

Have a chat with your helpdesk or DBA.  An inactive session is the state where there's no active I/O -- typical if the work is being done on a remote host.  Another thought, you may be bumping up against a timeout constraint in your user profile.  These aren't areas you're going to have access to.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.