FND and AD tables

Concurrent Manager
FND_CONCURRENT_QUEUES
FND_CONCURRENT_PROGRAMS
FND_CONCURRENT_REQUESTS
FND_CONCURRENT_PROCESSES
FND_CONCURRENT_QUEUE_SIZE
FND
FND_APPL_TOPS
FND_LOGINS
FND_USER
FND_DM_NODES
FND_TNS_ALIASES
FND_NODES
FND_RESPONSIBILITY
FND_DATABASES
FND_UNSUCCESSFUL_LOGINS
FND_LANGUAGES
FND_APPLICATION
FND_PROFILE_OPTION_VALUES
AD / Patches
AD_APPLIED_PATCHES
AD_PATCH_DRIVERS
AD_BUGS
AD_INSTALL_PROCESSES
AD_SESSIONS
AD_APPL_TOPS

Log file location for Oracle EBS R12

Log file location for Oracle EBS R12

Log file location for Oracle EBS R12

- Autoconfig log file:
Apps:
$INST_TOP/apps/$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/

- Concurrent log:
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log

- 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

Reference:
How to find location of Install, Autoconfig, Patching , Clone and other logs in R12 [ID 804603.1]
Oracle Application Server Diagnostic Tools and Log Files in Applications Release 12 [ID 454178.1]
Oracle Applications System Administrator’s Guide



Read more: http://prasanthapps.blogspot.com/2011/05/log-file-location-for-oracle-ebs-r12.html#ixzz1ho0BhdfZ

log files in R12

Where do concurrent request log files and output files go?

The concurrent manager first looks for the environment variable $APPLCSF
If this is set, it creates a path using two other environment variables:
$APPLLOG and $APPLOUT
It places log files in $APPLCSF/$APPLLOG
Output files go in $APPLCSF/$APPLOUT
So for example, if you have this environment set:
$APPLCSF = /u01/appl/common
$APPLLOG = log
$APPLOUT = out
The concurrent manager will place log files in /u01/appl/common/log, and
output files in /u01/appl/common/out
Note that $APPLCSF must be a full, absolute path, and the other two are
directory names.
If $APPLCSF is not set, it places the files under the product top of the application associated with the request. So for example, a PO report would go under $PO_TOP/$APPLLOG and $PO_TOP/$APPLOUT
Logfiles go to: /u01/appl/po/9.0/log
Output files to: /u01/appl/po/9.0/out
Of course, all these directories must exist and have the correct permissions.
Note that all concurrent requests produce a log file, but not necessarily an output file.



Where are the log files located in R12?

For DBA’s who mostly worked on 11i environments, finding the log files (Concurrent manager log, apache log etc.,) on a R12 environment might pose a threat initially, because these log files no longer reside in their old location ie., $APPLCSF/$APPLLOG or $APACHE_TOP/Apache/logs.
In R12, the log files are located in $LOG_HOME (which translates to $INST_TOP/logs)
Concurrent Reqeust related logs
$LOG_HOME/appl/conc -> location for concurrent requests log and out files
$LOG_HOME/appl/admin -> location for mid tier startup scripts log files
Apache Logs (10.1.3 Oracle Home which is equivalent to iAS Oracle Home)
$LOG_HOME/ora/10.1.3/Apache -> Location for Apache Error and Access log files
$LOG_HOME/ora/10.1.3/j2ee -> location for j2ee related log files
$LOG_HOME/ora/10.1.3/opmn -> location for opmn related log files
Forms & Reports related logs (10.1.2 Oracle home which is equivalent to 806 Oracle Home)
$LOG_HOME/ora/10.1.2/forms
$LOG_HOME/ora/10.1.2/reports
Related metalink notes to enable additional debugging
419839.1 – How to enable Apache, OC4J and OPMN logging in Oracle Applications R12
422419.1 – R12 – How To Enable and Collect Debug for HTTP, OC4J and OPMN

Patch info

 SELECT a.application_name,
DECODE (b.status, 'I', 'Installed', 'S', 'Shared', 'N/A') status,
patch_level
FROM apps.fnd_application_vl a, apps.fnd_product_installations b
WHERE a.application_id = b.application_id;

SELECT patch_name, patch_type, maint_pack_level, creation_date
FROM applsys.ad_applied_patches
ORDER BY creation_date DESC

R12: Clone fails with error "ORA-28000 The account is locked"

R12: Clone fails with error "ORA-28000 The account is locked"

R12: Clone fails with error "ORA-28000 The account is locked" [ID 1114244.1]




In this Document
  Symptoms
  Cause
  Solution
  References



Applies to:

Oracle Applications Manager - Version: 12.0.0 to 12.1.3 - Release: 12 to 12.1
Information in this document applies to any platform.
***Checked for relevance on 06-Feb-2012***

Symptoms

The clone of an E-Business Suite Instance of Release 12 is failing with following error :

...
Exception occurred: java.sql.SQLException: ORA-28000: the account is locked
ORA-28000: the account is locked
...

Cause

The issue is caused by the APPS Database account, which is locked.

The following script allows you to check the number of failed logins, which can lock the apps user :

select profile , resource_name, limit
from dba_profiles
where resource_name ='FAILED_LOGIN_ATTEMPTS';


Example output :

DEFAULT FAILED_LOGIN_ATTEMPTS : 10
AD_PATCH_MONITOR_PROFILE FAILED_LOGIN_ATTEMPTS : 3


For additional information, please review Note 114930.1 - 'Oracle Password Management Policy'.

Solution

To implement the solution, please execute the following steps:
1. Ensure that you have taken a backup of your Environment.

2. Increase the number of failed login which locks apps user (optional) :

alter profile AD_PATCH_MONITOR_PROFILE limit failed_login_attempts unlimited;
alter profile default limit failed_login_attempts unlimited password_lock_time 1/1440;

3. Unlock the locked APPS User account :

alter user apps account unlock;


4. Rerun the failed cloning commands.

5. Migrate the solution as appropriate to other Environments

Bne log error in R12

Web ADI Journal Upload Gives 500 Internal Server Error on Screen, BNE.LOG shows Integrator Parameter gl:ledger was not specified. [ID 1162176.1]


while upload JV of 8000 rouw gives internal server msg

check file bne.log in /user/tmp/bne.log

tail -1000f bne.log

error in file

Reviewing the BNE.log file shows the following:

<...> AM AJPRequestHandler-HTTPThreadGroup-166 ERROR The null pointer has occurred: Integrator Parameter gl:ledger was not specified.
<...> AM AJPRequestHandler-HTTPThreadGroup-166 ERROR Stack trace for the error: oracle.apps.bne.exception.BneFatalException: Integrator Parameter gl:ledger was not specified.


Clear cache using following link after loggin in sysadmin r12

http://finprod10.kaleconsultants.com:8000/OA_HTML/BneAdminServlet

lsnrctl listenr cmd

Start / Stop Net8 Listener process for TEST

addlnctl.sh

ps -ef |grep tnslsnr
to view listner on server

lsnrctl reload TEST


lsnrctl reload $listener_name

lsnrctl start $listener_name

lsnrctl stop $listener_name

FNDCPASS

http://www.appsdba.info/docs/oracle_apps/other/FNDCPASS.pdf


command to change application user "sysadmin" password
GO TO FNDPASS SCRIPT LOCATION FOR Production
cd /data/ERPP/erppapps/apps_st/appl/fnd/12.0.0/bin/
then run
FNDCPASS apps/kishore 0 Y system/manager USER sysadmin ebs@1234

============================================================
FNDCPASS apps/apps 0 Y system/manager USER KCLENTRY kale@1234

location of script :

/data/ERPP/erppapps/apps_st/appl/fnd/12.0.0/bin/FNDCPASS
/test/TEST/testapps/apps_st/appl/fnd/12.0.0/bin/FNDCPASS

How to Change Applications Passwords using Applications Schema Password Change Utility (FNDCPASS or AFPASSWD) [ID 437260.1]