What do you do with skipped updates of type 'Indexes'?

[LiamC]

Hi All,

We have just upgraded one of our Sub-prod instances to Vancouver.

Whilst doing the skipped record review I have seen multiple skipped records of type 'Indexes'.

**screenshot attached

I am unable to use the Resolve Conflicts tool, as I get the error message:

"Unable to compare, unable to find a current record"

Does anyone have experience with dealing with these?

Is there any danger to consider if we were to 'revert to baseline' for each of these?

Thanks,

Liam

[LiamC · Accepted solution]

Hi Ashby, 

I ended up raising this with NowSupport who reviewed the files and advised they could be marked as 'reviewed' and safely ignored.

NowSupport resolution
==============
Most Probable Cause: Since the file does not exist in the system, this records can be ignored.

Solution Proposed: Please find the local host logs that explains that Current version doesn't exist in your system.

2023-10-02 08:11:22 (056) worker.2 worker.2 txid=0593c60ff990 WARNING *** WARNING *** SkipResolver:: Current version doesn't exist for sysId-026ebd8397a531104fe63a1f2153af16

2023-10-02 08:11:22 (921) worker.2 worker.2 txid=0593c60ff990 WARNING *** WARNING *** SkipResolver:: Current version doesn't exist for sysId-4e6ebd8397a531104fe63a1f2153af12

You can simply mark the resolution state as reviewed and ignore these skipped records.

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

Best Regards,

Liam

[Dipu Joy]

You can ignore these if the existing indexes are present on the instance sys_db_object record for table "viz_map_source"

PRB==>  PRB1660056