Explore APPSDBA

Search This Blog

on April 18, 2017

Get link
Facebook
X
Pinterest
Email
Other Apps

Please find the scripts Monitoring Scripts here

Get link
Facebook
X
Pinterest
Email
Other Apps

Comments

HOW TO GET SQL_ID & SQL_TEXT FOR CONCURRENT REQUEST TROUBLESHOOTING

>> First get the Concurrent Request you are facing issue with. >> Then get the SID information for a running request by using below query connecting as apps user. SQL> column process heading "FNDLIBR PID" SELECT a.request_id, d.sid, d.serial# ,d.osuser,d.process 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 = b.oracle_process_id AND b.session_id=d.audsid AND a.request_id = &Request_ID AND a.phase_code = 'R'; >> AFter that get the SQL_ID and SQL_TEXT which will be helpfull for analysing for any conflicts by using v$locked_object and many so more options. col action format a20 col module form a30 select sid,sql_id,action,module from v$session where action like '%Conc%'; select sql_text from v$sqlarea where sql_id='SQL_ID'; Click here to see the SQL Queries To Analyze All Concurrent Requests i...

TO CHECK THE LOCKS FOR A PARTICULAR CONCURRENT PROGRAM OR REQUEST

If any Concurrent request is slow or takes more than normal time to complete,follow the below steps first to verify .. HighLevel Steps.. SQL >select * from v$session where process in(select os_process_id from fnd_concurrent_requests where request_id='<Req Id>'); Get SID from above sql. Take that sid and find object_id's from below command SQL >select * from v$locked_objects where session_id='SID' Now take all the object_id's and check any other session is locking those object_ids apart from the above SID... SQL >select * from v$locked_objects where object_id ='' if any session is locking check the status of that session from v$session. if that is inactive kill that session ... to free up the resource SQL >alter system kill session 'SID,SERIAL#';

ORA-00955,ORA-39120, ORA-02266 -Import Error due to referenced constraints Tips

Errors: ORA-00955: name is already used by an existing object ORA-39120: Table "OWNER"."TABLE_NAME" can't be truncated, data will be skipped. Failing error is: ORA-02266: unique/primary keys in table referenced by enabled foreign keys Most frequently we encounter issues while importing the dumps due to reference constraints which doesn't allow to insert data into the tables . Solution: Disable all the constraints related to the owners and reimport . To Findout constraints enabled on the tables use the below query . select 'alter table '||a.owner||'.'||a.table_name||' disable constraint '||a.constraint_name||';' from all_constraints a, all_constraints b where a.constraint_type = 'R' and a.status='ENABLED' and a.r_constraint_name = b.constraint_name and a.r_owner = b.owner and a.r_owner = '&OWNER'; Disable the constraints and rerun the import .Once import completed please re-en...

Powered by Blogger

Comments

Post a Comment