« on: March 15, 2010, 05:11:53 PM »
I think this may be the 4 gb limit coming back to haunt me. I had to change to a new copy of Win7 after my eval. copy expired so had to reinstall everything. I backed up my OML database and all seemed fine. The backup file came in at 4,187,132 kb (3.99GB). I then setup my new win7 and reinstalled everything including OML and no probs with SQL or anything. Rebooted machine opened OML and still fine, also accessed OML OK from my htpc over the network no probs. Then thought OK lets reinitiate my db from the backup. So ran the restore from backup tool and after a couple of minutes got the everything is fine shut down OML and restart message. However, now if i try to restart OML it just hangs at checking db and says OML has encountered a problem... aaaargh. Checked OML log but nothing in there so checked SQL log and found this message:
2010-03-15 16:41:31.96 spid51 Starting up database 'oml'.
2010-03-15 16:41:32.07 spid51 Error: 17204, Severity: 16, State: 1.
2010-03-15 16:41:32.07 spid51 FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL10.OML\MSSQL\DATA\OML.mdf for file number 1. OS error: 2(failed to retrieve text for this error. Reason: 15100).
2010-03-15 16:41:32.31 Logon Error: 18456, Severity: 14, State: 38.
2010-03-15 16:41:32.31 Logon Login failed for user 'oml'. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]
I then checked the data file location and discovered that the new oml.mdf file is larger than the backup and states it is 4.00 GB now. Is the not opening problem due to the fact that the backup file has been expanded by OML during the restore process and is now too big to be allowable by SQL??
Is there a way to trim off some of the backdrop/cover data using a utility other than OML db editor to bring the file back down under 4gb in size so it can be opened??
