1)REP-3000: Internal Error Starting Oracle Toolkit .

++++++++++++++++++++++++++++++++++++++++++++++++++

Cause : display has not set.

DISPLAY=<hostname>:<display_number>.0 ; export DISPLAY

2)ICM is creating zero bytes of log file.

++++++++++++++++++++++++++++++++++++++++++++++++++
Cause: No space left on the device

Soltion
++++++++
Compress or unwanted files.

3)Concurrent Processing - The Concurrent Manager Fails to Start on GSM Enabled Due
to DBMS_LOCK.Request ResultCall Failed to Establish ICM [ID 245563.1]
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

cause: Database Locking issue

symptom: Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1

from the call to DBMS_LOCK.Request

fix:

1. Stop all services and concurrent managers

2. Stop and restart the database
3. Restart the services and concurrent managers
4. Verify if the issue remains

4)ICM Not Starting: Node Name not Registered [ID 602942.1]

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Cause
++++++++
wrong host name defined

solution:
+++++++
This node name value can be changed by running the UNIX command setuname or the
hostname command. An example of this would be:
setuname -n newnodename

5)Cause: FDPRRC failed due to ORA-01654: unable to extend index

APPLSYS.FND_CONCURRENT_REQUESTS_N4 by 16 in tablespace APPS_TS_TX_IDX
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++
Cause:There is not enough space in tablespace APPS_TS_TX_DATA
Tablespace is 100%

Soltion
+++++++
Add datafile or resize

6)User are complaining there requests are showing inactive nomanager

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++
Cause:work shifts are not define.

Solution: After defining the workshift it is working fine.

7)i have done with my clone and when i am trying to start the concurrent manager
getting error saying
no FNDLIBR.
+++++++++++++++++++++++++++++++++++++
Relink application program

FNDLIBR ==> Got deleted.

8)tns issues
++++++++++++
An error has been established while contacting FNDFS_CTSST11 .

Cause:
Not able to ping to the above entyr

SOlution
++++++++
put the entry in in ifile on web/form node.

+++++++++++++++++++++++++
OS ISSUES
+++++++++++++++++++++++++
File system issue ==> unable to see the mount point.
Unix users login issues ==> like mailer user password is not working.
Connection timed out error ==> unable to login to unix box/Host.
Mount point mounted on wrong physical box.

++++++++++++++++
DB ISSUES
+++++++++++++++

Lets discuss the very basics of Concurrent Managers, again the very basics for the
beginners that read http://getappstraining.blogspot.com
Two things are obvious:-
1. Concurrent Manager is related to Concurrent Programs
2. Concurrent manager manages the concurrent(oops I mean parallel) execution of
concurrent programs.

So what's left to explain?.....Well nothing much, but I gave a commitment to one of

my readers that I shall write something about concurrent managers today. And now
when I begin to write, I realize it is worth writing something in plain English on
this topic.

Question:
Answer: There is something known as Concurrent Manager that runs in the background
all the time. This background process, called Concurrent Manager ideally will be
running 24x7.
As the name suggests, purpose of a concurrent manager is to manage the submitted
concurrent programs.

Question: When I submit a concurrent program( or call it concurrent request), how

does concurrent manager pick this up?
Answer: Concurrent manager will be running in the background waiting for a
concurrent program to be submitted. As soon as a concurrent program is submitted,
it then gets put in an execution queue by concurrent manager.

Question: Why does the Concurrent manager put a concurrent program into a queue?
Why doesn't the manager simply let the program run?
Answer: Because at any given point in time a concurrent manager can run no more
than say 10 programs concurrently. This figure of 10 is configurable of course.
First the manager puts a submitted program into a queue, next the manager checks if
there is a slot available (i.e. Less than 10 programs are currently running). If a
slot is found available, the concurrent manager then runs the program, or else it
keeps the concurrent program in a queue with status Pending.

Question: If we have two concurrent programs, that must never run in parallel(oops
I mean concurrently)....can concurrent manager manage such scenarios?
Answer: Of course it can. When you define a concurrent program, you can specify if
there are any incompatible programs. If incompatible concurrent programs exist,
then concurrent manager will wait for the incompatible program to complete.

++++++++++++++++
Application Patching issues
+++++++++++++++
1)
worker is trying to change the column width but failing it.
This is standard table.
i try to do it manually and it is again failing
we raised a SR with oracle they have given patch and we applied.
Now column width got changed.

alter table emp modify (ename varchar2(48));

2)I was applying an application patch but that patch is not able copy the c driver
to file system of oracle apps.
Solution:
+++++++++
i have copied the file manually and commented in the driver and started the adpatch
session it worked fine.

++++++++++
Database patching issue
++++++++++
I was trying to rollback the patch but patch got failed with error code 403.

I have raised an SR with oracle they have provided the soltuion with the command.

opatch rollback -id patchno _nod_sysmod

++++++++++++
space not getting released from the mount point
+++++++++++++++++++++++++++++++++++++++++++++
Deleted files holding the disk space.
Files are deleted but porcesses are running.

Some time your log filesystem might seem to get full, but actually some of the
deleted files might be holding the disk space.
in general you can kill the PID's if there is one or two deleted files.
When there is more than hundreds of deleted files and you have to kill all the
deleted files then you can use the below script.
But note killing more numbere of process or PID are actually not recommended.

lsof +L1 | grep 'deleted' | awk '{print $2}' | xargs kill -9