Archive for the ‘R12’ Category
Posted by appsdba11i on May 16, 2012
Recently i faced this issue after a upgrade activity
You are running adoafmctl.sh version 120.6.12000000.3
Starting OPMN managed OAFM OC4J instance …
adoafmctl.sh: exiting with status 152
–> Process (index=1,uid=129224376,pid=19811)
time out while waiting for a managed process to start
ias-component | process-type | pid | status
OC4JGroup:default_group | OC4J:oafm | N/A | Down
OC4JGroup:default_group | OC4J:oacore | ***** | Alive
OC4JGroup:default_group | OC4J:oacore | ***** | Alive
HTTP_Server | HTTP_Server | *&*&* | Alive
Issue resolved after doing below action :
Clear the TLD cache:
1)stop all middle tier services
2)Delete/backup all the files under directory:
mv _TldCache _TldCache_bkp
mv persistence persistence_bkp
3)start all middle tier services
Posted by appsdba11i on March 2, 2012
I got this is one of my test instance.concurrent req is failed with below error
in request Log file:
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 9123456
Review your concurrent request log and/or report output file for more detailed information.”
Program was terminated by signal 25.
The reports.log reached max file size(2GB).If $APPLCSF/$APPLLOG/reports.log will be huge — 2GB in size, then reports can
not append anything else to it and hence concurrent program accessing reports.log for its execution will error out.
bash-3.2$ ls -lrt reports.log
-rw-r–r– 1 aptest11i aptest1i 2147483617 Feb 05 18:42 reports.log
bash-3.2$ cp reports.log reports.log_BKP
bash-3.2$ cat /dev/null > reports.log
bash-3.2$ ls -lrt reports.log
-rw-r–r– 1 aptest1i aptest1i 0 Feb 05 18:43 reports.log
Issue is resolved after following Doc ID 842850.1
Posted by appsdba11i on February 27, 2012
we are unable to bring up apache after refresh
–> Process (index=1,uid=3892632383,pid=46981)
failed to start a managed process after the maximum retry limit
adapcctl.sh: exiting with status 0
msg in log file:
overwritten — Unclean shutdown of previous Apache run?
mod_ossl: Cannot allocate memory for the ‘shmcb’ session cache\n
Apache was not gene down properly
Take backup of ssl.conf
added this entry in ssl.conf
It should look Like This
diff ssl.conf ssl.conf_bkp
< #SSLSessionCache shmcb:/TEST/log/TEST_hostname/logs/ora/10.1.3/Apache/ssl_scache(512000)
after making this changes Issue Is resolved.
ref id : 754838.1
Posted in R12 | Tagged: failed to start a managed process after the maximum retry limit, mod_ossl: Cannot allocate memory for the 'shmcb' session cache, Unclean shutdown of previous Apache run? | Leave a Comment »
FRM – 92101 There was a failure in the forms server during startup. This colud happen due to invalid configuration
Posted by appsdba11i on February 24, 2012
We got a issue after Refresh in Test Instance.
we are unable to Open the forms and we are getting this error “FRM 92101 There was a failure in the forms server during startup. This colud happen due to invalid configuration “
bash-3.2$ cd $ORACLE_HOME/bin
bash-3.2$ ls -lrt frmweb
-rw-r–r– 1 appltest oracle 17177095 Jan 26 14:17 frmweb
Chmod 777 frmweb
Given 777 permission And Bounced Forms server. Its resolved the issue.
Posted by appsdba11i on September 7, 2011
In 11i We will Use f60gen to Compile Form.
In r12 we will use frmcmp_batch to compile form
Location of this file (frmcmp_batch)
i.e ex : /INST/product/1012/bin
Syntax : $ frmcmp_batch module=Formname.fmb userid=apps/**** output_file=output.fmx(location) module_type=form compile_all=special batch=yes
ex: $ frmcmp_batch module=/INSTANCE/applmgr/1213/au/12.0.0/forms/US/desired.fmb userid=apps/**** output_file=/INSTANCE/applmgr/1213/gl/12.0.0/forms/US/desired.fmx
module_type=form compile_all=special batch=yes
Posted by appsdba11i on May 16, 2011
dbc as name says is database connect descriptor file which stores database connection information used by application tier to connect to database. This file is in directory $FND_TOP/secure also called as FND_SECURE
Location of dbc file in 11i
$FND_TOP/SECURE OR $FND_SECURE
Location of dbc file in R12
What are things that we need to look for in .dbc file.
GUEST_USER_PWD –> (Guest username & passwd)
APPL_SERVER_ID –> Used to Identify the Databse by Server ID
GWYUID–> (APPLSYSPUB user name and passwd)
Other than this there are some of other things that will be there in dbc file . which wil impact the
[applmgr@acer ACER_acer]$ grep -i fnd acer.dbc
These Are The Default values.. The values will effect the performace..
We will the find the values that effect performace in future topics
Importannt of Guest Passwd
The .dbc file is mostly used to define database parameters,stands for database connect descriptor file, used to connectto database, it authenticate
users against database in FND_USER table.
Let’s see how it work’s
The .dbc file is actually the database connector descriptor file used to connect to database and this file is by-default located in $FND_TOP/secure directory, this file is quite important as whenever any program likes to connect to database like forms it uses dbc file where there you find the Guest_user_pwd ,when the guest user connect it does not allow it to directly connect to the database but it first connect goes via this file and cross verify the password of the guest which is kept in this file.
Webserver checks that username and passwords need to authenticate against database FND_USER table , so it needs first some user to check client’s username password in database . Guess which username password it uses ?? ( GUEST/ORACLE have you ever noticed why this user is there , Hope you know it now it Uses Guest User to autenticate your user in database )
Posted by appsdba11i on May 14, 2011
I am going to give some information about how to drop/deleting application user
We cannot delete a frontend user due to security reason.deleting cause some problem to the application.. If u want to delete the frontend user then deavtivate or enddate the user..
Methods to End-date application User..
Login to Oracle Applications – Select the System Administrator responsibility – Security – User – Define – Query the user name – then you can give end date in the Effectives Date To column.
Enddating user by sqlplus
1) backup fnd_user
SQL>CREATE TABLE FND_USER_BKP AS SELECT * FROM FND_USER;
2) The following SQL*Plus statement may be run from the APPS account:
SQL>update fnd_user set end_date=’14-jUN-2011′ where user_name like ‘%desired_ser_NAME%';
Modifying tables without the use of the Oracle Forms interface is NOT SUPPORTED.
How to Change the END_DATE for Applications Users through SQL*Plus [ID 1039608.6]
Posted in 11i Apps, R12 | Tagged: How to Change the END_DATE for Applications Users, How to Change the END_DATE for Applications Users through SQL*Plus, how to drop/Delete an application user | Leave a Comment »
Posted by appsdba11i on May 5, 2011
Snapshots are current views of your system: they are created once, and then updatedwhen appropriate to maintain a consistent view.
There are three types of snapshot’s
APPL_TOP snapshots & global snapshots & named Snapshots
An APPL_TOP snapshot lists patches and versions of files in the APPL_TOP.
AutoPatch uses an APPL_TOP snapshot to determine if prerequisite patches
have been applied to a particular APPL_TOP
A global snapshot lists patches and latest versions of files in the entire Applications system (that is, across all APPL_ TOPs).
Patch Wizard uses a global snapshot to determine which patches have already been applied.
Named snapshots are created once using AD Administration and not updated. Both store information about files, file versions, and bug fixes present in an APPL_TOP.
You can create as many named snapshots of each APPL_TOP as you want. You can also just create or update the current view snapshot. When creating a named snapshot for an APPL_TOP, the snapshot feature will first create or update the current view snapshot for that APPL_TOP. The bug fix information for a named snapshot is copied from the current view snapshot for that APPL_TOP.
APPL_TOP snapshot information is stored in the AD_SNAPSHOTS, AD_SNAPSHOT_FILES, and AD_SNAPSHOT_BUGFIXES tables.
By Using Adadmin we can maintain & update the snapshots..
adadmin>> Maintain Applications Files>> choose Maintain Snapshot Information.
Posted by appsdba11i on May 3, 2011
Locating and Creating the Application Context File
The application context file is an XML file named $CONTEXT_NAME.xml. The
CONTEXT_NAME variable is set to $SID or $SID_[hostname]. The application context file is located in the $APPL_TOP/admin directory, and it is applicable to all nodes that comprise the E-Business Suite.
If the application context file does not exist, it can be created by executing
the adbldxml.sh script:
This script will evaluate your environment in order to generate the context
file. A directory listing should confirm the existence of this application
Posted in R12 | Tagged: adbldxml.sh, Locating and Creating the Application Context File | Leave a Comment »