Q.In administer concurrent manager form there are two columns target and actual. What are these columns.
Q.How do i run/schedule a concurrent request from operating system level without logging into the applications.?
QWhat are the different ways to check Concurrent manger is running or not?
By using FNDLIBR fom os level, from the forms it can be check from navigatio>concurrent>Manager>Administer. It can be also checked by using script adcmctl.sh status finally it can be checked from OAM also.
QWaht is the default location of concurrent manager?
If environment variable set
$APPLCSF/$APPLLOG
$APPL_TOP/admin/SID/log(11i)
$/maildata_test/mcgm/R12/apptier/apps/rdb_mailserver2/logs/appl/conc/log (R12)
If environment variable not set
$FND_TOP/$APPLLOG
Q i have submitted a request and its showing the status inactive no manager
If the concurrent manager is up and running and the request goes to inactive no manager for some time it means the cache cycle is less. Cache size set on the concurrent >manager> Define form..
Basically this regulates how many requests a manager will pick up for each sleep cycle.the solution is either increase the sleep cycle or increase the number of manager process. The manager should be either slandered manager or any other manager for which the issue is coming.
Q I have submitted a request it has gone to pending standby status for a long time whereas other request are getting completed normally with out any issues. what could be the reason.?
If any particular request is going pending standby status and other request are getting completed it means that either is waiting for other request output or it is conflicting with some other request. If the request is conflicting check the queue of the conflict resolution manager for troubleshooting.
Q How do i process more concurrent request in parallel?
If you want to process more requests simultaneously there are two way by increasing target process for the manager and other one increasing cache size.
Q When do the tables FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROCESS need to be purged?
when the tables reached 20000 rows the performance being to diminish. You may want to run purge concurrent request on a regular basis depending on the amount of request being run.
Q What if the internal concurrent manager dies? All the managers also killed immediately after it?
No if the ICM dies the request continue to run normally except queue control requests.
Q Does the ICM run or schedule any request for itself?
No the ICM does not run or schedule any request. It has nothing to do with scheduling requests, or deciding which manager will run a particular request. Its function is only to run queue control requests which are requests to start up or shutdown other manager.It is responsible for start-up and shutdown of the whole concurrent processing facility and it also monitors the other managers periodically and restart them when they goes down. It can also take over the conflict resolution manager job and resolve incompatibilities.
Q If the ICM goes down do i need to kill all other managers before starting ICM?
No, If the ICM goes down no need to kill all other managers just simply start ICM
Q Can I delete Concurrent Manager?
Yes you can delete any concurrent manager for deleting , query for the manager in the defined concurrent manager form and delete the row.
Deleting the predefined manager not recommended and it should never done.
Qwhat is internal monitor?
This manager is used to implement parllel concurrent processing . It monitors whether the ICM is still running and if ICM crashes it will restart it on another node.
QHow do i clean out concurrent manager tables?
For this Oracle provide a script called cmclean.sql.
QI hit the restart button to start the standard manager but it still not started?
Asking a manager to restart sets the status to restart. The ICM will start in the next process monitor session or next time ICM starts. Use activate to start the manager immediately. Also when a manager deactivated manually the ICM will not start it you need to set it to restart or activate it manually.
Q What are the circumstances in which you need to bounce the concurrent manager?
Restart If the CM goes down abnormally it will automatically
restart the manager Y=the number of minutes the ICM N=no to restart after abnormal
waits before restarting the manager termination
Mailto MAILTO is a list of users who should receive mail whenever Current user
Manager terminates
Printer The default printer for sending the output files
Diag This is used for diagnosis If the CM is started with parameter N
diag=y then full diagnostic output is produced in the log file.
Pmon The number of sleep cycle ICM will wait before checking 20
Failed manager
Quesiz Number of pmon cycle the ICM waits between times it checks for 1
normal changes in concurrent manager operation
Q. What exactly happens when a concurrent request is submitted?
Once a concurrent request is submitted by the user, the table FND_CONCURRENT_REQUEST is automatically updated with the details of the request. The table also updated with the information about schedule of the concurrent whether its immediately scheduled or scheduled at a fixed time. Once the request is scheduled to run the concurrent manager checks the FND_CONCURRENT_REQUEST table to find the request is incompatible with any other request . If the request is incompatible then the Conflict resolution manager take care of the request and find out what are the incompatibilities and resolve them. If there are incompatibilities then it checks for any other special manager assigned to that particular request. If there are any special manager to take care of this request then it goes to the queue of that manager else the standard manager takes care of the same.Once the requset is processed FND_CONCURRENT_REQUEST updated with that status.
Q.In the administer concurrent manager form, what is the significance of the terminate button?
The terminate button used to terminate any concurrent manager. When you terminate internal manager all the manager automatically ge deactivated and all the running request are terminated. If you want to terminate a particular manager, select that manager and click terminate. The status of the manager changes to deactivate after a few seconds and all the requests are processed by that manager are immediately terminated. Once the manager terminated it does not starts automatically. You have to manually restart it using the restart button.
Q In administer concurrent manager form what is the significance of the deactivate button and how can you deactivate a manager from there?
For deactivating a particular manager select that manager and press the deactivate button. In case of deactivation, all the requests are processed before shutdown manger does shutdown. If the internal manager goes deactivated all other manager goes deactivated and all requests are processed before manger going down.This is the main difference between terminate and deactivation. In termination all running request are terminated immediately whereas in case of deactivation all the running requests are allowed to complete first.
QIn administer concurrent manager form, what is the significance of the verify button and for which manager its available?
The verify button enable for only internal manager. One of the function of the internal manager is to monitor the processes of the each concurrent manager. The process of monitoring the other manager process by IM is known as a PMON cycle.When you click the verify button you can force the process monitoring or the PMON activity to occur.The verify button also available for conflict resolution manager.
Q What is parallel processing and what is the significance of the same?
Parallel concurrent processing is the way to distribute concurrent manager across multiple nodes in a cluster, massively parallel or networked environment. It helps in distributing the load across multiple nodes thereby fully utilizing the hardware resource
In case of parallel concurrent processing all the managers are assigned a primary and secondary node. The managers are started on primary node by default. In case of failure or Oracle instance failure all the concurrent manager get into secondary node. If the primary node available all concurrent manger get back to the primary node.During that migration process a manger spread across on both nodes .
In case of parallel concurrent processing it may happen that in a node where parallel co current processing is configured, the Oracle instance may or may not be running. The node which s not running Oracle, the concurrent manager connect via Net8 to a node where is running oracle.
The internal concurrent manager can run on any node and can active and reactive concurrent managers on all nodes. Since the internal concurrent managers must be active at all times, it needs high fault tolerance. To provide this fault tolerance parallel concuncurent processing uses internal monitor processes. The job of Internal monitor is to monitor constantly the internal manager and start it when it is fails.Only one monitor process can be active on a single node. You have to decide which nodes have an internal monitor process when you configured system. You can also assign each internal monitor process a primary and a secondary node to ensure fail over protection. Internal monitor process like concurrent manager assigned a work shifts and are activated and deactivated by the internal concurrent manager.
Q I have defined for nodes of the concurrent manager Now do i need to start the concurrent manager from all the nodes?
No, even if you have defined the concurrent manager in four different nodes you need not start the concurrent manager from all the nodes. You just need to start the concurrent on primary node GSM will take care of starting the concurrent manager form all other nodes.
QThe user comes to you saying that the request are taking a lot of time to complete. what is the debugging approach ?
Target columns lists the number of processes that are running for each manager for a particular work shift.
Actual column that is currently how many process are running. If actual column is zero then there are no process are running for that particular manager.
If the Target column is zero then there is no work shift assigned for that manager or the current work-shift does not specify any target processes. If the target column not zero then the manger goes down or manager processes have either failed.
Q.How do i run/schedule a concurrent request from operating system level without logging into the applications.?
A Concurrent request can be scheduled/ru from the operating system using the CONCSUB utility.CONCSUB means concurrent submit.
By using FNDLIBR fom os level, from the forms it can be check from navigatio>concurrent>Manager>Administer. It can be also checked by using script adcmctl.sh status finally it can be checked from OAM also.
QWaht is the default location of concurrent manager?
If environment variable set
$APPLCSF/$APPLLOG
$APPL_TOP/admin/SID/log(11i)
$/maildata_test/mcgm/R12/apptier/apps/rdb_mailserver2/logs/appl/conc/log (R12)
If environment variable not set
$FND_TOP/$APPLLOG
Q i have submitted a request and its showing the status inactive no manager
If the concurrent manager is up and running and the request goes to inactive no manager for some time it means the cache cycle is less. Cache size set on the concurrent >manager> Define form..
Basically this regulates how many requests a manager will pick up for each sleep cycle.the solution is either increase the sleep cycle or increase the number of manager process. The manager should be either slandered manager or any other manager for which the issue is coming.
Q I have submitted a request it has gone to pending standby status for a long time whereas other request are getting completed normally with out any issues. what could be the reason.?
If any particular request is going pending standby status and other request are getting completed it means that either is waiting for other request output or it is conflicting with some other request. If the request is conflicting check the queue of the conflict resolution manager for troubleshooting.
Q How do i process more concurrent request in parallel?
If you want to process more requests simultaneously there are two way by increasing target process for the manager and other one increasing cache size.
Q When do the tables FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROCESS need to be purged?
when the tables reached 20000 rows the performance being to diminish. You may want to run purge concurrent request on a regular basis depending on the amount of request being run.
Q What if the internal concurrent manager dies? All the managers also killed immediately after it?
No if the ICM dies the request continue to run normally except queue control requests.
Q Does the ICM run or schedule any request for itself?
No the ICM does not run or schedule any request. It has nothing to do with scheduling requests, or deciding which manager will run a particular request. Its function is only to run queue control requests which are requests to start up or shutdown other manager.It is responsible for start-up and shutdown of the whole concurrent processing facility and it also monitors the other managers periodically and restart them when they goes down. It can also take over the conflict resolution manager job and resolve incompatibilities.
Q If the ICM goes down do i need to kill all other managers before starting ICM?
No, If the ICM goes down no need to kill all other managers just simply start ICM
Q Can I delete Concurrent Manager?
Yes you can delete any concurrent manager for deleting , query for the manager in the defined concurrent manager form and delete the row.
Deleting the predefined manager not recommended and it should never done.
Qwhat is internal monitor?
This manager is used to implement parllel concurrent processing . It monitors whether the ICM is still running and if ICM crashes it will restart it on another node.
QHow do i clean out concurrent manager tables?
For this Oracle provide a script called cmclean.sql.
QI hit the restart button to start the standard manager but it still not started?
Asking a manager to restart sets the status to restart. The ICM will start in the next process monitor session or next time ICM starts. Use activate to start the manager immediately. Also when a manager deactivated manually the ICM will not start it you need to set it to restart or activate it manually.
Q What are the circumstances in which you need to bounce the concurrent manager?
- when you modify the definition of the printer
- when you modify the environment variables say you have changed the APPLTMP and APPLPTMP variable
- when all the requests are pending or hanging
Q What are the reasons a CM (concurrent manager) hangs?
- Long running jobs
- The Internal manager was activated by some one other than owner of the application system
- The OS file system is full.
- Its not able to create log files
- You've down the Internal Manager but actual has number on it.
- The database hanging may be because of archive logs full
- Pending/standby requests are too many
QThe Different parameter of startmgr utility
Parameters Description Default
sysmgr sqlplus sername/pwd that owns the foundation tables Applsys/<pwd>
Mgrname the name of the manager Internel Manager
Log file the logfile of the manager $FND_TOP/$APPLLOG
or
$APPLCSF/$APPLLOG
Sleep the number of seconds the ICM should wait
before checking for the new request from the table 60sec
FND_CONCURRENT_REQUESTS
Restart If the CM goes down abnormally it will automatically
restart the manager Y=the number of minutes the ICM N=no to restart after abnormal
waits before restarting the manager termination
Mailto MAILTO is a list of users who should receive mail whenever Current user
Manager terminates
Printer The default printer for sending the output files
Diag This is used for diagnosis If the CM is started with parameter N
diag=y then full diagnostic output is produced in the log file.
Pmon The number of sleep cycle ICM will wait before checking 20
Failed manager
Quesiz Number of pmon cycle the ICM waits between times it checks for 1
normal changes in concurrent manager operation
Q. What exactly happens when a concurrent request is submitted?
Once a concurrent request is submitted by the user, the table FND_CONCURRENT_REQUEST is automatically updated with the details of the request. The table also updated with the information about schedule of the concurrent whether its immediately scheduled or scheduled at a fixed time. Once the request is scheduled to run the concurrent manager checks the FND_CONCURRENT_REQUEST table to find the request is incompatible with any other request . If the request is incompatible then the Conflict resolution manager take care of the request and find out what are the incompatibilities and resolve them. If there are incompatibilities then it checks for any other special manager assigned to that particular request. If there are any special manager to take care of this request then it goes to the queue of that manager else the standard manager takes care of the same.Once the requset is processed FND_CONCURRENT_REQUEST updated with that status.
Q.In the administer concurrent manager form, what is the significance of the terminate button?
The terminate button used to terminate any concurrent manager. When you terminate internal manager all the manager automatically ge deactivated and all the running request are terminated. If you want to terminate a particular manager, select that manager and click terminate. The status of the manager changes to deactivate after a few seconds and all the requests are processed by that manager are immediately terminated. Once the manager terminated it does not starts automatically. You have to manually restart it using the restart button.
Q In administer concurrent manager form what is the significance of the deactivate button and how can you deactivate a manager from there?
For deactivating a particular manager select that manager and press the deactivate button. In case of deactivation, all the requests are processed before shutdown manger does shutdown. If the internal manager goes deactivated all other manager goes deactivated and all requests are processed before manger going down.This is the main difference between terminate and deactivation. In termination all running request are terminated immediately whereas in case of deactivation all the running requests are allowed to complete first.
QIn administer concurrent manager form, what is the significance of the verify button and for which manager its available?
The verify button enable for only internal manager. One of the function of the internal manager is to monitor the processes of the each concurrent manager. The process of monitoring the other manager process by IM is known as a PMON cycle.When you click the verify button you can force the process monitoring or the PMON activity to occur.The verify button also available for conflict resolution manager.
Q What is parallel processing and what is the significance of the same?
Parallel concurrent processing is the way to distribute concurrent manager across multiple nodes in a cluster, massively parallel or networked environment. It helps in distributing the load across multiple nodes thereby fully utilizing the hardware resource
In case of parallel concurrent processing all the managers are assigned a primary and secondary node. The managers are started on primary node by default. In case of failure or Oracle instance failure all the concurrent manager get into secondary node. If the primary node available all concurrent manger get back to the primary node.During that migration process a manger spread across on both nodes .
In case of parallel concurrent processing it may happen that in a node where parallel co current processing is configured, the Oracle instance may or may not be running. The node which s not running Oracle, the concurrent manager connect via Net8 to a node where is running oracle.
The internal concurrent manager can run on any node and can active and reactive concurrent managers on all nodes. Since the internal concurrent managers must be active at all times, it needs high fault tolerance. To provide this fault tolerance parallel concuncurent processing uses internal monitor processes. The job of Internal monitor is to monitor constantly the internal manager and start it when it is fails.Only one monitor process can be active on a single node. You have to decide which nodes have an internal monitor process when you configured system. You can also assign each internal monitor process a primary and a secondary node to ensure fail over protection. Internal monitor process like concurrent manager assigned a work shifts and are activated and deactivated by the internal concurrent manager.
Q I have defined for nodes of the concurrent manager Now do i need to start the concurrent manager from all the nodes?
No, even if you have defined the concurrent manager in four different nodes you need not start the concurrent manager from all the nodes. You just need to start the concurrent on primary node GSM will take care of starting the concurrent manager form all other nodes.
QThe user comes to you saying that the request are taking a lot of time to complete. what is the debugging approach ?
- You can run trace on the request id to find the expensive sqls and then tell the developer to fix the same.
- you can check the program incompatibilities in the concurrent request
- you can check the query which the concurrent program is executing and see if it is creating nay locks in the database
- many times the users schedule the request to run at a later time.
- You cab check the parameters with which the request is run.
Q Waht are the things take care when you defining a concurrent program.
- selecting an executable file to run the program
- Choosing the execution method for program
- Defining the parameter for the program
- defining the printing information
No comments:
Post a Comment