Hi,
This one has got me confused (not hard I know).
We have a massive 9.1D09 database (80GB) running on a windows 2000 server which is closed down at 8pm each day to be backed up. The database is then copied via FTP to another server. We have reports running off the database using Crystal Enterprise throughout the day so there are potentially reports still running when the database is shut down. We use two types of driver to connect to the database - SQL92 and Openlink.
Recently we are seeing the FTP copy failing due to the *.D* files being locked even after shutdown. I'm a decent progress developer but only a novice DBA and although I can get to the bottom of most database problems this one's got me stumped.
The log file isn't giving too much avay in this instance. The one common line I see each time the FTP copy fails is:
WDOG 116: Broker disappeared, updating <file-name>.lk file. (4194)
Followed by:
WDOG 116: Multi-user session end. (334)
The database is definately not runnning when the FTP transfer starts.
I've spoken to our Software vendor who provide the database and software and they are convinced that the SQL92 connections at the time the database is shut down are to blame but I dont see why this could be when the log file has reported "multi user session ended".
Any ideas?
This one has got me confused (not hard I know).
We have a massive 9.1D09 database (80GB) running on a windows 2000 server which is closed down at 8pm each day to be backed up. The database is then copied via FTP to another server. We have reports running off the database using Crystal Enterprise throughout the day so there are potentially reports still running when the database is shut down. We use two types of driver to connect to the database - SQL92 and Openlink.
Recently we are seeing the FTP copy failing due to the *.D* files being locked even after shutdown. I'm a decent progress developer but only a novice DBA and although I can get to the bottom of most database problems this one's got me stumped.
The log file isn't giving too much avay in this instance. The one common line I see each time the FTP copy fails is:
WDOG 116: Broker disappeared, updating <file-name>.lk file. (4194)
Followed by:
WDOG 116: Multi-user session end. (334)
The database is definately not runnning when the FTP transfer starts.
I've spoken to our Software vendor who provide the database and software and they are convinced that the SQL92 connections at the time the database is shut down are to blame but I dont see why this could be when the log file has reported "multi user session ended".
Any ideas?