Wednesday, November 26, 2014

PROCESS and DISCARD folders are not accessile by Oracle Workflow mailer



Even after creating the PROCESS and DISCARD folders under the dedicated email account, we were getting the error as "The FOLDER DOES NOT EXIST for THE NOMINATED MAIL ACCOUNT"


Solution:


i) Login into MAIL SERVER IMAP using the telnet

telnet abc.mailer.com 143

Connected to abc.mailer.com
Escape character is '^]'.


ii) Login into IMAP server using the dedicated account created for the Oracle Workflow Mailer using the login command. (1 i.e. a number before the command is mandatory for all IMAP commands )

1 login <IMAP Account> <IMAP Account password>
1 OK LOGIN completed

iii) List all the folders under this account:

1 list "" "*"

The output will show the children and parent directories available for this account and all the folder information displayed in this command output is case sensitive.

In my case the PROCESS and DISCARD folders created at user level are created under the PARENT INBOX i.e. INBOX.PROCESS and INBOX.DISCARD.


Use the same listed folder names for configuring the workflow mailer to resolve the above error.




adopmnctl.sh: exiting with status 2



   After a brief OS update when we started the Oracle Apps Services, opmn services were stalled and it was ending with the following error for OACORE,FORMS,OAFM and FORMS-C4WS.

OPMN Services are failed to start with the error:
Starting Apache...
Apache started successfully.


Starting OACORE oc4j...
EXIT CODE is 2. Please check the log file for more details.


Starting FORMS oc4j...
EXIT CODE is 2. Please check the log file for more details.


Starting OAFM oc4j...
EXIT CODE is 2. Please check the log file for more details.


Starting FORMS-C4WS oc4j...
EXIT CODE is 2. Please check the log file for more details.



adopmnctl.sh: exiting with status 2


There is no entry in any of the log file even after enabled the logging and restarting the services.

Solution:

The Problem was due to the changes made automatically in /etc/hosts file.

Just need to correct the entries of your application server  host to IP details and restart the services. This will clear the error.