Question
NASCO
US
Last activity: 1 Oct 2019 5:01 EDT
BIX 8.2 unable to extract to target database with exception
We run BIX from command line and write it into DB tables. We upgraded from 7.1.8 to 8.2 and we have no issues in our 7.1.8 with the same configuration.
When executing the command we are getting below exception.
We have database instance name with JNDi name mentioned in the rule.
We have target database information in prconfig file.
We were able to load the data when run from designer studio with out issues.
ERROR - Encountered bad Data-Admin-DB-Name definition
com.pega.platform.datastore.ConfigurationException: Data-Admin-DB-Name "PegaBIX" has both a JDBC URL ("jdbc:db2://111.1111.111.11:11111/#######:currentSchema=BIXSTG;fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;progresssiveLocators=2;useJDBC4ColumnNameAndLabelSemantics=2;") and a JNDI-named data source ("jdbc/PegaBIX") specified (either in the instance or in prconfig)
at com.pega.platform.datastore.connection.internal.config.jdbc.JdbcConfigurationFactory.validate(JdbcConfigurationFactory.java:366) ~[datastore.jar:?]
at com.pega.platform.datastore.connection.internal.config.jdbc.JdbcConfigurationFactory.getDataSourceConfiguration(JdbcConfigurationFactory.java:69) ~[datastore.jar:?]
at com.pega.platform.datastore.connection.internal.config.jdbc.JdbcStore.buildConnectionConfiguration(JdbcStore.java:87) ~[datastore.jar:?]
We run BIX from command line and write it into DB tables. We upgraded from 7.1.8 to 8.2 and we have no issues in our 7.1.8 with the same configuration.
When executing the command we are getting below exception.
We have database instance name with JNDi name mentioned in the rule.
We have target database information in prconfig file.
We were able to load the data when run from designer studio with out issues.
ERROR - Encountered bad Data-Admin-DB-Name definition
com.pega.platform.datastore.ConfigurationException: Data-Admin-DB-Name "PegaBIX" has both a JDBC URL ("jdbc:db2://111.1111.111.11:11111/#######:currentSchema=BIXSTG;fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;progresssiveLocators=2;useJDBC4ColumnNameAndLabelSemantics=2;") and a JNDI-named data source ("jdbc/PegaBIX") specified (either in the instance or in prconfig)
at com.pega.platform.datastore.connection.internal.config.jdbc.JdbcConfigurationFactory.validate(JdbcConfigurationFactory.java:366) ~[datastore.jar:?]
at com.pega.platform.datastore.connection.internal.config.jdbc.JdbcConfigurationFactory.getDataSourceConfiguration(JdbcConfigurationFactory.java:69) ~[datastore.jar:?]
at com.pega.platform.datastore.connection.internal.config.jdbc.JdbcStore.buildConnectionConfiguration(JdbcStore.java:87) ~[datastore.jar:?]
at com.pega.platform.logicaldatastore.connection.internal.config.ConfigurationMapImpl.registerDbName(ConfigurationMapImpl.java:198) ~[logicaldatastore.jar:?]
at com.pega.platform.logicaldatastore.connection.internal.config.ConfigurationMapImpl.registerDbName(ConfigurationMapImpl.java:140) ~[logicaldatastore.jar:?]
at com.pega.platform.logicaldatastore.connection.internal.config.ConfigurationMapImpl.initializeSetOfDbNames(ConfigurationMapImpl.java:129) ~[logicaldatastore.jar:?]
at com.pega.pegarules.data.internal.store.ConnectionBrokerAdapter.initializeConfigurationMaps(ConnectionBrokerAdapter.java:202) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.store.ConnectionBrokerAdapter.initializeConfigurationMaps(ConnectionBrokerAdapter.java:193) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.PRDataProviderImpl.getConnectionBroker(PRDataProviderImpl.java:743) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.PRDataProviderImpl.getConnectionManager(PRDataProviderImpl.java:710) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.PRDataProviderImpl.isMultiTenantEnvironment(PRDataProviderImpl.java:1381) ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.archive.ParUtilsImpl.setStageDirectory(ParUtilsImpl.java:215) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:526) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:172) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:145) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.EngineImpl.startEngineImpl(EngineImpl.java:249) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.EngineImpl.startEngine(EngineImpl.java:125) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.EngineImpl.startEngine(EngineImpl.java:111) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.ExtractImpl.main(ExtractImpl.java:759) ~[prprivate.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) ~[?:1.8.0]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) ~[?:1.8.0]
at java.lang.reflect.Method.invoke(Method.java:508) ~[?:1.8.0]
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:381) ~[prbootstrap.jar:8.2.1-225]
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:422) ~[prbootstrap.jar:8.2.1-225]
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224) ~[prbootstrap-api.jar:8.2.1-225]
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:273) ~[prbootstrap-api.jar:8.2.1-225]
at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85) ~[prbootstrap-api.jar:8.2.1-225]
***Moderator Edit-Vidyaranjan: Updated SR details***
Accepted Solution
Pegasystems Inc.
IN
Hi Aravind,
Please change the Data-Admin-DB-Name to have the “How to connect” option to be “use configuration in preferences”. Resolved with SR-D43989.
Thanks
Pegasystems Inc.
IN
Hi Aravind,
Are you getting successful connection message when you do a test connectivity for this external DB?
Please check if it is a different DB, then if you have deployed the jdbc jar of this external DB in you application server or not.
Regards,
Vikash
NASCO
US
Hi Vikash,
We are extracting the DATA to a separate reporting DB and this is not external DB.
When we do a test connectivity from DB instance rule it gives success message and it extracts data when we run from designer studio
But we have this issue for running from command line.
Regards
Aravind
Accepted Solution
Pegasystems Inc.
IN
Hi Aravind,
Please change the Data-Admin-DB-Name to have the “How to connect” option to be “use configuration in preferences”. Resolved with SR-D43989.
Thanks
Pegasystems Inc.
IN
As per SR-D43989,The root cause of this issue is conflict with the JNDI configuration in the prconfig.xml as well as in the Data-Admin-DB-Name instance. It got resolved by changing Data-Admin-DB-Name to have the “How to connect” option to be “use configuration in preferences”
Thanks,
Abhinav