Archive for the ‘Oracle EBS Application’ Category

« Older Entries
Newer Entries »

IAP-CANNOT READ FIELD (FIELDNAME=PARAMETER.CONFIG)

September 8th, 2025, posted in Oracle EBS Application
Share

IAP-CANNOT READ FIELD (FIELDNAME=PARAMETER.CONFIG)
=================================================

#woesOfDBA, #WoesOfDba, #woesOfDBA, #WoesOfDba, woes of dba, Woes Of Dba, immam dba,dba immam, #immam_dba, #immamDba, #dbaimmam, #dba_immam, IAP-CANNOT READ FIELD,

Issue : One of the concurrent request got failed due to below error on 
R12 Clone instance.

Error :- IAP-CANNOT READ FIELD (FIELDNAME=PARAMETER.CONFIG) 

Application Version  :- 12.1.2
Database version : 11.2.0.3.0

Issue cause : 

The ‘APPLFSTT’ parameter didn’t setup to TWO_TASK name in the  MT node 
LISTENER.ora.

MT node listener.ora :-
APPLFSTT=DXXX2I_FO;DXXX2I_BALANCE;DXXX2I,

Solution :-

1. Change the parameter value for ‘APPLFSTT’ in the APPS LISTENER.ora file 
to show TWO_TASK (SID name) value.
Changes :  APPLFSTT=DXXX2I;DXXX2I_FO;DXXX2I_BALANCE;
2. Bounce your middle Tier.
3. Retest the issue. 


Refer Metalink Doc id :Concurrent Processing - Error AP-CANNOT
READ FIELD (FIELDNAME=PARAMETER.CONFIG) When Viewing the 
Concurrent Request Output [ID 466410.1]
Share
read more no comments

ORA-01194: file 1 needs more recovery to be consistent

September 2nd, 2025, posted in Oracle EBS Application, Oracle Queries
Share

ERROR :

SQL> startup
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: ‘/u01/app/oracle/oradata/denemedb/system01.dbf’

SOLUTION :

SQL> show parameter undo

NAME |TYPE |VALUE
— —| — — — | — — — — — —
undo_management |string |AUTO

SQL> alter system set undo_management=manual scope=spfile;

SQL> ALTER SYSTEM SET “_allow_resetlogs_corruption”= TRUE SCOPE = SPFILE;

SQL> ALTER DATABASE OPEN RESETLOGS;

SQL> alter system set undo_management=AUTO scope=spfile;

SQL> shutdown immediate

SQL> startup
Share
read more no comments

Oracle User ICX:Session Timeout Increase In E-Business Suite 12.1/12.2

August 20th, 2025, posted in Oracle EBS Application
Share

ICX:Session Timeout to change the session Timeout in Oracle Apps R122 version:

Increase oracle forms session timeout in r122
To change oracle forms session time out via “ICX:session Timeout” Profile in oracle application.
ICX:Session Timeout is a profile provided in Oracle apps which controls the time for which a session is valid. Post that time out limit, the user gets below error.
Log on session is no longer valid. Would you like to log back in so you can continue working? If you do not log in, any outstanding data changes in your forms will not be saved.

When the user clicks on the Yes button, App opens the login page. Enter the password and login again to continue. Click No to exit from the current session.
30 minutes is the value of this profile in any production instance. It is fine for production instance but for development instance, this may not be ideal, as you will repeatedly get this message and you need to log in again and again.
Just increase the value of this profile to avoid the timeout message.

Set ICX:Session Timeout profile

Now let me show how you can change this profile. You can set this profile at the site or user level. It is always better to set at the user level.

Log in to Oracle Apps Instance. Navigate to System Administrator->Profile->System. Query profile the ICX:Session Timeout for the user. The default value is 30 and is set at the site level. We are going to set it a user level.
Enter the new value greater than 30 and click on Save.
Log off and log in again.

This will make sure that your Oracle apps session will never time out in a smaller interval.

Summary :

ICX:Session Timeout provides an easy way to increase the session limit. It is good to increase only in development or test instance, but production let it be default 30.
This tip should work for both Oracle App 11i and R12 release. I hope you found this small tip useful.
To set the User Session Timeout, test the following steps in a development instance and then migrate accordingly !!

If suppose we executed autoconfig on application again default value 30 will be added to “ICX:session Timeout” Profile.
So we need to change the value in autoconfig file itself.
1. If R12.2 EBS instance view  $CONTEXT_FILE change the value for vairable “s_sessiontimeout” in config file then execute the autoconfig.sh in oracle application.

Share
read more no comments

Query To List Scheduled Jobs in Oracle Database

July 12th, 2025, posted in Oracle EBS Application, Oracle Queries
Share

Query : 

select owner as schema_name,
       job_name,
       job_style,
       case when job_type is null 
                 then 'PROGRAM'
            else job_type end as job_type,  
       case when job_type is null
                 then program_name
                 else job_action end as job_action,
       start_date,
       case when repeat_interval is null
            then schedule_name
            else repeat_interval end as schedule,
       last_start_date,
       next_run_date,
       state
from sys.all_scheduler_jobs
order by owner,
         job_name;

Columns :

  • schema_name – name of the schema
  • job_name – name of the job
  • job_style:
    • REGULAR
    • LIGHTWEIGHT
  • job_type – inline job action type
    • PLSQL_BLOCK
    • STORED_PROCEDURE
    • EXECUTABLE
    • CHAIN
    • SQL_SCRIPT
    • BACKUP_SCRIPT
    • EXTERNAL_SCRIPT
    • PROGRAM
  • job_action – PL/SQL code or program/routine name to call
  • start_date – when job will be launched first time
  • schedule – inline schedule PL/SQL expression, calendar string or name of the schedule
  • last_start_date – last date on which the job started running
  • next_run_date: next date on which the job is scheduled to run
  • state:
    • Disabled
    • Scheduled

Rows

  • One row: represents one job
  • Scope of rows: all jobs in database
  • Ordered by job schema, job name
Share
read more 2 comments

Failure of Web Server bridge: No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.

February 2nd, 2025, posted in Oracle EBS Application
Share

EBS Forms in our financial applications suddenly does not work. The message on the webpage is

Failure of Web Server bridge:
No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.

The error message does not tell the true problem. When checking into services on OS level, I saw Oracle EBS Forms service was not running and also saw errors from startup script $ADMIN_SCRIPTS_HOME/adstrtal.sh:

Forms service failed to start. 
The Node Manager is already up.

ERROR: Unable to start up the managed server forms_server1
Server specific logs are located at $EBS_DOMAIN_HOME/servers/forms_server1/logs
05/13/24-20:56:26 :: admanagedsrvctl.sh: exiting with status 1

Java error exists in Forms log file $EBS_DOMAIN_HOME/servers/forms_server1/logs/forms_server1.out

<May 13, 2024 8:56:25 PM EDT> <Emergency> <Store> <BEA-280060> <The persistent store "_WLS_forms_server1" encountered a fatal error, and it must be shut down: weblogic.store.PersistentStoreFatalException: [Store:280020]There was an error while reading from the log file
weblogic.store.PersistentStoreFatalException: [Store:280020]There was an error while reading from the log file
        at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:128)
        at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:435)
        at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:423)
        at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:126)
        at weblogic.store.admin.FileAdminHandler.activate(FileAdminHandler.java:207)
        Truncated.
Caused By: java.io.EOFException: premature EOF: expected=512, actual=126
        at weblogic.store.io.file.StoreFile.readBulk(StoreFile.java:316)
        at weblogic.store.io.file.Heap.readStoreFile(Heap.java:1142)
        at weblogic.store.io.file.Heap.getNextRecoveryFile(Heap.java:1226)
        at weblogic.store.io.file.Heap.open(Heap.java:373)
        at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:117)
        Truncated.

Seems WebLogic failed to open a file, but the log did not say which file. I knew that Linux Admins just did server maintenance and rebooted server after they applied monthly patches and Security updates on OS level. That was the only change in the application environment recently.

After searching around, I found the Java errors match the description in Oracle Doc ID 3017110.1 ( Managed Forms Server Fails To Start - Displaying Message: FAILED_NOT_RESTARTABLE - ERROR: The persistent store "_WLS_forms_server1" could not be deployed: weblogic.store.PersistentStoreFatalException [Store:280020] ).

The document points out the problem is caused by CrowdStrike, which locks a Forms file in $EBS_DOMAIN_HOME/servers/forms_server#/data/store/default.
CrowdStrike is installed in /opt/CrowdStrike. It is owned by root, and it is running constantly on the Linux server.

$ ps -ef | grep falcon-sensor
root 1081 1079 0 May13 ? 00:22:23 falcon-sensor

1. Delete/rename below .DAT file (I guess CrowdStrike does not like the file name and so locks it)

    $ cd $EBS_DOMAIN_HOME/servers/forms_server1/data/store/default
    $ ls -altr
    total 1028
    drwxr-xr-x 4 user group 40 Sep 13 2023 ..
    -rw-r--r-- 1 user group 1049088 May 13 20:51 _WLS_FORMS_SERVER1000000.DAT
    drwxr-xr-x 2 user group 42 May 13 20:56 .
    $ rm _WLS_FORMS_SERVER1000000.DAT

    2. Re-start services cleanly by

    $ADMIN_SCRIPTS_HOME/adstrtal.sh
    Or
    $ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start forms_server1

    The permanent fix is that the Secure team rolls back the CrowdStrike change (and applies it again until CrowdStrike fixes the problem), because its new update touches an Oracle Forms data file wrongly during its scan.

    Share
    read more no comments
    « Older Entries
    Newer Entries »