Archive for the ‘Oracle Queries’ Category

« Older Entries

Find Long Running Concurrent Request In Oracle

October 1st, 2024, posted in Oracle EBS Application, Oracle Queries
Share

Looking on how to check long running concurrent request in Oracle Apps 11i or R12? Here’s the overview of the SQL query script to detect the session information of each program.First you need to get the listing of running concurrent request in Oracle Apps 11i or R12. You can use the SQL query script as below to obtain the list of running request.

SELECT a.request_id
,a.oracle_process_id "SPID"
,frt.responsibility_name
,c.concurrent_program_name || ': ' || ctl.user_concurrent_program_name
,a.description
,a.ARGUMENT_TEXT
,b.node_name
,b.db_instance
,a.logfile_name
,a.logfile_node_name
,a.outfile_name
,q.concurrent_queue_name
,a.phase_code,a.status_code, a.completion_text
, actual_start_date
, actual_completion_date
, fu.user_name
,(nvl(actual_completion_date,sysdate)-actual_start_date)1440 mins ,(SELECT avg(nvl(a2.actual_completion_date-a2.actual_start_date,0))1440 avg_run_time
FROM APPLSYS.fnd_Concurrent_requests a2,
APPLSYS.fnd_concurrent_programs c2
WHERE c2.concurrent_program_id = c.concurrent_program_id
AND a2.concurrent_program_id = c2.concurrent_program_id
AND a2.program_application_id = c2.application_id
AND a2.phase_code || '' = 'C') avg_mins
,round((actual_completion_date - requested_start_date),2) * 24 duration_in_hours
FROM APPLSYS.fnd_Concurrent_requests a,APPLSYS.fnd_concurrent_processes b
,applsys.fnd_concurrent_queues q
,APPLSYS.fnd_concurrent_programs c
,APPLSYS.fnd_concurrent_programs_tl ctl
,apps.fnd_user fu
,apps.FND_RESPONSIBILITY_TL frt
WHERE a.controlling_manager = b.concurrent_process_id
AND a.concurrent_program_id = c.concurrent_program_id
AND a.program_application_id = c.application_id
AND a.phase_code = 'R'
AND a.status_code = 'R'
AND b.queue_application_id = q.application_id
AND b.concurrent_queue_id = q.concurrent_queue_id
AND ctl.concurrent_program_id = c.concurrent_program_id
AND a.requested_by = fu.user_id
AND a.responsibility_id = frt.responsibility_id
ORDER BY a.actual_start_date DESC

You can see the request id and other relevant information from the result. Based on the SPID associated to each running request, query the v$session or v$session_longops table to see what is the request id doing in the backend.

SELECT b.sid, b.serial#, a.spid, b.program, b.osuser, b.machine,
b.type, b.event, b.action, b.p1text, b.p2text, b.p3text, b.state, c.sql_text,b.logon_time
FROM v$process a, v$session b, v$sqltext c
WHERE a.addr=b.paddr
AND b.sql_hash_value = c.hash_value
AND b.STATUS = 'ACTIVE'
AND a.spid = '11696'
ORDER BY a.spid, c.piece

Replace v$session with gv$session if the database is running on RAC environment. Enable or set trace if you wish to know more details on the session.

Share
read more no comments

Steps to Kill Long Running Concurrent Job in R12

July 8th, 2024, posted in Oracle Queries
Share

Step 1) Find SID and Serial Number for Concurrent Job

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,
gv$process c,
gv$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 = 2063673
AND a.phase_code = 'R';

Step 2) Kill the long running session

--ALTER SYSTEM KILL SESSION 'SID, serial#' IMMEDIATE;
ALTER SYSTEM KILL SESSION '523, 4965' IMMEDIATE;

Step 3) Update fnd_concurrent_requests table to mark the request in error and completed

update fnd_concurrent_requests
set status_code='X', phase_code='C'
where request_id=2063673;

commit;

update fnd_concurrent_requests
set status_code='E', phase_code='C'
where request_id=2063673;

commit;

If this does not solve your problem then try restarting Standard Concurrent Manager and Output Post Processor Concurrent Manager.

Share
read more no comments

ORA-01552: cannot use system rollback segment for non-system tablespace ‘TEMP’

April 15th, 2024, posted in Oracle Queries
Share

ORA-01552: cannot use system rollback segment for non-system tablespace “string”

Cause: Used the system rollback segment for non-system tablespace operations.

If this is a clone database, this will happen when attempting any data modification  outside the UNDOTBS tablespace.

Solution :

1) Switch to Automatic Undo Management

$ sqlplus / as sysdba
alter system set undo_management=auto scope=spfile;
2) Restart the database.
SQL> Shutdown immediate;
SQL> startup
Share
read more no comments

ORA-27037: Unable To Obtain File Status

February 4th, 2024, posted in Oracle Queries
Share
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 12/24/2023 09:23:19
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /u03/archive2/1_4134_983485279.dbf
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3

This ORA-19625 errors are related with file specified as input to a copy or backup operation, or as the target for an incremental restore, could not be identified as an Oracle file. An OS-specific error accompanies this error to help pinpoint the problem.
To solve this error, Specify an different file and retry the operation.
Try to run the following commands.

RMAN> crosscheck copy of archivelog all
RMAN> crosscheck archivelog all
RMAN> resync catalog
RMAN> delete force obsolete;
RMAN> delete expired archivelog all ;

If the problem is not solved,then Files were deleted at OS level and Archive log files were deleted at OS level. To solve this error, Run the following commands.

RMAN> Change archivelog '' UNCATALOG ;

Please note the first archive log name would be present in the error message ORA-19625:
For example :-

RMAN-06059: expected archived log not found, lost of archived log
ORA-19625: error identifying file /var/opt/arch_oltp28_1_744738.arc
ORA-27037: unable to obtain file status
RMAN> Change archivelog '/var/opt/arch_oltp28_1_744738.arc' uncatalog;

Run the archive log backup command check if you still get the error
Keeping specify the archive log file name reported in ORA-19625 till backup of archive log goes fine
Or

RMAN> Change Archivelog all Uncatalog ;

Please note the above command will uncatalog the information about the Archive log from catalog database.

Share
read more no comments

Oracle APPS User Password From Backend

November 19th, 2023, posted in Oracle Queries
Share

Below steps to get the forgotten apps user password in oracle apps R12.

Step 1:

Connect to sys user

SQL> show user USER is “SYS”

Step 2:

Create function to know the encrypted password

SQL>create FUNCTION
apps.decrypt_pin_func(in_chr_key IN VARCHAR2,in_chr_encrypted_pin IN VARCHAR2)
RETURN VARCHAR2 AS LANGUAGE JAVA NAME
‘oracle.apps.fnd.security.WebSessionManagerProc.decrypt(java.lang.String,java.lang.String) return java.lang.String’;
/ Function created.

Step 3:

Query for password
SQL> set linesize 200 long 300
SQL> select ENCRYPTED_FOUNDATION_PASSWORD from apps.fnd_user where USER_NAME=’GUEST’; ENCRYPTED_FOUNDATION_PASSWORD
—————————————————————————————————- ZGC679A64D8394F23E12CA4EB288F264FC09EBC9144C06181E921F88A972E231E9B530E7810DE42AC6103FC3CCD317CA3391

Step 4:

Apps password using encrypted guest password

SQL> SELECT
apps.decrypt_pin_func
(‘GUEST/ORACLE’,
‘ZGC679A64D8394F23E12CA4EB288F264FC09EBC9144C06181E921F88A972E231E9B530E7810DE42AC6103FC3CCD317CA3391’)
from dual;
APPS.DECRYPT_PIN_FUNC
(‘GUEST/ORACLE’,
‘ZGC679A64D8394F23E12CA4EB288F264FC09EBC9144C06181E921F88A972E231E9B530E7810DE42AC6103FC3CCD317CA3391’)
———————————————————————————————————————————————
APPS

Step 5:

Test the password is working fine or not

SQL> conn apps/APPS123;
Connected.
Share
read more no comments
« Older Entries