Archive for the ‘Oracle EBS Application’ Category

Adcfgclone error Oracle error -25153: ORA-25153: Temporary Tablespace is Empty has been detected in

October 27th, 2019, posted in Oracle EBS Application, Oracle Queries
Share
 | 50% completed ERROR: InDbCtxFile.uploadCtx() : Exception : Error executng BEGIN fnd_gsm_util.append_ctx_fragment(:1,:2,:3); END;: 1; Oracle error -25153: ORA-25153: Temporary Tablespace is Empty has been detected in FND_GSM_UTIL.APPEND_CTX_FRAGMENT.
oracle.apps.ad.autoconfig.oam.InDbCtxFileException: Error executng BEGIN fnd_gsm_util.append_ctx_fragment(:1,:2,:3); END;: 1; Oracle error -25153: ORA-25153: Temporary Tablespace is Empty has been detected in FND_GSM_UTIL.APPEND_CTX_FRAGMENT.
at oracle.apps.ad.autoconfig.oam.InDbCtxFile.uploadCtx(InDbCtxFile.java:220)
at oracle.apps.ad.autoconfig.oam.CtxSynchronizer.uploadToDb(CtxSynchronizer.java:328)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBCtx(FileSysDBCtxMerge.java:678)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.updateDBFiles(FileSysDBCtxMerge.java:222)
at oracle.apps.ad.context.CtxValueMgt.processCtxFile(CtxValueMgt.java:1680)
at oracle.apps.ad.clone.ApplyApplTop.runCVM(ApplyApplTop.java:510)
at oracle.apps.ad.clone.ApplyApplTop.runAutoConfig(ApplyApplTop.java:552)
at oracle.apps.ad.clone.ApplyApplTop.doConf(ApplyApplTop.java:339)
at oracle.apps.ad.clone.ApplyApplTop.doApply(ApplyApplTop.java:382)
at oracle.apps.ad.clone.ApplyApplTop.(ApplyApplTop.java:267)
at oracle.apps.ad.clone.ApplyAppsTier.(ApplyAppsTier.java:105)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:67)
at java.lang.Thread.run(Thread.java:595)

 

 

Solution:

Add Tempfile to the temporary tablespace. It will resolve the issue !!

Share

ORA-48913 Writing into trace file failed, file size limit 10485760 reached

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

ORA-48913: Writing into trace file failed, file size limit [10485760] reached

ERROR:-
Non critical error ORA-48913 caught while writing to trace file
"/apps/PROD/db/diag/rdbms/prod/PROD/trace/PROD_dbrm_6874.trc"
Error message: ORA-48913: Writing into trace file failed, file size limit [10485760] reached.

In some environments DBAs limit the size of trace files generated by the database. This included all trace files that could get generated under USER_DUMP_DEST/DIAGNOSTIC_DEST). The parameter to set the limit for trace files is MAX_DUMP_FILE_SIZE and its value is in OS number of blocks. After setting this value, if any trace file size would increase form the size specified in this parameter, ORA-48913 would be recorded in alert log file.

 

Cause : 

The reason was Parameter MAX_DUMP_FILE_SIZE is set too low.

Solution :

We can increase the setting for the parameter MAX_DUMP_FILE_SIZE or set it to unlimited
MAX_DUMP_FILE_SIZE specifies the maximum size of trace files (excluding the alert file). Change this limit if you are concerned that trace files may use too much space.
A numerical value for MAX_DUMP_FILE_SIZE specifies the maximum size in operating system blocks.
A number followed by a K or M suffix specifies the file size in kilobytes or megabytes.
The special value string UNLIMITED means that there is no upper limit on trace file size. Thus, dump files can be as large as the operating system permits.


SQL> show parameter max_dump_file

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
max_dump_file_size string 20000


SQL> alter system set max_dump_file_size=UNLIMITED scope=both;

System altered.


SQL> show parameter max_dump_file

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
max_dump_file_size string UNLIMITED

 

OR

 

SQL> show parameter dump_file

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
max_dump_file_size string 20480

SQL> select max(lebsz) from x$kccle;

MAX(LEBSZ)
----------
512

SQL> alter session set max_dump_file_size=’1024M’;

Session altered.

SQL> show parameter max_dump_file_size

NAME TYPE VALUE
———————————— ———– ———–
max_dump_file_size string 1024M
Share

How To Cancel or Restart the Cost Manager

December 18th, 2018, posted in Concurrent Request, Oracle EBS Application, Oracle Queries
Share

Behavior of Cost Manager:

Cost manager is not a typical concurrent manager that it finishes after is costing some transactions.

Cost manager it is rescheduling itself based on the the process interval specified in interface managers form.

Cost Manager should stay in this status : “Pending Scheduled” and will restart itself based on the process interval specified in interface managers form. It calculates the re-launch time as start time + process interval.

 

2 – Run the cmclean.sql script available from MOS Note 134007.1

3 – Restart the Cost Manager

     Inventory> Setup : Transactions> Interface Managers

     Select  ‘Cost Manager’ – choose Tools > Launch Manager

Also review << Note 304313.1>>

  1. Restart the concurrent processes.
  2. Run the below select and update scripts to update the uncosted and/or erred records in the tables indicated.
  3. Relaunch the Cost Manager. Select and Update scripts for paragraph 5. above:

SQL> select count(*) from MTL_MATERIAL_TRANSACTIONS where COSTED_FLAG = ‘E’;

SQL> select count(*) from MTL_MATERIAL_TRANSACTIONS where COSTED_FLAG = ‘N’;

SQL > Update MTL_MATERIAL_TRANSACTIONS set COSTED_FLAG = ‘N’, TRANSACTION_GROUP_ID = NULL where COSTED_FLAG = ‘E’ or COSTED_FLAG = ‘N’;

If there are unprocessed records in MTL_MATERIAL_TRANSACTIONS_TEMP, then, also run the following:

  1. To see if there are records in mtl_material_transactions_temp, run:

SQL> select * from mtl_material_transactions_temp;

  1. If rows are returned from the SQL in a. above, then run:

SQL> Update MTL_MATERIAL_TRANSACTIONS_TEMP Set PROCESS_FLAG = ‘Y’, LOCK_FLAG = ‘N’, TRANSACTION_MODE = 3, ERROR_CODE = NULL Where TRANSACTION_HEADER_ID = ;

(OR)

Resubmit all transactions using this procedure:

  • Shut down the cost manager
  • Make a backup of the table mtl_material_transactions
  • Perform the following update

SQL > update mtl_material_transactions

set costed_flag = ‘N’,

transaction_group_id = NULL,

transaction_set_id = NULL

where costed_flag = ‘E’ or costed_flag = ‘N’ ;

Commit ;

 

 

Update MTL_MATERIAL_TRANSACTIONS set COSTED_FLAG = ‘N’, TRANSACTION_GROUP_ID = NULL where COSTED_FLAG = ‘E’ or COSTED_FLAG = ‘N’;


 

Uncosted/failed transactions can be resubmitted through the application itself.
Costs -> View Transactions -> Material Transactions.
From the menu, Tools Select All: Tools Submit All

Else, use the following script to submit the records in MMT table:

    update mtl_material_transactions MMT
    set MMT.costed_flag = 'N',
    MMT.error_code = NULL,
    MMT.error_explanation = NULL,
    MMT.transaction_group_id = NULL,
    MMT.transaction_set_id = NULL
    where MMT.organization_id = &organization_id
    and MMT.costed_flag in ('N','E')
    and NOT  EXISTS ( SELECT 1
    FROM MTL_TRANSACTION_ACCOUNTS MTA
    WHERE MMT.TRANSACTION_ID = MTA.TRANSACTION_ID);

commit;

  1. Re-start the cost manager.
    Restart the cost manager via Inventory > Setup > Transactions >
    Interface Managers > Tools > Launch Manager. Set up a periodic scheduling interval of every five
    minutes.
    Note — Cost Manager should not be scheduled through request form to run Periodically.
    Cost Manger  should be scheduled through Interface managers only.
Share

Find Concurrent Manager Jobs By Query

May 6th, 2018, posted in Concurrent Request, Oracle Queries
Share

Query :

 

select sess.sid,
 sess.sql_hash_value,
 oracle_process_id OS_PROCESS_ID,
 fusr.description user_name ,
 fcp.user_concurrent_program_name progName,
 to_char(actual_Start_date,'DD-MON-YYYY HH24:MI:SS') StartDate,
 request_id RequestId,
 (sysdate - actual_start_date)*24*60 ETime_in_Mins
from apps.fnd_concurrent_requests fcr,
 apps.fnd_concurrent_programs_tl fcp,
 apps.fnd_user fusr,
 v$session sess
where fcp.concurrent_program_id = fcr.concurrent_program_id
 and fcr.program_application_id = fcp.application_id
 and fcp.language = 'US'
 and fcr.phase_code = 'R'
 and fcr.status_code = 'R'
 and fcr.requested_by = fusr.user_id
 and fcr.oracle_session_id = sess.audsid (+)
-- and p.addr = sess.paddr
 order by 6 DESC
Share

Cancel All Pending Concurrent Request

December 27th, 2017, posted in Concurrent Request
Share

Oracle : Cancel All Pending Concurrent Request

Updating base tables directly is not supported or recommended by Oracle – this update would be OK to execute in a non-production instance. In a production instance, use APIs or cancel the pending requests thru the forms interface

 

update FND_CONCURRENT_REQUESTS set phase_code='C',status_code='D' where phase_code='P' ;
Share