Download and Installation steps for Setup loader Utility

Download and install the Setup Loader Utility: Before the official kick-off of the Implementer Workshop, your Oracle Accelerators trained DBA needs to complete the installation of the Setup Loader utility. This is a 3 step process:

Step 1: Enter a Service Request (SR) for Setup Loader utility
• Log a Service Request in My Oracle Support requesting the Setup Loader Utility (SLU) download.
• This service request triggers the generation of a Request Identification Number (RIN).
• Plan a lead time of three business days for this request to be fulfilled.

Step 2: Download & install Setup Loader Utility
• Go to E-Delivery area on Accelerators Online and paste the RIN.
• You will be presented with links to download the Setup Loader Utility.
• Download all the disks (using a Download Manager) and install on your hardware.

Step 3: Download and run the Oracle Business Accelerator Diagnostic Utility (OBADU)
• An Accelerator trained DBA must read My Oracle Support Note 549683.1 and download the OBADU.
• The OBADU gathers and reports E-Business Suite environment information to help the implementer DBA assess whether the install is successful.
• DBA must run the OBADU to verify the installation. The OBADU output will inform the DBA of appropriate actions to take if any steps have errored out.
• If unable to resolve issues, the DBA may raise a My Oracle Support Service Request and attach the output of this utility.

Step 4: Full Backup of OBA Installation
• After validating the installation execute a full instance backup.
• This back up will be used to refresh the installed E-Business Suite quickly as required.
Further reading:
• My Oracle Support Note 456200.1: Leading Practice: Setup Loader Utility install
• My Oracle Support Note 471411.1: Accelerator Project Tasks and Times
• My Oracle Support Note 430777.1: Release 12 Installation FAQ
• My Oracle Support Note 554318.1: Using Download Manager for OBA Setup Loader Utility
• My Oracle Support Note 549683.1: MANDATORY DOWNLOAD: OBA Diagnostic Utility for e-Business Suite Available
• 'Install Related' section in the Accelerator Knowledge Browse Area on My Oracle Support


Applies to:
Oracle Accelerators
Linux x86
Linux x86-64
What is being announced?
Oracle Business Accelerator Diagnostic Utility (OBA DU) for eBusiness Suite is available for download.
The Diagnostic Utility is a set of command line diagnostic scripts used to gather and report information about an Oracle Business Accelerator for E-Business Suite environment. The utility generates formatted output displaying useful system information for the implementer DBA to assess whether the install is successful. The output also informs the DBA on the appropriate actions to be taken, if necessary, on various steps that have errored out.
Who should download the Diagnostic Utility?
An approved DBA MUST download and run the Diagnostic utility to verify that the install is successful. This is mandatory before running the Configuration Tool. In case the DBA is unable to fix the issues as per the suggestion(s) noted in the Diagnostic Utility report, then the DBA must raise a Service Request on My Oracle Support against Oracle Accelerator product (Product ID: 1690) with the Diagnostics report output to expedite the resolution of install issues.

What do you need to do?
Steps to download the Diagnostic Utility are as follows:
1. Log in to Accelerators Online with your SSO Login ID.
2. Click on the Oracle logo under section E-Delivery. Click on Continue button.
3. Check two check-boxes for Customer License Agreement and Click Proceed button
4. Enter the Request Identification Number provided below and click proceed (while you copy-paste the Request Identification Number make sure you DO NOT have any spaces, it should be one continuous number from the start to he end)
Request Identification Number for Linux:
DC24713F486F631F0B6A989DAAB1035640B20DF8E2B6882774E6211724A8A9335B27719DCB8FE88B44DB5F0F8001D2D7D1402064CA1FDFBE7C4D5833DCE7BB027E2695BDB799EFAA1F5F43C4B4FB8EA1637C20A128F99F7CE69C2B5B648345B5A1D87FB738D82629294D3B4A2C4CCEF93A804EBCF8F3399021ED2C8B1328288F628912AB3D982445BD601EEC73BF424A674F264335750DAE6B7104F3D2DC0F12BB097128B2593683
Request Identification Number for Sun Solaris:
DC24713F486F631F0B6A989DAAB1035640B20DF8E2B6882774E6211724A8A9335B27719DCB8FE88B44DB5F0F8001D2D7D1402064CA1FDFBE98C7140AA52CA756554A6CD4B92355B15FC93B60539D524609916829440987C687607C56B323F025C3E775EE5C60D9DA70B04CFC854F178850B24CB3123749B26E577F9397A3DDF091283CBBB660A7798FE53C4E95468A1DE9B50A06A2E62608AB6AB54D70066775E181503DBEC90E4F8C904236CA4ECED9
Notes:
1. The Accelerator Diagnostic Utility is NOT part of Oracle Support Diagnostics (see E-Business Support Diagnostics Overview)
2. The Utility has been designed for use by Oracle Application DBAs on Oracle Business Accelerator environments only
3. The utility does not alter any data or configuration in your system
4. For accurate diagnostic information, the utility needs to be executed on both Application and Database tiers.
5. OBA DU must be run every time a new instance is created, or when an instance is refreshed with a previous backup that was taken after installing the Setup Loader Utility. This is a MANDATORY step prior to requesting a Pre-Project Review and should constitute as the sign-off step for the DBA before handing over the instance to the Project Manager.
6. OBA DU output must be verified by the DBA and checked for any errors (navigate to the Instance Information link in the file index.html.) Any error must be corrected as per the instructions.
IMPORTANT: You MUST upload the OBA DU output to a pre-project review for every OBA project.
---------------------------------------------------------------------------------------------------------
Common Errors: Following are the common errors seen in OBADU output
1. Display Variable set incorrectly - ensure that the DISPLAY (“s_display”) value in $CONTEXT_FILE is updated to a valid working VNC or to an Xserver console value and run AUTOCONFIG. (Example: :10.0). VNC should not be started on port 0:0
2. SWAP memory is less than the size of the Physical memory on the server - Although this is shown as an alert, please note that this will impact your performance, so ensure that minimum SWAP is twice the size of the Physical memory.
3. UTF8 characterset is not used - by default OBA installer selects UTF8 characterset, and if this is overriden then install errors will occur.
Who to contact for more information?
If you are unable to resolve any errors, then log an SR on My Oracle Support against Oracle Accelerator product (id: 1690) and upload the output for verification.