In my current scenario I am inserting data to Teradata table. As per the requirement if due to some issue if transaction fails I have to notify admin using email and suspend message for resuming.
I am receiving a message
Making a connection to Teradata to check if db is up or not. If it downs I am shooting mail from exception block.
Then I am opening new scope and inserting data into Teradata.
In order to test scenario at the beginning I am updating wrong connection string in SSO. So that it fails in first scope and I will get mail. This part is working file.
After that I am again updating my SSO with correct connection string and restarting the host instance. But when I am resuming my orchestration instance, it is going into Active state.
Also there is no other instance running on the server, so there is no issue in opening new connection with db.
Can any one suggest me what could be the issue.