Database Networking (MOSC)

MOSC Banner

Oracle 12: Windows clients experience timeout after 30 mins of inactivity

edited Aug 27, 2015 4:36PM in Database Networking (MOSC) 4 commentsAnswered ✓

Our databases are on HP-UX Itanium (64-bit)

We have upgraded one database from 11g to 12c using dbua (fully automated) and another one manually.

Windows clients that connect to either of the 2 upgraded databases experience timeouts after about 30 minutes.

notes:

- the SAME clients do not experience the timeouts when connecting to 11g databases.

- the timeouts occur whether the windows clients get their initial connection thought the 11g or the 12c listener.

- The timeout symptoms include; ORA-03113 'end-of-file on communication channel', IO Error: Socket read timed out, 'Closed connection: Vendor code 17008' (or vendor code 17002)

- I have noted that the server-side shadow task is still running!! and is still visible in v$session...

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center