Thanks for your response Regina. Looks like its an issue at the database layer which was fixed. We are still trying to communicate with them about the exact fix which is sometimes hard to get quickly. i will update this thread as soon as I get an answer on this from our DBA.
Thanks,
Tsar