Applications 11i Health Check After Maintenance

1. Verify Maintenance Mode is disabled (applicable to 11.5.10 and customers with AD I patchset level (Patch 3180816(AD I) or Patch 4038964 (AD I1))).

2. Personal Home Page: Use http://hostname.domain:port
2.1. Login into Personal Home page as Sysadmin User
2.2. Choose Application Adminsitrator Responsibility to log into core applications.
2.3. Check whether User/Responsibility Administrator Screen is coming up without errors.
2.4. Submit "Generate Concurrent Processing Environment Information" Concurrent Request and "Active Users" report. Once completed normally then use export function (MainMenu/File/Export). If errors check your APPS_LISTENER is up and running else further debugging is needed.
2.5 Select “Concurrent Manager Administer” and check the status of “Service Manager”. If Service Manager is not running, Shutdown concurrent managers, run cmclean.sql and restart concurrent managers.

3. SSP Products: Login to applications using step 1 and select Sales Online, iExpenses or iProcurement responsibility. Check whether pages are coming up or not, If customer is licensed for it.

4. Reports Server and Discoverer: To be tested only in the case the customer is licensed for any Business Intelligence Modules
4.1. Report Server: Login to applications using step 1 and select responsibility like Financial Intelligence. Run report Earnings per Share and ensure that graphs are displayed without any errors.
4.2. Discoverer Viewer:http://hostname.domain:port/discoverer4i/viewer (in case of failure, run $ORACLE_HOME/discwb4/util/checkdiscoverer.sh to check status of each component)
4.3. Discoverer Plus: http://hostname.domain:port/discwb4/html/english/welcome.htm(in case of failure, run $ORACLE_HOME/discwb4/util/checkdiscoverer.sh to check status of each component)

5. Check Jserv is Up and running :
5.1. http://hostname.domain:port/servlets/Hello 5.2 For Multi-MT instances, perform the following check using machine name URL for each MT and make sure the page comes uphttp://hostname:domain:port/OA_HTML/AppsLocalLogin.jsp

6. JTF Login Page for customers using CRM (Check for each MT using real host names) http://hostname.domain:port/OA_HTML/jtflogin.jsp

7. Workflow: Login to OAM. Navigate to “Workflow Manager” and make sure “Notification Mailers” and “Agent Listeners” are up.

8. Ensure Database is in archive log mode ( If it was disabled for patching/upgrade)
$sqlplus " / as sysdba"
SQLarchive log list

9. Optional: Check multiple JVM's have come up if configured. Only if autoconfig was run, check that number of JVMs configured is same as it was before change.

10. Check the invalid object count and make sure that there is no additional invalid objects after the maintanence

11.Run apps diagnostics testsLogin to Personal Home Page using http://hostname.domain:port
Click on System Administration responsibility
Run below tests under Diagnostics page
a) PL/SQL ping
b) JSP Ping
c) AOL/J Database Connection Pool Status
d) Servlet ping

These checks will make sure all necessary components of oracle applications functioning well.