12.07.2015 Views

General Error Messages - InterSystems Documentation

General Error Messages - InterSystems Documentation

General Error Messages - InterSystems Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

TSQL <strong>Error</strong> <strong>Messages</strong>Table 3–36:TSQL <strong>Error</strong> Codes - 4300 to 4399<strong>Error</strong> Code4301430443054306431643184320432243234324432543264327432843294330433143324333DescriptionDatabase in use. The system administrator must have exclusive use of thedatabase to restore the log.A USER ATTENTION signal raised during RESTORE LOG is being ignored untilthe current restore completes.The log in this backup set begins at LSN %.*ls, which is too late to apply to thedatabase. An earlier log backup that includes LSN %.*ls can be restored.The preceding restore operation did not specify WITH NORECOVERY or WITHSTANDBY. Restart the restore sequence, specifying WITH NORECOVERY orWITH STANDBY for all but the final step.Can only RESTORE LOG in the master database if SQL Server is in single usermode.File '%ls' has been rolled forward to LSN %.*ls. This log terminates at LSN %.*ls,which is too early to apply the WITH RECOVERY option. Reissue the RESTORELOG statement WITH NORECOVERY.File '%ls' was only partially restored by a database or file restore. The entire filemust be successfully restored before applying the log.This log file contains records logged before the designated point-in-time. Thedatabase is being left in load state so you can apply another log file.The database is marked suspect. Transaction logs cannot be restored. UseRESTORE DATABASE to recover the database.Backup history older than %ls has been deleted.Could not delete entries for backup set ID '%ls'.The log in this backup set terminates at LSN %.*ls, which is too early to apply tothe database. A more recent log backup that includes LSN %.*ls can be restored.The log in this backup set contains minimally logged changes. Point-in-timerecovery is inhibited. RESTORE will roll forward to end of logs without recoveringthe database.File '%ls' is missing. Rollforward stops at log sequence number %.*ls. File iscreated at LSN %.*ls, dropped at LSN %.*ls. Restore transaction log beyondbeyond point in time when file was dropped or restore data to be consistent withrest of database.This log file contains records logged before the designated mark. The databaseis being left in load state so you can apply another log file.The log in this backup set cannot be applied because it is on a recovery pathinconsistent with the database.The database cannot be recovered because the files have been restored toinconsistent points in time.RESTORE LOG has been halted. To use the database in its current state, runRESTORE DATABASE %ls WITH RECOVERY.The database cannot be recovered because the log was not restored.132 Caché <strong>Error</strong> Reference

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!