NodeManager not starting WLS 10.3.6 On Solaris 11 on SPARC: Java: Fatal: Libucb.so.1: Open Failed: No Such File Or Directory

Applies to: Oracle Weblogic Server - Version 10.3.6 and later Oracle Solaris on SPARC (32-bit) Oracle Solaris on SPARC (64-bit) SPARC Sun SPARC Sun OS Symptoms Node Manager fails to start in WLS 10.3.6 running on Solaris 11 on SPARC. The following error is seen in the node manager logs: Mar 04, 2013 3:10:55 PM weblogic.nodemanager.server.NMServer main SEVERE: Fatal error in node manager server weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:269) at weblogic.nodemanager.server.NMServerConfig.(NMServerConfig.java:210) at weblogic.nodemanager.server.NMServer.init(NMServer.java:182) at weblogic.nodemanager.server.NMServer.(NMServer.java:148) at weblogic.nodemanager.server.NMServer.main(NMServer.java:380) at weblogic.NodeManager.main(NodeManager.java:31) Caused by: java.lang.UnsatisfiedLinkError: /u01/app/weblogic/wls10.3.6/wlserver_10.3/server/native/solaris/sparc/libnodemanager.so: ld.so.1: java: fatal: libucb.so.1: open failed: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary1(ClassLoader.java:1939) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1864) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1854) at java.lang.Runtime.loadLibrary0(Runtime.java:845) at java.lang.System.loadLibrary(System.java:1084) at weblogic.nodemanager.util.UnixProcessControl.(UnixProcessControl.java:24) at weblogic.nodemanager.util.ProcessControlFactory.getProcessControl(ProcessControlFactory.java:22) at weblogic.nodemanager.server.NMServerConfig.initProcessControl(NMServerConfig.java:267) ... 5 moreCause libucb.so.1 is not obsolete in Solaris 11 but it is not installed by default. So the ucb resources are not available until your Solaris sysadmin installs them. See http://www.oracle.com/technetwork/systems/solaris-developer/o10-015-s11-isv-adoption-198348.pdf for changes to the ucb directory in Solaris 11. Solution Have your Solaris sysadmin install the compatibility/ucb package from http://pkg.oracle.com/solaris/release/en/index.shtml and the ucb libraries should be available. See https://forums.oracle.com/forums/thread.jspa?messageID=10512396 for more instructions. And the set the env variable export LD_LIBRARY_PATH=/u01da/MW_Home/wlserver_10.3/server/native/solaris/sparc:/lib/ PS: No need to set any soft link After installing the library I was able to start the node manager succesfully ...

Automatic Storage Management

What's ASM and how it works? http://ora-x2.blogspot.com/2011/05/whats-asm-and-how-it-works.html#!/2011/05/whats-asm-and-how-it-works.html http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/10g/r2/prod/install/asminst/asminst_otn.htm?cid=4507&ssid=103147333707116 This article provides a general insight on working of Oracle ASM and the associated admin tasks. Oracle ASM is a volume manager and a file system for Oracle database files that supports single-instance Oracle Database and Oracle Real Application Clusters (Oracle RAC) configurations. Oracle ASM uses disk groups to store data files; an Oracle ASM disk group is a collection of disks that Oracle ASM manages as a unit. Within a disk group, Oracle ASM exposes a file system interface for Oracle database files. The content of files that are stored in a disk group is evenly distributed to eliminate hot spots and to provide uniform performance across the disks. The performance is comparable to the performance of raw devices. The Oracle ASM normal and high redundancy disk groups enable two-way and three-way mirroring respectively. You can use external redundancy to enable a Redundant Array of Independent Disks (RAID) storage subsystem to perform the mirroring protection function. You can add or remove disks from a disk group while a database continues to access files from the disk group. When you add or remove disks from a disk group, Oracle ASM automatically redistributes the file contents and eliminates the need for downtime when redistributing the content. Oracle ASM also uses the Oracle Managed Files (OMF) feature to simplify database file management. OMF automatically creates files in designated locations. OMF also names files and removes them while relinquishing space when tablespaces or files are deleted. Oracle ASM Files Files that are stored in Oracle ASM disk groups are called Oracle ASM files. Each Oracle ASM file is contained within a single Oracle ASM disk group. Oracle Database communicates with Oracle ASM in terms of files. This is similar to the way Oracle Database uses files on any file system. You can store the various file types in Oracle ASM disk groups, including: · Control files · Data files, temporary data files, and data file copies · SPFILEs · Online redo logs, archive logs, and Flashback logs · RMAN backups · Disaster recovery configurations · Change tracking bitmaps · Data Pump dumpsets Striping in ASM explained : Oracle ASM striping has two primary purposes: · To balance loads across all of the disks in a disk group · To reduce I/O latency Coarse-grained striping provides load balancing for disk groups while fine-grained striping reduces latency for certain file types by spreading the load more widely. Lets first understand how the files are stored in ASM. The lowest level of granularity in ASM in "Allocation Unit " (AU) . When you create a disk group, you can set the Oracle ASM allocation unit size with the AU_SIZE disk group attribute. The values can be 1, 2, 4, 8, 16, 32, or 64 MB, depending on the specific disk group compatibility level. Larger AU sizes typically provide performance advantages for data warehouse applications that use large sequential reads Next comes the EXTENT . All files in ASM are stored as set or collection of extents. An extent is made up of multiple Allocations units (AU) . Each extent fits in one single disk. To accommodate increasingly larger files, Oracle ASM uses variable size extents. OK with the above AU and Extents explained, lets continue with Striping : To stripe data, Oracle ASM separates files into stripes and spreads data evenly across all of the disks in a disk group. The fine-grained stripe size always equals 128 KB in any configuration; this provides lower I/O latency for small I/O operations. The coarse-grained stripe size is always equal to the AU size (not the data extent size). Figures 1 is illustrations of Oracle ASM file striping. In both illustrations, the allocation unit size has been set to 1 M (AU_SIZE = 1M) for the disk group which consists of 8 disks. The Oracle ASM instance is release 11.2 and the disk group compatibility attributes for ASM and RDBMS have been set to 11.2, so variable extents are shown in the graphic Figure 1 Discovering Disks in ASM The disk discovery process locates the operating system names for disks that Oracle ASM can access. Disk discovery finds all of the disks that comprise a disk group to be mounted. The set of discovered disks also includes disks that could be added to a disk group. An Oracle ASM instance requires an ASM_DISKSTRING initialization parameter value to specify its discovery strings. Only path names that the Oracle ASM instance has permission to open are discovered. The exact syntax of a discovery string depends on the platform, ASMLIB libraries, and whether Oracle Exadata disks are used. For example: For general storage : ASM_DISKSTRING = '/dev/raw/disk*' For Exadata: ASM_DISKSTRING = 'o/*/data*' Make sure to change the device permissions to read/write and ownership to grid:asmadmin or oracle:dba ( the owner of the disk devices should be the same as the owner of the Oracle binary software. The group ownership should be OSDBA of the Oracle ASM instance, which is defined at installation) How to maintain it? Let’s talk about some general administrative tasks that you would be doing. Some useful queries · Checking which instances are served by the ASM and which diskgroups belong to which DB, with V$ASM_CLIENT view SQL> SELECT dg.name AS diskgroup, SUBSTR(c.instance_name,1,12) AS instance, SUBSTR(c.db_name,1,12) AS dbname, SUBSTR(c.SOFTWARE_VERSION,1,12) AS software, SUBSTR(c.COMPATIBLE_VERSION,1,12) AS compatible FROM V$ASM_DISKGROUP dg, V$ASM_CLIENT c WHERE dg.group_number = c.group_number; · Checking which disks belong to the Diskgroups with v$ASM_DISKGROUP and v$ASM_DISK SQL> SELECT SUBSTR(d.name,1,16) AS asmdisk, d.mount_status, d.state, dg.name AS diskgroup FROM V$ASM_DISKGROUP dg, V$ASM_DISK d WHERE dg.group_number = d.group_number; · Check available free space in disk groups SQL> select group_number "Group", disk_number "Disk", path "Path", header_status, trunc(free_mb/1024) "Free GB", trunc(total_mb/1024) "Total GB", round(free_mb/total_mb, 3)*100 "Pct Free" from v$asm_disk / · Viewing Intelligent Data Placement information with V$ASM_FILE SQL> SELECT dg.name AS diskgroup, f.file_number, f.primary_region, f.mirror_region, f.hot_reads, f.hot_writes, f.cold_reads, f.cold_writes FROM V$ASM_DISKGROUP dg, V$ASM_FILE f WHERE dg.group_number = f.group_number and dg.name = 'DATA'; Create GRID Disks For Exadata only : CellCLI> CREATE GRIDDISK ALL PREFIX=sales, size=75G Create Disk Groups The SQL statement in Example below creates a disk group named data with normal redundancy consisting of two failure groups controller1 or controller2 with four disks in each failure group. The data disk group is typically used to store database data files. Creating the DATA disk group CREATE DISKGROUP data NORMAL REDUNDANCY FAILGROUP controller1 DISK '/devices/diska1' NAME diska1, '/devices/diska2' NAME diska2, '/devices/diska3' NAME diska3, '/devices/diska4' NAME diska4 FAILGROUP controller2 DISK '/devices/diskb1' NAME diskb1, '/devices/diskb2' NAME diskb2, '/devices/diskb3' NAME diskb3, '/devices/diskb4' NAME diskb4 ATTRIBUTE 'au_size'='4M', 'compatible.asm' = '11.2', 'compatible.rdbms' = '11.2', 'compatible.advm' = '11.2'; Checking ASM alert log All the ASM related files are stored under $ORACLE_BASE/diag or the directory that you list in the init.ora DIAGNOSTIC_DEST initialization parameter $ ls $ORACLE_BASE/diag/asm/+asm/+ASM alert cdump hm incident incpkg ir lck metadata stage sweep trace Note : You can do all the tasks using oracle database console or Enterprise manager grid control GUI. General Helpful commands: # Start / Stop ASM and Listener srvctl stop listener srvctl start listener srvctl stop asm srvctl start asm srvctl status asm # Connect to local/remote ASM isntance $ sqlplus / as sysasm (local connection ) $ sqlplus sys@\"myhost.mydomain.com:1521/+ASM\" AS SYSASM (remote connection) Other considerations: Disk Sizing The number of disks required depends on the size of your database. At the minimum its recommended to have two disk groups. One for Data and one for Recovery area. Each diskgroup should have a minimum of four grid disks for better performance. Keep all the disks of same size and performance in the diskgroup. ASM Disk Rebalancing Oracle ASM automatically initiates a rebalance after storage configuration changes, such as when you add, drop, or resize disks. The power setting parameter determines the speed with which rebalancing operations occur. You can minimize the impact on database performance with the setting of the POWER_LIMIT initialization parameter. Backup the ASM binaries and init.ora files Remember to backup your ORACLE_HOME and GRID_INFRASTRUCTURE binaries using OS backup tools. For 11.2 you can move the ASM init.ora to one of the diskgroups. The disk group COMPATIBLE.ASM should be set to 11.2 $ sqlplus / as sysasm SQL> CREATE SPFILE = '+DATA/asmspfile.ora' FROM PFILE = '$ORACLE_HOME/dbs/asmpfile.ora'; If you create the spfile to some other location then, create a PFILE with one line in it that identifies the path to the SPFILE. For example: Create the /u01/oracle/dbs/spfileasm_init.ora file that contains: SPFILE='+DATA/asm/asmparameterfile/asmspfile.ora' Alternatively use the ASMCMD to fix the auto lookup ASMCMD> spset +DATA/asm/asmparameterfile/asmspfile.ora Restart the ASM to read the new spfile.

Oracle E-Business Suite Installation Guide: Using Rapid Install Release 12.2 (12.2.0)

Oracle E-Business Suite Installation Guide: Using Rapid Install Release 12.2 (12.2.0) Part Number E22950-15 Getting Started This chapter contains basic information about using Rapid Install to install or upgrade an Oracle E-Business Suite system, a general description of the Rapid Wizard interface, and a description of the setup steps you must complete before you begin an installation or upgrade. This chapter covers the following topics: How Rapid Install Works Installed Components and System Requirements Before You Install Starting Rapid Install Gathering Configuration Information What To Do Next How Rapid Install Works With Rapid Install, you can perform the following tasks: Install a new, fully configured Oracle E-Business Suite system, including the latest certified Oracle E-Business Suite technology stack and patches, product family release update packs, release update packs, and other updates available at the time of this Oracle E-Business Suite release. Lay down the file system and configure server processes for an upgraded system. Rapid Install employs a wizard that guides you through the screens used to carry out the selected task. On the wizard screens, you enter configuration values for your system; these will typically be saved in the Oracle E-Business Suite database for later use. Previous releases of Oracle E-Business Suite only used a text file, config.txt, to store the supplied configuration values. The name of this configuration file includes the database SID, to give a file name of conf_.txt (for example, conf_PROD.txt). This file stores the information collected by Rapid Install for all database and Applications nodes. Rapid Install stores copies of the conf_.txt file in three separate locations: Database 11gR2 /appsutil: This copy is used on database nodes, on Applications nodes in multi-node installs, and in upgrades. It is permanently stored and not deleted. $INST_TOP: This copy is used on Applications nodes in multi-node installs, and in upgrades. It is permanently stored and not deleted. /tmp/: This copy is used by Rapid Install during the installation run. It is deleted when the installation is completed. Release 12.2 utilizes the conf_.txt file in certain situations, for example where the database has not yet been created. The configuration file is also employed in multi-node (distributed) installs, where you only need to enter the install information once, on one machine, and can then copy the configuration file to other machines as required. If you are installing in an environment where different machines are used to support the database and Applications tiers (as is typically the case), you would run Rapid Install on each machine in turn, starting with the database machine. For example, you might have three machines: one for the database tier and two for the Applications tier. So you would run Rapid Install a total of three times, once on each machine. In a multi-node environment that uses a shared application tier file system, you must run Rapid Install on the primary Applications node first. If you are using a non-shared application tier file system, the order in which you run Rapid Install on the Applications nodes does not matter. In either type of environment, you cannot run Rapid Install on more than one node in an Oracle E-Business Suite system at once. The main configuration engine used by Rapid Install is called AutoConfig. Rapid Install supplies the configuration information to AutoConfig, which stores the configuration for each node in a node-specific configuration file called a context file . Important: AutoConfig is delivered with, and required by, a new installation of Oracle E-Business Suite Release 12.2. AutoConfig simplifies and standardizes the management of your system configuration: after the initial installation, you can use the Configuration Editor in Oracle Applications Manager to update the values of parameters for Oracle E-Business Suite components, and then run an AutoConfig script to populate the system configuration files with new values. Note: For further details of AutoConfig and other management tools, see the Technical Configuration chapter of Oracle E-Business Suite Concepts. Installing New Systems Rapid Install automatically supplies values for most of the many parameters your Oracle E-Business Suite system will need. You do, however, have a initial choice to make: you can either supply a number of your own parameters and carry out a Standard install, or you can opt for an Express install and let Rapid Install supply default values for nearly all the parameters. A Standard install gives you more flexibility to configure your system to meet particular requirements for your site, while an Express install is useful if you know that the default settings will suffice, or you wish to set up a test system where the settings do not matter. Both types offer the option of installing either a fresh database (one that is fully configured but contains no transaction data), or a Vision Demo database (one that contains example transaction data for a fictitious company, to use for training or demonstration purposes). Installation Strategies and Terminology The installation process for Oracle E-Business Suite has been designed to provide as much flexibility as possible, enabling you to install a basic system and subsequently add machines in order to meet specific deployment requirements or simply the need for growth. The following terms are used when installing Oracle E-Business Suite: A server is the traditional term for a process that provides a particular functionality. This term, in the sense of a denoting a single process, is less appropriate for some components of the Release 12 architecture. Where applicable, the replacement term of service is used. A node is a logical grouping of servers, and therefore fundamentally a software concept rather than a hardware concept, although it is often also used to refer to the machine on which a particular node is installed. For example, an Applications node is a combination of a specific configuration, node file system, and instance file system, which together support the services needed for it to act as an Applications node. This book will also refer to the primary Applications node (which may be the only Applications node), and the database node, which supports the Oracle database server. A tier is a logical grouping of services, potentially spread across more than one physical machine. The three-tier architecture that comprises an Oracle E-Business Suite installation is made up of the database tier, which supports and manages the Oracle database; the Applications tier, which supports and manages the various Oracle E-Business Suite components, and is sometimes known as the middle tier; and the desktop tier, which provides the user interface via an add-on component to a standard web browser. New Installation (Standard) In a new Standard installation, you define many aspects of the configuration. You will need to choose where to install the required nodes (database node and primary Applications node). For simpler installations, the database node and the Applications node can be installed on the same machine. This type of installation is generally used for small systems or for demonstration purposes. More commonly, the database node is installed on one machine, and the Applications node on another machine. This provides improved manageability, scalability, and performance. Applications tier processing can be distributed across multiple Applications nodes. You can also specify additional Applications nodes if you wish to scale up the Applications tier; typically, the additional nodes will be located on their own machines, to help increase availability and flexibility of your system. Oracle E-Business Suite Release 12.2.0 only supports a unified APPL_TOP, i.e. the APPL_TOP is no longer separated into different parts (Concurrent Processing, Forms, Web). However, although all Applications nodes use a unified APPL_TOP, different sets of services can be specified on different nodes. This allows you to create specialized nodes, for example to support Concurrent Processing or Web serving. Note: See Oracle E-Business Suite Concepts for more information about the Oracle E-Business Suite architecture and file system. New Installation (Express) In an Express installation, you set up a fully configured, single-user/single-machine system using a few basic configuration parameters, such as database type and name, top-level installation directory, and port pools choice. The remaining directory specifications and mount points are supplied by Rapid Install using default values. An Express installation includes a set of core products and uses the US7ASCII character set. Upgrading an Existing System to Release 12.2 There are two distinct paths for upgrading an existing system, depending on the release being upgraded from: Release 11i (11.5.10) to Release 12.2 Release 12.0 or 12.1 to Release 12.2 Note: See Performing an Upgrade in this book. See also Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.2 or Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to 12.2. Installed Components and System Requirements This section lists the certified components installed with Rapid Install, and the system requirements for an Oracle E-Business Suite Release 12.2 installation. Technology Stack Components Rapid Install automatically installs and configures the required technology stack components for both the database node and the Applications node. The database tier technology stack for a new Oracle E-Business Suite Release 12.2 installation consists of an Oracle 11g Release 2 Oracle Home for both new installations and upgrades. Important: Oracle E-Business Suite Release 12.2 requires Oracle Database Enterprise Edition. No other editions are supported. The Applications node technology stack includes, among other components: Oracle Application Server 10g (10.1.2.3), which includes: Oracle Forms Oracle Reports Oracle Fusion Middleware 11g, which includes: Oracle WebLogic Server Note: In Release 12.2, the required Java Development Kit (JDK) is automatically installed by Rapid Install. You do not need to install the JDK separately. Detailed, product-specific notes on My Oracle Support describe use of these optional components with Oracle E-Business Suite. You can also check product certifications from My Oracle Support by clicking on the Certifications tab (which may be under the More tab). System Software, Patch Level, and Networking Requirements This section describes the system software needed on different platforms, patch level requirements in multi-node installations, and essential networking requirements. System Software The following maintenance tools must be installed on all machines, and their locations specified both in the $PATH of the account that runs the wizard, and in the $PATH of the accounts that will own the database tier and Applications tier file systems. Note: See Create Login Accounts in this chapter, and Node-specific Parameters in Configuration Details. Platform-Specific Software Requirements Operating System Required Maintenance Tools Oracle Solaris SPARC (64-bit) ar, ld, make, X Display Server Linux x86-64 ar, gcc, g++, ld, ksh, make, X Display Server IBM AIX on Power Systems (64-bit) ar, cc, ld, linkxlC, make, X Display Server HP-UX Itanium ar, cc, aCC, make, X Display Server Additionally, the following utilities are required on all UNIX-based operating systems: unzip, df, ps, and wall. Note: Oracle E-Business Suite is not currently supported on Microsoft Windows Server. Example information about working in Microsoft Windows is provided for future reference only. Operating System Patch Levels In a multi-node installation: All application tier nodes must be at the same operating system patch level All database tier nodes must be at the same operating system patch level In addition, Oracle recommends that operating system kernel parameter settings should match on all nodes of a particular tier (either application or database). While this is not essential, it simplifies management and maintenance by allowing the machines to be regarded as in effect identical. Networking The key networking requirement is for the hosts file to include an entry for the installation machine, formatted as follows: . Important: The hostname must be no longer than 30 characters. Shared Memory Permissions On applicable UNIX and Linux platforms, ensure that the /dev/shm directory has neither the 'noexec' nor 'nosuid' permissions set. If it has, you may encounter the following Oracle JVM JIT runtime error: ORA-29516: Aurora assertion failure: Assertion failure at joez.c: Bulk load of method java/lang/Object. failed; insufficient shm-object space CPU, Memory, and Disk Space Requirements Because there are different product combinations, different user profiles, and different configurations, there is no one sizing answer for all hardware platforms. Some hardware vendors have sizing worksheets that model the CPU and memory requirements of Oracle E-Business Suite on their hardware. The most reliable strategy to ensure that the hardware is sized appropriately is to install a test environment, and then conduct a benchmark test with a configuration, product mix, and user load that simulates your own current and expected workloads. These conditions can help verify performance before you install your production-ready environment. An alternative is to ask Oracle Consulting Services or your hardware vendor to find another Oracle E-Business Suite system running a product mix and user profile similar to yours. CPU Requirements CPU requirements for running Oracle E-Business Suite depend on, in no particular order: Number of concurrent users and their usage profiles Number of concurrent manager processes and the types of jobs that they are running Load for activities other than Oracle E-Business Suite Size of the database Desired response time Memory Requirements The Oracle E-Business Suite Database requires adequate memory to support the specific needs of a given installation. To determine the total memory requirements on the machine where the database is installed, you must take the following into account: Oracle Database overhead Size of System Global Area (SGA) Number of concurrent users Any non-Oracle software that has to run on the machine (this is not recommended) You should aim to allow for any expected growth in usage over the planned lifetime of the Oracle E-Business Suite system. It is, however, relatively straightforward to scale up a system later to meet additional requirements, either by adding nodes to the application tier or employing Oracle Real Application Clusters (Oracle RAC) on the database tier. Important: To help determine your memory requirements for the various Oracle E-Business Suite Database components, refer to My Oracle Support Knowledge Document 396009.1, Database Initialization Parameters for Oracle E-Business Suite Release 12. Minimum Memory for an Oracle E-Business Suite Installation The minimum amount of memory needed to run Oracle E-Business Suite is about 6 GB for the database tier machine and 10 GB for an application tier machine. This kind of configuration would typically support 10 or fewer users in addition to online patching activity. Important: For detailed guidance and recommendations on this subject, refer to the section, "Database and Application Tier Sizing." Single-user single-host non-production system For the special case of a system that will only be employed by a single user to develop or test patches, the minimum memory requirement is 8 GB. Important: This figure represents the minimum amount of memory that can be employed, and may rise either to meet the needs of new releases or the deployment of components such as additional managed servers. Disk Space Requirements Rapid Install installs the file system and database files for all products, regardless of their licensed status. The approximate file system disk space requirements for a standard installation are: File System Space Requirements for Standard Installation Node Space Required Database node file system (Fresh install) 90 GB (includes database files and 11gR2 database Oracle Home). Database node file system (Vision Demo database) 200 GB (includes database files and 11gR2 database Oracle Home). Applications node file system (OracleAS 10.1.2 Oracle Home, Oracle FMW Oracle Home, COMMON_TOP, APPL_TOP, and INST_TOP) 144 GB (64 GB used for dual application tier file system, plus 80 GB that must be kept free for file system cloning). Also, see Note below for language considerations. Note: The minimum recommended space required for each active language is 16 GB in the file system (for both APPL_TOPs), and 3 GB in the database. For more information, refer to My Oracle Support Knowledge Document 1314621.1, Oracle E-Business Suite NLS Release Notes, Release 12.2. Warning: At present, Rapid Install does not support installing Oracle E-Business Suite into a directory that has more than 2 TB of free space. This is because of address space restrictions. Stage area For a production database installation, running Rapid Install from a stage area requires at least 48 GB to accommodate the file system and database files in the stage area. See Set Up the Stage Area Important: As the size of the staging area mainly depends on the database size, care should be taken to size it according to the enterprise needs and database footprint. Oracle E-Business Suite log and output files Many Oracle E-Business Suite products generate log and output files during runtime. The disk space needed varies with the number of users and transactions, and depends on how frequently you purge these files. Tip: Log and output files are not automatically purged. Determine a strategy for archiving and purging these files after the installation, and monitor the disk space they consume to determine how much space you may need in the future. Temporary directories and files For install time temporary disk space, Rapid Install uses the directory defined by the TMPDIR variable (on UNIX) or TEMP and TMP variables (on Windows). You should ensure there is adequate (typically, several GB) of free temporary space before starting an installation. At runtime, Oracle E-Business Suite requires temporary disk space. For example, each concurrent manager writes temporary parameter files, Oracle Reports writes temporary format files, and Oracle Forms writes temporary buffer records. Rapid Install sets the temporary directory based on the value you supply on node-specific settings screens. The directory defined by the TMPDIR variable is also used for some temporary files, such as certain patches. Updates and patches You will need disk space for applying updates, patches, maintenance packs, family packs, and minipacks, and for any backup files that may be created. Note: For further information, refer to Oracle E-Business Suite Maintenance Guide. Other files The total disk space estimate must account for the requirements of files other than those directly related to Oracle E-Business Suite. For example: Operating system software Online backups Custom applications development files Files for any other software that you use Database and Application Tier Sizing Guidelines This section contains database and application tier sizing information based on a test upgrade from Oracle E-Business Suite Release 12.1.3 to Release 12.2. The Release 12.1.3 database was 456 GB in size. General Sizing Guidelines Below are some general sizing guidelines for Oracle E-Business Suite Release 12.2. In addition to the memory needed based on the sizing guidelines below, you should allow an extra 2 GB of free memory for the database tier machine, and an extra 3 GB of free memory for the application tier machine (for Online Patching). The sizing of various transactions depend on the transaction type (such as Oracle Application Framework, Forms, or batch programs), and the transaction workload (light, medium, or heavy). Some transactions may require more memory (such as those for Oracle Configurator). Note: You should always size your systems based on tests using representative data and workloads for your own environment. Oracle Application Framework Transactions The following table shows the memory used for OAF-type transactions with light to medium workload characteristics: Number of Concurrent Users Database Machine Memory Number of Database Machine CPUs Application Tier Machine Memory Number of Application Tier Machine CPUs 0-10 4 GB 2 6 GB 2 100-200 8 GB 2 8 GB 2 200-400 12 GB 4 10 GB 4 400-800 20 GB 8 14 GB 8 You should plan your resources according to these figures. Important: Figures of this kind represent a minimum amount of memory, and your specific requirements may need more. Oracle Forms Transactions Each Oracle Forms process requires 40 MB of memory on the application tier. So the memory required is given by the formula: (Number of concurrent Oracle Forms users) x 40 MB The following table lists the additional memory for the given number of users: Number of Users Required Memory 100 4 GB 200 8 GB 400 16 GB 800 32 GB On the database tier, there is one database session per open form, with a minimum of two database sessions per Oracle Forms user (one session for the Navigator form, and one for the active form). Each Oracle Forms session requires approximately 30 MB of PGA memory on the database. For Oracle Forms processes on the database, an additional 30 MB per session for the PGA allocation is needed. The following table lists the memory required for the number of sessions: Number of Forms Sessions Required Memory 100 3 GB 200 6 GB 400 12 GB 800 24 GB Database Size for Example Upgrade The data in the following table was determined from the upgrade from Release 12.1.3 to Release 12.2. Before Upgrade Database Size (GB) After Upgrade Database Size (GB) Delta (GB) % Growth 456 481 25 5.5 Environment Details for Example Upgrade The environment details for this upgrade are as follows: Operating system: Oracle Linux Enterprise Edition Server Release 5.8 Server memory: 34 GB Number of CPUs: 32 Oracle Database Release: 11.2.0.3 Oracle E-Business Suite Release: 12.1.3 Note: The database tier and application tier are on the same machine in this example. Database configuration is as follows: SGA: 5 GB Shared pool: 1 GB PGA: 3 GB Log buffer: 30 MB job_queue_processes: 32 For more information on performing upgrades, refer to: Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2 and Oracle E-Business Suite Upgrade Guide, Release 11i to 12.2. Note: During the upgrade of the "Admin Tier", batchsize and number of workers used were 1000 and 32 respectively. Application Tier Size for Example Upgrade Oracle E-Business Suite Release 12.2 is installed with three file systems, to accommodate the new Online Patching feature. fs1 (production file system) - Used by the current users of the system. fs2 (copy of production file system) - Used by the patching tools. fs_ne (non-editioned file system) - Used to store data that is kept in the file system (such as data import and export files, reports, and output and log files). In addition, the pre-upgrade file system has a requirement for an INST_TOP. All three file systems in the Release 12.2 installation serve a single database. The file system in use by the running application is never patched. All patches are applied to the secondary file system. The following table lists the data for the example upgrade scenario from Release 12.1.3: Component Before Upgrade Size After Upgrade Size ORACLE_HOME 3.6 GB 3.6 GB APPL_TOP 28 GB N/A INST_TOP 20 MB N/A fs1 (APPL_TOP+ INST_TOP) N/A 30 GB fs2 (APPL_TOP+ INST_TOP) N/A 29 GB fs_ne N/A 660 KB JVM Parameter Settings for 64-bit Java on WLS Web Tier If you are running Oracle E-Business Suite on 64-bit Java, bear in mind the following key points: You can support 150-180 users per 1 GB of JVM heap size. Usually, one JVM is allocated per 2 CPUs. Only the maximum allocated heap (Xmx) has an impact on response time. Changing the initial heap size (Xms) does not have an impact on response time. For best results, use multiple managed instances. For example, two managed instances with a total of 4 GB heap size for each instance will provide a much better response times than one JVM with a total heap size of 8 GB. Note: For more information, refer to the section "Customizing the number of instances of a particular service type" in Chapter 3, Technical Configuration, of Oracle E-Business Suite Setup Guide. Further to the previous point, use JVMs with a maximum of 4 GB, and scale for more users by using additional managed instances. There are two benefits from doing this: Garbage collection (GC) activity is more easily balanced (automatically) with multiple managed instances. Each instance will be able to utilize a separate connection pool. In essence, you need to maintain a balance between the allocated JVM heap size per instance and the available connection pool for that instance. Careful sizing is needed for the concurrent manager components, especially Java concurrent programs. If you will be processing relatively large volumes of data, you may need to increase the Xms/Xmx settings for the Java concurrent programs. This is normally done via the options field of the define concurrent program screen. Note that when you increase the number of workers, the memory requirements may increase significantly: this is because each Java concurrent worker will require at least an amount of memory specified by the value of Xms. Before You Install You must follow all the relevant steps in this section before you begin the installation. Rapid Install handles the details of the installation or upgrade actions based on the information you enter on the Rapid Install screens. If you collect the necessary information before you begin, the installation or upgrade will be completed more rapidly. In addition to meeting the prerequisites described in this book and in the platform-specific notes, you should also ensure you understand the licensing agreement for your organization. Review Associated Documentation Before running Rapid Install, you should refer to My Oracle Support Knowledge Document 1320300.1, Oracle E-Business Suite Release Notes, Release 12.2. In addition, you should carefully read the relevant Oracle E-Business Suite platform-specific Installation and Upgrade document. These are listed in My Oracle Support Knowledge Document 1583131.1, Oracle E-Business Suite Release 12.2 Information Center - Install. For troubleshooting hints and tips, refer to My Oracle Support Knowledge Document 1378579.1, Troubleshooting Rapid Install for E-Business Suite Release 12.2. Create Operating System Accounts Before running Rapid Install, you must create the operating system accounts that will be used in the installation of the database node and Applications node file systems. Details of this process depend on whether you are using a UNIX system or Windows system. Consult the appropriate operating system documentation as required. For UNIX users The operating system user that owns the database node file system and starts the database node services is called the oracle user. This user must be created with a primary group of 'dba'. The operating system user that owns the Applications node file system and starts the Applications node services is called the applmgr user. The names of both these accounts must be the same on all nodes in an Oracle E-Business Suite system. Note: The term "UNIX" refers to all variants of that operating system, including Linux. Single-user UNIX installations In order to prepare for a single-user installation, you must first create an oracle user account and log in as the oracle user to run Rapid Install. The account should be created with a default shell that is compatible with the Bourne shell. Note: If using the Korn Shell (ksh), ensure that the $ENV environment variable is not set before starting the installation, as it can alter variables that are set by the Oracle installation scripts. The command unset ENV can be used to unset the variable if necessary. Multi-user UNIX installations In order to prepare for a multi-user installation, you must first create an oracle user account and an applmgr user account. Both should be created with a default shell that is compatible with the Bourne shell. Log in as root to run Rapid Install. Then specify the oracle user as the Oracle OS user, and the applmgr user as the Apps OS user. The oracle user is the account that owns the database node technology stack (11gR2 Oracle Home) and the database files. The default name for the oracle user is ora. For example, for a production (PROD) environment, the default Oracle OS username might be oraprod. The applmgr user is the account that owns the Applications node technology stack (APPL_TOP, COMMON_TOP, OracleAS 10.1.2 Oracle Home, and Oracle Fusion Middleware Oracle Home). The default name is appl. For example, for a Vision Demo (VIS) environment, the default Apps OS username might be applvis. On machines containing multiple nodes, you can assign one user account to be the owner of the database node file system, and another to be the owner of the Applications node file system. For this type of install, Rapid Install can install both nodes in one run if the install is started by the root user. If you are installing on a machine with only one node to install, or with all nodes sharing the same user, you can run the install as either the root user or the specific user for those nodes. For Windows users On Windows, the user who runs Rapid Install owns the file system for all components (both the database file system and the Oracle E-Business Suite file system). The Windows installation is therefore equivalent to the UNIX single-user installation. Before you install Oracle E-Business Suite, make sure the user account for the installation has full local administrative privileges, and permission to print to either local or network printers. We recommend that you create a new domain-level account (for example, oracle) and make it a member of these groups: Administrators (local user) Domain Users (domain user) This account does not need to be a member of any other group, and must not be a member of the GUEST group. Refer to Windows Help for information on creating accounts and assigning accounts to groups. Set Up the Stage Area This section describes the tasks you need to perform to download the Release 12.2 installation software and create the stage area where the software will reside in readiness for installation. Note: Network-attached storage devices (such as NFS-mounted disk volumes) can be used for the stage area. For the required mount options, refer to My Oracle Support Knowledge Document 359515.1, Mount Options for Oracle Files When Used With NAS Devices. Obtain Installation Software The Oracle E-Business Suite Release 12.2 Media Pack includes Oracle E-Business Suite, Oracle Database 11gR2, and Oracle Fusion Middleware. It is obtainable in Zip format from the Oracle Software Delivery Cloud (edelivery.oracle.com). Note: If you are supplied with the software on DVDs, the following principles still apply to the organization of the software. Each Zip file is identified as "_NofM". For the complete set of files for a given Part Number, you need all the Zip files from 1 to M. For example, if Oracle Part Number "V15690-01" — corresponding to "Oracle E-Business Suite Release 12.2 for Linux x86-64 Rapid Install APPL_TOP - Disk 1 (Part 1 of 3)" — is divided into three parts, you must download the three Zip files V15690-01_1of3.zip, V15690-01_2of3.zip, and V15690-01_3of3.zip. Important: Before you download the files, read the Release Notes for the specific release you are installing. Create the Stage Area You must first create a directory, called StageR122, into which you will download the installation software mentioned above. You then unzip the requisite files and build the stage area, in readiness for running Rapid Install. This section describes the steps to follow. Create Stage Area Directory Issue the appropriate command for your operating system in the desired location on the file system. For UNIX Users In the following example, the stage area directory is created under a mount point called /u01: $ cd /u01 $ mkdir Stage122 For Windows Users In the following example, the stage area directory is created on the F: Drive: C:\>F: F:\>mkdir Stage122 Download Software and Unzip Start Here Files After creating the stage area directory, download only the following components of the Oracle E-Business Suite Release 12.2 Media Pack into it: Oracle E-Business Suite Release 12.2.0 Rapid Install Start Here Oracle E-Business Suite Release 12.2.0 Rapid Install (All Disks and Parts) Oracle E-Business Suite Release 12.2.0 for Rapid Install Technology One-Off Patches Oracle WebLogic Server 11gR1 (10.3.6) Generic and Coherence Oracle Fusion Middleware Web Tier Utilities 11g Patch Set 5 (11.1.1.6.0) for Warning: If any other components are downloaded to the Release 12.2 stage directory, Rapid Install may subsequently fail as follows: Fatal Error: TXK Install Service oracle.apps.fnd.txk.config.ProcessStateException: OUI process failed : Exit=1 See log for details. CMD= /stage/apps/LINUX/R12.2/Installation/TechInstallMedia/ohs11116/Disk1/runInstaller -waitForCompletion -ignoreSysPrereqs -force -silent -responseFile /global/oracle/vis12.2/fs2/inst/apps/vis12.2_hostname/temp/cfgHome/response/APPS_OHS_HOME/txkOHS_11116.rsp To resolve this issue, delete the incompatible components from the stage directory, re-download them to a suitable directory elsewhere, and then re-run Rapid Install. Once you have downloaded the components listed above, unzip the "Oracle E-Business Suite Release 12.2.0 Rapid Install Start Here" files (only), and proceed to run the buildStage script as described in the next section. Run buildStage Script This script has several functions, which are selected from a series of menus. A key function is to unzip the rest of the installation software for subsequent use by Rapid Install: in the process, various subdirectories are created under the stage area. Important: Running the buildStage script is a mandatory pre-installation step. The buildStage options you should choose depend on whether you have an existing stage area or not. The buildStage script is run as follows on UNIX and Windows. UNIX $ cd /u01/StageR122/startCD/Disk1/rapidwiz/bin $ buildStage.sh Windows C:\>F: F:\>cd StageR122\startCD\Disk1\rapidwiz\bin F:\>buildStage.cmd The buildStage menus are shown below. Main Menu Build Stage Menu ------------------------------------------------------ 1. Create new stage area 2. Copy new patches to current stage area. 3. Display existing files in stage TechPatches. 4. Exit menu Enter your choice [4]: These options are used as follows. Main Menu - Option 1 Use this option if you want to create a new stage area, for example if you are performing an installation from scratch. It will unzip the downloaded software and apply the one-off patches. Choosing this option will display a submenu that shows the available platforms: Rapid Install Platform Menu ------------------------------------------------------ 1. Oracle Solaris SPARC (64-bit) 2. Linux x86-64 3. IBM AIX on Power Systems (64-bit) 4. HP-UX Itanium 5. Exit Menu Enter your choice [5]: Specify the platform on which you want to install Oracle E-Business Suite. You will then be prompted for the location of the installation software you downloaded: Please enter the directory containing the zipped installation media: Enter the full path to the directory. The stage area will then be built for you. Main Menu - Option 2 This option updates the technology one-off patches for an existing stage area. Choosing option 2 will display the submenu that shows the available platforms: Rapid Install Platform Menu ------------------------------------------------------ 1. Oracle Solaris SPARC (64-bit) 2. Linux x86-64 3. IBM AIX on Power Systems (64-bit) 4. HP-UX Itanium 5. Exit Menu Enter your choice [5]: Specify the applicable platform, and the buildStage script will stage the technology one-off patches packaged with the startCD into the stage/TechPatches directory. Main Menu - Option 3 This option displays (in a tree format) the files in your stage/TechPatches directory: Enter your choice [4]: 3 Directory /s0/oracle/XB45/startCD/Disk1/rapidwiz/bin/../../../../TechPatches |--DB | |--11071989 | | |--p11071989_112030_Linux-x86-64.zip | |--11820674 | | |--p11820674_R12_LINUX.zip | |--12949905 | | |--p12949905_112030_Linux-x86-64.zip | |--12951696 | | |--p12951696_112030_Generic.zip | |--12955701 | | |--p12955701_112030_Linux-x86-64.zip | |--13040331 | | |--p13040331_112030_Linux-x86-64.zip | |--13388104 Stage Area Structure The stage area you have built consists of a top-level directory, with subdirectories startCD, EBSInstallMedia, TechInstallMedia, and TechPatches. Stage Area Directories the picture is described in the document text The startCD directory contains Rapid Install itself (in a subdirectory called Disk1), plus supporting files and documentation. The EBSInstallMedia directory contains the following subdirectories: AppDB (Oracle E-Business Suite Database) Apps (Oracle E-Business Suite products) AS10.1.2 (Oracle Application Server 10.1.2) The TechInstallMedia directory contains the following subdirectories: database (Oracle11gR2 ORACLE_HOME) ohs11116 (Oracle HTTP Server) wls1036_generic (Oracle WebLogic Server, part of Oracle Fusion Middleware) The TechPatches directory contains the following subdirectories: MiddleTier (Application tier patches) DB (Database Tier patches) Starting Rapid Install The stage directory has now been created and the downloaded Oracle E-Business Suite software unzipped. Verify oraInst.loc (UNIX only) If you are using a UNIX platform, you should now verify the existence and contents of the oraInst.loc file. . Check that oraInst.loc exists in the correct directory for your platform: Linux and IBM AIX on Power Systems - /etc Oracle Solaris - /var/opt/oracle Confirm that the contents of oraInst.loc look like this: inventory_loc=/oracle/oraInventory where /oracle/oraInventory points to the directory where the central inventory is to be located. This location must be writeable by the user account that is to run Rapid Install. If the oraInst.loc file does not exist, create it in the correct directory with contents as shown above. Run the rapidwiz Command You are now ready to start Rapid Install as shown in the examples below. The exact path will depend on the disk location you specified for your staging area. UNIX: $ cd /startCD/Disk1/rapidwiz $ ./rapidwiz Windows: C:\>f: F:\>cd \startCD\Disk1\rapidwiz F:\\startCD\Disk1\rapidwiz>rapidwiz.cmd Special Startup Options If required, you can add parameters to the Rapid Install startup command to change its behavior. Using an Alias For the Host Machine If you want to use an alias (not the actual name of the host machine), use the -servername parameter when you start Rapid Install. UNIX: $ rapidwiz -servername Windows: D:\RAPIDWIZ> Rapidwiz.cmd -servername Gathering Configuration Information The Rapid Install wizard provides input screens to gather system-specific values for configuring a new or upgraded system. Important: You should be familiar with system requirements, resources, and product licensing agreements before you run Rapid Install. You should also have a adequate understanding of Oracle DBA and system administrator responsibilities. Note: When you are entering values for Rapid Install, ensure that you specify the actual locations for the directories involved, so that AD utilities can properly identify the directories afterward. Do not specify the directory locations as symbolic links. Top-level Directories and Mount Points Rapid Install needs to be told the locations of the top-level directories and mount points on the database node, and the Applications node(s). It derives subdirectories from these top-level directories. Important: Only the values for the base directories can be specified. The derived values for other directories must be left at the default values that are calculated by Rapid Install. Products and Country-specific Functionalities During the installation, Rapid Install automatically installs all products, country-specific functionalities (localized products), and required shared products in the database and in the file system, regardless of license status. Licensed products are those specified in your licensing agreement with Oracle. However, you must indicate on the Rapid Install wizard screens which products and country-specific functionalities you have licensed to register them as being active in your system. This active flag is important during any patching and other system-wide maintenance tasks that are performed after the initial installation or upgrade. NLS Settings Oracle E-Business Suite Release 12.2.0 provides multilingual support for text parts of Oracle E-Business Suite, and for product data. Because it offers support for the Unicode AL32UTF8 character set, you can, if required, run a number of languages in a single instance. You choose the character set for both the database and application products when you run Rapid Install. Important: The choice of character sets should be made carefully. It is possible to convert from some character sets to others at a later stage, but there are restrictions. For example, you can convert from US7ASCII to AL32UTF8, but not from AL32UTF8 to US7ASCII. The profile options for language and territory are configured at the site level when you run Rapid Install. The language you choose as the base language is used for the language profile. The default settings for date and number formats are derived from the territory profile setting. Note: For an introduction to NLS and related subjects, see Globalization Support in Oracle E-Business Suite Concepts. For an in-depth discussion of globalization issues, see My Oracle Support Knowledge Document 393861.1, Oracle Applications Globalization Guide (Release 12). Port Pool The various features and components of Oracle E-Business Suite require the availability of a large number of ports on your system. To simplify deployment and management of the various ports, Oracle E-Business Suite includes the concept of a port pool. The port pool concept includes a mechanism for determining a default base value for each type of port; formatted values, which often contain multiple ports; and a mechanism for determining a unique value for each pool. The net result of this is that there are 100 different port pools (sets), which are guaranteed to contain non-overlapping values. You simply specify the pool you want to use, and a consistent set of port values are chosen for all the required ports. Important: The introduction of online patching in Oracle E-Business Suite Release 12.2 means that a separate port pool is needed for each of the two file systems (run and patch) that online patching requires. However, the Oracle HTTP Server port, Active web port, Java Object Cache (JOC) port, and Database port must be the same for both file systems. Ports Used By Oracle E-Business Suite Port Name Description and Comments Node Manager Port Port used by Node Manager. WLS Admin Server Port Port used by WLS Admin Server. WLS OACORE Application Port Port used by WLS OACORE Applications. WLS Forms Application Port Port used by WLS Forms Applications. WLS OAFM Application Port Port used by WLS OAFM Applications. WLS Forms-C4WS Application Port Port used by WLS Forms-C4WS Applications. WLS Portlet Application Port Port used by WLS Portlet Applications. OHS Administration Proxy Port Proxy port used by OHS. Oracle HTTP Server uses this port for internal communication with Oracle Fusion Middleware Control. Database Port Port on the database server used by the Oracle Net listener. RPC Port RPC port on the concurrent processing server that receives incoming Report Review Agent requests. Web SSL Port Port used by Web SSL (Secure Sockets Layer). ONS Local Port Oracle Notification Server Local Port. ONS Remote Port Oracle Notification Server Remote Port. ONS Request Port Oracle Notification Server Request Port. Web Listener Port Port on the Web server used by the Web listener. Active Web Port Defaults to the value of web port. When a load balancer is used, the value of this port should be changed to the port on which the load balancer is listening for http requests. Forms Port Port on the Forms server used by the Forms Listener. Metrics Server Data Port Port on the Primary Web Node used by the Primary Forms Metrics Server Process to collect server load data. The data can be used to distribute Forms clients among Forms server nodes. Metrics Server Request Port Port on the Forms server used by the Metrics Server as a request port. JTF Fulfillment Server Port JTF Fulfillment Server Port Number. MSCA Server Port MSCA Server Port Number. MSCA Telnet Server Port MSCA Telnet Server Port Number. MSCA Dispatcher Port MSCA Dispatcher Port Number. Java Object Cache Port Port used by the Java Object Caching infrastructure. Must be same on all application tier nodes. If there are firewalls separating the application tier nodes, this port must be opened on all firewalls. OC4J JMS Port Range for OACORE Java JMS Port Range for the OACORE Oracle Container. OC4J JMS Port Range for Forms Java JMS Port Range for the Forms Oracle Container. OC4J JMS Port Range for Home Java JMS Port Range for the Home Oracle Container. OC4J JMS Port Range for OAFM Java JMS Port Range for the OAFM Oracle Container. OC4J JMS Port Range for Forms-C4WS Java JMS Port Range for the Forms-C4WS Oracle Container. OC4J AJP Port Range for OACORE Java AJP Port Range for the OACORE Oracle Container. OC4J AJP Port Range for Forms Java AJP Port Range for the Forms Oracle Container. OC4J AJP Port Range for Home Java AJP Port Range for the Home Oracle Container. OC4J AJP Port Range for Oafm Java AJP Port Range for the OAFM Oracle Container. OC4J AJP Port Range for Forms-C4WS Java AJP Port Range for the Forms-C4WS Oracle Container. OC4J RMI Port Range for OACORE Java RMI Port Range for the OACORE Oracle Container. OC4J RMI Port Range for Forms Java RMI Port Range for the Forms Oracle Container. OC4J RMI Port Range for Home Java RMI Port Range for the Home Oracle Container. OC4J RMI Port Range for OAFM Java RMI Port Range for the OAFM Oracle Container. OC4J RMI Port Range for Forms-C4WS Java RMI Port Range for the Forms-C4WS Oracle Container. DB ONS Local Port Database Oracle Notification Server Local Port. The recommended value is between 6300 and 6399. DB ONS Remote Port Database Oracle Notification Server Remote Port. The recommended value is between 6400 and 6499. Oracle Connection Manager Port Port on Oracle Connection Manager server used by Oracle Connection Manager listener. Navigating in the Wizard The Rapid Install input screens are in the form of a wizard, which prompts you for the information needed to install a new Oracle E-Business Suite system or upgrade an existing one. The following conventions apply to navigating in the wizard. Input Fields and Drop-down Lists Complete or accept the default in input fields (provided they are not grayed out). Type information directly into input boxes, or select information from the list of valid options in fields that have a drop-down menu. Drop-down lists present all the valid options for an input field. Click an option to select it. Combo boxes also present valid options in the form of a drop-down list. They also allow you to replace an option on the list by typing in a valid option. When this type of input is allowed, it is noted in the text. Buttons and Keys You can select from mutually exclusive options by clicking the appropriate radio button. On each screen, you can click the Tab key or press the Up or Down Arrow keys to move between options. There are buttons at the bottom of each screen that allow you to Cancel the Rapid Install process or move either Back to the previous screen or forward to the Next screen. Vertical and horizontal scroll bars make it possible to move hidden fields into view. Help Most screens offer mouse-over help for individual fields: a description of the information that goes in the field appears in a small text box when you move the mouse over the field. In addition, most screens display a Help button. Click it to see screen-level help — a general description of the screen, and a summary of the input fields that it displays. Once you have reviewed the information on a help screen, clicking OK returns you to the wizard screen from where you requested the help. What To Do Next Start Rapid Install and begin the installation process by choosing one of the following paths: If you want to create a new Oracle E-Business Suite Release 12.2.0 system on a single machine or a group of machines, follow the steps in Standard Installations. If you want to upgrade an Oracle E-Business Suite system from Release 11i, Release 12.0, or Release 12.1, follow the steps in Performing an Upgrade. When you have completed the steps in the chapter that applies to your system, read and follow the applicable instructions in Finishing Tasks to finish the installation or upgrade.

JDK 7 Installation on the Oracle Solaris Operating System and to check the version of jdk in 32 bit and 64 bit

http://docs.oracle.com/javase/7/docs/webnotes/install/solaris/solaris-jdk.html To check the jdk version The output that you show from java -version is from a 32-bit version. If it is 64-bit, you'll see something like "64-bit Server VM" in there instead of "Client VM". java -d64 -version If it's not a 64-bit version, you'll get a message that looks like: This Java instance does not support a 64-bit JVM. Please install the desired version. http://docs.oracle.com/javase/7/docs/webnotes/install/solaris/solaris-jdk.html

Informatica PowerCenter and PowerConnect Adapters 9.5.1 Download

Please follow the below steps to download Informatica PowerCenter and PowerConnect Adapters 9.5.1 and Oracle Business Intelligence Data Warehouse Administration Console 11g Step 1 : Go to edelivery.oracle.com Step 2 :Click on Sign In (give your emaild id and password ) Step 3: Accept the Terms and Conditions and Export Restrictions . Step 4 :Select a Product Pack Oracle Business Intelligence Platform : Microsoft Windows x64 (64-bit) Click Go Step 5: Oracle Business Intelligence 11g Media Pack for Microsoft Windows x64 (64-bit) Click Continue Step 6: Download Oracle Business Intelligence Data Warehouse Administration Console 11g and Informatica PowerCenter and PowerConnect Adapters 9.5.1 for Windows x86 (64-bit) (Part 1 of 4) V41973-01 Part 1 of 4 867M Download Oracle Business Intelligence Data Warehouse Administration Console 11g and Informatica PowerCenter and PowerConnect Adapters 9.5.1 for Windows x86 (64-bit) (Part 2 of 4) V41973-01 Part 2 of 4 2.0G Download Oracle Business Intelligence Data Warehouse Administration Console 11g and Informatica PowerCenter and PowerConnect Adapters 9.5.1 for Windows x86 (64-bit) (Part 3 of 4) V41973-01 Part 3 of 4 2.0G Download Oracle Business Intelligence Data Warehouse Administration Console 11g and Informatica PowerCenter and PowerConnect Adapters 9.5.1 for Windows x86 (64-bit) (Part 4 of 4) V41973-01 Part 4 of 4 2.0G Step 7: whoooooooooooom