Support Article
JobExecutionException: Activity execution failed
SA-76405
Summary
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(JobSchedulerProcessor.java:54) ~[pega-executor.jar:?]
[sshexec] at com.pega.platform.executor.jobscheduler.scheduler.internal.JobRunTimeImpl.execute(JobRunTimeImpl.java:67) ~[executor.jar:?]
[sshexec] at com.pega.platform.executor.jobscheduler.scheduler.internal.JobRunTimeDecorator.execute(JobRunTimeDecorator.java:57) ~[executor.jar:?]
[sshexec] at com.pega.platform.executor.jobscheduler.scheduler.internal.JobExecutionTemplate.executeJob(JobExecutionTemplate.java:45) ~[executor.jar:?]
[sshexec] at com.pega.platform.executor.jobscheduler.scheduler.internal.JobExecutionTemplate.run(JobExecutionTemplate.java:35) ~[executor.jar:?]
[sshexec] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_171]
[sshexec] at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_171]
[sshexec] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[?:1.8.0_171]
[sshexec] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[?:1.8.0_171]
[sshexec] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_171]
[sshexec] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_171]
[sshexec] at java.lang.Thread.run(Thread.java:748) [?: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(JobSchedulerProcessor.java:68) ~[pega-executor.jar:?]
[sshexec] at com.pega.platform.executor.jobscheduler.internal.JobSchedulerProcessor.execute(JobSchedulerProcessor.java:51) ~[pega-executor.jar:?]
Steps to Reproduce
- Upgrade Pega 7.2 to Pega 8.1.
- 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.
Resolution
Perform the following local-change:
- 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).
- 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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.