This chapter covers the following topics:
This section discusses known issues regarding the concurrent program that creates mobile users, Manages Mobile Users. This Java concurrent program creates mobile users. JDK 1.3.1 is required in the concurrent tier.
The Concurrent Program Fails to Create Mobile Users
Problem: After the patch is applied and the post-installation setup is completed, the concurrent program still does not work.
Resolution: Restart the concurrent managers so that the new environment settings are initialized. To find out whether a concurrent request is being initialized to JDK 1.3.1 settings, use the following script:
select variable_name,value
from fnd_env_context e,
fnd_concurrent_processes p,
fnd_concurrent_requests r
where p.concurrent_process_id = e.concurrent_process_id
and p.concurrent_process_id = r.controlling_manager
and r.request_id=&request_id
and e.variable_name in ('AF_JRE_TOP','AFJVAPRG','AF_CLASSPATH')
This script accepts a concurrent request ID and prints the environment settings for that request.
The Concurrent Program Only Works Intermittently
Problem: The concurrent program only works intermittently.
Resolution: Make sure all concurrent managers are restarted. It is possible that only one concurrent manager was restarted. However, a concurrent request might be started by any of the concurrent managers. If all the concurrent managers are not restarted, then some of the requests might not have the correct settings. To verify this, use the script listed above for requests that fail.
The Concurrent Program Log Shows the Error Message "oracle.lite.web.resource.ResourceException: java/lang/ThreadLocal"
Problem: The log generated by the concurrent request shows this error.
Resolution: This is the clearest indication that the JDK version is not 1.3.1. The above mentioned class (ThreadLocal) is in JDK 1.2.2 or higher. Again, check if the environment settings are correct.
All Environment Settings Appear Correct, But the Concurrent Program Still Does Not Work
Problem: The environment settings that appear in the script listed in "The Concurrent Program Fails to Create Mobile Users" indicate that JDK 1.3.1 is used. However, the concurrent program still fails.
Resolution: Look into the concurrent request's log file and look for any exceptions. Then for each of the environment variables AF_JRE_TOP, AFJVAPRG, and AF_CLASSPATH, check if the files listed exist.
Upload errors are generated during the upload process when some of the data fails to be applied to the enterprise database. Upload errors can be caused by the following:
System issues.
It is possible that the system is on a different mobile patch level than what is required.
Setup issues.
The correct business process type or the correct profile setting is not set on the enterprise system. For example, it is necessary that the expense type for an expense line is set correctly.
Faulty data or conflicts.
Oracle Mobile Application Foundation maintains a log of all upload errors. You can use the Mobile Application Foundation Administration Console to view and manage these errors. See the upload errors sections in Chapter 8 Administrative Tasks for further details.