List of potential SQL errors seen in the 2D Map after improper SQL 2008 upgrade to SQL 2012 and how to overcome/resolve

Document created by sirha02 Employee on Jan 20, 2016Last modified by sirha02 Employee on Jan 21, 2016
Version 3Show Document
  • View in full screen mode

Please find below the list of potential errors to be found in the 2D Map after the NSM MDB has been upgraded from SQL 2008 to SQL 2012 as a result of the MDB Migration procedure not being followed correctly

 

  1. 2D Map crashing

  2. a lot of objects in Unplaced Objects folder

  3. Unable to delete many objects in the Unplaced Objects folder

  4. **ERROR 53** Repository error when trying to Open Details, ...

  5. "CAE0326: Required parameter IPV6/IPV4 address missing." Error appears when trying to delete the object in the Unplaced Objects folder

  6. New servers discovered are placed in the Unplaced Objects folder

 

To resolve the issue, please perform the below procedure on the SQL 2012 MDB machine:

 

Please note we would be modifying the SQL query here - please take a backup of the existing MDB first before proceeding with the below procedure and revert back the changes if the issue is not resolved

 

Open the SQL Management Studio on the SQL 2012 MDB machine with NSM installed and navigate as below:

  • under Databases select mdb
  • select Tables
  • search for the table dbo.tng_managedobject
  • under dbo.tng_managedobject
  • select Triggers and now double click on tng_tu_managedobject

 

In the SQL query which now opens on the right side, search for the below:

 

 

if( update(severity) or update(status_no))

 

if( ( 1 in (select acknowledge from deleted)) and ( 1 in

 

select acknowledge from inserted)))

 

begin

 

select 80001

 

raiserror 80001 'Update severity or status_no failed Since one of acknowledges is on(1). '

 

rollback transaction

 

return

 

end

 

Now replace the line but remember replace ONLY IF the below line does not contain the parenthesis ( )  from 'Update severity or ... to ...acknowledges is on(1).  ' as observed below:

raiserror 80001 'Update severity or status_no failed Since one of acknowledges is on(1). '

 

 

Replace the above line with:

raiserror ( 'Update severity or status_no failed Since one of acknowledges is on(1). ',80001,1)

 

 

=============

Also search for:

=============

 

 

    if( update(class_name) or update(uuid))

    begin

      select 80002

 

 

    raiserror 80002 'Do not allow to update uuid of an object,

the transaction failed. '

 

    rollback transaction

 

return

 

end

 

Now replace the following line again remember to replace ONLY IF the below line does not contain the parenthesis ( )  from 'Do not allow ... to ...the transaction failed. ' as observed below:


raiserror 80002 'Do not allow to update uuid of an object,

the transaction failed. '

 

Replace the above line with:

raiserror ('Do not allow to update uuid of an object, the transaction failed. ',80002 ,2)

 

 

====================================

Our final query should look like the below:

=====================================

.

.

.

if( update(severity) or update(status_no))

 

if( ( 1 in (select acknowledge from deleted)) and ( 1 in

 

select acknowledge from inserted)))

 

begin

 

select 80001

 

raiserror ( 'Update severity or status_no failed Since one of acknowledges is on(1). ',80001,1)

rollback transaction

 

return

 

end

 

 

( update(class_name) or update(uuid))

 

begin

 

select 80002

 

raiserror ('Do not allow to update uuid of an object, the transaction failed. ',80002 ,2)

rollback transaction

return

end

.

.

.

 

 

Now click on anywhere on the white space in the query screen (this is just to ensure no word is selected/highlighted) and click on the Red Excalamatory execute icon !

 

If you see the below two Message then we are all set:

 

  1. Command(s) completed successfully.
  2. and the message with green tick mark Query executed successfully

 

Now save the query as below:

Click on File > Save SQLQuery.sql (usually under C:\Users\Administrator\Documents\SQL Server Management Studio)

 

Now, close the 2D Map, restart the unicenter and awservices - better to reboot the machine and verify the issue is resolved

 

Note:

  1. The above issue occurs if the MDB Migration was not performed properly
  2. Please revert the changes back if the issue is not resolved

Attachments

    Outcomes