Probable Causes |
Remedy |
---|---|
When a process is initiated, the system will check in the database to figure out what the next file should be named, such as 105.ctx. When it gets the name, it bumps that number up in the database, so the next file will be 106.ctx, etc. If an older database is restored, the older database will think that the next file should be 105.ctx. However, that file already exists in the Disk Group directory (processed via the pre-existing database), so file collision will occur. This error may also occur if no Disk Group is assigned to the Document Type configured in the COLD. |
Locate and remove all extraneous files, and/or Force Promote the Disk Group(s). |