Skip to main content

Anybody had this error on the sync monitor in mWorkOrder?

 

DB_SWITCH_SESSION:Could not switch database proxy session to user username]

 

Apparently the user’s account got locked prior to sending new transactions to IFS.  Since then we have unlocked the account but we are still getting this error on the user’s sync monitor.  Looking at the Sync Traces, data from IFS to mobile are working, but we have over 200+ queued transactions waiting to be sent from Mobile to IFS.  We have run the query to check if they have the IFSSYS proxy user setup and they do.  Any ideas for this error in mobile?  Idle time on the Oracle profile is unlimited too.

 

 

Anybody had this error on the sync monitor in mWorkOrder?

 

DB_SWITCH_SESSION:Could not switch database proxy session to user username]

 

Apparently the user’s account got locked prior to sending new transactions to IFS.  Since then we have unlocked the account but we are still getting this error on the user’s sync monitor.  Looking at the Sync Traces, data from IFS to mobile are working, but we have over 200+ queued transactions waiting to be sent from Mobile to IFS.  We have run the query to check if they have the IFSSYS proxy user setup and they do.  Any ideas for this error in mobile?  Idle time on the Oracle profile is unlimited too.

 

 

Can you check the Oracle Profile Idle Time parameter value? It should always be set to UNLIMITED.
 

The connection pool needs to be restarted after you’ve changed the profile.

 

Actually found another thread for it now, luckily we had the same advice :) 

 

https://community.ifs.com/technology-infrastructure-cloud-integration-dev-tools-50/db-switch-session-could-not-switch-database-proxy-session-to-user-username-240

Actually found another thread for it now, luckily we had the same advice :) 

 

https://community.ifs.com/technology-infrastructure-cloud-integration-dev-tools-50/db-switch-session-could-not-switch-database-proxy-session-to-user-username-240

My Oracle profile was already on unlimited for idle time.  We’ve done no changes to this.

Found that if you resend the transaction from mobile, the error gets resolved.  Just ensure the account is unlocked before resending from mobile.

Reply


Terms & ConditionsCookie settings