Subject: FAQ (Concurrent Manager Unix specific) Type: TOP20 Status: PUBLISHED Creation Date: 11-APR-2000 PURPOSE ------- To deliver a set of frequently asked questions against the Unix AOL Concurrent Manager issues. SCOPE & APPLICATION ------------------- This reference would be most useful for one who is seeking additional information regarding Unix Concurrent Manager issues. Concurrent Manager FAQs ----------------------- What Concurrent managers are supported by the Sysadmin team? The Internal, Standard, and Conflict resolution managers are the managers supported by the sysadmin team. The setup and related issues to other managers would need to be directed within the associated product group. ie. Inventory manager ************************************************************** Where do the concurrent request and log files reside? $APPLCFS/out or $Product_Top/out ************************************************************** Where are temporary files located? $APPLPTMP $APPLTMP $REPORTS25_TMP ************************************************************** How do you change PMON to LOCK? Check process monitor (PMON) method. Connect as database user "APPS". SELECT profile_option_value FROM fnd_profile_option_values WHERE level_id = 10001 AND level_value = 0 AND application_id = 0 AND profile_option_id = (SELECT profile_option_id FROM fnd_profile_options WHERE profile_option_name = 'CONC_PMON_METHOD'); This should return one row with a value of 'LOCK' If the value is 'RDBMS' or 'OS' run the script $FND_TOP/sql/AFIMPMON.SQL - this will set the PMON method to LOCK instead of RDBMS. Stop database and restart database server. If not already shutdown in previous step, stop and restart the database. If running on NT, restart the NT Server completely. ************************************************************** How to start the CCM under Unix as APPS: STARTMGR sysmgr=APPS/APPS How to shut down the CCM under Unix as APPS: concsub apps/ sysadmin 'System Administrator' SYSADMIN CONCURRENT FND ABORT ie. is generally APPS ************************************************************** How do I terminate a concurrent request that cannot be canceled? Identify the request number to terminate. Please shut down the concurrent managers and issue the following sql command as applsys: update fnd_concurrent_requests set status_code = 'E', phase_code = 'C' where Request_id = ; (reqnum = request number) ************************************************************** One of your managers is not activating. Check the count in sys.dual, system.dual, & apps.fnd_dual. There should only be one (1) row for each. If the count is greater, change to one only. This is done from sqlplus as apps as follows: select * from SYS.DUAL; Any extra rows should be deleted. delete rownum from SYS.DUAL; rownum = the row number to delete Any extra rows for apps.fnd_dual must be removed performing the following SQL command: delete from fnd_dual where rownum < (select max(rownum) from fnd_dual); Bounce your managers. ************************************************************** If the ICM itself should go down, requests will continue to run normally, except for 'queue control' requests. If the ICM should go down, you can restart it with 'startmgr'. You do not need to kill the other managers first. ************************************************************** How do I purge requests that are in Pending status? The Purge Concurrent Requests program will only purge requests that are in Completed status. You will have to set their status to Completed before purging them. Using sqlplus as APPLSYS perform the following: UPDATE fnd_concurrent_requests SET phase_code = 'C' WHERE phase_code = 'P' RELATED DOCUMENTS ----------------- Note 104664.1