A
Alex Chan
Hi All,
I know this might not be an appropriate newsgroup for this question. I
have tried to search in OTN but seems no good solution exists. Just see any
developers face similar problem before
I have used Oracle Data Provider.NET (ODP) and built a C# window
service. I have used the oracle connection pooling as default. However, as
my oracle database would be down for backup every night. Every day, i need
to restart my C# service in order to avoid the TNS Packet Writer failure
error. I know this is becoz the previous connections pooled are no longer
valid due to the shutdown of Oracle database.
ODP suggest using an option in the connection string "valid
connection=true" to avoid this problem, however, performance penalty will be
paid for the round trip checking of connection, that indeed violates the
objective of using connection pool i think.
Any developers encountered this problem? any standard way to tackle
this?
Regards,
Alex
I know this might not be an appropriate newsgroup for this question. I
have tried to search in OTN but seems no good solution exists. Just see any
developers face similar problem before
I have used Oracle Data Provider.NET (ODP) and built a C# window
service. I have used the oracle connection pooling as default. However, as
my oracle database would be down for backup every night. Every day, i need
to restart my C# service in order to avoid the TNS Packet Writer failure
error. I know this is becoz the previous connections pooled are no longer
valid due to the shutdown of Oracle database.
ODP suggest using an option in the connection string "valid
connection=true" to avoid this problem, however, performance penalty will be
paid for the round trip checking of connection, that indeed violates the
objective of using connection pool i think.
Any developers encountered this problem? any standard way to tackle
this?
Regards,
Alex