Data Consistency Check for Statement QBM_PCustomSQLFill (4378441)

When running a Database Consistency Check, the following error is logged:

Error running statement: 
exec QBM_PCustomSQLFill 

exec QBM_PCustomSQLCompile
Database error 50000: re-throw in Procedure QBM_PExecuteSQLWithRetry_LLP, Line 21
Database error 50000: re-throw in Procedure QBM_PExecuteSQLWithRetry_LLP, Line 13
Database error 50000: re-throw in Procedure QBM_PViewDrop, Line 14
Database error 3930: detected in (SRV=[server], DB=[database]) Direct SQL cmd, Line 1
Code starting with: 
drop view if exists "OneIM_UserStatusll"
Database error 3930: The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.--------------------
Error 50000 [sampleObject](V) 50000	0	re-throw in Procedure QBM_PExecuteSQLWithRetry_LLP, Line 21
Database error 50000: re-throw in Procedure QBM_PExecuteSQLWithRetry_LLP, Line 13
Database error 2714: detected in (SRV=[server], DB=[database]) Procedure [sampleObject], Line 1
Database error 2714: There is already an object named '[sampleObject]' in the database.

Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.
Uncommittable transaction is detected at the end of the batch. The transaction is rolled back.

This is due to multiple rows in the QBMCustomSQL table that both try to create a view with the same name, [sampleObject].

To resolve this error, a decision must be made on which of the two QBMCustomSQL entries to keep.