What is the diff between apps,applsys,applsyspub

1:What is the diff between apps,applsys,applsyspub?

Apps is a schema which does not contain any tables of itself. it contains all the synonyms of all the table in Oracle apps. But it also contains packages, functions, and procedures.

Applsys schema contains all the tables required for administrative purpose. The default password is apps.

Applsyspub schema is responsible for password checking. Its password is pub.

2) What is batch size in in while applying Patch?

It is contained the how many tables to entered at a time. We give size 5000 it will be entered 5000 tables

3) What is the importance of APPSLISTNER?

APPS Listener is different from Database listener. It is basically RPC listener and is used for various purpose checking log and out file for Concurrent request is one of them.

Check the 8.0.6_HOME/network/admin//listener.ora and you will be able to see entries related to FNDFS and FNDSM

Also check the file adalnctl.txt located at $COMMON_TOP/admin/log and you will see the log file of APPS listener.

4) Why we are using Cache size and sleep seconds in Concurrent program?

Cache size – defines a number of requests concurrent manager remembers (fetches) from fnd_concurrent_requests table, so that it would not have to re-query the table after each execution of a concurrent request;

Sleep Seconds – number of seconds your manager waits between checking the list of pending concurrent requests.

  

PENDING	Normal	Request is waiting for the next available manager.
	Standby	Program to run request is incompatible with other program(s) currently running.
	Scheduled	Request is scheduled to start at a future time or date.
	Waiting	A child request is waiting for its Parent request to mark it ready to run. For example, a report in a report set that runs sequentially must wait for a prior report to complete.
RUNNING	Normal	Request is running normally.
	Paused	Parent request pauses for all its child requests to complete. For example, a report set pauses for all reports in the set to complete.
	Resuming	All requests submitted by the same parent request have completed running. The Parent request is waiting to be restarted.
	Terminating	Running request is terminated, by selecting Terminate in the Status field of   the Request Details zone.
COMPLETED	Normal	Request completes normally.
	Error	Request failed to complete successfully.
	Warning	Request completes with warnings. For example, a report is generated successfully but fails to print.
	Cancelled	Pending or Inactive request is cancelled, by selecting Cancel in the Status field of the Request Details zone.
	Terminated	Running request is terminated, by selecting Terminate in the Status field of   the Request Details zone.
INACTIVE	Disabled	Program to run request is not enabled. Contact your system administrator.
	On Hold	Pending request is placed on hold, by selecting Hold in the Status field of the Request Details zone.
	No Manager	No manager is defined to run the request. Check with your system administrator.