I recommend you to start with this article to get R12 up and running.

Run as Oracle user:

$ . ./vis.sh

Note the dot and space in front of a script to assign variables to the current environment.

EBS 12.0.4 on OEL5.3
EBS 12.1.1 on OEL5.4
RDBMS 10g on OEL5.3
RDBMS 11g on OEL5.3 and OEL5.4

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:

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.

Unable to authenticate session

You might see this screen instead of the login screen.

If this happends in Firefox but IE works ok then try to clear the Firefox cache in \Tools\Clear Private Data and then ensure to also select Cookies.

Slow database connection

You might see Oracle Applications starting very slowly – like taking more than a half an hour. This could be due to slow sqlnet connection.

First open a command line and type:

$ sqlplus apps/apps

This should connect fast as it bypasses sqlnet. If not you have a CPU or IO performance problem.

Next try:

$ sqlplus apps/apps@VIS

If this is slow then you might have a slow sqlnet connection.

Check /etc/hosts:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
::1                     localhost.localdomain localhost

I have experiences either the ::1 is missing or pointing to the wrong ip name. Ensure the two lines points to the same name. The problem arises as the new sqlnet has started to use ipv6 which is the ::1 entry.

In 12.0.4 ipv6 was not used but in 12.1.1 ipv6 was introduces maybe with RDBMS 11g

ORA-01031: insufficient privileges

If you get this during database startup on 11g on OEL 5.4 it may be because you have incorrect security setup.

This was not a problem in 10g but Oracle can’t stop changing things…this is also called progress!

1. Check /etc/passwd and ensure you got the following line:

oracle:x:500:500:oracle:/home/oracle:/bin/bash

This is normally set correct. The important bit is the default group – the second 500 value.

2. Check /etc/group and ensure you got the following lines:

bin:x:1:root,bin,daemon,oracle
deamon:x:2:root,bin,daemon,oracle
sys:x:3:root,bin,adm,oracle
adm:x:4:root,adm,daemon,oracle
oracle:x:500:oracle
oinstall:x:501:oracle

So add oracle user not only to the usual oralce created groups but also to bin,daemon,sys and adm groups.