FND STATUS_CODE

A Waiting
B Resuming
C Normal
D Cancelled
E Error
F Scheduled
G Warning
H On Hold
I Normal
M No Manager
Q Standby
R Normal
S Suspended
T Terminating
U Disabled
W Paused
X Terminated
Z Waiting

PHASE_CODE column
C Completed
I Inactive
P Pending
R Running

linux ps --option

linux ps --option

PROCESS STATE CODES
Here are the different values that the s, stat and state output specifiers
(header "STAT" or "S") will display to describe the state of a process.
D    Uninterruptible sleep (usually IO)
R    Running or runnable (on run queue)
S    Interruptible sleep (waiting for an event to complete)
T    Stopped, either by a job control signal or because it is being traced.
W    paging (not valid since the 2.6.xx kernel)
X    dead (should never be seen)
Z    Defunct ("zombie") process, terminated but not reaped by its parent.

For BSD formats and when the stat keyword is used, additional characters may
be displayed:
<    high-priority (not nice to other users)
N    low-priority (nice to other users)
L    has pages locked into memory (for real-time and custom IO)
s    is a session leader
l    is multi-threaded (using CLONE_THREAD, like NPTL pthreads do)
+    is in the foreground process group

difference between base table and multi-org table?

multi_org tables have the colums org_id and end's with _all but not in base tables

BASE TABLES ENDS WITH _B, TABLES WHICH ARE HAVING _B HAS TO BE TRANSLATED TO MULTIPLE LANGUAGES
EXAMPLE ITEM INFORMATION IS STORED IN BASE TABLE WHICH HAS TO BE TRANSLATED FOR THIS WE HAVE ANOTHER TABLE WHICH ENDS WITH _TL

_ALL : Table holds all the information about different operating units. Multi-Org environment. You can also set the client_info to specific operating unit to see the data specific to that operating unit only.
_TL  These tables provide multiple language support.
_B these are the BASE tables.
_F these are date tracked tables, which occur in HR and Payroll.
_V tables are the views created on base tables
_VL are views for multi language tables which combines the row of the base table with the corresponding row of the _TL table where the LANGUAGE = USERENV('LANG').
_S are sequences, used for finding new values for the primary key of a table.
_A are Audit Shadow Tables
_AVN and _ACN are Audit Shadow Views (when data was changed, and with what value

Linux exit Variables

$$ = The PID number of the process executing the shell.

$? = Exit status variable.

$0 = The name of the command you used to call a program.

$1 = The first argument on the command line.

$2 = The second argument on the command line.

$n = The nth argument on the command line.

$* = All the arguments on the command line.

$# The number of command line arguments.

Find the model and serial number of a Linux server

dmidecode -t system

HTTP server process becomes swamped and does not respond to OPMN

Error: Process ping Failed: HTTP_Server`HTTP_Server~1

As per the metalink note :ID 1103744.1

The reason for issue is as below .

As the NAS mount gets busier, the HTTP server process becomes swamped and does not respond to OPMN. OPMN then restarts the process, causing all forms users connected to that Application server to fail with the FRM-92100 error.

Self service session users are much less likely to notice the issue as most self service application screens are stateless HTML, so no context is lost when the HTTP server is bounced.

But the recommended settings for the Network-attached storage (NAS) file system have not been implemented.

Solution

To implement the solution, please execute the following steps:

1:- Stop ALL middle tier services
2:- Update the $CONTEXT_FILE and change "s_lock_pid_dir" to a directory on a local disk.

For example

/d01

3:- Run autoconfig

4:- Ensure that the NAS device is configured with the correct mount options.

On Linux, it should be using "nolock" option.
On Solaris, it should be using "llock" option.

5:- Start ALL middle tier services
6:- Retest the issue.
7:- Migrate the solution as appropriate to other environments.

enjoy madi......