User guide

When server is terminated by this timeout the following message will be logged in the server
log:
Server terminated due to inactivity
2006-02-08 12:28:03.578 : Forced disconnect by Server terminated due
to inactivity @ LOCAL
A server inactivity timeout will occur if, for the length of time specified, no new client
connection is made to that server. In other words the timeout period is started after each new
connection. If the timeout expires and there are current connections still using the server, the
timeout period will be reset to start again.
Thus the timeout value is the minimum time that the server will accept between new
connection requests before closing down, but due to current server activity this may be
extended until there are no more connections current.
Contents
8.9 JDBC Hint Methods
Several methods in the JDBC classes are considered to provide hints to the drivers or
underlying database system and do not have to be strictly observed. Many existing drivers
silently ignore these methods.
To allow compatibility with other drivers, you may specify that optional hint methods be
ignored by using the usehints connection switch:
@usehints=false
This setting tells the Oracle JDBC for Rdb drivers to ignore hint methods.
By default the Oracle JDBC for Rdb drivers will observe hint methods.
The following methods are perceived as non-mandatory hints:
• Connection.setReadOnly()
• ResultSet.setFetchDirection()
• ResultSet.setFetchSize()
• Statement.setFetchDirection()
• Statement.setFetchSize()
8.10 Lockwait and Maxtries
116