I keep getting the following error, whenever I execute any
transaction batch job in CG 22.214.171.124 running in zOS WAS 126.96.36.199. All those
applications run perfectly well in zOS WAS 188.8.131.52 though :
"PMGR1012E: The current backend id DB2UDBNT_V82_1, does not match the data source connected to."
I have set the backend id in the ejbdeploy command using the
attribute "-dbvendor DB2UDBOS390_V9" ( our LREE DB is DB2 v9.1 in zOS ). When I check the resulting ear file, the file ibm-ejb-jar-bnd.xmi contains "currentBackendId="DB2UDBOS390_V9_1", which is at it
So, my question is: Where is the backend id DB2UDBNT_V82_1 coming from ?
I have attached the joblog and the ear file.
Any help, suggestions will be much appreciated.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
3 replies Latest Post - 2012-07-20T14:32:01Z by SystemAdmin
Pinned topic Backend Id problem in zOS WAS 7
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-07-20T14:32:01Z at 2012-07-20T14:32:01Z by SystemAdmin
Re: Backend Id problem in zOS WAS 72010-04-19T16:57:21Z in response to SystemAdminJay,
The problem most likely is not with your app, but rather, with the endpoint system app, GEE. The datasource jndi name for the endpoint is set in the admin console on page: Job Scheduler > WebSphere Endpoints. For the datasource/endpoint mapping to work, the datasource must be accessible to the dmgr. You can confirm this by using the "Test Connection" feature in the admin console for that datasource. The reason this matters is because the dmgr must connect to the datasource in order to dynamically obtain its backendid. This backendid is then used to configured the endpoint's GEE app. Default is Derby, which is what you're getting. You should be able to resolve this by taking the following steps:
- Ensure endpoint datasource is accessible from the admin console ("Test Connection" must work successfully).
- Reassign endpoint datasource (Job Scheduler > WebSphere Endpoints).
- Save&sync config.
- Restart WCG endpoint server(s).
- Rerun batch job to verify error is gone.
Re: Backend Id problem in zOS WAS 72012-07-20T14:32:01Z in response to SystemAdminIN MY CASE i don't have an endspoint i use server standalone in windows
what can i do?
this is my error
com.ibm.ws.exception.WsEJBException: nested exception is: com.ibm.ws.ejbpersistence.utilpm.PersistenceManagerException: PMGR1012E: The current backend id ORACLE_V10_1, does not match the data source connected to