Share the content if you found it is useful (You can share using 300 community websites) click "share" at the end of the post.

You are encouraged to leave a comment.








Wednesday, January 28, 2009

Patching and Password Issues (Deep Dive)

Adpatch is running and fails on one of the workers. To fix this worker and continue with the patch installation, a new patch needs to be applied. Considering that only 1 adpatch session can run on an instance at any given time, how can a patch be applied when adpatch is already running?

Solution Description
1. Using the adctrl utility, shutdown the workers.

a. adctrl

b. Select option 3 "Tell worker to shutdown/quit"

2. Backup the FND_INSTALL_PROCESSES table which is owned by the APPLSYS schema

a. sqlplus applsys/ applsys_password

b. SQL> create table fnd_Install_processes_back as
select * from fnd_Install_processes;

c. The 2 tables should have the same number of records.

SQL> select count(*) from fnd_Install_processes_back;

SQL> select count(*) from fnd_Install_processes;

3. Backup the AD_DEFERRED_JOBS table.

a. $ sqlplus applsys/applsys_passwd

b. SQL> create table AD_DEFERRED_JOBS_back
as select * from AD_DEFERRED_JOBS;

c. The 2 tables should have the same number of records.

SQL>select count(*) from AD_DEFERRED_JOBS_back;

SQL> select count(*) from AD_DEFERRED_JOBS;

4. Backup the .rf9 files located in $APPL_TOP/admin//restart directory.

At this point, the adpatch session should have ended and the cursor should be back at the Unix prompt.

a. cd $APPL_TOP/admin/

b. mv restart restart_back

c. mkdir restart

6. Drop the FND_INSTALL_PROCESSES table and the AD_DEFERRED_JOBS table.

a. $ sqlplus applsys/

b. SQL> drop table FND_INSTALL_PROCESSES;

c. SQL> drop table AD_DEFERRED_JOBS;

8. Apply the new patch.

9. Restore the .rf9 files located in $APPL_TOP/admin/restart_back directory.

a. cd $APPL_TOP/admin/

b. mv restart restart__back1

c. mv restart_back restart

10. Restore the FND_INSTALL_PROCESSES table which is owned by the APPLSYS schema.

a. sqlplus applsys/

b. create table fnd_Install_processes as select * from fnd_Install_processes_back;

c. The 2 tables should have the same number of records.

select count(*) from fnd_Install_processes;

select count(*) from fnd_Install_processes_back;

11. Restore the AD_DEFERRED_JOBS table.

a. sqlplus applsys/

b. create table AD_DEFERRED_JOBS as select * from AD_DEFERRED_JOBS_back;

c. The 2 tables should have the same number of records.

select count(*) from AD_DEFERRED_JOBS_back;

select count(*) from AD_DEFERRED_JOBS;

12. Re-create synonyms

a. sqlplus apps/apps

b. create synonym AD_DEFERRED_JOBS for APPLSYS.AD_DEFERRED_JOBS;

c. create synonym FND_INSTALL_PROCESSES FOR APPLSYS.FND_INSTALL_PROCESSES;

13. Start adpatch, it will resume where it stopped previously.



MANUAL METHOD For changing the APPS Password
- Follow the steps exactly. MUST: Back up the table fnd_oracle_userid.

1)Have all users log out of applications.
2) Shutdown the concurrent managers.
3) Log into applications as SYSADMIN.
4) Navigate to the Register Oracle IDs form
(Security -> Oracle -> Register)
5) Query up all available Oracle IDs.
6) Log into SQL*Plus as SYSTEM.
$ sqlplus SYSTEM/
7) In applications session, enter the new password for APPLSYS:
A) View -> Query by example -> Run
B) Change password of applsys ->
press down arrow.
C) Verify password of applsys -> press down arrow.
D) File save. DO NOT requery or exit the form!
8) In the SQL*Plus session run the following command

SQL> alter user applsys identified by ;

9) In applications session, entered the new password for APPS:

A) View -> Query byexample -> Run
B) Change password of apps ->
press down arrow.
C) Verify password of apps ->
press down arrow.
D) File save. DO NOT requery or exit the form!
10) In Unix SQL*Plus
$ alter user apps identified by ;
11) Exit Oracle Applications.
12) Close Browser.
13) Log out of SQL*Plus.
14) Open new Browser session and Log into Oracle Applications.
15) Restart concurrent managers after changing batch startup script password.
Proceed with exactly the above steps to change the remaining Oracle Database Accounts (Database User name on the Oracle Users form
(Security -> Oracle -& gt; Register).
Thus if there are 140 applications passwords to update it will take a few hours.

II. BATCH METHOD Patch 1685689 offers a utility to allow changing passwords
with the command FNDCPASS with the required parameters (see usage below).

This utility should give the applications administrator the ability to run the applications

passwords change in batch.

NOTE: The patch 1685689 is not obsolete yet as of the updating of this blog

README from patch 1685689 A NEW C EXECUTABLE TO CHANGE APPLICATION, ORALCE USER AND APPLSYS PASSWORD

Usage =====
FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS WELCOME



No comments:

Related Posts Plugin for WordPress, Blogger...

Let us be Friends...

Share |

Popular Posts

Recent Comments