Login failed for few users in oracle ebs R12.2.4

Dear Brothers/Sisters,

This issue happened only to few of the users. I could not find any error in application logs to figure out root cause.

Try the below once before you actually fixing the issue. Sometime the below help if there is no setup related issue.

1) Stop application $ADMIN_SCRIPTS_HOME/adstpall.sh
re-compile JSP pages

perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile --flush -p 2 -log /tmp/ojspc_error.log

Start application $ADMIN_SCRIPTS_HOME/adstrtal.sh

Retest issue .


But in my case i had to do the below to figure out the issue.

2)

Is it possible to enable FNS_debug log on any user then provide fnd log by following steps
FND Debug Steps

1) Set below profile options on user level

FND: Debug Log Enabled YES
FND: Debug Log Filename NULL
FND: Debug Log Level STATEMENT
FND: Debug Log Module %

Provide fnd.wf.worklist% in module for mobile apps else keep %

2) SELECT MAX(LOG_SEQUENCE) before_seq
FROM FND_LOG_MESSAGES;

3) Run your test case/ Produce issues

4) SELECT MAX(LOG_SEQUENCE) after_seq
FROM FND_LOG_MESSAGES;

5) Retrieve error messages and save in Excel format.

SELECT module, message_text
FROM fnd_log_messages
WHERE log_sequence between &before_seq and &after_seq
ORDER BY log_sequence;


Found the below in excel sheet :


fnd.plsql.APP_EXCEPTION.RAISE_EXCEPTION.dict_auto_log

Oracle error -1654: ORA-01654: unable to extend index APPLSYS.FND_LOGINS_N2 by 16 in tablespace APPS_TS_ARCHIVE has been detected in FND_SIGNON.AUDIT_USER.


fnd.plsql.FND_SESSION_MANAGEMENT.createSessionPrivate


Exception:-20001 ORA-20001: Oracle error -20001: ORA-20001: Oracle error -1654: ORA-01654: unable to extend index APPLSYS.FND_LOGINS_N2 by 16 in tablespace APPS_TS_ARCHIVE has been detected in FND_SIGNON.AUDIT_USER. has been detected in FND_SIGNON.NEW_PROXY_ICX_SESSION.

- Error is due to No space in one of the tablespace. This bigger step could have been avoided if i just have looked into DB alert log. I was chasing behind everything instead of DB alert log :-)

I found this step is really helpful when i thought what if there is no error in DB. I would be happy if it helps someone. It will be appreciated any feedback about this blog.

Thanks!
~Sikky

How to find the error when nothing is logged in the logs in R12.2?

Dear Brothers/Sisters,

We were getting these error in few of the pages in AP module and none of the notification worked due to this error.

"You have encountered an unexpected error. Please contact the System Administrator for assistance"

There is an another similar kinda issue i have blogged aboutm

Please read : EBS login page is not working   Few users unable to log into R12


Troubleshooting is very simple technique when you find out the error. All you have to know is where to find that one. Once you found the cause of the trouble, fixing is simple thing.

Main goal of this post to share my ideology to narrow the issue and how we can trace the error stack in OAF page when we have no clue.

I did the below the moment i noticed the error :

- Apache, oacore, oafm, forms logs
- Alert log in DB
- Mount point sizes in app and db server.

Everything seems to be normal and i had to clue to figure out the cause. So i had to trace one of the page as all the ways are closed. Let me summarize the events i had to figure out the error.

- Set FND: Diagnosticts profile option set to yes to user
- Reproduce the error

After i enabled debug option to my user, i could figure at least what was cause of the error.  I saw the additional options in the error page. When i clicked exception detail i can see error stack.

- See about this page or exception detail to find the error. I have highlighted the error in yellow.



Error Stack:

## Detail 0 ## java.sql.SQLException: ORA-20001: SQL_PLSQL_ERROR: N, ROUTINE, MO_GLOBAL.INIT, N, ERRNO, -20001, N, REASON, ORA-20001: APP-FND-02902: Multi-Org profile option is required. Please set either MO: Security Profile or MO: Operating Unit profile option. ORA-06512: at "APPS.PO_DOCUMENT_TOTALS_PVT", line 475 ORA-06512: at line 1 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548) at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:213) at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1111) at

- This error is specific to our env and cause of the error is one of the profile option (MO: Security profile). Profile option had been set to null value recently due to which few modules went into error. After fixing it, everything became normal. 

How i did?

-  First thing error was in production. 

-  I tried to replicate the error in recent clone which was cloned 3 days ago. Luckily i had the same error

- We had 2 more dev instance left which was not cloned for  a while. I was able to see error pages were working fine when i tried to replicate the error.

- So quickly i looked for profile option value to see what value it had. 

- Error disappeared after i set the same value in production. 

To implement the solution, please execute the following steps: 

1. Go into the responsibility: System Administrator 

2. Navigate to Profiles > System > check Site option 

3. Be sure that either profile for Multi-Org Access Control 'MO: Security Profile' OR 'MO: Operating Unit' is set appropriately. 

4. Retest the issue 

*** Value presented in the profile option was specific to our env. Please make sure with the consultants before you set this value in production***

Main goal of this post to share my ideology to narrow the issue and how we can trace the error stack in OAF page when we have no clue.

We can trace the error from the database as well. Please do the following to figure out the cause from tables.  

A. 

To Enable FND debug: 

Navigate Responsibility: System Administrator > Profile => System 

a. Find the FND profile options for User who is submitting the process to debug. 

User: User submitting the process 

Profile: FND:%Debug% 

b. Set the following Profile values at the user level 

FND: Debug Log Enabled :Yes 

FND: Debug Log Filename : NULL 

FND: Debug Log Level : STATEMENT 

FND: Debug Log Module : % 

c. Save. 

B. 

Get the current log sequence in the FND table. 

select max(log_sequence) from fnd_log_messages ; -- start 

C. 

Reproduce the issue 

D. Get the sequence in the FND log 

select max(log_sequence) from fnd_log_messages ; -- end 

E. Spool the output of the following query to an excel file which gives FND debug log: 

Run this script and replace start and end with the sequences you obtained from steps B and D. 

select module, message_text 

from fnd_log_messages 

where log_sequence between <start> and <end>;

Thanks!
~Sikky

step by step procedure to run concurrent recovery wizard in R12.2.4?

Dear Brothers/Sisters,

This post is all about the concurrent manager recovery wizard which will surprise you at critical time. This wizard comes up in-built and we dont need to make any extra efforts to configure. I have provided the step by step screen shots from home page to wizard ending page.

Please utilize this wizard when your ICM does not start even though after multiple bounce. I think oracle is developing their ERP with the real time scenarios, when this CM were failed to start it just reminded me my childhood days. When i dont get up from bed my mother used to splash water in face, the same idea gonna work our here as well to wake up CM.

 I have tested this in production and test when my CM failed to start and it worked like a champ. Please run this when your CM failed to start for no reason. But tried killing all FNDLIBR processed for the specific instance which causes trouble and try to restart CM. If there is no zombie processes registered in db, CM restart may help.

I can see this error in ICM logs which where helpless. No error in DB alert log. And finally i decided to run this wizard. You dont need to shutdown CM for this activity and ICM must be running while running this wizard.

Segmentation Fault - core dumped : The PROD_1027@PROD internal concurrent manager has terminated with status 139 - giving up.


========================================================================
Starting PROD_1027@PROD Internal Concurrent Manager -- shell process ID 1673

          logfile=/u01/oracle/PROD/fs_ne/inst/PROD_******logs/appl/conc/log/PROD_1027.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=30
             pmon=4
           quesiz=1
          Reviver is ENABLED

Segmentation Fault - core dumped
The PROD_1027@PROD internal concurrent manager has terminated with status 139 - giving up.

How to access the concurrent manager recovery wizard?

- Log into sysadmin user
- Navigate to oracle applications manager under System administrator responsibility
- Click any menu option under Oracle Applications Manager

- Click Site Map after landing to this page.

NAvigate to Diagnostics and Repair tab and at the right side you can see Wizard.

Thats it! its tedious to find the Concurrent manager recovery wizard. Once you found it, it will make the job easier.

Issue is due to there are run away processes are registered in database which does not allow CM to start. Once i hit update button, Wizard will clear the run away processes from DB.

For more Info :

Concurrent Manager Recovery Wizard - Oracle Applications Manager Troubleshooting and Diagnostics (Doc ID 2130545.1)