@Priyesh

I looked into your suggestion but found that we are getting this issue over a couple of Custom Indexes that were defined over a Subject that were not registered into the console which was the main root cause. Currently we've dropped them and are looking into it to resolve the issue permanently.

Thanks,

Ranadeep

Hi,

I'm not running Metadata Validation process while other batches are running and am using MS Sql Server as my DB.

Hi Sriharsha,

these Custom Indexes were created on a XREF Table which are getting dropped whenever we are publishing other changes to HUB. Is there a chance we can register them on a  XREF Table which can help us getting away from this Issue.

Thanks,

Rana

Hi Everyone,

Thank you all for chiming in. We were able to deploy Custom Indices successfully over an XREF Table using SIF API Call as mentioned in KB Article (144917 ) instead of creating and deploying the Index with a Store Proc We've used following SIF API SOAP XML Call

SOAP XML

 

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:siperian.api">

 

 

   <soapenv:Header/>

 

 

   <soapenv:Body>

 

 

      <urn:registerCustomIndex>

 

 

         <!--Optional:-->

 

 

         <urn:username>admin</urn:username>

 

 

         <!--Optional:-->

 

 

         <urn:password>

 

 

            <urn:password>admin</urn:password>

 

 

            <urn:encrypted>false</urn:encrypted>

 

 

         </urn:password>

 

 

         <urn:orsId>localhost-orcl-MDM_SAMPLE</urn:orsId>

 

 

         <urn:tableName>C_PARTY_XREF</urn:tableName>

 

 

         <urn:rowidColList>SVR1.IS1~SVR1.IWG</urn:rowidColList> <!-- multiple columns separated by tilda -->

 

 

         <urn:indexType>NI</urn:indexType>

 

 

      </urn:registerCustomIndex>

 

 

   </soapenv:Body>

 

 

</soapenv:Envelope>

 

and then followed next steps as listed in article 144917. As a safety feature we've cleared up the cache to make sure we don't end up with errors which worked for us.