R12 – Managing
This article applies to EBS 12.0.4 on OEL5.3.
I recommend you to start with this article to get R12 up and running.
Login
This is my own login script which you can see here.
Login to OEL as Oracle and run login script:
$ . ./vis.sh
Ensure you also got the first dot so it is the current environment you are setting environment variables for.
Startup
Start database:
$ addbctl start
Start database listener:
$ addlnctl start VIS
Start application server and concurrent managers:
$ adstrtal apps/apps
Shutdown
Start with shutting down application server and concurrent managers:
$ adstpall apps/apps
Wait until all concurrent processes has stopped.
I use this commend to check for that:
$ ps –fed | grep VIS
When only the database processes are left then shut down the database:
$ addbctl stop
Then finally stop the listener:
$ addlnctl stop VIS
Connect
Enter the following URL in Firefox to connect to EBS
http://localhost.localdomain:8000/OA_HTML/AppsLogin
Login as SYSADMIN and password SYSADMIN
Modify Managers
After installing R12 you have more than 200 oracle processes running – check with:
$ ps –fed | grep VIS | wc –l
The managers take up cpu and disk i/o.
Reduce the number of concurrent managers running to something like this:
Use Define Concurrent Managers and reduce to workshift to 0 for non-essential managers.
Also reduce the Standard Manager to 2. You need a minimum of two of a program starts a sub process.
This should get you down to around 120 processes. The system should feel more responsive now.
If you need to work with Inventory or similar find the managers relating to this application and re-activate.
Errors
Remove Persistent Locks (error 204)
If the adstrtal.sh returns error 204 it may be due to locks. Use the following script rmlock.sh:
|
#!/bin/bash |
Timeouts (error 150)
If the adstrtal.sh returns error 150 it may be due to timeouts. This can happen for any of the subscripts called by adstrtal.sh especially if you try to start EBS within Virtualbox or you have a slow USB disk.
To remedy do the following:
$ vi $CONTEXT_FILE
Manually search and replace >100< with >900<
$ vi opmn/config/opmn.xml
Manually update timeout from >600< to >1800<
Internal Server Error (error 500)
If the browser comes out with:
500 Internal Server Error
…and much more…
Then the JSP files may be corrupt.
I fixed it by compiling them:
Compile JSP:
$ cd $FND_TOP/patch/115/bin
$ perl ojspCompile.pl –compile –flush -p 2
Temp Tablespace Exceeded (ORA-01652)
The default temp tablespace datafile is around 1G which may be too small
In order to change this you can issue this command from SQL as SYSTEM:
sql> alter database tempfile ‘/oracle/VIS/db/apps_st/data/temp1_01.dbf’ autoextend on maxsize 10000m ;
Which enables the system to extend the file to 10Gb
Be sure to extend all tempfiles which on a standard VIS installation is temp1_01.dbf and temp2_01.dbf.