This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Corruption in APM_ApplicationTemplate table.

stevenstadel over 4 years ago

After our last upgrade we are seeing corruption on the SQL table APM_ApplicationTemplate.

DBCC CHECKTABLE (Orion.dbo.APM_ApplicationTemplate) found 173 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 14 seconds. Internal database snapshot has split point LSN = 02832433:0002c030:000e and first LSN = 02832429:0000cc87:0002.

We can't run a repair without putting the database into single user mode which means taking an outage.

Since this issue appeared after our latest upgrade what is the consequence for restoring the table from before the upgrade? We can restore the table from before the last upgrade which will give us all the templates that we had before except for the ones that were added with the last SAM version. This in itself is not a problem as we can backup all of the new templates and re-import and re-apply them. The one main issue I see is the AppInsight for Active Directory that was introduced in the last upgrade.

We are not able to backup the AppInsight for Active Directory though the GUI. What is the best way to restore the table and then get this feature added back in?

Your thoughts are appreciated.

Top Replies

Parents

0 serena over 4 years ago

Hi Steve,
Just following up here - our team looked into reported corruption cases and the underlying cause was identified as a MS SQL issue. The linked workaround suggests that this is addressed by applying the latest cumulative updates to your SQL server.
https://support.microsoft.com/en-ca/help/3213240/fix-changing-the-data-type-and-then-updating-the-table-with-more-than
Cancel
Vote Up 0 Vote Down

Cancel
0 stevenstadel over 4 years ago in reply to serena

Hello Serena,
Our DBAs did see this KB as well. It didn't apply in our case because we were already beyond the CU level mentioned and the APM_ApplicationTemplate Table only had 850 records in it, less than the > 4000 mentioned in the article.
For testing purposes, we did set up an environment with absolute latest SQL 2016 SP2 CU 10, loaded the Orion environment from before the upgrade, and still had the corruption.
Cancel
Vote Up +1 Vote Down

Cancel

Reply

0 stevenstadel over 4 years ago in reply to serena

Hello Serena,
Our DBAs did see this KB as well. It didn't apply in our case because we were already beyond the CU level mentioned and the APM_ApplicationTemplate Table only had 850 records in it, less than the > 4000 mentioned in the article.
For testing purposes, we did set up an environment with absolute latest SQL 2016 SP2 CU 10, loaded the Orion environment from before the upgrade, and still had the corruption.
Cancel
Vote Up +1 Vote Down

Cancel

Children

0 serena over 4 years ago in reply to stevenstadel

stevenstadel wrote:
Hello Serena,
Our DBAs did see this KB as well. It didn't apply in our case because we were already beyond the CU level mentioned and the APM_ApplicationTemplate Table only had 850 records in it, less than the > 4000 mentioned in the article.
For testing purposes, we did set up an environment with absolute latest SQL 2016 SP2 CU 10, loaded the Orion environment from before the upgrade, and still had the corruption.

One other suggestion from the team is that if you still have this corruption present on your test environment run the following:

exec sp_tableoption 'dbo.APM_ExternalSetting', 'large value types out of row', '1'

exec sp_tableoption 'dbo.APM_ApplicationTemplate', 'large value types out of row', '1'

exec sp_tableoption 'dbo.APM_ComponentDefinition', 'large value types out of row', '1'

0 stevenstadel over 4 years ago in reply to serena

Thank you for the update! We have blown away that environment, unfortunately.
One suggestion I have is to add in a DBCC CHECKTable against the whole database as part of an upgrade process to identify potential issues before a sign off that the upgrade was successful. We will be adding this to our upgrades moving forward. Not sure of the ramifications of adding it to the wizard (It can take some time depending on the DB size) but thought I'd make the suggestion.
Cancel
Vote Up +3 Vote Down

Cancel