IT33748: ENABLING LOG BACKUP FOR MICROSOFT SQL FAILS WITH MESSAGES CTGGE1046, CTGGA1951, CTGGA2296

APAR status

• Closed as program error.

Error description

• The log backup enabling stops with the following messages seen
  in the job log :
  
  
  ERROR,,<timestamp>,2,CTGGE1046,[<MSSQLServerIP>] Last
  transaction log backup for [<DBName>] on [<MSSQLInstanceName>]
  occurred at <timestamp of last log> and failed.
  
  WARN,,<timestamp>,2,CTGGA1951,[<MSSQLServerIP>] Enable log
  backup status was reported as failed: null
  
  ERROR,,<timestamp>,2,CTGGA2296,Enable log backup failed for
  database <DBName>:Last run for database [<DBName>] failed.
  
  In
  the job log bundle, the command.log file will give more details
  :
  
  [<timestamp>] Debug 604 Thread-1 agent_sql_log: Executing
  Query lsn command SELECT TOP 1 first_lsn, last_lsn FROM
  msdb.dbo.backupset WHERE DESCRIPTION = N'[<DBName>] transaction
  log backup at [<timestamp of last log>] for SLA policy
  [<SLAName>]' ORDER BY last_lsn DESC
  [<timestamp>] Debug 604
  Thread-1 agent_sql_log: Exception encountered when attempting
  to repeat an operation (0/3)
  ...
  [<timestamp>] Error 604
  Thread-1 agent_sql_log: <CTGGE1062> Failed to query the LSN
  record data for database [<DBName>] on instance
  [<MSSQLInstanceName>].
   The following error occurred [An
  exception occurred while executing a Transact-SQL statement or
  batch.].
  		 Discontinuity checks for this database will not
  work until this issue is resolved.
  [<timestamp>] Debug 604
  Thread-1 agent_sql_log: Full transaction log backup error:
   Micr
  osoft.SqlServer.Management.Common.ExecutionFailureException:
  
  An exception occurred while executing a Transact-SQL statement
  or batch.
  		 ---> System.Data.SqlClient.SqlException: Invalid
  column name 'DESCRIPTION'.
   at Microsoft.SqlServer.Management.Co
  mmon.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action,
  Object execObject, DataSet fillDataSet, Boolean
  catchException)
   at Microsoft.SqlServer.Management.Common.Server
  Connection.ExecuteWithResults(String sqlCommand)
   --- End of
  inner exception stack trace ---
   at
  SqlLogBackup.Utils.RetryOperation(Action`2 a, Int32
  repetitions, Int32 delay)
   at
  SqlLogBackup.SqlController.BackupVdiLog(DatabaseInstanceEx
  database)
  [<timestamp>] Error 604 Thread-1 agent_sql_log:
  <CTGGE1061> Failed to update LSN record data for database
  [<DBName>] on instance [<MSSQLInstanceName>],
   error [Column
  'first_lsn' does not belong to table Table.].
  		 Discontinuity
  checks for this database will not work until this issue is
  resolved.
  [<timestamp>] Error 604 Thread-1 agent_sql_log:
  <CTGGE1052> Log backup failed for database [<DBName>] on
  instance [<MSSQLInstanceName>]. Error: 0x80131500
  
  This problem
  is observed because of the Microsoft SQL collation
  feature.
  Collations in SQL Server provide sorting rules, case,
  and accent sensitivity properties for the data.
  In the above
  example, casing sensitivity is active.
  The column name on the
  SQL server is defined in lowercase : 'description' but the
  query uses uppercase letters : 'DESCRIPTION'.
  That caused the
  "Invalid column name 'DESCRIPTION'" error.
  
  IBM Spectrum
  Protect Plus Versions Affected:
  IBM Spectrum Protect Plus
  10.1.x
  
  Initial Impact: Medium
  
  Additional Keywords: SPP,
  SPPLUS, TS003881567, invalid
  

Local fix

• Set the SQL Server or the msdb system database to use a case
  insensitive collation.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus level 10.1.5 and 10.1.6            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in 10.1.7. Note that this is subject   *
  * to change at the discretion of IBM                           *
  ****************************************************************
  

Problem conclusion

• Made a change to a SQL query to match the column name even with
  case sensitivity
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels