TNS-12549: TNS:operating system resource quota exceeded

-
Today I faced a new issue after refreshed my TEST Instance. After the refresh has completed, took a complete bounce on both DB and APPS Tiers. While bringing back the DB, listener process is not getting started and throws the below error. Quick googling provide me the solution for this issue.

Issue: 

TNS-12549: TNS:operating system resource quota exceeded
TNS-12560: TNS:protocol adapter error
TNS-00519: Operating system resource quota exceeded
Linux Error: 28: No space left on device

 Solution: 

Delete unwanted files under the /var mount point or under the /var/tmp folder. Now re-start the listener and this time, listener will start without any issues.

Ref : Listener / Database Startup fails with underlying OS error Linux Error: 28: No Space Left On Device (Doc ID 553709.1)
****************************நன்றி****************************

Comments

Post a Comment

Popular posts from this blog

Common R12.2 adcfgclone Issues

-
ERROR: Failed to configure the target system – Failed to enable EBS_LOGON trigger The clone procedure for EBS R12.2 is quite different when compared with EBS R12.1. This post covers very generic   issues we may encounter while configuring the target server as a part of clone Process. ERROR : 1 Checking the port pool 6 done: Port Pool 6 is free Report file located at /u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/admin/out/portpool.lst The new APPL_TOP context file has been created : /u01/appl_PROD/PROD/fs2/inst/apps/PRODERP_erpnode3/appl/admin/PRODERP_erpnode3.xml Check Clone Context logfile /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/bin/CloneContextPatch_0811105848.log for details. FMW Pre-requisite check log file location : /u01/appl_PROD/PROD/fs1/EBSapps/comn/clone/FMW/logs/prereqcheck.log Running: FMW pre-req check... ERROR: Run file system configuration has failed Check the logfile /u01/appl_PROD/PROD/fs1/inst/apps/PRODERP_erpnode3/admin/l...
Read more

REP-3000: Internal error starting Oracle Toolkit

-
Image
Resolving "REP-3000: Internal error starting Oracle Toolkit" in Oracle EBS (11i / R12) When running concurrent programs in Oracle E-Business Suite (EBS) that produce PDF , PostScript , or HTML  output, DBAs frequently encounter the infamous runtime exception: ' REP-3000: Internal error starting Oracle Toolkit' .   This issue is notorious for disrupting the Output Post-Processor (OPP)  and concurrent manager operations across both Linux and UNIX platforms. In this post, we will examine the architectural reason behind the REP-3000 error, walk through testing the OS-level X11 display environment, update the EBS Context File, and ensure persistent display settings across AutoConfig executions.  1. Understanding the Cause: Why Does Oracle Reports Need a DISPLAY Variable? The core engine responsible for generating character-based, PDF, or PostScript reports in legacy Oracle Developer / Oracle Reports (such as ' rwrun'  or ' rwserver' ) relies on Oracle Toolk...
Read more

Error 404 -- Not Found From RFC 2068 hypertext Transfer Protocol -- HTTP/1.1

-
Image
In my environment we are having EBS(12.2.5) running with 12.1.0.2 database. One day in our DEV Instance  Front-End is not opening and faced the below error. So I followed the below steps as a solution and it worked. First, generate the JAR files Next, reload the generated jar files to the respective database  Now compile the APPS schema to reduce the count of Invalid objects. Once everything completed, you can clear your browser cache and try to login to the application., but normally the above steps will be accompanied by clearing the middle tier cache. So I gave the below steps to clear the middle tier cache from backend. To clear the cache, follow the below steps. Stop the application services Navigate to $OA_HTML/cabo/images/cache Take a backup of contents of the folder cache and then clear all the contents inside that cache folder Navigate to $OA_HTML/cabo/styles/cache Take a backup of contents of the folder ca...
Read more