Skip to main content

 

Druva Documentation

SQL errors

This topic lists the SQL errors that you may encounter while working  with Phoenix. 

SQL1

Error Message : Streams were not uploaded properly in previous backup cycle. 

Error Description: This error can occur if the data that was getting uploaded at the time of backup got corrupted due to network issues. 

Error Solution: Use a different restore point. 

SQL2

Error Message:  No database found for restore

Error Description: This error occurs if a database was not selected for restore.

Error Solution: Select a database and then attempt a restore. 

SQL3

Error Message: Metadata mismatched.

Error Description: This error can occur if the metadata of the database selected for backup does not match with the database metadata when it was backed up earlier. 

Error Solution: Run a full backup. 

SQL4

Error MessageSpecified instance not found on present application server.:[Attempting to restore to instance <logical path of instance> not found in server]

Error Description: This error can occur:

  • During restore to the original location, if the specified instance is not present on the target machine.

Error Solution:  To resolve the error:

  • Restore the database file to an alternate location. These files can be used to restore databases by attaching it to other SQL instance.

SQL5

Error Message:  sqlcmd utility failed to get query result.:[Error in fetching the SERVERPROPERTY('ProductVersion') for sql server instance: <instance name>.]

                                    OR

                                     sqlcmd utility failed to get query result.:[Error in fetching the SERVERPROPERTY('ProductLevel') for sql server instance: <instance name>..]

Error Description:  This error can occur because of one of the following reasons:

  • sql cmd is not configured.
  • Some error with the sqlcmd.

Error Solution:   To resolve this error:

  • On the command prompt, type "sqlcmd" to check if sql cmd is configured.
  • Retry the operation.

Note: This error is applicable for SQL agent versions 4.6.5 and earlier. 

SQL6

Error Message:  Phoenix SQL agent found no instance/database on the server to backup if the SQL service is not running or the backup policy is set to exclude all the databases.

Error Description:  This error can occur because of one of the following reasons:

  • Log chain is broken for selected databases.
  • All databases in simple recovery mode for log backup.
  • All databases excluded from UI.

Error Solution:   To resolve this error:

  • Ensure at least one instance is online and in working state.
  • Check backup policy and the excluded folder entries.
  • Trigger full/differential backup.
  • Disable third-party backup tool.
  • At least one database should have FULL recovery mode.
  • Update excluded databases list.

SQL7

Error Message:  PYODBC Library error

Error Description:   This error can occur because of one of the following reasons:

  • Connection with SQL server lost.
  • Meta information for database not available.
  • Not enough permission to access SQL server.

Error Solution:   To resolve this error:

  • Check if SQL server instance is up and running.
  • Permissions for local system account enabled as per documentation.

SQL8

Error Message:  VDILIB application error

Error Description: This error can occur because of one of the following reasons:

  • Local network connection disabled
  • Unable to create virtual connection with SQL server
  • Not enough permissions to access SQL server
  • The point-in-time or transaction mark restore of the database fails when log chain for database breaks due to  changed/replaced data files.

Error Solution:  To resolve this issue:

  • Wait for next log backup
  • Permissions for local system account enabled as per documentation.

SQL9

Error Message:  SQL Agent internal error occurred

Error Solution:   Contact Druva Support.

SQL10

Error Message:  Insufficient transaction logs to restore marked transaction

Error Description:  This error can occur because of:

  • Broken transaction log chain.

SQL11

Error Message:  Invalid time-stamp for point in time restore

Error Description:  This error can occur because of:

  • Provided timestamp for database is not valid

Error Solution:   To resolve this issue:

  • Try some other point in time restore

SQL12

Error Message:  Database is not compatible on a for target SQL server. Please check version compatibility level. 

Error Description:   This error can occur because of:

  • SQL Server restore instance is incompatible.

Error Solution:  To resolve this issue:

  • Try to restore your database on a compatible SQL server instance.

                                                      See ALTER DATABASE Compatibility level

Note: This issue is not applicable on SQL server agent 4.6.5 and earlier. 

  • Was this article helpful?