JDBC log growth

, ,
1

We use the WmDB package to interact with our SyBase database.
Problem is that the JDBC.log file keeps growing and we have found no way of truncating it except shutting down the Integration server, delete the file and then restarting Integration Server.

On our production environment we would like to not see this log at all. Anyway of avoiding this log or alternatively is there a way to truncate it.

We are currently running on IS 4.6

2

In UNIX case, you can simply just rename the JDBC.log to something else. You can run a cron to do that. But, The problem with WIN is that the file will be locked and you can’t rename it.

Currently we’re having similar problem and haven’t found any idea how to fix this. If you have solution, please let us know.