In R12 Get APP-FND-01564 ORA-01116 ORA-01110 ORA-27041 Errors When Running Concurrent Requests

In our live server we are getting below error message:

In R12 Get APP-FND-01564 ORA-01116 ORA-01110 ORA-27041 Errors When Running Concurrent Requests

I raised SR and found the following solution:

Cause
The error would appear if the output of the lsof command is greater than the value of the ulimit.


Use the following command to check the number of open files used by applmgr:


$ lsof -u applmgr | wc -l
Compare the result to the value in ulimit:

$ ulimit -n


Solution
Modifying the Number of Open File Descriptors

Open the /etc/security/limits.conf file and change the existing values for "hard" and "soft" parameters as follows. Restart the system after making changes.


Note:
If the current value for any parameter is higher than the value listed in this document, then do not change the value of that parameter.


* hard nofile 65535
* soft nofile 4096
* hard nproc 16384
* soft nproc 2047

Note:
* means all users listed in /etc/passwd would inherit the above values.

but no luck, after doing all above still the problem occurs...

then it is found this error occurring because of corrupted nls files (eg: lx40030.nlb)

kindly do the following step to resolve the above matter:

1.stop all applications services & DB services ,and recreate the nls 9idata directory :-

-backup and remove the corrupted $ORACLE_HOME/nls/data/9idata directory

-Re-Create $ORACLE_HOME/nls/data/9idata directory

On the database server node, as the owner of the Oracle RDBMS file system and database instance, run the $ORACLE_HOME/nls/data/old/cr9idata.pl script to create the $ORACLE_HOME/nls/data/9idata directory.

eg: How to run cr9idata.pl script

$perl cr9idata.pl {hit enter}

After creating the directory, make sure that the ORA_NLS10 environment variable is set to the full path of the 9idata directory whenever you enable the 10g Oracle home.

-The above steps must be performed after patch installation and before lauching the application server environment.

3.retest the issue.

If above changes didn't help then apply the following patch and repeat the same steps as mentioned above.

Patch 5257698