It's not 12i ! It's only R12 !!

Hello !!
what to call the product next to 11.5.10(11i)? Many still using 12i.


I was there with R12 product development where none using 12i internally.

There was a name 11.5.10P for awhile(P for Plus 11.5.10+) then Dev, Unit test cycle of the product next to 11.5.10 named as R12.

So keep always saying R12 not 12i .

Little bit about DB Vault and FNDCPASS.

Recently 11i is certified with Database Vault. Nilesh explained the details in the blog http://blogs.oracle.com/schan/2008/02/07#a2375.
Metalink note ID to integrate ebiz suite 11i with 10.2.0.3 is 428503.1.
If you look at the note, you will see once you integrated Ebiz 11i with Database Vault, you will use Database Vault User account manager user or the user which has been granted DV_ACCTMGR Role to change the password instead of system password in FNDCAPSS utility.
to Change apps password when 11i integrated with db vault

FNDCPASS apps/appspassword 0 Y DV_ACCTMGR/DV_ACCTMGR_Pass SYSTEM APPLSYS NewAppsPassword
to change other schema passwords
FNDCPASS apps/appspassword 0 Y DV_ACCTMGR/DV_ACCTMGR_Pass ORACLE AP/AP_PASSWORD
This is newly introduced to handle db vault situation.

Hi Everyone!!
Here is good option of opmnctl utility you can use to find various good information like memory usage, start time, ports being used.
By default, adopmnctl.sh status gives short status message
[applmgrr12@champ scripts]$ ./adopmnctl.sh status
You are running adopmnctl.sh version 120.4
Checking status of OPMN managed processes...
Processes in Instance: r12test_champ.champ.dunno.com
-------------------+--------------------+---------+---------
ias-component process-type pid status
-------------------+--------------------+---------+---------
OC4J oafm 5693 Alive
OC4J forms 5692 Alive
OC4J oacore 5691 Alive
HTTP_Server HTTP_Server 5694 Alive
ASG ASG N/A Down
-----------------------------------------------------------------
adopmnctl.sh: exiting with status 0adopmnctl.sh: check the logfile /app/inst/apps/r12test_champ/logs/appl/admin/log/adopmnctl.txt for more information ...
To get more information from status control code, change the following line inadopmnctl.sh script from "opmnctl $control_code " to "opmnctl $control_code -l "(autoconfig will override this file. If you want to make this permanent you need to look for autoconfig template file.
if [ $control_code = "status" ]; then
printf "Checking status of OPMN managed processes...\n
"if [ -f "$LOGAP" ]; then
printf "\n`date +%D-%T` :: $program: Checking the status of Oracle Process Manager (OPMN)\n\n" >>
$LOGAP
/app/inst/apps/r12test_champ/ora/10.1.3/opmn/bin/opmnctl $control_code -l 2>&1 tee -a $LOGAP
fi
exit_code=$?;
elif
After changing you will see the below long status message
[applmgrr12@myhost scripts]$ ./adopmnctl.sh status
You are running adopmnctl.sh version 120.4Checking status of OPMN managed processes...
Processes in Instance: r12test_myhost.myhost.mydomain.com
-------------------+--------------------+---------+----------+------------+----------+--------
ias-component process-type pid status uid memused uptime ports
-------------------------------------------------------------------------------------------------
OC4J oafm 5693 Alive 1972203545 148544 0:38:59 jms:24525,ajp:25025,rmi:25525OC4J forms 5692 Alive 1972203544 96212 0:00:25 jms:23525,ajp:22025,rmi:20525OC4J oacore 5691 Alive 1972203543 120000 0:38:59 jms:23025,ajp:21525,rmi:20025HTTP_Server HTTP_Server 5694 Alive 1972203554 8386112 0:38:59 http1:7777,http2:7200ASG ASG N/A Down N/A N/A N/A N/A
adopmnctl.sh: exiting with status 0adopmnctl.sh: check the logfile /app/inst/apps/r12test_myhost/logs/appl/admin/log/adopmnctl.txt for more information ...

R12: Aware about context file changes !!

Here is the main change in R12. Context File is no more in $APPL_TOP/admin directory!!!
Appltop context file has been moved to $INST_TOP/appl/admin directory.
Experienced Apps DBA's usually changes context files manually rather changing by OAM.Oralce Strongly suggest to use OAM to modify the context file.
I worked recently with 11i to R12 upgraded environment, where actual context file was present in $INST_TOP/appl/admin and old copy was present in $APPL_TOP/admin, one of my 11i experienced colleague modified $APPL_TOP/admin context_file and ran autoconfig accidentally which made big mess.
It led to rework and another downtime in Alpha environment.
11i Apps DBA's who are moving to R12 have to remember this. Irrespective of 11i or R12, I would suggest to use 'vi $CONTEXT_FILE' after making the copy of the context file by 'cp $CONTEXT_FILE_bkp_date'. Otherwise use OAM!!
you can get the context_file paths from FND_OAM_CONTEXT_FILES

Name Null? Type
===================================================
NAME
VERSION
PATH
LAST_SYNCHRONIZED
TEXT
LAST_UPDATE_DATE
LAST_UPDATED_BY
CREATION_DATE
CREATED_BY
LAST_UPDATE_LOGIN
NODE_NAME
STATUS
SERIAL_NUMBER
EDIT_COMMENTS
CTX_TYPE

Lets Startup and Shut down R12 !!

Order of Startup Shutdown
————————————–
As in Oracle Apps 11i order for startup isA) Start Database Tier Services–Start Database Listener–Start DatabaseThenB) Start Application/Middle Tier Services– adstrtal.sh
Order for shutdown in Oracle Apps R12 is
A) Stop Application/Middle Tier Services– adstpall.shThen
B) Stop Database Tier Services–Stop Database–Stop Database Listener
Database Tier Scripts in R12
————————————–
For Database tier you need to start database and database listener. Scripts are located in Database_Install_Dir/db/tech_st/10.2.0/appsutil/scripts/$CONTEXT_NAME- For DatabaseUse script addbctl.sh
- For Database Listener
Use script addlnctl.sh
or alternatively you can uselsnrctl startstop listener_name (For Database Listener)sqlplus “/as sysdba”SQL> startup shutdown immediate
Middle/Application Tier Scripts in R12————————————————-
Scripts for Application Tier services in R12 are located in “Install_base/inst/apps/$CONTEXT_NAME/admin/scripts“
where CONTEXT_NAME is of format SID_HOSTNAME
i) adstrtal.sh Master script to start all components/services of middle tier or application tier. This script will use Service Control API to start all services which are enabled after checking them in context file (SID_HOSTNAME.xml or CONTEXT_NAME.xml)
ii) adstpall.shMaster script to stop all components/services of middle tier or application tier.
iii) adalnctl.sh Script to start / stop apps listener (FNDFS and FNDFS). This listener will file will be in 10.1.2 ORACLE_HOME (i.e. Forms & Reports Home)listener.ora file will be in $INST_TOP/apps/$CONTEXT_NAME/ora/10.1.2/network/admin directory(Mostly similar to one in 11i with only change in ORACLE_HOME i.e. from 8.0.6 to 10.1.2 )
iv) adapcctl.shScript to start/stop Web Server or Oracle HTTP Server. This script uses opmn (Oracle Process Manager and Notification Server) with syntax similar to opmnctl [startstop]proc ohslike opmnctl stopproc ohs .
(In 11i this script directly used to call apachectl executable but now calls opmnctl which in turn calls apachectl. In 11i web server oracle home was 1.0.2.2.2 but in R12 its 10.1.3)
v) adcmctl.sh Script to start / stop concurrent manager, Similar to one in 11i. (This script in turn calls startmgr.sh )
vi) adformsctl.shScript to start / stop Forms OC4J from 10.1.3 Oracle_Home. This script will also use opmnctl to start/stop Forms OC4J likeopmnctl stopproc type=oc4j instancename=forms
vii) adformsrvctl.shThis script is used only if you wish to start forms in socket mode. Default forms connect method in R12 is servlet.

If started this will start frmsrv executable from 10.1.2 Oracle_Home in Apps R12
viii) adoacorectl.shThis script will start/stop oacore OC4J in 10.1.3 Oracle_Home. This scripts will also use opmnctl (similar to adapcctl & adformsctl) to start oacore instance of OC4J like
opmnctl startproc type=oc4j instancename=oacore

ix) adoafmctl.shThis script will start/stop oafm OC4J in 10.1.3 Oracle_Home. This scripts will also use opmnctl (similar to above) to start oacore instance of OC4J like
opmnctl startproc type=oc4j instancename=oafm

x) adopmnctl.shThis script will start/stop opmn service in 10.1.3 Oracle_Home. opmn will control all services in 10.1.3 Oracle_Home like web server or various oc4j instances. If any services are stopped abnormally opmn will/should start them automatically.

xi) jtffmctl.shThis script will be used to start/stop one to one fulfilment server.

xii) mwactl.shTo start / stop mwa telnet server where mwa is mobile application.
Log File Location for Startup Shutdown Services in R12———————————————————————-Log files for startup/shutdown scripts for application/mid tier in R12 are in $INST_TOP/apps/$CONTEXT_NAME/logs/appl/admin/log(adalnctl.txt, adapcctl.txt, adcmctl.txt, adformsctl.txt, adoacorectl.txt, adoafmctl.txt, adopmnctl.txt, adstrtal.log, jtffmctl.txt )

Forget APPS Password !! Don't worry !! Just look at this !!

We need to change apps password manually, if you forgot and can’t check it in wdbsvr.app at $IAS_ORACLE_HOME/Apache/modplsql/cfg .
Please remember that the APPLSYS and APPS passwords alwayshave to be the same. Always change both at the same time. When changing thesepasswords, it is important to change the APPLSYS password first and the APPS later.
please back up the FND_ORACLE_ID and FND_USER tables before beginning.
1. Have all users log out of applications.
2. Shutdown the concurrent managers. (You can’t shutdown using adcmctl.sh if you don’t know apps password so use frontend)
3. Log in to applications as System Administrator.
4. Navigate to Security> Oracle> Register
5. Query up all available Oracle Ids.
(NOTE: do not log out of this session of Applications until you have verifiedthat all the following steps have been completed successfully).
6. At the same time, login to SQL*PLUS as the SYSTEM user.
7. In the applications session, enter the new password for APPLSYS. Re-enter (Same time do it in SQLPLUS ,after finishing Application part))the same password when asked to re-enter the password to confirm.
8. Save the change.
Note: At this point of the procedure you will see a “Caution” dialog box which states the following:
“You are changing the APPLSYS password. Doing so will affect the whole system”.
NOTE: The first character of the APPLSYS password MUST NOT BE a numeric.Use only alpha characters for the first character in the APPLSYS password.all APPS schema passwords to match the APPLSYS password.
9. In the same applications session, change the APPS password.
Note: Re-query the form (query - run) every time after changing the APPSpassword. If it is not re-queried and the APPS password is changed again, it isimpossible to continue.
10. In the SQL*Plus session, issue the following statements to change thepasswords in the database, where ‘XXX’ is the password assigned to thatuser in the previous steps:
sql>ALTER USER APPLSYS IDENTIFIED BY XXX;sql>ALTER USER APPS IDENTIFIED BY XXX;“Remember don’t log out from the application yet”
11. Open a NEW session in applications, WITHOUT CLOSING THE PREVIOUS SESSION,and log in.
If log in is successful, the change was successful. Otherwise, repeat steps 5onward, ensuring the same password is used for both APPLSYS and APPS, in bothapplications and SQL*Plus.
Followed the Metalink Doc Note:160337.1But no need to change the password for APPLSYSPUB and in metalink note they did not mention about autoconfig..
The most important thing … Please run autoconfig. so that change will effect the entire system.