Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

JobExecutionException: Activity execution failed



Post Pega 8.1 upgrade, the Command Line Business Intelligence Exchange (BIX) extract does not run.

Error Messages

Warning message in the BIX log: 
Node state has not been captured for the db name your_target_DB as db

[sshexec] [CHEDULER_THREAD_POOL] [STANDARD] [ ] [ ] (JobScheduler) ERROR   - Exception in executing Job[pyPersistNodeState]
  [sshexec] com.pega.platform.executor.jobscheduler.scheduler.JobExecutionException: Activity execution failed with [User marked activity execution to failed with message [ There is no configuration (no Data-Admin-DB-Name instance) for database your_target_DB]]
  [sshexec]     at com.pega.platform.executor.jobscheduler.internal.JobSchedulerProcessor.execute( ~[pega-executor.jar:?]
  [sshexec]     at com.pega.platform.executor.jobscheduler.scheduler.internal.JobRunTimeImpl.execute( ~[executor.jar:?]
  [sshexec]     at com.pega.platform.executor.jobscheduler.scheduler.internal.JobRunTimeDecorator.execute( ~[executor.jar:?]
  [sshexec]     at com.pega.platform.executor.jobscheduler.scheduler.internal.JobExecutionTemplate.executeJob( ~[executor.jar:?]
  [sshexec]     at ~[executor.jar:?]
  [sshexec]     at java.util.concurrent.Executors$ ~[?:1.8.0_171]
  [sshexec]     at ~[?:1.8.0_171]
  [sshexec]     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201( ~[?:1.8.0_171]
  [sshexec]     at java.util.concurrent.ScheduledThreadPoolExecutor$ ~[?:1.8.0_171]
  [sshexec]     at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:1.8.0_171]
  [sshexec]     at java.util.concurrent.ThreadPoolExecutor$ [?:1.8.0_171]
  [sshexec]     at [?:1.8.0_171]
  [sshexec] Caused by: com.pega.platform.executor.jobscheduler.scheduler.JobExecutionException: User marked activity execution to failed with message [ There is no configuration (no Data-Admin-DB-Name instance) for database your_target_DB]
  [sshexec]     at com.pega.platform.executor.jobscheduler.internal.JobSchedulerProcessor.identifyUserMarkedFailure( ~[pega-executor.jar:?]
  [sshexec]     at com.pega.platform.executor.jobscheduler.internal.JobSchedulerProcessor.execute( ~[pega-executor.jar:?]

Steps to Reproduce

  1. Upgrade Pega 7.2 to Pega 8.1.
  2. Use the same BIX setup as Pega 7.2 in Pega 8.1.

Root Cause

A defect or configuration issue in the operating environment.
The BIX Command Line is set up to use the Admin user that could view the Pega 7.2 schema which had your_target_DB Data-Admin-DB-Name configured to use the JDBC URL.
In Pega 8.1, your_target_DB Data-Admin-DB-Name should be set to 'Use configuration in preferences'. Despite configuring your_target_DB Data-Admin-DB-Name to 'Use configuration in preferences', the BIX Command Line Pega engine reads your_target_DB Data-Admin-DB-Name from the Pega 7.2 database schema and hence fails


Perform the following local-change:
  1. Ensure your_target_DB Data-Admin-DB-Name uses the 'Use Configuration in Preferences' option (this also requires updating Pega application's prconfig.xml to reference JNDI data source defined on the application server).
  2. Run the BIX Command Line with a database user (non Admin) that can only view the Pega schemas for Pega 8.1.

Published April 2, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us