Wednesday, October 22, 2014

A call to flushChanges on the current MDSSession does not specify the correct transaction key

Interesting issue in a SOA/BPM today.
Redeployment of the application (SOA) and restart went through without an issue.

However the stresstest came back almost immediately. The AdminServer.out showed the error "A call to flushChanges on the current MDSSession does not specify the correct transaction key". Even more astonishing was the error TNS-12516 when trying to connect to the database.

After a little bit of searching we found that the database alert log said it could not extend the SOA_INFRA tablespace.

Adapted this and everything went back to normal.

4 comments:

O记 - Wei Peng said...

I have the same problem, could you give me a details about how to fix this issue and why occur that problem ?
I don't find SOA_INFRA tablespace in my DB.

Thanks
Peter.Peng

Karthikeyasiva Prasad said...

hi,iam also facing the same issue can you please suggest me to solve this....

Pathri said...

Hi,

i am also facing the same issues,
Please suggest me what to do,
if you guys got the solution for this same problem.

Thanks

குழலி said...

Please explain the resolution to fix this issue. we are also facing the same issue.