Hi Stefan,
you can create /etc/tnsname.ora with connect string you need.
Then just change db_name in /etc/rhn/rhn.conf to the tnsname you've created
(instead of default //host:port/name) and that's it :).
Thanks a lot Michael! That did the trick. The file is actually called
Stefan Lasche wrote:
% Hi Stefan,
%
% you can create /etc/tnsname.ora with connect string you need.
% Then just change db_name in /etc/rhn/rhn.conf to the tnsname you've created
% (instead of default //host:port/name) and that's it :).
%
%
% Thanks a lot Michael! That did the trick. The
We have enabled keepalive on the Oracle server using SQLNET.EXPIRE_TIME, but
the situation has not changed.
I believe you need to specify
ENABLE=BROKEN
in your tnsnames.ora to enable TCP keepalive.
We can not use ENABLE=BROKEN on the Oracle Client, since Spacewalk uses
Oracle
s...@mms-dresden.de wrote:
% We have enabled keepalive on the Oracle server using SQLNET.EXPIRE_TIME, but
% the situation has not changed.
%
% I believe you need to specify
%
% ENABLE=BROKEN
%
% in your tnsnames.ora to enable TCP keepalive.
%
% We can not use ENABLE=BROKEN on the
Hi,
there is a firewall between our Spacewalk-Server and our Oracle-DB, that
silently drops connections that have not been used for one hour.
When the Spacewalk-Server tries to reuse Database connections after they
have been idle for more than 60 minutes, it won't succeed. It takes quite a
s...@mms-dresden.de wrote:
% Hi,
%
% there is a firewall between our Spacewalk-Server and our Oracle-DB, that
% silently drops connections that have not been used for one hour.
...
% Since the firewall's behavior can't be adjusted, the most obvious solution
% would be to enable keepalive probes
On Fri, Jun 07, 2013 at 10:30:21AM +0200, s...@mms-dresden.de wrote:
First I tried to set SQLNET.EXPIRE_TIME = 10 in
/etc/rhn/tns_admin/osa-dispatcher/sqlnet.ora - which should tell the Oracle
Instant Client to use its implemented keepalives procedures. It just doesn't
work.
As pointed out
