ORA-02394: exceeded session limit on IO usage error

This error comes, when the sessions exceeds the value of LOGICAL_READS_PER_SESSION defined in user profile. To fix it , We need to increase the value of LOGICAL_READS_PER_SESSION in the user profile.

 ORA-01102: Cannot Mount Database In EXCLUSIVE Mode

This error comes, when cluster_database parameter is set to false. Change it to TRUE and try to start again.

 OCI/DLL Not Found(Cannot load OCI DLL:<path to OCI.DLL>)

This problem commonly occurs when customers use a 64-bit Oracle client, which is not supported. Toad requires a 32-bit client.

If you have a 32-bit client, make sure that the Oracle BIN directory is in your system path. This directory will be ORAWIN\BIN, or ORANT\BIN, or something similar.

To check your path, Open a command line window, type PATH, and then press Enter.

 ORA-00020: maximum number of processes exceeded

ps -ef|grep pmon

kill -9 

startup nomount

SQL> alter system set processes=2000 scope=spfile; 

startup force

 Some of the ports specified for the patch file system are not available when running prepar

[root@proderp ~]# netstat -nlp | grep 10000/anyport

kill the process ID, if  it is other than EBS is using

 Nodes x are listed in the ADOP_VALID_NODES table but not in the FND_NODES table

This is how to fix it:

Logon to sqlplus as applsys: sqlplus applsys

On sqlplus:

truncate table fnd_oam_context_files;

truncate table fnd_nodes;

truncate table adop_valid_nodes;

Run autoConfig on the DB tier

Run autoconfig on the run file system

Logon to sqlplus as system: alter trigger ebs_logon disable;

Run Autoconfig on the patch file system

Logon to sqlplus as system: alter trigger ebs_logon enable;

 ADOP fails with [ERROR] ETCC not run in the database node DBHOSTNAME in R12.2

Reason:

It might be due to mismatch in host name between APPS.FND_NODES and APPLSYS.TXK_TCC_RESULTS tables.

Solution:

1. Login to the database as APPS schema.

2. Validate the data in FND_NODES  and TXK_TCC_RESULTS  table.

3. Download the ETCC Patch - 17537119 ,unzip the patch and  run the following on the Database Node (Recommended)

Please note if it's a RAC database you have to run on all nodes individually.

sh checkDBpatch.sh

or 

3. Update the correct node name in APPLSYS.TXK_TCC_RESULTS table.

 ORA-01113: file x needs media recovery Error

% oerr ora 01113

01113, 00000, “file %s needs media recovery”

// *Cause: An attempt was made to online or open a database with a file that

// is in need of media recovery.

// *Action: First apply media recovery to the file.

SQL> startup mount

2. Find the name of the redo log file which belongs to the active group

SQL> SELECT MEMBER FROM V$LOG G, V$LOGFILE F WHERE G.GROUP# = F.GROUP# AND G.STATUS = 'CURRENT';

SQL> select GROUP#, STATUS from v$log;

SQL> alter system set "_allow_resetlogs_corruption"=TRUE scope=spfile;

SQL> shutdown immediate;

SQL> startup mount;

3. Using a backup control file, start the cancel based recovery. The system may suggest a non-existing archive log

— ignore it and specify the log file name {with full path} that you got in the above step

SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL

ORA-00279: change 21375038 generated at 09/21/2007 20:12:47 needed for thread 1

ORA-00289: suggestion : /export/pspp/oracle/dbs/arch1_4_633901491.dbf

ORA-00280: change 21375038 for thread 1 is in sequence #4

Specify log: {=suggested filename AUTO CANCEL}

/OraRedo/RedoLogFiles/siamst_log01.dbf

Log applied.

Media recovery complete.

If no luck Cancel < -- Enter CANCEL here

4. Finally open the database in RESETLOGS mode.

It is recommended to reset the online logs after incomplete recovery or recovery with a backup control file

SQL> ALTER DATABASE OPEN RESETLOGS;

Database altered.