Check the document here
Thank you
Osama
For the people who think differently Welcome aboard
Check the document here
Thank you
Osama
The link here
Enjoy
Osama
Application Release :-
Using Apps User.
SQL> select release_name from apps.fnd_product_groups;
RELEASE_NAME
————————————————–
12.2.2
Done
Thanks
I installed Oracle E-business suite on Linux 64bit Operating system version 6.7 without any issue and the EBS version was R12.2.0 and the default database version which is 11.2.0.3.
But i choose to upgrade to EBS R12.2.4 and Oracle database 12c both done without any issues or even small error in the logs , auto config done successfully without any issue as well, the application started without any single error.
But when trying to access to the EBS application Link
I tried to compile the JSP but :-
[oracle@ammebs scripts]$ tail -f /u01/oracle/tbdlamm/fs_ne/EBSapps/log/adop/16/apply_20160114_142741/20518047/log/u20518047.log
enumerating jsps…7829
updating dependency…6473
parsing jsp…6473
writing deplist…7829
initializing compilation:
eliminating children…5954 (-1875)
searching uncompiled…5682 (2253 were stale)
translating and compiling:
searching untranslated…5622 (3369 were stale)
translating jsps… 85% complete: 4800/5622 ETA: 53s
translating jsps…5622/5622 in 7m31s
compiling jsps…
The Logs shows only this error :-
[213441] !!SEVERE WARNING!! TIMEOUT[600 seconds] EXPIRED DURING COMPILATION
I increased the apache timeout in the context file for nothing .
When access the EBS Application Link :-
From RFC 2068 Hypertext Transfer Protocol — HTTP/1.1:
10.4.5 404 Not FoundThe server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
I opened SR and now it’s 45 days without any solution !!!!
Any idea
Thank you guys 🙂
Osama
I will speaking About Fusion middleware Join me, i hope to see you there inchallah 🙂
Thanks
Osama
ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view.
Regarding to Oracle Documentation there is some restriction should be considered while trying to create materialized view Check Here or here.
But there is always workaround,
1- i create dummy table contain 1 row with 1 column only contains sysdate.
2- create Job that this sysdata on daily basis.
3- call this column in where condition of materialized view.
Problem solved.
Thanks
Osama
2015 is almost done and the doors will be closed soon, and start the new year 2016 within 5 days only, I would like to thank everyone here , Family , Friends and my blog readers who keep me motivated always to write new articles when i can, and special thanks to my mother.
i learnt a lot of things this years, sadness moment gives me experience and the happiness teach me and show me who is my real friends, i met new people around the worlds make new friends, discuss different topics with people, one of the biggest achievement for me this year to be Oracle ACE Director a dream come true, when i remember this moment i also remember my friends who nominate me because without them it will not be possible Gurcan Orhan, Heli Helskyaho, Jeff Smith , Tim Hall, kamran agayev, Iloon Ellen-Wolff, Kai Yu, and Tariq Farooq , and i would like to take this opportunity to thanks Oracle ACE program who make it real for me and for the biggest effort they provide it to us.
So let me summarize the 2015 :-
so this what i did to make the import faster ( which i completed it as well ) :-