Sujeet APPS DBA

###How to Kill Zombie Processes on Linux  Defunct processes may also be known as "zombie" processes. They do not use any system resources - CPU, memory etc. but may be seen as entries in their respective operating system process table.   A zombie is already dead, so you cannot kill it. To clean up a zombie, it must be waited on by its parent, so killing the parent should work to eliminate the zombie. (After the parent dies, the zombie will be inherited by pid 1, which will wait on it and clear its entry in the process table.) If your daemon is spawning children that become zombies, you have a bug. Your daemon should notice when its children die and wait on them to determine their exit status.   ##What Causes Zombie Processes on Linux?  A poorly written parent process might not call the wait() function when the child process is created. This means nothing is watching for state changes in the child process, and the SIGCHLD signal will be ignored. Or, perhaps another applicati

 How to increase processes, sessions, and transactions parameters in Oracle 12R1. Whenever DB processes are utilized 100% then it’s NOT allowed any new sessions/connections to DB’s instances and we get the below error: ORA-00020: No more process state objects available ORA-20 errors will not be written to the alert log for If we are planning to increase “PROCESSES” parameter so, we  should also plan to increase the “SESSIONS” and “TRANSACTIONS” parameters.  A basic formula for determining  these parameter values is as follows:           processes=x         sessions=x*1.1+5         transactions=sessions*1.1 Cause: All process state objects are in use. Action: Increase the value of the PROCESSES initialization parameter. Before starting on the solution, we understand what is processes, sessions & transactions: PROCESSES: It specifies the maximum number of operating system user processes that can simultaneously connect to Oracle. Its value should allow for all background processes

 This error may be returned if you are trying to export or import using oracle data pump,  but invalid directory name has been provided during this process.  Following is an example of this. Error: [oracle@hostname ~]$ expdp system/manager DIRECTORY=dpump_dir DUMPFILE=system.dmp logfile=system.log schemas=system Export: Release 11.2.0.3.0 - Production on Wed Aug 2022 10:07:55  Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Partitioning, Automatic Storage Management, OLAP, Data Mining and Real Application Testing options ORA-39002: invalid operation ORA-39070: Unable to open the log file. ORA-39087: directory name DPUMP_DIR is invalid Solution: Check the directory is exists or not, If not exist then create the directory with proper path:  If the directory exists then check grant on the directory, if the grant missing then provide grant  SQL> CREATE OR REP

SYMPTOMS Using Edge browser when concurrent program output is saved the output file name defaulting to FNDWRR.txt.This is happening only for txt format output type files. Expected Behaviour: --------------------- When concurrent program output is saved the file name should default with program name. For ex: For Active User concurrent program the Output should be Active_Users.txt STEPS ----------------------- The issue can be reproduced at will with the following steps: 1.Using Edge Browser Connect to EBS application 2.Navigate to System administrator responsibility 3.Submit Active User concurrent Program 4.Click On view Output 5.Program output open in edge browser. 6.Save the output using option Ctrl+S This issue is only for output format of type txt and only in Edge browser. Other browsers like the IE, Chrome the concurrent program outputs were getting saved with expected file naming convention. CAUSE Edge browser failed to convert the output file name when using existing viewer optio

Error :- ora-39002 invalid operation ora-39070 unable to open the log file ora-39087 directory name DATAPUMP is invalid Solution :- create a new directory object (as a SYS user or as a user with CREATE ANY DIRECTORY privilege granted), grant READ and WRITE privileges on that DIRECTORY, and perform data pump export/import tasks. Make sure that the /u01/EXPDP_IMPDP directory has 660 permission. create or replace your directory and grant the following privileges' to user(system). [oracle@prod u01]$ mkdir EXPDP_IMPDP [oracle@prod u01]$ chmod 660 EXPDP_IMPDP [oracle@QA u01]$ sqlplus sys/*****@PDB1 as sysdba SQL*Plus: Release 12.2.0.1.0 Production on Thu Jul 7 11:30:58 2022 Copyright (c) 1982, 2016, Oracle.  All rights reserved. Last Successful login time: Sat Jun 25 2022 14:49:08 -04:00 Connected to: Oracle Database 12c EE High Perf Release 12.2.0.1.0 - 64bit Production SQL> create directory EXPDP_IMPDP as '/u01/EXPDP_IMPDP'; Directory created. SQL> GRANT READ, WRITE ON DI

 How to change Oracle Applications R12.1.3 Port-8002 to 8050 Step:-1 Dowm Application Tier [applprod@prd-erp01 ~]$ cd $ADMIN_SCRIPTS_HOME [applprod@prd-erp01 scripts]$ ./adstpall.sh apps/apps Step:-2 Open your  Context XML file for edit it.  Go to Context XML path :- $INST_TOP/appl/admin/ Take backup of .XML file :- cp Oracle_prd-erp01.xml Oracle_prd-erp01.xml-bkp10MAY22 Edit Oracle_prd-erp01.xml file with below parameter port value replace from 8002 to 8050. Change the value from 8002 to be 8050 on the following lines:       <web_port oa_var="s_webport" oa_type="PORT" base="8000" step="1" range="-1" label="Web Listener Port">8050</web_port>       <activewebport oa_var="s_active_webport" oa_type="DUP_PORT"  base="8000" step="1" range="-1" label="Active Web Port">8050</activewebport>       <login_page oa_var="s_login_page">http:/