How to kill the INACTIVE database Session

Find the inactive session:

To find the inactive session from the database to executing below query
 

SELECT s.inst_id, s.sid, s.serial#, p.spid, s.username, s.program FROM gv$session s JOIN gv$process p ON p.addr = s.paddr AND p.inst_id = s.inst_id WHERE s.type != 'BACKGROUND';

Kill the session:

To kill the session use the below script

 SQL> ALTER SYSTEM KILL SESSION 'sid,serial#';

Note:
Killing sessions can be very destructive if you kill the wrong session, so be very careful when identifying the session to be killed. If you kill a session belonging to a background process you will cause an instance crash.


References 
How to Check if Dead Connection Detection (DCD) is Enabled in 9i ,10g and 11g (Doc ID 395505.1
Dead Connection Detection (DCD) Explained (Doc ID 151972.1 

Why several Process remain KILLED in V$SESSION (Doc ID 107686.1

Error while Purg the concurrent request - ORA-0001 unique constraint %s.%s

Error:

while run the purg concurrent program
Error while Purg the concurrent request - ORA-0001 unique constraint %s.%s

Fix:

APPLIES TO:
Oracle Concurrent Processing - Version 12.1.3 and later
Information in this document applies to any platform.
 
SYMPTOMS
While running FNDCPPUR, it errors out the following:
APP-FND-01564: ORACLE error 1 in request
Cause: request failed due to ORA-00001: unique constraint (%s.%s) violated

CAUSE
Bug 13703211 - FNDCPPUR APP-FND-01564: ORA-00001 UNIQUE CONSTRAINT (%S.%S) VIOLATED
Issue happens when running FNDCPPUR with parameters MODE = COUNT and VALUE=1
 
SOLUTION
 
Base bug is from RDBMS and was still in progress when writing this note:
Bug 14013076 - LEN ATTRIBUTE OF VARCHAR STRUCTURE IS CORRUPTED IN BATCH FETCH OF ROWS
Workaround:
Two patches below are necessary for the workaround to work:

- Patch 10106197:R12.FND.B
- Patch 12747284:R12.FND.B
 
Then try to run with FNDCPPUR with same parameters, but with COUNT >= 2. Once completed, you should be able to run it as before with no issue. This is a workaround
because the issue may reappear later.

Error-95493-For the following transaction objects, the column EVENT_ID is missing or has the wrong data type

Issue:

Error-95493-For the following transaction objects, the column EVENT_ID is missing or has the wrong data type

  Error Log:

     95493            Please inform your system administrator or support representative   Error
                        that:

                        For the following transaction objects, the column EVENT_ID is
                        missing or has the wrong data type. This column is mandatory for
                        all transaction objects, and it must have the data type number.



Solution:

Make sure the custom table contain the EVENT_ID column in Header and line table if not 
Add the EVENT_ID column on both header and lines table.

Then click on the "Create and assign sources" now issue will be resolved.

APP-XLA-95388-the transaction does not include all the system transaction identifier

Issue:

APP-XLA-95388-the transaction does not include all the system transaction identifier for the entity of the event class. Please make sure that all the system transaction identifier column are included in this view.

Solution:

Make sure system transaction identifiers with your custom table header_id

ERROR ORA-00020 maximum number of processes (%s) exceeded

Issue:

Error when connecting the database using $sqlplus / ' as sysdba' 

ERROR ORA-00020 maximum number of processes (%s) exceeded

Fix:

Step-1

Restart the server and Edit init.ora file to increase the number of processes.

or 

Connect to sqlplus with sysdba

#sqlplus / ' as sysdba'
$show parameter;
or
$show parameter process;

Step-2

$ALTER SESSION SET processes = 2000 (your value);

Cause:  An operation requested a resource that was unavailable.

            The maximum number of processes is specified by the initialization

             parameter PROCESSES.

            When this maximum is reached, no more requests are processed.

Action: Try the operation again in a few minutes.

            If this message occurs often, shut down Oracle, increase the PROCESSES

            parameter in the initialization parameter file, and restart Oracle.

"Please define a party tax profile option for operating unit & Org_Id"

Error:
Receivables Activity Error
Please define a party tax profile for Operating Unit 159

Solution:

Responsibility: Tax Managers
Navigation: Parties > Party Tax > Profiles

1. Query:
Party Type: Operating Unit Owning Tax Content
Party Name: Populate your Operating Unit Name

2. Click on GO

3. Click on Create Tax Profile and then 

 4. Click only Apply button without doing anything

 Now tax profile created successfully 

Receivables Activity Error: Please Define A Party Tax Profile For Operating Unit & ORG_ID (Doc ID 419019.1)

Oracle E-Business Suite R12 - Layers of Access Control

Successive Layers of Access Control

Access Control with Oracle User Management is implemented in successive layers and each layer builds upon the one that precedes it. Organizations can, optionally, uptake the various layers depending on the degree of automation and scalability they wish to build upon the existing Function and Data Security models.

There are six layers of access control. The Core Security layers include:

•      Function Security

•      Data Security

The next four layers are part of Oracle User Management:

•      Role-Based Access Control

•      Delegated Administration

•      Registration Processes

•      Self Service and Approvals

 

Increasing Flexibility and Scalability

In general, access control with Oracle User Management (OUM) begins with basic system administration tasks, and then progresses to more distributed, local modes of administration, ultimately enabling users to perform some basic, predefined registration tasks on their own. Details of the various levels of access control, and the increasing level of flexibility and automation that they provide are provided later in the lesson. However, the following general guidelines may be considered for now:

System Administrator

Oracle’s Function Security and Data Security mechanisms constitute the base layers of the security system, and contain the traditional system administrative capabilities. Organizations can, optionally, add more layers to the system depending on the degree of flexibility they want.

By themselves, Function Security and Data Security limit the scope of OUM to basic system administration by granting access to specific menus and to the data accessed from within those menus.

Local Administrators

When Role-Based Access Control and Delegated Administration are added to the Data Security and Function Security layers, system administration tasks can be distributed to local administrators who manage a subset of the organization’s users.

End Users

Registration Processes and Self Service and Approvals distribute system administration further by automating some registration tasks so that end users can perform them.

Self Service and Approvals

After the registration processes have been configured as per requirements, individuals can subsequently perform self-service registration tasks, such as obtaining new user accounts or requesting additional access to the system. In addition, organizations can use the Oracle Approvals Management engine to create customized approval routing for these requests.

Example

An organization may enable users to request a particularly sensitive role. However, before the user is granted the role, the organization can specify that two approvers, a manager and a vice president, must provide their approval.