Hi Readers,
After a long break I am updating my blog.
Its very difficult to find out patch/RUP details. Currently I am working on implementation project so thought to share few things.
After installation R12.1.1 you need to apply RUP2 patch to upgrade release 12.1.1 to 12.1.2
Here is the patch no's .
First apply pre-requisite then apply RUP2.
a)Pre-requisite - 8502056 - R12.AD.B.DELTA.2 - will take 1 hr
b)Oracle E- business RUP2 - 7303033 [12.1.1 to 12.1.2] - will take 10-12 hrs.
fyi,
select release_name from fnd_product_groups;
Regards
Guru
Wednesday, February 10, 2010
Sunday, May 11, 2008
Change Sysadmin Password from backend
Hi Folks,
As you very much aware that you can change SYSADMIN password using FNDCPASS utility
FNDCPASS apps/appspwd 0 Y system/manager USER SYSADMIN sysadminpwd
Here I am giving another way to change the SYSADMIN password and Application User Login passwords using fnd_user_pkg from backend. Here is the procedure
sql> declare
var_l boolean;
begin
var_l=fnd_user_pkg.change_password('sysadmin','sysadminpwd');
end;
sql> PL/SQL Procedure Successfully Compiled.
You can verify from backend that password has changed successfully or not without login to the application.
sql>select fnd_web_sec.validate_login('sysadmin','sysadminpwd') from dual;
should returns 'Y'.
Happy Reading
Thanks
--Guru
As you very much aware that you can change SYSADMIN password using FNDCPASS utility
FNDCPASS apps/appspwd 0 Y system/manager USER SYSADMIN sysadminpwd
Here I am giving another way to change the SYSADMIN password and Application User Login passwords using fnd_user_pkg from backend. Here is the procedure
sql> declare
var_l boolean;
begin
var_l=fnd_user_pkg.change_password('sysadmin','sysadminpwd');
end;
sql> PL/SQL Procedure Successfully Compiled.
You can verify from backend that password has changed successfully or not without login to the application.
sql>select fnd_web_sec.validate_login('sysadmin','sysadminpwd') from dual;
should returns 'Y'.
Happy Reading
Thanks
--Guru
Monday, May 5, 2008
AppsLocalLogin.jsp gives blank page in R12
Hi Everyone,
Recently I faced one problem in R12 instance. I was not able to see the login screen after application URL. I got blank page on AppsLocalLogin.jsp or sometimes I got a message unable to autheticate the session instead of giving me username and password screen. Backend side everything is working fine. I did lot of head strikes and searched lot of docs but did not found any. I also compiled all the JSPs,cleared persistence logs etc. but problem did not get resolved. Finally after 5-6 hours hardwork I got the soultion , one of my collegue has written the update trigger on apps.fnd_user table as below
CREATE TRIGGER xyz_trigger
BEFORE INSERT ON UPDATE
ON apps.fnd_user
FOR EACH ROW
BEGIN xx_demo.launch_work_process (:NEW.user_id, :NEW.user_name);
END;
Simply, I disabled the update trigger and it works for me. AppsLocalLogin.jsp Page is opening fine.
But I could not understand how it happens. If anyone of you know the reason then please update me .
Thanks
--Guru
Recently I faced one problem in R12 instance. I was not able to see the login screen after application URL. I got blank page on AppsLocalLogin.jsp or sometimes I got a message unable to autheticate the session instead of giving me username and password screen. Backend side everything is working fine. I did lot of head strikes and searched lot of docs but did not found any. I also compiled all the JSPs,cleared persistence logs etc. but problem did not get resolved. Finally after 5-6 hours hardwork I got the soultion , one of my collegue has written the update trigger on apps.fnd_user table as below
CREATE TRIGGER xyz_trigger
BEFORE INSERT ON UPDATE
ON apps.fnd_user
FOR EACH ROW
BEGIN xx_demo.launch_work_process (:NEW.user_id, :NEW.user_name);
END;
Simply, I disabled the update trigger and it works for me. AppsLocalLogin.jsp Page is opening fine.
But I could not understand how it happens. If anyone of you know the reason then please update me .
Thanks
--Guru
Friday, March 28, 2008
Upgrade 12.0.0 to 12.0.4
Hi Friends,
I install 12.0.0 in HPUX-PA-RISC(64-bit). I was doing cloning without following cloning doc and prerequisites(406982.1) and failed to do so.AS per cloning doc I planned to upgrade (RUP2)12.0.2 but finally I decided directly upgrade to 12.0.4 .Refer note (402308.1) and metalink note
(465776.1)
Below are the steps I follow in upgrade.
1> Take cold backup of the application as well as database . After completion start the application and database
2> Download patch RUP4(6435000).
3> Also download one prerequisite patch for this.R12.AD.A.DELTA.4(6510214).
4> Put your application in Maintenanace mode using 'adadmin' utility.
5> Note down your release_name from fnd_product_groups and patch_evel for AD from fnd_product_installations.
5> Install prerequisite patch of RUP4 i.e.R12.AD.A.DELTA.4(6510214) using adpatch . Dont merge this patch with RUP4.
6> Verify ad_bugs and fnd_product_installations table that this patch has applied successfuly.
7> Compile apps scehma using adadmin.
8> Now start applying 6435000 patch using adpatch . I did not specify any option becuase this is a major upgrade .Let patch decide what to do.
9> After fininshing the copy portion , This patch will run more than 18000 jobs . Will take more than 14 hrs without fail.
10>After completion of these jobs this patch drops the fnd_install_processes and ad_deferred_jobs and creates again fnd_install_processes and ad_deffered_jobs to run 250 and 900 jobs for compile pl/sql and compile forms.
11>During this patch the time consuming task is gather stats and adutlrcmp.sql for compiling objects.(took more than 5 hours ).
After completion of this patch verify the log files.. and check ad_bugs and fnd_product_groups table.
Major issues I faced
1> when patch starts compiling invalid objects taking more than 2.5 hrs and hang on library cache locks. I was trying to skip the worker but on backendside script is still running. And I am not able to kill this sql properly because this script already ran 2.5 hrs.Then I planned to abort my adpatch session.I killed my adpatch session.Dont worry guys this will not harm anything.Then I find this compilation script and write exit; in the first line. worker will read this file from the first line and exit this file and start execution next steps.YOu can compile manually after completion of this patch.
2>Second script is gather stats took time ,the procedure I followed , choose 6th option from adctrl and status goes to failed for this worker then I edit the gather stat sql with exit; in the first line and restart the worker.It will automatically exit the script and move on.
you can find above scripts in $AD_TOP/patch/sql
2>If you are planning to apply this from the scratch then drop fnd_install_processes and ad_deferred_jobs table but use adpatch options=nocopyportion and edit your compilation script and gather stat scripts with exit; in the first line.(nocopyportion is used because you save your more than 1.5 hrs becaue copying is already done in the previous session and no need to choose start previous session.)
3>After successfully completion of this patch my apache is not coming up. Then I applied patch (6616965). This problem occurs only in HPUX platform
If you have any questions please write me....
Cloning concepts for R12 will come in next post.....
I install 12.0.0 in HPUX-PA-RISC(64-bit). I was doing cloning without following cloning doc and prerequisites(406982.1) and failed to do so.AS per cloning doc I planned to upgrade (RUP2)12.0.2 but finally I decided directly upgrade to 12.0.4 .Refer note (402308.1) and metalink note
(465776.1)
Below are the steps I follow in upgrade.
1> Take cold backup of the application as well as database . After completion start the application and database
2> Download patch RUP4(6435000).
3> Also download one prerequisite patch for this.R12.AD.A.DELTA.4(6510214).
4> Put your application in Maintenanace mode using 'adadmin' utility.
5> Note down your release_name from fnd_product_groups and patch_evel for AD from fnd_product_installations.
5> Install prerequisite patch of RUP4 i.e.R12.AD.A.DELTA.4(6510214) using adpatch . Dont merge this patch with RUP4.
6> Verify ad_bugs and fnd_product_installations table that this patch has applied successfuly.
7> Compile apps scehma using adadmin.
8> Now start applying 6435000 patch using adpatch . I did not specify any option becuase this is a major upgrade .Let patch decide what to do.
9> After fininshing the copy portion , This patch will run more than 18000 jobs . Will take more than 14 hrs without fail.
10>After completion of these jobs this patch drops the fnd_install_processes and ad_deferred_jobs and creates again fnd_install_processes and ad_deffered_jobs to run 250 and 900 jobs for compile pl/sql and compile forms.
11>During this patch the time consuming task is gather stats and adutlrcmp.sql for compiling objects.(took more than 5 hours ).
After completion of this patch verify the log files.. and check ad_bugs and fnd_product_groups table.
Major issues I faced
1> when patch starts compiling invalid objects taking more than 2.5 hrs and hang on library cache locks. I was trying to skip the worker but on backendside script is still running. And I am not able to kill this sql properly because this script already ran 2.5 hrs.Then I planned to abort my adpatch session.I killed my adpatch session.Dont worry guys this will not harm anything.Then I find this compilation script and write exit; in the first line. worker will read this file from the first line and exit this file and start execution next steps.YOu can compile manually after completion of this patch.
2>Second script is gather stats took time ,the procedure I followed , choose 6th option from adctrl and status goes to failed for this worker then I edit the gather stat sql with exit; in the first line and restart the worker.It will automatically exit the script and move on.
you can find above scripts in $AD_TOP/patch/sql
3> I also faced below error frequently
/d04/apoc/apps/tech_st/10.1.3/appsutil/jdk/jre/bin/java ...Exception in thread "main" java.sql.SQLException: Io exception: Socket read timed outat oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:387)at oracle.jdbc.driver.PhysicalConnection.
Then I shutdown my other R12 instance running on same server will resolve my issue and I restarted my patch.
Note:
1>If you killed your adpatch seesion. then try using previous session to start.2>If you are planning to apply this from the scratch then drop fnd_install_processes and ad_deferred_jobs table but use adpatch options=nocopyportion and edit your compilation script and gather stat scripts with exit; in the first line.(nocopyportion is used because you save your more than 1.5 hrs becaue copying is already done in the previous session and no need to choose start previous session.)
3>After successfully completion of this patch my apache is not coming up. Then I applied patch (6616965). This problem occurs only in HPUX platform
If you have any questions please write me....
Cloning concepts for R12 will come in next post.....
Thanks
--Guru
Subscribe to:
Posts (Atom)