Hi Muni,
We also faced the similar issue when our PI System's DB and OS got changed.
Workaround that we used was to manually select the adapter engine for the iFlow and then activate and deploy.
One reason for this behavior might be the change in Adapter engine after you changed the underlying Database.
Try this workaround and and suggest if it works or not.
Regards
Vj