, , ,

Solved: Workflow Error When Clicking View Status Diagram on Status Monitor

When you want to view the status diagram of workflow process on status monitor page from the workflow administrator responsibility, maybe you get the error page like below:
The solution for the above issue is set the Server Timezone profile option on the Site level.
After that you can able to see the status diagram in workflow status monitor.
 
/by
, , , ,

Solved: You cannot run a page which is not Self Secured when the MAC fails

Sometimes we will face below issues in R12.

Issue 1:
You have insufficient privileges for the current operation. Please contact your System Administrator.

You cannot run a page which is not Self Secured when the MAC fails.

Resolution:
 
Set the below 3 profiles to None
1) FND Function Validation Level
2) FND Validation Level
3) Framework Validation Level
JDev-2
Issue 2:
Unexpected URL parameters have been detected and will be ignored Solution:
 
Resolution:

In JDeveloper, go to menu Tools–>Embedded OC4J Server Preferences–>Global–>Startup–>Select Default Local IP Address.
JDev-3
 
 
/by
, , , ,

Oracle Apps Log Files Locations in R12

Autoconfig log file:
Apps:
$INST_TOP/appl/$CONTEXT_NAME/admin/log/$MMDDHHMM/adconfig.log

Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/adconfig.log $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/NetServiceHandler.log

Startup/Shutdown Log files:

$INST_TOP/logs/appl/admin/log

Apache, OC4J and OPMN:

$LOG_HOME/ora/10.1.3/Apache 
$LOG_HOME/ora/10.1.3/j2ee 
$LOG_HOME/ora/10.1.3/opmn

Patch log:

$APPL_TOP/admin/$SID/log/
Workflow Mailer log:
$APPLCSF/$APPLLOG/FNDCPGSC*.txt

Concurrent log:

$INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log
OAM (Oracle Application Manager) log:
$APPLRGF/oam/

Clone log:

Preclone log files in source instance

Apps:
$INST_TOP/apps/$CONTEXT_NAME/admin/log/ (StageAppsTier_MMDDHHMM.log)

Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log)

Clone log files in target instance:

Apps :
$INST_TOP/apps/$CONTEXT_NAME/admin/log/ApplyAppsTier_.log

Db:
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_.log

– Alert Log File:
$ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log

Concurrent OUT Directory:
$APPLCSF/$APPLOUT  or $APPLCSF/out
APPL_TOP – this is the top level directory for the Applications
  • $APPLCSF – the top level directory where the concurrent manager stores the log and out files of concurrent requests
  • $APPLCSF/$APPLLOG – concurrent request log files( As describe above)
  • $APPLCSF/$APPLOUT – concurrent request out files( As describe above)
  • $APPLTMP – Applications temporary files
  • $APPLPTMP – PL/SQL temporary files   or /usr/tmp (default tmp directory)
Startup and shutdown messages:
–Startup/Shutdown error message related to tech stack (10.1.2, 10.1.3 forms/reports/web)
$INST_TOP/logs/ora/ (10.1.2 & 10.1.3)
$INST_TOP/logs/ora/10.1.3/Apache/error_log[timestamp]
$INST_TOP/logs/ora/10.1.3/opmn/ (OC4J~…, oa*, opmn.log)$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.2/network/ (listener log)
$INST_TOP/logs/appl/conc/log (CM log files)
Other log files in R12

1) Database Tier
1.1) Relink Log files :
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME /MMDDHHMM/ make_$MMDDHHMM.log

1.2) Alert Log Files :
$ORACLE_HOME/admin/$CONTEXT_NAME/bdump/alert_$SID.log

1.3) Network Logs :
$ORACLE_HOME/network/admin/$SID.log

1.4) OUI Logs :
OUI Inventory Logs :
$ORACLE_HOME/admin/oui/$CONTEXT_NAME/oraInventory/logs

2) Application Tier

$ORACLE_HOME/j2ee/DevSuite/log
$ORACLE_HOME/opmn/logs
$ORACLE_HOME/network/logs

Tech Stack Patch 10.1.3 (Web/HTTP Server)
$IAS_ORACLE_HOME/j2ee/forms/log
$IAS_ORACLE_HOME/j2ee/oafm/log
$IAS_ORACLE_HOME/j2ee/oacore/log
$IAS_ORACLE_HOME/opmn/logs
$IAS_ORACLE_HOME/network/log
$INST_TOP/logs/ora/10.1.2
$INST_TOP/logs/ora/10.1.3
$INST_TOP/logs/appl/conc/log
$INST_TOP/logs/appl/admin/log

Patching related log files in R12 :
Application Tier– adpatch log – $APPL_TOP/admin//log/
Developer (Developer/Forms & Reports 10.1.2) Patch – $ORACLE_HOME/.patch_storage
Web Server (Apache) patch – $IAS_ORACLE_HOME/.patch_storage
Database Tier opatch log – $ORACLE_HOME/.patch_storage
/by
, , ,

Purge/Delete Completed Concurrent Requests in Apps

Error:Delete/Purge COMPLETED concurrent requests

Concurrent request history should not exceed 50K rows, or else it will start impacting on performance

SQL> select count(*) from FND_CONCURRENT_PROCESSES;

COUNT(*)
———-
552

SQL> select count(*) from FND_CONCURRENT_REQUESTS;

COUNT(*)
———-
85009 ==>>> Should always be below 50K, Else run “Purge Concurrent Request”
SQL>

SQL> select count(*) from FND_CONCURRENT_REQUESTS

2 where request_date > sysdate-7;

COUNT(*)
———-
19757

SQL> col “Min request|Date” for a20;

SQL> col “Max request|Date” for a20;

SQL> select min(request_date) “Min request|Date”,max(request_date) “Max request|Date” from FND_CONCURRENT_REQUESTS;

Min request|Date Max request|Date
——————– ——————–
18-NOV-09 01-NOV-11

SQL>

To clean old history of “COMPLETED” requests, follow the below note, to purge the queue

Concurrent Processing Tables and Purge Concurrent Request and/or Manager Data Program (FNDCPPUR) [ID 104282.1]

System Administrator -> Requests -> Run

Select “Single Request”

Mode = 14 days – delete all older than 14 days. Don’t make this window to small.

To view the above submitted request, do the following

Enter the request ID and “Find”

While Running:

Status on successful completion is shown below “Completed”, “Normal”


Extract from the Log File:

FNDCPPUR module: Purge Concurrent Request and/or Manager Data
+—————————————————————————+
Current system time is 01-NOV-2011 12:57:03
+—————————————————————————+
Purged 46616 entrie(s) from FND_CONCURRENT_REQUESTS :-01-NOV-2011 13:07:22

Purged 0 entrie(s) from FND_FILE_TEMP :-01-NOV-2011 13:07:22

Purged 7082 entrie(s) from FND_CRM_HISTORY :-01-NOV-2011 13:07:25

Purged 0 entrie(s) from FND_TM_EVENTS :-01-NOV-2011 13:07:25

Purged 346 entrie(s) from FND_TEMP_FILES :-01-NOV-2011 13:07:25

Purged 0 entrie(s) from FND_ENV_CONTEXT :-01-NOV-2011 13:07:46

Purged 1 entrie(s) from FND_DUAL :-01-NOV-2011 13:07:46

Purged 2 entrie(s) from FND_CONFLICTS_DOMAIN :-01-NOV-2011 13:07:46

+—————————————————————————+
Start of log messages from FND_FILE
+—————————————————————————+

/by
, ,

R12 – Enabling/Disabling “FND: Debug Log Enabled” from Putty

When trying to enable “FND: Debug Log Enabled”, in the below window, it might sometime be that the option to set it to Yes/No, is grayed out, and cannot be changed. Without spending too much time fixing this, you can also enable/disable it from within a sqlplus session, connected as the apps user.
To enable it, do the following
SQL> SELECT PROFILE_OPTION_ID,PROFILE_OPTION_NAME FROM FND_PROFILE_OPTIONS_VL
WHERE START_DATE_ACTIVE <= SYSDATE
and NVL(END_DATE_ACTIVE,SYSDATE) >= SYSDATE
and ( SITE_ENABLED_FLAG = ‘Y’ or APP_ENABLED_FLAG = ‘Y’ or RESP_ENABLED_FLAG = ‘Y’ or USER_ENABLED_FLAG = ‘Y’ or SERVER_ENABLED_FLAG = ‘Y’ or SERVERRESP_ENABLED_FLAG = ‘Y’ or ORG_ENABLED_FLAG = ‘Y’)
and ( UPPER(USER_PROFILE_OPTION_NAME) LIKE ‘%FND%DEBUG%’
and (USER_PROFILE_OPTION_NAME LIKE ‘%f%’ or USER_PROFILE_OPTION_NAME LIKE ‘%F%’))
order by user_profile_option_name;
PROFILE_OPTION_ID PROFILE_OPTION_NAME
—————– ———————————–
             4176 AFLOG_ENABLED
             3098 AFLOG_FILENAME
             3099 AFLOG_LEVEL
             8470 AFLOG_BUFFER_MODE
             3100 AFLOG_MODULE
             8468 DEBUG RULE THRESHOLD
6 rows selected.
SQL>
Description: cid:image003.png@01CD17D0.99AE3620
SQL>
col profile_option_value for A20;
col profile_option_id for 999999999;
select PROFILE_OPTION_ID, PROFILE_OPTION_VALUE from FND_PROFILE_OPTION_VALUES
where profile_option_id in (‘4176‘,’3098′,’3099’);
SQL>
Description: cid:image005.png@01CD17D0.99AE3620
SQL> update FND_PROFILE_OPTION_VALUES
set PROFILE_OPTION_VALUE = ‘Y’
where PROFILE_OPTION_VALUE = ‘N’
and PROFILE_OPTION_ID = 4176; 
Description: cid:image006.png@01CD17D0.99AE3620
2 rows updated.
SQL> commit;
Commit complete.
SQL>

col profile_option_value for A20;
col profile_option_id for 999999999;
select PROFILE_OPTION_ID, PROFILE_OPTION_VALUE from FND_PROFILE_OPTION_VALUES 
where profile_option_id in (‘4176′,’3098′,’3099’);  => All will show ‘Y’ now

Description: cid:image007.png@01CD17D0.99AE3620
To disable it, just set it to NO again:
SELECT PROFILE_OPTION_ID,PROFILE_OPTION_NAME FROM FND_PROFILE_OPTIONS_VL
WHERE START_DATE_ACTIVE <= SYSDATE
and NVL(END_DATE_ACTIVE,SYSDATE) >= SYSDATE
and ( SITE_ENABLED_FLAG = ‘Y’ or APP_ENABLED_FLAG = ‘Y’ or RESP_ENABLED_FLAG = ‘Y’ or USER_ENABLED_FLAG = ‘Y’ or SERVER_ENABLED_FLAG = ‘Y’ or SERVERRESP_ENABLED_FLAG = ‘Y’ or ORG_ENABLED_FLAG = ‘Y’)
and ( UPPER(USER_PROFILE_OPTION_NAME) LIKE ‘%FND%DEBUG%’
and (USER_PROFILE_OPTION_NAME LIKE ‘%f%’ or USER_PROFILE_OPTION_NAME LIKE ‘%F%’))
order by user_profile_option_name
PROFILE_OPTION_ID    PROFILE_OPTION_NAME
—————–    ——————-
4176                 AFLOG_ENABLED
3098                 AFLOG_FILENAME
3099                 AFLOG_LEVEL
8479                 AFLOG_BUFFER_MODE
3100                 AFLOG_MODULE
8465                 DEBUG RULE THRESHOLD
col profile_option_value for A20;
col profile_option_id for 999999999;
select PROFILE_OPTION_ID, PROFILE_OPTION_VALUE from FND_PROFILE_OPTION_VALUES
where profile_option_id in (‘4176‘,’3098′,’3099’);
PROFILE_OPTION_ID PROFILE_OP
—————– ———-
          3099       1
          4176       Y
          3098       NULL
SQL>

update FND_PROFILE_OPTION_VALUES
set PROFILE_OPTION_VALUE = ‘N’
where PROFILE_OPTION_VALUE = ‘Y’
and PROFILE_OPTION_ID = 4176;  => AFLOG_ENABLED will show ‘N’ now

/by