What is the Exadata and Exalogic servers

Oracle Exalogic Elastic Cloud is the world’s first and only integrated middleware machine—a combined hardware and software offering designed to revolutionize data center consolidation. Enterprises can bring together tens, hundreds, or even thousands of disparate, mission-critical, performance-sensitive workloads on Oracle Exalogic with maximum reliability, availability, and security. Oracle Exalogic’s unique high-bandwidth, low-latency interconnect fabric means that complex, distributed applications can run with a responsiveness simply not achievable with typical servers used in data centers today.

Oracle Exadata Database Machine provides an optimal solution for all database workloads, ranging from scan-intensive data warehouse applications to highly concurrent OLTP applications. With its combination of smart Oracle Exadata Storage Server Software, complete and intelligent Oracle Database software, and the latest industry standard hardware components from Sun, the Database Machine delivers extreme performance in a highly-available, highly-secure environment. With Oracle’s unique clustering and workload management capabilities, the Database Machine is also well-suited for consolidating multiple databases onto a single grid. Delivered as a complete pre-optimized and pre-configured package of software, servers, and storage, the Sun Oracle Database Machine is simple and fast to implement and ready to tackle your large-scale business applications.


Thanks
Srini

11i / r12 India Localization Patch Tool

Introduction to India Localization Patch:
Pre-Requisite Patch Check:
select * from jai_applied_patches where patch_number = ‘<Patch_Number>’;
Object Details:
Check the status of the objects that will be updated by the patch driver.
select owner, object_name, object_type, last_ddl_time, status
from all_objects
where object_type like '<OBJ_TYP>' and object_name = ‘<OBJ_NAME>’;
India Localization Patch Tool – 11.5.10.2

Object Version:
select object_name||';;' ||
decode(object_type,'TRIGGER','en','VIEW','vw','PACKAGE','pls','PACKAGE
BODY','plb','compile')||';;' || jai_get_sql_ver_f(object_name, object_type)
from user_objects
where object_name in ‘(‘<OBJ_NAME>');
India Localization Patch Tool – 11.5.10.2

Checking FND Version:
select patch_level, application_name
from fnd_product_installations fpi, fnd_application_tl fat
where patch_level is not null and fpi.application_id = fat.application_id and patch_level like
'%FND%' ;
Invalid objects:
select count(*) from dba_objects where status='INVALID';
India Localization Patch Tool – 11.5.10.2

Connection to JA schema:
Object Backup:
India Localization Patch Tool – 11.5.10.2

Patch Top:
Copy the patch to JA_TOP and unzip it. Change the directory to patch folder. Inside the
patch folder you can see a sql supplied by oracle to find out the version of all the objects
which patch will be updating.
Patching:
DB, Concurrent Node:
perl $JA_TOP/inpatch/indpatch.pl drvr_file=8277581.drv fnd_patchset=H
appspwd=<PWD> japwd=<PWD> mode=D systempwd=<PWD>
perl $JA_TOP/inpatch/indpatch.pl drvr_file=8277581.drv fnd_patchset=H
appspwd=<PWD> japwd=<PWD> mode=C systempwd=<PWD>
strings -a ja_in_localization_setup_checks_trg.sql | grep Header
Form Node 1:
India Localization Patch Tool – 11.5.10.2

perl $JA_TOP/inpatch/indpatch.pl drvr_file=8277581.drv fnd_patchset=H appspwd=
<PWD> japwd=<PWD> mode=F systempwd=<PWD>
strings -a ja_in_localization_setup_checks_trg.sql | grep Header
Form Node 2:
perl $JA_TOP/inpatch/indpatch.pl drvr_file=8277581.drv fnd_patchset=H
appspwd=<PWD> japwd=<PWD> mode=F systempwd=<PWD>
strings -a ja_in_localization_setup_checks_trg.sql | grep Header
Backup Folder:
A backup folder will be created inside the patch top. In this location you can find all the
objects that are going to be replaced by patching.
India Localization Patch Tool – 11.5.10.2

Patch Log Location and Log File:
India Localization Patch Tool – 11.5.10.2

and more ….
Monitoring:
There is no tool to monitor India Localization Patch like how we can adctrl for adpatch in
EBS. But we can find by checking for the processes running in OS.

 

 

Thanks

Srini