Showing posts with label Database. Show all posts
Showing posts with label Database. Show all posts

Thursday, November 6, 2014

How to create .dbc file in oracle

 

Navigate to $INST_TOP/admin/install directory

Find the adgendbc.sh script

Run the command adgendbc.sh, It will generate .dbc file under $INST_TOP/appl/fnd/secure

Saturday, December 28, 2013

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

Friday, December 27, 2013

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.