Core Workflow - EBS (MOSC)

MOSC Banner

Workflow does't start after in new cloned enviornment

edited Nov 21, 2013 5:27AM in Core Workflow - EBS (MOSC) 6 commentsAnswered ✓
Hello:

We Cloned our QA environment all the cloning scripts completed OK but the following Workflow Service are down.  I cleaned up the FND_NODE table and run the autoconfig and completed OK and regenerate the JAVA with force option.

The issue is critical for us and I appreciated if you can shed some light on this issue.

-Workflow Agent Listener Service
-Workflow Mailer Service
-Workflow Document Web Services Service

I ran wfver.sql and I noticed that the output is point to wrong (source) environment and not pointing to QA environment.   I checked and verified the AF_CLASSPATH in context file its point to the correct QA environment and I am wondering from where it's picking up the following source information.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS Workflow Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center