The bug is not marked as a regression so although reported for 10.2HF1, it is very likely it also existed in 10.2.0 so I'd suggest trying the workaround.
Yes, that is correct and the solution worked.
Actually, this was happening for higher env. on which we do not have permission. So, do not have the luxury of test and try solutions, of course for the right reasons.
But then facing another issue when testing the cleanse in MDM. This cleanse has a target table, and it worked fine in lower env, lsitner was not given the SERVICE_NAME in CONNECT_DATA
Appreciate your help!
It has been resolved. The DB connection created between IDQ server and the MDM application was not working when testing the cleanse. Once the connection was up and running the testing got successful.