Hi All,

we run in 2 total different Installations, the JDBC Driver.
Installation 1 = IDM 3.01, JDBC 2.1.7 - Snycing with MSSQL Server
Installation 2 = IDM 3.5.1, JDBC from 3.5.1 - Syncing with Oracle
Both Installation run on a OES Server, with SLES9

Now, watching the NDS DIB Directory, we see 4 Files as follows:

.\jdbc_[GUID of the Driver I Guess - long Number].db (old Date)
3GByte
.\jdbc_[GUID of the Driver I Guess - long Number].lg (old Date) 8
Byte

jdbc_[GUID of the Driver I Guess - long Number].db (current Time)
800MByte
jdbc_[GUID of the Driver I Guess - long Number].db (current Time)
8 Byte

jdbc_[GUID of the Driver I Guess - long Number].db.1.bad (old Date)
14MByte
jdbc_[GUID of the Driver I Guess - long Number].db.1.bak (old Date)
399MByte
jdbc_[GUID of the Driver I Guess - long Number].lg.1.bad (current
Time) 8 Byte
jdbc_[GUID of the Driver I Guess - long Number].lg.1.bak (current
Time) 8 Byte

jdbc_[GUID of the Driver I Guess - long Number].db.2.bad (old Date)
700MByte
jdbc_[GUID of the Driver I Guess - long Number].lg.2.bad (current
Time) 8 Byte
(Size for this Example are for the IDM3.0.1 Installation, but are very
similar vor Installation 3.5.1)

The DataBase contains something like 200 Entries with no more then five
Attributes - which is a very Small Table. To avoid to much traffic, the
Databasse is accessd trough a DB-View, to see only this relevant TABLE
and only the required Attributes

--> Watching the Files with the current Date, these Files constantly
GROW and GROW and GROW.

We set a Driver Cache Limit to 128'000K which is 128MByte, if we do not
miscalculate?

Can anyone explain why this is the cause.
Can we delete the BAD/BAk Files
Can we limit this, or do we have problem here?
Is there a Problem we did not see?

Best Regards

Oliver


--
okuepfer
------------------------------------------------------------------------
okuepfer's Profile: http://forums.novell.com/member.php?userid=2725
View this thread: http://forums.novell.com/showthread.php?t=352919