Posts

Performance of concurrent request

 Performance of concurrent request can be tracked in many ways. Please perform the below steps and provide the output to the cases 1. Check the SID of the concurrent request using query: SELECT a.request_id, d.sid, d.serial# ,d.osuser,d.process , c.SPID ,d.inst_id FROM apps.fnd_concurrent_requests a,apps.fnd_concurrent_processes b,v$process c,v$session d WHERE a.controlling_manager = b.concurrent_process_id AND c.pid = .oracle_process_id AND b.session_id=d.audsid AND a.request_id =&req_id AND a.phase_code = 'R'; 2. Get the row fetched using the SID from step 1. column name format a30 word_wrapped column vlu format 999,999,999,999 select b.name, a.value vlu from v$sesstat a, v$statname b where a.statistic# = b.statistic# and sid =&sid and a.value != 0 and b.name like '%row%' 3. Check Database session status and what it is running set echo off set linesize 132 set verify off set feedback off set serveroutput on; declare SID number := 0 ; SERIAL number := 0 ; usern

11G ODI Temp usage

OBIA 11g ODI Temporary Table Consume Large Tablespace, How To Purge These Tables ? (Doc ID 1572972.1) To BottomTo Bottom APPLIES TO: Business Intelligence Applications Consumer - Version 11.1.1.7.0 and later Information in this document applies to any platform. GOAL There are some temporary tables consuming huge amounts of space in the DW_DATA tablespace. The table's name listed as below: C$_<Session ID number>.1GB How can we purge these data? and when to purge these data ? SOLUTION These tables are automatically purged once the interface is run successfully. If there are failed sessions, then this table is not dropped immediately. This helps in debugging the failed sessions. At the end of the load plan which  is generated using Load Plan Generator (LPG), we have a step called Finalize Batch Load , under which there is a step called Clean Work and Flow Tables. This automatically drops any such stale tables that are older than 30 days. You can reduce this default of 30 day
 How to Manually Delete AWR Snapshots We have to manually purge the Optimizer Statistics, split the partitions of AWR objects and purge the AWR Snapshots manually. 1.) Run the below script to check the current space usage of Optimizer Statistics Histogram & AWR tables, its relevant indexes in SYSAUX tablespace.      SQL> conn / as sysdba      SQL> @?/rdbms/admin/awrinfo.sql      Output is written to awrinfo.lst in the current working directory 2.) Check the statistics availablility from Optimizer Statistics Histogram table by number of days.     SQL>  select systimestamp - min(savtime) from sys.wri$_optstat_histgrm_history; The query will return a result similar to the followiing: SYSTIMESTAMP-MIN(SAVTIME) ---------------------------- +000000099 22:30:28.418491 3.) Purge the Statistics by altering the number of days. i.e for this case the number of days are 7, it will purge stats more than 7 days old     SQL>  exec dbms_stats.purge_stats(sysdate - 7);     Executing DBMS
Image
State management from RMAN to Media Management Layer has time out Normal RMAN backup communication to Media API has fail on returning control to Oracle RMAN Waiting for 'Backup: sbtbackup' ORA-7445 core dump [strlen()+80] Oracle RMAN to Tape has fail from media vendor code for Media Management Layer
 For EBS upgrade to 19c, this method provides the functionality of UTL_FILE_DIR in the 19c using Database Directory Objects. Migrating UTL_FILE_DIR Settings when Upgrading to Oracle Database 19c Perform the steps in this section as part of your database upgrade when you are instructed to store the UTL_FILE_DIR parameter values in one of the following documents: Interoperability Notes: Oracle E-Business Suite Release 12.2 with Oracle Database 19c ,  Document 2552181.1 Using Oracle 19c RAC Multitenant (Single PDB) with Oracle E-Business Suite Release 12.2 ,  Document 2530665.1 Interoperability Notes: Oracle E-Business Suite Release 12.1 with Oracle Database 19c ,  Document 2580629.1 Using Oracle 19c RAC Multitenant (Single PDB) with Oracle E-Business Suite Release 12.1 ,  Document 2530680.1 You should run the  txkCfgUtlfileDir.pl  script twice in different modes to complete this task. First you run the script in  getUtlFileDir  mode to retrieve the directory paths formerly specified in t

12c: emctl start agent Fails or Hangs or Timeout or Connection Refused

EM 12c: emctl start agent Fails or Hangs or Timeout or Connection Refused Due to PKCS11 'security.pkcs11.P11SecureRandom.implNextBytes' Reported in Thread Dump 'Hang detected' (Doc ID 1427773.1) APPLIES TO: Enterprise Manager Base Platform - Version 12.1.0.1.0 to 12.1.0.2.0 [Release 12.1] Oracle Solaris on SPARC (64-bit) SYMPTOMS $AGENT_INST/bin/emctl start agent fails to start or gets hung Oracle Enterprise Manager Cloud Control 12c Release 2 Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved. Starting agent ........................................................................................... OR $AGENT_INST/bin/emctl start agent fails with following error Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0 Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved. Agent status could not be determined. Check the agent process Consult the log files in: /oracle/product/Agent_home/agent_inst/sysman/log $AGENT_INST/bin/emctl