Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Download
Standard view
Full view
of .
Look up keyword
Like this
2Activity
0 of .
Results for:
No results containing your search query
P. 1
Patching for Oracle Apps

Patching for Oracle Apps

Ratings: (0)|Views: 132|Likes:
Published by Krishna

More info:

Published by: Krishna on Jul 30, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
See more
See less

04/04/2015

pdf

text

original

 
 While generating snapshots before patching if we see Integrity Error then we need toremove the following file SNAPSHOT.TXT from $APPL_TOP/admin/sid/out.Issue with APPLSYS and APPS passwordScenario 1: As you know that apps and applsys password should be in synch and should be changedusing FNDCPASS.There can be situation where a novice user changes applsys password from the backenddatabase. In that case when you try to start the services it will show following error  APP-FND-01496: Cannot access application ORACLE passwordCause: Application Object Library was unable access your ORACLE password.You can even reproduce this issue (ofcourse after taking the backup of FND_USER andFND_ORACLE_USERID table) using the following steps1. Use the ALTER USER command to change the APPLSYS password2. Try to run the adstrall.sh script to start Apps services.3. You will get an error ³Cannot complete applications logon. You may have entered aninvalid applications password, or there may have been a database connect error.´4. Then try FNDCPASS to fix password and you will get the error the APP-FND-01496error.If this situation happens then you cannot access the application. Infact the services evenwont start.Resolution to such problem is to rollback the 2 tables FND_USER andFND_ORACLE_USERID. Once you rollback the tables, apps and applsys passwordswill be in synch and password will be older one. You can then run FNDCPASS andchange the password.Scenario 2:Some times when you run FNDCPASS, you get following error  APP-FND-01502: Cannot encrypt application ORACLE passwordCause: Application Object Library was unable encrypt your ORACLE password. Action: Contact your support representative. (ORACLEUSER=APPS_SERV)The error comes because the table fnd_oracle_userid contain rows for schemas that doesnot exist. Those rows must be deleted from the table.Use the following query to get the details of the schema that doest not existsselect * from fnd_oracle_useridwhere oracle_username not in(select username from all_users);The rows returned by this query can be deleted from FND_ORACLE_USERID table.This will resolve this issue.Scenario 3:
 
There can be situation where users has update APPLSYS password using ALTERcommand in database directly and also you dont have backup of those tables. Under suchsituation, it is very difficult to recover the application and make it working. Stillfollowing methodology is proposed which might help you to restore the password backand make your application work fine.For this to work you should have some other application (may be debug or UAT) which ishaving the same passwords or default passwords for schemas. If you have suchapplication the following the below steps in the application which is affected by passwordmismatch.This method is for resetting apps and applsys passwords. Below are the SQL statementsthat will help you reset the APPS and APPLSYS passwords to APPS, the APPLSYSPUBpassword to PUB, and the SYSADMIN password to SYSADMIN.WARNING: This procedure will cause all user passwords to become invalid. ALL userspasswords will need to be reset through the sysadmin responsibility.Step 1) Reset the Oracle User IDsOpen a SQL*Plus as SYSTEM and reset the passwords for the APPS, APPLSYS, and the APPLSYSPUB Oracle user ID: ALTER USER apps IDENTIFIED BY apps; ALTER USER applsys IDENTIFIED BY apps; ALTER USER applsyspub IDENTIFIED BY pub;Step 2) Backup the FND_ORACLE_USERID and FND_USER tables (even though thesetables are rightnow corrupted, do take a backup. You can restore the same when ever you want).Open a SQL*Plus session as APPLSYS and backup the tablescreate table FND_ORACLE_USERID_BAK as (select * fromFND_ORACLE_USERID);create table FND_USER_BAK as (select * from FND_USER);Step 3) Reset the APPS and APPLSYS application encrypted passwordsOpen a SQL*Plus session as APPLSYS and update the FND_ORACLE_USERID table.update FND_ORACLE_USERIDset ENCRYPTED_ORACLE_PASSWORD =µZGA34EA20B5C4C9726CC95AA9D49EA4DBA8EDB705CB7673E645EED570D5447161491D78D444554655B87486EF537ED9843C8 
 
where ORACLE_USERNAME in (¶APPS¶, µAPPLSYS¶);commit;This encrypted string we are updating is the default encrypted string for apps. So if your application is having apps password the encrypted string will look like this. We areupdating this encrypted string here directly.Verify the table update:select ENCRYPTED_ORACLE_PASSWORDfrom FND_ORACLE_USERIDwhere ORACLE_USERNAME IN (¶APPS¶, µAPPLSYS¶);Step 4) Reset the APPLSYSPUB application encrypted passwordOpen a SQL*Plus session as APPLSYS and update the FND_ORACLE_USERID table.update FND_ORACLE_USERIDset ENCRYPTED_ORACLE_PASSWORD =µZG31EC3DD2BD7FB8AD2628CE87DDDF148C1D2F248BE88BE987FDF82830228A88EF44BC78BC7A9FAD4BFB8F09DAD49DF7280E¶where ORACLE_USERNAME = (¶APPLSYSPUB¶);commit;The above encrypted string is the encrypted string for password pub. If your applsyspubpassword is pub then the encrypted string in FND_ORACLE_USERID will look likethis.Verify the table update:select ENCRYPTED_ORACLE_PASSWORDfrom FND_ORACLE_USERIDwhere ORACLE_USERNAME = µAPPLSYSPUB¶;Once these updates are done, try your luck by running FNDCPASS and it should workfine.Hope this help !!!ReferencesMetalink note ID 445153.1Metalink note ID 429244.1Oracle Apps Technology BlogPATCHINGError message: ORA-01013: user requested cancel of current operationResolution to error: If this error occurs, simply use adctrl to restart the worker on thecurrent machine.Error message: Patch not applied successfully, adpatch did not cleanup its restart files(*rf9)Resolution to error: If this error occurs, execute the following as the instance owner:

Activity (2)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->