Wednesday, August 27, 2008
How is the Workflow Background Process / OTL Workflows for Employees setup?
Answer is provided at
Sucharitha.com > Forum > Oracle HRMS Application Help > Oracle Time & Labor > How is the Workflow Background Process / OTL Workflows for Employees
How to Validate Multiple OTL Batches at One Time Before Moving to BEE?
Check out the answer at Sucharitha.com > Forum > Oracle HRMS Application Help > Oracle Time & Labor > How to Validate Multiple OTL Batches at One Time Before Moving to BEE?
How to Add Lov to a Timecard?
check out the answer at
Sucharitha.com > Forum > Oracle HRMS Application Help > Oracle Time & Labor > How to Add Lov to a Timecard?
How to enable Date Tracking for the Oracle Time and Labor OTL product
Check out the answer @
Sucharitha.com > Forum > Oracle HRMS Application Help > Oracle Time & Labor > How to enable Date Tracking for the Oracle Time and Labor (OTL) product.
Thursday, July 19, 2007
Release 11i Documentation Titles (11.5.10)
Click on the link below and check for the document you want and post a comment if you need more information .
http://spreadsheets.google.com/pub?key=pd7jnzILIpyYazX-mzhfoPw
Wednesday, July 18, 2007
Troubleshooting Concurrent Manager (UNIX specific)
PURPOSE:
This template requires the essential matter for troubleshooting Unix Concurrent Manager Problems.
SCOPE & APPLICATION:
-------------------
This reference is intended for use by one who is familiar with the concurrent manager process.
Trouble shooting UNIX concurrent manager
----------------------------------------
1. Have you tried shutting down, running the cmclean script and re-starting the Concurrent Managers?
[YES] Check logfiles
[NO] Try it, customer may have been logged in as the wrong user or incorrectly typed the startup command.
You can run the cmclean.sql script within Note 134007.1 to reset the concurrent
Manager tables whilst the Concurrent Managers are down.
2. Are there any FNDLIBR processes still running even after the attempted shutdown?
Use command PS -ef | grep FNDLIBR
[YES] UNIX: Use kill -9 to clean them up
[NO] Continue troubleshooting
3. Are there any errors in the logfiles?
Logfiles are in $FND_TOP/log or $APPLCSF/$APPLLOG if defined.
Logfiles are usually named STD.MGR or the CCM name(i.e. PRDMGR.MGR)
[YES] Make note of the errors and search Metalink for these errors.
If no resolution is found, open a SR and upload the logfiles.
[NO] Have ct restart the Concurrent Manager from the command line to have a new log file created.
Command to start the CCM:
startmgr sysmgr=apps_schema_owner/password logfile=std.mgr
* This should create logfile std.mgr
* If no logfile exists, check for UNIX permissions and space on filesystem.
4. How many rows are in FND_CONCURRENT_REQUEST and
FND_CONCURRENT_PROCESSES tables?
Check the FND tables using the sql statements below. When these tables reach above 3-4K rows performance begins to suffer when viewing report output and the Internal Concurrent Managers often does not start due to the lengthy search through
FND_CONCURRENT_PROCESSES table. You may want to run Purge Concurrent
Request and/or Manager Data on a regular basis.
Please run diagnostic script found under Note 200360.1 for common problematic issues.
Upload the output from the diagnostic script to the SR for Oracle Support review.
5. Are any processes pending in the Internal or Conflict resolution Manager?
Pending jobs in either the Internal or Conflict Resolution Manager may prevent the Concurrent Manager from starting. The best course of action before starting the Concurrent Managers is to cancel any "Deactivate" or "Verify" jobs pending in the Internal Manager and to place any other pending jobs on hold.
Additional Information:
1. Number of records in the following Tables:
FND_CONCURRENT_REQUESTS
FND_CONCURRENT_PROCESSES
FND_DUAL
Command: Logged in SQLPLUS as APPLSYS(or demo - APPDEMO)
select count(*) from FND_CONCURRENT_REQUESTS
2. Sometimes it is necessary to rebuild the Concurrent Manager views.
This is non-destructive.
Concurrent Manger views can be rebuilt by running the following
Command at the command line: FNDCPBWV is a immediate concurrent
program that is a part of FNDLIBR.
UNIX & Windows NT
FNDLIBR FND FNDCPBWV apps/apps SYSADMIN 'System Administrator'
SYSADMIN
VMS:
FNDLIBR "FND" "FNDCPBWV" apps/apps "SYSADMIN" "System
Administrator" "SYSADMIN"
USEFUL SCRIPTS
--------------
Note 213021.1 Concurrent Processing (CP) / Apps Reporting Scripts
RELATED DOCUMENTS
-----------------
Note 74717.1: Troubleshooting Concurrent Manager Startup problems
Note 97798.1 ORA-904 when starting concurrent managers
Note 230121.1 Routine AFPEIM encountered an error while starting Concurrent Manager on Cloned instance
Note 1059201.6 Status pending with 'Inactive No Manager' cor Concurrent Requests
Note 113135.1 Conflict Resolution Manager FNDCRM Does Not Start; No
Error Message.
Note 123607.1 CONCSUB SYSADMIN 'System Administrator' GIVES INVALID RESPONSIBILITY ERROR
Note 2055375.6 RESET PMON METHOD (CHOICES: LOCK, OS, RDBMS)
Note 2069781.6 Basic Troubleshooting of the Concurrent Managers
Note 2120154.6 Unable to start the ccm after install - core dump
Note 171855.1 CCM.sql Diagnostic Script for Concurrent Manager
Note 185036.1 Unable to Startup or Shutdown the Concurrent Managers in 11.5.5 by Using the Syntax adcmctl.sh apps/<psswd> Start or Stop
Installation and Configuration using AutoConfig
Oracle E-Business Suite Release 11i with 9i RAC
Installation & Configuration Using AutoConfig
________________________________________
This document describe the steps required to install and setup an Oracle Applications Release 11i (11.5.10) environment with Oracle database 9i Release 2 (9.2.0.8) Real Application Cluster (RAC).
This document is divided into the following sections:
Section 1: Overview
Section 2: Environment
Section 3: Pre-requisites For RAC conversion.
Section 4: Installation/Configuration
Section 5: References
For complete information on the above sections click on the link below:
http://docs.google.com/Doc?id=dhs3fvh6_29fp7pz4