Delphix Products

We have upgraded the Delphix Continuous Compliance from version 6.0.13 to version to 6.0.24 in our Lab. It is fresh setup on the new infrastructure and now we are migrating the objects from old Delphix engine to new one.

While migrating the environments from old engine to new engine we are facing the below error - "All references to the legacy algorithm 'TelephoneNoLookup' must be updated to an algorithm of type COMPONENT, as this algorithm not available. This includes indirect references that occur when 'TelephoneNoLookup' is the default algorithm for one or more domains. It is no longer possible to import environments that reference this algorithm via engine sync."}.

We tried to remove the domain from profile sets which were using the same algorithm but still environment migration is failing. Any suggestion on this will be helpful. We do not want to loose the current configuration of the objects in new engine.  

Thanks.

We have upgraded the Delphix Continuous Compliance from version 6.0.13 to version to 6.0.24 in our Lab. It is fresh setup on the new infrastructure and now we are migrating the objects from old Delphix engine to new one.

While migrating the environments from old engine to new engine we are facing the below error - "All references to the legacy algorithm 'TelephoneNoLookup' must be updated to an algorithm of type COMPONENT, as this algorithm not available. This includes indirect references that occur when 'TelephoneNoLookup' is the default algorithm for one or more domains. It is no longer possible to import environments that reference this algorithm via engine sync."}.

We tried to remove the domain from profile sets which were using the same algorithm but still environment migration is failing. Any suggestion on this will be helpful. We do not want to loose the current configuration of the objects in new engine.  

Thanks.

The reason you get those warnings is that in version 6.0.15 we replaced any LEGACY algorithms with Java SDK based algorithms.
During the upgrade to 6.0.15 old legacy algorithms got converted to SDK based algorithms. So you have two options:

1) upgrade "old" engine to 6.0.15 and export algorithms again > you should get only SDK algorithms (type=COMPONENT).
You should be able to import into v24 successfully.
(the version is called 24 > not  6.0.24, after version 6.0.17 Delphix switched to single number versioning > 7 )

2) when you export algorithms from old engine exclude the ones where type=LEGACY.  Then you should be able to import into v24.

We have upgraded the Delphix Continuous Compliance from version 6.0.13 to version to 6.0.24 in our Lab. It is fresh setup on the new infrastructure and now we are migrating the objects from old Delphix engine to new one.

While migrating the environments from old engine to new engine we are facing the below error - "All references to the legacy algorithm 'TelephoneNoLookup' must be updated to an algorithm of type COMPONENT, as this algorithm not available. This includes indirect references that occur when 'TelephoneNoLookup' is the default algorithm for one or more domains. It is no longer possible to import environments that reference this algorithm via engine sync."}.

We tried to remove the domain from profile sets which were using the same algorithm but still environment migration is failing. Any suggestion on this will be helpful. We do not want to loose the current configuration of the objects in new engine.  

Thanks.

Thanks Rahim and Tino for your responses. A one suggestion that we tried is removing the reference to the algorithm manually in environment export file. Example- 

{

      "objectIdentifier" : {

        "id" : "TELEPHONE_NO"

      },

      "objectType" : "DOMAIN_REFERENCE",

      "revisionHash" : "de84bc0c24435cb289660bac666aeef4b9c33d41"

    },

{

      "objectIdentifier" : {

        "algorithmName" : "TelephoneNoLookup"

      },

      "objectType" : "ALGORITHM_REFERENCE",

      "revisionHash" : "98ed0b91036b2f7bcb67dc536b6c15497df6237b"

    },

We removed the references for algorithm as highlighted and tried the environment migration. Migration got through but we do not see any other objects created under the migrated environment in new engine. I have attached a sample environment export for a reference.

The reason you get those warnings is that in version 6.0.15 we replaced any LEGACY algorithms with Java SDK based algorithms.
During the upgrade to 6.0.15 old legacy algorithms got converted to SDK based algorithms. So you have two options:

1) upgrade "old" engine to 6.0.15 and export algorithms again > you should get only SDK algorithms (type=COMPONENT).
You should be able to import into v24 successfully.
(the version is called 24 > not  6.0.24, after version 6.0.17 Delphix switched to single number versioning > 7 )

2) when you export algorithms from old engine exclude the ones where type=LEGACY.  Then you should be able to import into v24.

We have upgraded the Delphix Continuous Compliance from version 6.0.13 to version to 6.0.24 in our Lab. It is fresh setup on the new infrastructure and now we are migrating the objects from old Delphix engine to new one.

While migrating the environments from old engine to new engine we are facing the below error - "All references to the legacy algorithm 'TelephoneNoLookup' must be updated to an algorithm of type COMPONENT, as this algorithm not available. This includes indirect references that occur when 'TelephoneNoLookup' is the default algorithm for one or more domains. It is no longer possible to import environments that reference this algorithm via engine sync."}.

We tried to remove the domain from profile sets which were using the same algorithm but still environment migration is failing. Any suggestion on this will be helpful. We do not want to loose the current configuration of the objects in new engine.  

Thanks.

Thanks Rahim and Tino for your responses. A one suggestion that we tried is removing the reference to the algorithm manually in environment export file. Example- 

{

      "objectIdentifier" : {

        "id" : "TELEPHONE_NO"

      },

      "objectType" : "DOMAIN_REFERENCE",

      "revisionHash" : "de84bc0c24435cb289660bac666aeef4b9c33d41"

    },

{

      "objectIdentifier" : {

        "algorithmName" : "TelephoneNoLookup"

      },

      "objectType" : "ALGORITHM_REFERENCE",

      "revisionHash" : "98ed0b91036b2f7bcb67dc536b6c15497df6237b"

    },

We removed the references for algorithm as highlighted and tried the environment migration. Migration got through but we do not see any other objects created under the migrated environment in new engine. I have attached a sample environment export for a reference.

The reason you get those warnings is that in version 6.0.15 we replaced any LEGACY algorithms with Java SDK based algorithms.
During the upgrade to 6.0.15 old legacy algorithms got converted to SDK based algorithms. So you have two options:

1) upgrade "old" engine to 6.0.15 and export algorithms again > you should get only SDK algorithms (type=COMPONENT).
You should be able to import into v24 successfully.
(the version is called 24 > not  6.0.24, after version 6.0.17 Delphix switched to single number versioning > 7 )

2) when you export algorithms from old engine exclude the ones where type=LEGACY.  Then you should be able to import into v24.

We have upgraded the Delphix Continuous Compliance from version 6.0.13 to version to 6.0.24 in our Lab. It is fresh setup on the new infrastructure and now we are migrating the objects from old Delphix engine to new one.

While migrating the environments from old engine to new engine we are facing the below error - "All references to the legacy algorithm 'TelephoneNoLookup' must be updated to an algorithm of type COMPONENT, as this algorithm not available. This includes indirect references that occur when 'TelephoneNoLookup' is the default algorithm for one or more domains. It is no longer possible to import environments that reference this algorithm via engine sync."}.

We tried to remove the domain from profile sets which were using the same algorithm but still environment migration is failing. Any suggestion on this will be helpful. We do not want to loose the current configuration of the objects in new engine.  

Thanks.