DIAGNOSTICS (UNIX) Use Equivalent Commands for Windows for Java Mailer issues

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem: DIAGNOSTICS (UNIX) Use Equivalent Commands for Windows for Java Mailer issues



Solution:



DIAGNOSTICS (UNIX) Use Equivalent Commands for Windows.
 Please download and run the Java Mailer Diagnotics Test contained in Note: 274764.1

 Please review the "Known Issues for Oracle Workflow Mini-pack 11i.OWF.G" section in Note: 225947.1 andNote: 231286.1

For ORA-24033 Errors:

RDBMS 9.2.0.1 - 9.2.0.3 Customers ONLY:

desc sys.dbms_aqin there should be 3 AQ$_DEQUEUE_IN repeated in it. If there is less than 3 AQ$_DEQUEUE_IN, you need to download and reapply Patch 2805491 which was re-released as a Generic Patch on July 29. Make sure this manual step in the readme is done correctly:

Apply patch 2805491


Patch Special Instructions:
# ---------------------------
# After the patch has been applied please reload the package into
# the database. To do this connect as SYS and execute the following;
#
# SQL> @?/rdbms/admin/prvtaqin.plb
#
# It is recomended that the system should be in a quiescent state.

Apply patch 2757441:

# Patch Special Instructions:
# ---------------------------
# After the patch has been applied please reload the package into
# the database. To do this connect as SYS and execute the following;
#
# SQL> @?/rdbms/admin/prvtreut.plb
#
# It is recomended that the system should be in a quiescent state.

For All Database Versions:

sqlplus apps/apps @$FND_TOP/patch/115/sql/wfmqsubc.sql applsys apps (Adds Subscribers/Recipients)
 Increase Diagnostics:

1. Please change the * Log Level from Exception to Statement on the Workflow Mailer
Configuration page in OAM page 3.

2. Increase Diagnostics Level on Workflow Mailer and Agent Listener Services:

a) Terminate the mailer or agent listener service

b) Edit log level of Mailer or Agent Listener service by:

In OAM Sitemap > Status Overview > View All > Generic Service Component
Container > select Workflow Mailer Service or Workflow Agent Listener Service >
Edit > Edit Service Parameters >

Change from:

SVC_WRITE_DIAG_TO_GSM_LOG=Y:SVC_CONTAINER_LOOP_SLEEP=10:
SVC_CONTAINER_READ_TIMEOUT=10:SVC_CONTAINER_LOG_LEVEL=4:
SVC_COMP_MONITOR_LOOP_SLEEP=60:SVC_COMP_MONITOR_ONDEMAND_FREQ=300:
SVC_COMP_MAX_ERROR_COUNT=5:SVC_PROXY_SET=NONE:
SVC_PROXY_HOST=NONE:SVC_PROXY_PORT=NONE

To:

SVC_WRITE_DIAG_TO_GSM_LOG=Y:SVC_CONTAINER_LOOP_SLEEP=10:
SVC_CONTAINER_READ_TIMEOUT=10:SVC_CONTAINER_LOG_LEVEL=1:
SVC_COMP_MONITOR_LOOP_SLEEP=60:SVC_COMP_MONITOR_ONDEMAND_FREQ=300:
SVC_COMP_MAX_ERROR_COUNT=5:SVC_PROXY_SET=NONE:
SVC_PROXY_HOST=NONE:SVC_PROXY_PORT=NONE

> OK > Save > select Workflow Mailer or Workflow Agent Listener Service > Start
 Return Diagnostics back to Default after uploading log:

1. Please change the * Log Level from Statement to Exception on the Workflow Mailer Configuration
page in OAM page 3.

2. Decrease Diagnostics Level on Workflow Mailer and Agent Listener Services:

a) Terminate the mailer or agent listener service

b) Edit log level of Mailer or Agent Listener service by:

In OAM Sitemap > Status Overview > View All > Generic Service Component Container >
select Workflow Mailer Service or Workflow Agent Listener Service > Edit > Edit Service Parameters >

Change from:

SVC_WRITE_DIAG_TO_GSM_LOG=Y:SVC_CONTAINER_LOOP_SLEEP=10:
SVC_CONTAINER_READ_TIMEOUT=10:SVC_CONTAINER_LOG_LEVEL=1:
SVC_COMP_MONITOR_LOOP_SLEEP=60:SVC_COMP_MONITOR_ONDEMAND_FREQ=300:
SVC_COMP_MAX_ERROR_COUNT=5:SVC_PROXY_SET=NONE:
SVC_PROXY_HOST=NONE:SVC_PROXY_PORT=NONE

To:

SVC_WRITE_DIAG_TO_GSM_LOG=Y:SVC_CONTAINER_LOOP_SLEEP=10:
SVC_CONTAINER_READ_TIMEOUT=10:SVC_CONTAINER_LOG_LEVEL=4:
SVC_COMP_MONITOR_LOOP_SLEEP=60:SVC_COMP_MONITOR_ONDEMAND_FREQ=300:
SVC_COMP_MAX_ERROR_COUNT=5:SVC_PROXY_SET=NONE:
SVC_PROXY_HOST=NONE:SVC_PROXY_PORT=NONE

> OK > Save > select Workflow Mailer or Workflow Agent Listener Service > Start
 Please use ADADMIN to regenerate your jar files using force=y.

Example Errors in your workflow mailer log $APPLCSF/$APPLLOG/FNDCPGSC.txt:

unexpected RuntimeException or other Throwable occurred -> java.lang.NoSuchMethodError
java.lang.NoSuchMethodError

 Please run $FND_TOP/sql/wfver.sql from your concurrent manager server node OS making sure to spool and upload the output. Support need the output to make sure your WF AQ (contains rules, valid, etc), packages, etc are valid.

The last entries in the wfver.sql output should have the same settings as your adovars.env parameters beginning with AF settings for JDK 1.3.1.

 Please review/upload your adovars.env. You must have migrated your concurrent manager tier to JDK 1.3.Note: 130091.1.

These are the correct parameters for the concurrent manager to use JDK 1.3:

AF_JRE_TOP=[JDK13_TOP]

AFJVAPRG=[JDK13_TOP]/bin/Java

AF_CLASSPATH=[JDK13_TOP]/lib/dt.jar:[JDK13_TOP]/lib/tools.jar:
[JDK13_TOP]/jre/lib/rt.jar:[JDK13_TOP]/jre/lib/i18n.jar:
$JAVA_TOP/appsborg2.zip:$JAVA_TOP/apps.zip:
$ORACLE_HOME/forms60/Java:$JAVA_TOP

where [JDK13_TOP] is the full path to the JDK 1.3 installation top directory on Unix.

 Please review the following Metalink Notes as OWF G uses Java and just like Rapidwiz requires an X Server to function correctly:

Note: 181244.1 Using VNC or XVFB as the X server for Applications 11i

Note: 153960.1 FAQ: X Server testing and troubleshooting

 Please run and upload the results of the following:

grep jar $APPL_TOP/admin/adjborg2.txt

It should point to these two files on your concurrent manager node which MUST exist:

aqapi.jar and jmscommon.jar

unzip -l $JAVA_TOP/appsborg2.zip | grep -i jms | wc –l

If this returns 0, then please manually add the path to to the AF_CLASSPATH in the adovars.env residing on the concurrent manager node as a test. appsborg2.zip is the file that should contain these jar files. They are added when you regenerate your jar files and adjborg2.txt is read and used to rebuild appsborg2.zip.

 Please check the timestamp on the classes in these directories for the error could not start Service Component Container because an unexpected RuntimeException or other Throwable occurred -> java.lang.NoSuchMethodError
java.lang.NoSuchMethodError:

$JAVA_TOP/oracle/apps/fnd/cp/gsc

$JAVA_TOP/oracle/apps/fnd/wf/common
 Please provide the versions of these two classes if the timestamp actually shows that you regenerated the classes today and your concurrent manager server node:

strings –a $JAVA_TOP/oracle/apps/fnd/cp/gsc/SvcComponentContainer.class|grep Header

strings -a $JAVA_TOP/oracle/apps/fnd/wf/common/WorkflowResourceStore.class|grep Header

 Listener and Mailer Services will not start if Local System is Disabled. This status is displayed in the $FND_TOP/sql/wfver.sql output:

Status
----------
DISABLED
 Bounce concurrent manager and retest.

References:



Java Mailer and Other 11.5.9/OWF G Current Issues in Applications 11i [ID 260393.1]

Get Oracle Certifications for all Exams
Free Online Exams.com