How to troubleshoot An error occurred on a query to database" or "Database Query Failure errors that occur during a backup or restore.
|Article:TECH72460|||||Created: 2010-01-18|||||Updated: 2011-06-02|||||Article URL http://www.symantec.com/docs/TECH72460|
How to troubleshoot An error occurred on a query to database or Database Query Failure errors that occur during a backup or restore.
V-79-57344-33938 - Backup or restore operation terminated abnormally. An error occurred on a query to database.
0xe0008492 - Database Query Failure. See the job log for details.
- SQL 2005 backups fail on specific databases with error "The backup of full-text catalog 'FullTextCatalog' is not permitted because it is not online."
- Backup of full-text catalog not permitted because it not online" occurs during a full backup of SQL 2005 Databases
- Backup of SQL database fails with error "It is acting as a mirror database."
- Differential/Log backup of SQL database fails with the error "The Backup Exec SQL Agent was not used to create the last full backup of this database. You must use the SQL Agent to run a full backup before you run a differential backup or transaction log backup"
- SQL database backups fail with error "The transaction log for database 'Databasename' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases".
- SQL backup fails with "Cannot open backup device "DBNAME". Operating system error 0x80070002 (The system cannot find the file specified.)
- After applying Hot fix 38 for Backup Exec 11d or upgrading to Backup Exec 12, differential backups fail when using the SQL Agent to backup the Backup Exec Database (BEDB)
- The error "Database Query Failure. See the job log for details" (e0008492 HEX or a0008492 HEX) is reported while Backing up Microsoft Office SharePoint Server (MOSS) 2007.
- The error "Database Query Failure. See the job log for details" (e0008492 HEX or a0008492 HEX) is reported when backing up a Microsoft SQL database
- A Full Database Backup of a MS SQL 7.0 or MS SQL 2000 database reports the error "The log file for database <DATABASE_NAME> is full. Back up the transaction log for the database to free up some log space".
- SQL redirect restore job fails if destination machine path is selected thru the browse button.
- The Restore of a SQL 2005 database which has full text indexing enabled fails.
- An error occurred on a query to database occurs when a SQL restore is attempted.
- Restore of SQL 2005 database fails with the error message "The tail of the log for the database "TEST1" has not been backed up. Use BACKUP LOG WITH NORECOVERY to backup the log if it contains work you do not want to lose. Use the WITH REPLACE or WITH STOPAT clause of the RESTORE statement to just overwrite the contents of the log."
- "Exclusive access could not be obtained because the database is in use" when performing a Microsoft SQL 2000 or SQL 2005 restore operation
- Restore of Microsoft x64 SQL2005 Master database fails with the error "An error occurred on a query to database master" if the option "Automate master database restore" is selected.
- Error Message "An error occurred on a query to database master" is displayed in the job log when restoring master database to a Microsoft SQL server where the master database location has changed.
- When trying to restore a Microsoft SQL 2000 database to a Microsoft SQL 7 server, the Microsoft SQL restores fail with the error: "The backed-up database has on-disk structure version 539. The server supports version 515 and cannot restore or upgrade this database."
- "An error occurred on a query to database <databasename>. Cannot apply the backup on device '<database GUID>' to database '<databasename>'. " occurs during an SQL Differential Restore
- "Database Query Failure. See the job log for details" (a0008492 HEX or e0008492 HEX) is reported during a restore of a SQL database
Backup or restore operation terminated abnormally. An error occurred on a query to database.
Database Query Failure. See job log for details
Article URL http://www.symantec.com/docs/TECH72460