We are running DB2 Connect Version v8.1.7.445
DB2 Connect is our passthru for the Distributed world to be able to talk to the mainframe databases.
We make infrequent changes to what Mainframe Databases are cataloged in DB2 Connect but when we do, we need the changes to be immediate.
What I have found is that we have DIR_CACHE=YES in our dbm config
so when I make catalog entry changes in the DB2 Configuration assistant, they do not take effect until I restart the DB2 Service. Since this is a Production box, I am looking for a command that will flush the DIR_Cache without having to cycle the DB2 Service.!!! Can anyone help? .
DB2 Connect is our passthru for the Distributed world to be able to talk to the mainframe databases.
We make infrequent changes to what Mainframe Databases are cataloged in DB2 Connect but when we do, we need the changes to be immediate.
What I have found is that we have DIR_CACHE=YES in our dbm config
so when I make catalog entry changes in the DB2 Configuration assistant, they do not take effect until I restart the DB2 Service. Since this is a Production box, I am looking for a command that will flush the DIR_Cache without having to cycle the DB2 Service.!!! Can anyone help? .