Oracle Apps DBA stuff

Starting the Listener Fails With: TNS-12557 or TNS-12555: TNS:Permission Denied

2012-01-27T20:51:00.003+03:00

Starting the Listener Fails With: TNS-12557 or TNS-12555: TNS:Permission Denied [ID 343253.1]

		Modified 30-SEP-2011 Type PROBLEM Status PUBLISHED

In this Document
  Symptoms
  Changes
  Cause
  Solution
  References

Applies to:

Oracle Net Services - Version: 10.2.0.1.0 to 11.1.0.7.0 - Release: 10.2 to 11.1
Information in this document applies to any platform.
This issue could present on any UNIX platform.

Checked for relevance on 30-SEP-2011.

Symptoms

An attempt to start the Listener using lsnrctl start yields any of the error stacks below:

TNS-12555: TNS:permission denied
TNS-12560: TNS:protocol adapter error
TNS-00525: Insufficient privilege for operation
Linux Error: 1: Operation not permitted

TNS-12560: TNS:protocol adapter error
TNS-00530: Protocol adapter error
HPUX Error: 20: Not a directory

TNS-12557: TNS: Protocol adapter not loadable
TNS-12560: TNS: Protocol adapter error
TNS-00527: Protocol Adapter not loadable

TNS-12555: TNS:permission denied
TNS-12560: TNS:proto adapter error
TNS-00525: Insufficient privilege for operation
IBM/AIX RISC System/6000 Error: 1: Not owner

Using only the IPC protocol in the listener.ora and a level 16 listener trace reveals the following:


[16-JUL-2008 09:16:55:995] nsc2addr: entry 
[16-JUL-2008 09:16:55:995] nsc2addr: (ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROCFSTST)) 
[16-JUL-2008 09:16:55:995] sntuscrt: entry 
[16-JUL-2008 09:16:55:995] sntuscrt: failed to change permissions of dir /tmp/.oracle 
[16-JUL-2008 09:16:55:995] sntuscrt: exit 
[16-JUL-2008 09:16:55:995] ntusb2adr: entry 
[16-JUL-2008 09:16:55:995] ntusb2adr: KEY = EXTPROCFSTST 
[16-JUL-2008 09:16:55:995] ntusb2adr: exit 
[16-JUL-2008 09:16:55:995] nsc2addr: normal exit 

Note the following error stack:

[16-JUL-2008 09:16:55:996] nsopen: opening transport... 
[16-JUL-2008 09:16:55:996] ntusconn: entry 
[16-JUL-2008 09:16:55:996] ntusconn: connect: operation 2 
[16-JUL-2008 09:16:55:996] ntuscnp: entry 
[16-JUL-2008 09:16:55:996] sntusgph: entry 
[16-JUL-2008 09:16:55:996] sntusgph: fail to search /tmp/.oracle 
[16-JUL-2008 09:16:55:996] sntusgph: exit 
[16-JUL-2008 09:16:55:996] ntus2err: entry 
[16-JUL-2008 09:16:55:996] ntus2err: sd=10, op=1, resnt[0]=530, resnt[1]=20, resnt[2]=0 
[16-JUL-2008 09:16:55:996] ntus2err: exit 
[16-JUL-2008 09:16:55:996] ntuscnp: exit 
[16-JUL-2008 09:16:55:996] ntusconn: exit 
[16-JUL-2008 09:16:55:996] nserror: entry 
[16-JUL-2008 09:16:55:996] nserror: nsres: id=0, op=65, ns=12560, ns2=0; nt[0]=530, nt[1]=20,nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
[16-JUL-2008 09:16:55:996] nsopen: unable to open transport

Changes

This is either a new installation or some permissions changes have taken place on the /.../.oracle directory.

Cause

1) Ensure that /tmp/.oracle or /var/tmp/.oracle directory exists.

2) Confirm that the user who is trying to start the listener has adequate read and write permissions on the directory specified above. The permissions should be 777.

3) If the /tmp directory has reached full capacity, this would cause the listener to fail to write the socket files.

Solution

To implement the solution, please use the following example:

1. cd /var/tmp

2. Check the whether the .oracle directory exists:

cd .oracle

3. If the directory does not exist, request the System Administrator create the directory and set the ownership as root:root with the permissions set to 01777

mkdir /var/tmp/.oracle
chmod 01777 /var/tmp/.oracle
chown root /var/tmp/.oracle
chgrp root /var/tmp/.oracle

4. Next try starting the TNS Listener using the ‘lsnrctl start ’ command.

References

Related

Products

Oracle Database Products > Oracle Database > Net Services > Oracle Net Services

Errors

OPERATION NOT PERMITTED; TNS-525; TNS-12555; TNS-12557; TNS-530; TNS-12560; TNS-527

Creating a Connection from Hyperion BI+ Interactive Reporting to an Oracle Database

2012-01-20T07:02:00.000+03:00

Creating a Connection from Hyperion BI+ Interactive Reporting to an Oracle Database [ID 1050593.1]

		Modified 19-JUL-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution

Applies to:

Hyperion BI+ - Version: 9.3.0.0.00 to 9.3.3.0.00 - Release: 9.3 to 9.3
Information in this document applies to any platform.
Oracle Database
Oracle*Net
ODBC
***Checked for relevance on 19-Jul-2011***

Goal

Creating connections from Hyperion BI+ Interactive Reporting to Oracle Database

Solution

There are two options (ODBC, Oracle*Net):

ODBC

Create ODBC connection using MERANT OEM 5.2 32-BIT Oracle Wire Protocol (in Microsoft Windows that would be in Control Panel > Administrative Tools > Data Sources (ODBC) > System DSN tab; in Unix .odbc.ini file)
Create an OCE file (with the same name as the intended Hostname/Provider to be assigned in LSC below) on Microsoft Windows using Interactive Reporting Studio (File menu > New... > A New Database Connection File > OK button) using ODBC/ODBC or ODBC/Oracle as "What connection software do you want to use?"/"What type of database do you want to connect to?"
Launch Hyperion > Reporting and Analysis > Utilities and Administration > Service Configurator > Local Service Configurator and double click on DAS.
Create a new data source using ODBC/ODBC (or ODBC/Oracle) as Connectivity Type/ Database Type; "Select the name of the data source:".
Restart Services.
Import this OCE file in workspace to be available as a data source for BQY files.

ORACLE*NET (SQL*NET)

Install Oracle database client software on machine with DAS server and machine with IR Studio; Ensure tnsnames.ora file points to database to be queried.
Create an OCE file on Microsoft Windows using Interactive Reporting Studio (File menu > New... > A New Database Connection File > OK button) using Oracle Net/Oracle as "What connection software do you want to use?"/"What type of database do you want to connect to?"
Launch Hyperion > Reporting and Analysis > Utilities and Administration > Service Configurator > Local Service Configurator and double click on DAS.
Create a new data source using Oracle Net/Oracle as Connectivity Type/ Database Type; "Select the name of the data source:".
Restart Services.
Import this OCE file in workspace to be available as a data source for BQY files.

UpdateNativeDir Utility

2012-01-18T17:52:00.004+03:00

UpdateNativeDir Utility

UpdateNativeDir Utility

What is the UpdateNativeDir utility used for?

This utility is used to update external user and group identities in the Hyperion Native Directory for those

objects that have moved in the external directory.The data related to all the external providers in the search
order is synchronized.

This utility is used also delete user and group entries from the Hyperion Native Directory that cannot be located in
the external directory. User and group information such as membership, provisioning, cache will be deleted from
Native Directory if the user or group is not found in the external providers.

Where can the UpdateNativeDir utility be installed from?

Its located in HYPERION_HOME/Common/ Utilities/SyncOpenLDAPUtility directory

When is a user or group deleted from Hyperion Native Directory?

When a user is actually removed from external directory OR

External provider is removed from search order of CSS.xml

When is a user or group updated in the Hyperion Native Directory?

If the user is moved from one OU to other and the new OU is configured in CSS.xml.

When is a user or group not updated or deleted in the Hyperion Native Directory?

If any provider of the user/group type is not reacheable due to communication problems OR

There are no changes to the user.

How to run the UpdateNativeDir?

To run this utility, make sure that JAVA_HOME in updateNativeDir.bat (or .sh) is modified so that it points to
a value Java Runtime.

Run the script provided (UpdateNativeDir.sh or UpdateNativeDir.bat) giving absolute path of CSS.xml as argument. Ensure
that all the required jar files and dll files are located in lib/bin folder.

Usage:

-Windows:

updateNativeDir.bat -cssLocation D:\CSS.xml [-options]
-Unix:

updateNativeDir.sh -cssLocation /vol1/CSS.xml [-options]

where options include:

-cssLocation - Required. Absolute path to the location of the CSS.xml configuration file

-nodelete - Optional. When provided the utility will not delete any users/groups from Native Directory.

The users/group that will be deleted is listed in the CSSMigration-Deleted*.log log file

-noprompt - Optional. Silent mode operation. No manual key press needed. Can be used for scheduled jobs.

-noupdate - Optional. When provided the utility will not update any users/groups in Native Directory.

The users/group that will be update is listed in the CSSMigration-Update*.log log file

-doprovider - Optional. When provided the utility will also perform Provider Migration.

Examples:

File Path with out options :

updateNativeDir -cssLocation D:\CSS.xml

File Path with options :

updateNativeDir -cssLocation D:\CSS.xml -noprompt -nodelete

HTTP Path with out options:

updateNativeDir -cssLocation http://hss_machine_name:port_number/

interop/framework/getCSSConfigFile

HTTP Path with options :

updateNativeDir -cssLocation http://hss_machine_name:

port_number/interop/framework/getCSSConfigFile -noprompt -nodelete

What are the logs generated by this Utility?

4 log files will get created under "\updateNativedir\logs" folder each time the utility is run.

If utility unable to create in the above mentioned folder due to any reason, it will get created under

"$TMP\Hyperion-logs" or "%TEMP%\Hyperion-logs" folder each time the utility is run.

Files created:

CSSMigration-Ambiguous_.log

CSSMigration-Deleted_.log

CSSMigration-Updated_.log

CSSMigration-Ignored_.log

WARNING: Provisioning data will be lost for any providers that are not listed on console.

The data related to all the external providers in the search order is synchronized. User and group

information such as membership, provisioning, cache will be deleted from Native Directory if
the user or group is not found in the external providers.

After this utility is run, we need to restart HSS so that the cache is refreshed and the data updated. The
other option is to wait for cache to refresh.

How to Update Database Connection in Shared Services Registry Using the EPMSYS_REGISTRY.bat Utility

2012-01-18T17:29:00.001+03:00

How to Update Database Connection in Shared Services Registry Using the EPMSYS_REGISTRY.bat Utility [ID 1212454.1]

		Modified 19-SEP-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution
HOW TO CHANGE PRODUCT DATABASE CONNECTION DETAILS USING EPMSYS_REGISTRY.BAT

Applies to:

Hyperion Financial Management - Version: 11.1.1.1.00 to 11.1.2.0.00 - Release: 11.1 to 11.1
Hyperion Planning - Version: 11.1.1.1.00 to 11.1.2.0.00 [Release: 11.1 to 11.1]
Information in this document applies to any platform.

Goal

This is a guide by example on how to directly update a product-specific database connection in the EPM registry using the command line utility EPMSYS_REGISTRY.bat.

Solution

HOW TO CHANGE PRODUCT DATABASE CONNECTION DETAILS USING EPMSYS_REGISTRY.BAT

Introduction:

This small guide will take you through updating the Calc manager database connection server name from vm0rpianese64 to cm0rpianese11 as an example but the procedure could be applied on any other EPM system product. One instance where using the configuration utility may fail to update the database connection details is when alias name is being used for the database server name instead of the physical server name.

Procedure:

Start a command prompt and change directory to \hyperion\common\config\9.5.0.0 on the shared services server
Execute the following command to view the specific product component details. In this example, we are using CALC MANAGER, and take note of the Ids of the following component:
- DATABASE_CONN -> af46278784e183e27f77898d11edadbe2cb7a49

Use the following command, while using the DATABASE_CONN ID value, to view the database connections component details. Looking at the details below, two entries are of interest:
- NAME
- PROPERTIES -> dbJdbcUrl
And as a final check we will view the last node in the screen below to ensure that the changes have been taken into account (CHILD COMPONENTS - Child 1)

Now we will update the database connection details by changing the database server name from vm0rpianese64 to vm0rpianese11.
The following command shows the currently stored database connection details (note: the property name is case sensitive):

The updateproperty command is then used to change the server name in the connection string from vm0rpianese64 to vm0rpianese11

The following command will change the NAME property so that the server name is updated

Perform a check by running the following command to make sure that the Database connection for Calc manager ahas been updated in the list of Database connection by querying the ID field of the CHILD COMPONENTS – Child1 (from 2nd screenshot above)

Launch the HTML registry report by running the epmsys_registry.bat and make sure that the following have been udpated

NOTE:

Special note when running the above epmsys_registry in a Linux environment:

When running the epmsys_registry with view option with ID on Linux the following error will show:

“java.lang.ArrayIndexOutOfBoundsException: 1 at com.hyperion.hit.registry.regedit.RegEditUtility.main(RegEditUtility.java:112) An error occured duringthe operation. Detailed Message is– 1”

This is because in Linux/UNIX environments, the # character needs to be escaped with a \character. To prevent this error, use \ID. If you will add the same in the doc it will be really helpful.

Ex: Instead of epmsys_registry view # af46278784e183e27f77898d11edadbe2cb7a49

use

epmsys_registry view \#af46278784e183e27f77898d11edadbe2cb7a49

Related

Products

Middleware > Enterprise Performance Management > Financial Management > Hyperion Financial Management
Middleware > Enterprise Performance Management > Planning > Hyperion Planning

Errors

ERROR USE

Rate this document

HOW TO FIND THE SHARED SERVICES REGISTRY

2012-01-18T17:28:00.001+03:00

HOW TO FIND THE SHARED SERVICES REGISTRY

In this Document
Goal
Solution
References

Applies to:

Hyperion BI+ - Version: 11.1.1.0.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Goal

How do I find the Shared Services Registry in Enterprise Performance Management System 11 Console?

Solution

You can find the Shared Services Registry under Application Groups in the Shared Services Console (/interop).
The following menu navigation will get you there:

Shared Services console > Application Groups > Foundation > Deployment Metadata > Shared Services Registry

You must navigate and expand to the lowest level in a particular branch of the hierarchy tree before you can highlight and 'right click' to EXPORT or IMPORT a particular SS Registry Key for editing.

How to Change the Shared Services and Registry Repository Password?

2012-01-18T17:26:00.000+03:00

How to Change the Shared Services and Registry Repository Password?

In this Document
Goal
Solution

Applies to:

Hyperion Essbase - Version: 11.1.1.0.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.
Checked for relevance on 03-08-2010

Goal

How to Change the Shared Services and Registry Repository Password?

Solution

To change the password for the Shared Services and Registry repository:

1. Using the database administration Console, change the password of the user account that was used to
configure the Shared Services database.

2. Stop all the EPM System Web applications and services and processes.

3. Start EPM System Configurator, and under the Foundation tasks--> select Configure Database.

4. On the "Shared Services and Registry Database Configuration" page, select Connect to a previously configured Shared Services database.

5. Keep the existing database and user, then enter the new password.

6. Continue the configuration, and click Finish when you are done.

7. Restart the Web applications and services and processes.

How to Configure FDM to Authenticate Against Shared Services

2012-01-18T17:25:00.001+03:00

How to Configure FDM to Authenticate Against Shared Services [ID 745230.1]

		Modified 17-AUG-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution
Configure Shared Services for v2 of LDAP
Restart SharedServices Service
Configure FDM LoadBalance Manager
Test Authentication Provider

Applies to:

Hyperion Financial Data Quality Management - Version: 9.3.1.0.00 and later [Release: 9.3 and later ]
Information in this document applies to any platform.

Goal

The following is an outline of the steps required to leverage SharedServices as an authentication mechanism for situations where only SharedServices native accounts are used.

It is key to note that FDM releases prior to v11.1.1.2.00 do not 'integrate' with SharedServices. This article will only cover information on how to leverage the LDAP directory provider SharedServices has built-in for 'Native' accounts.

Solution

Configure Shared Services for v2 of LDAP

Browse to the Shared Services directory :
\SharedServices\x.x\OpenLDAP
Open the sldap.conf file
Add the following lines:
# Added to support FDM Authentication
allow bind_v2

Restart SharedServices Service

Start -> Run -> Services.msc
Restart 'Hyperion SharedServices9 OpenLDAP'

Configure FDM LoadBalance Manager

Start -> Hyperion System 9 Applications+ -> Financial Data Quality Management ->
LoadBalance Manager -> LoadBalance Manager Configuration
Choose the 'Authentication Providers' Tab
Click 'Add'
From the drop down choose 'LDAP'
Provide/Enter a Description
In the Server Name field enter the Shared-Services Server Name
In the Port field enter 58089
In the Directory Info Tree field enter 'DC=css,DC=Hyperion,DC=com'
In the User Name field enter: 'CN=911,OU=People'
This is the 'Admin' account for SharedServices If you want to use another user, you can use an LDAP browser to find another person to bind as and enter that CN above.
In the Password/Confirm Password fields enter the password for the account
Click the 'User Verification Tab'
Enter a Logon Attribute 'cssDisplayNameDefault'

Test Authentication Provider

Go back to the 'General' tab and click 'Logon Test'
Enter a valid Shared Services UserName/Password
If successful save the changes to the Authentication Provider

Attachments

FDM Shared Service Authentication.pdf (169.03 KB)

Related

Oracle Hyperion Financial Data Quality Management Master Note

2012-01-18T17:21:00.001+03:00

Oracle Hyperion Financial Data Quality Management Master Note [ID 1126261.1]

		Modified 22-SEP-2011 Type DIAGNOSTIC TOOLS Status PUBLISHED

In this Document

Purpose ---
Oracle Hyperion Financial Data Quality Management Master Note ---
Installation and Configuration:
Error Messages/Bugs
General Information

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.0.00 and later [Release: 11.1 and later ]
Information in this document applies to any platform.

Purpose ---

The purpose of this document is to act as a quick reference for Financial Data Quality Management.

Oracle Hyperion Financial Data Quality Management Master Note ---

EPM release 11.1.2.1.000 is now generally available---Please review the following Articles prior to installation.

Release Announcement: Document 1306738.1
EPMA Mandatory Patch: Document 1308127.1
DRM Recommended PSU: Document 1309442.1

The following links will offer specific target articles on the corresponding topics for FDM.

Link to FDM Documentation Click here

Installation and Configuration:

Document 1308568.1 How to Use the UPSShell.EXE To Launch a Custom Script for FDM
Document 1161892.1 Configuring Necessary Roles in Windows 2008 for FDM Web Server [Video]
Document 1162823.1 Enable Drill Through to FDM in a Financial Report [Video]
Document 1067430.1 Migrating an FDM Application From a System 9 Environment to a FDM version 11.1.1.0 and Higher Environment [Video]
Document 967036.1 How to setup Drill Through from Smart View into Financial Data Quality Management (FDM)
Document 728181.1 Error After Loading New Mapping to a Location. "Error While Parsing Entity Name"
Document 1052993.1 How to Setup Drill Through from Financial Management (HFM) to Financial Data Quality Management (FDM) Version 11.1.1.3
Document 816183.1 DCOM Error Message in Windows Event Viewer for Load Balance Manager or Application Server components
Document 986694.1 Export to Excel Hangs in FDM 11.1.1.3. How to Un-Register Essbase Add-In in EPM System 11.1.1.3
Document 603737.1 FDM Schema Update Error "91 - Object Variable with Block Variable Not Set"
Document 1078450.1 BULK INSERT ERROR ON IMPORT IN FDM
Document 815038.1 Cannot Publish Report to Excel for One Location
Document 951369.1 Configure and use ERPi as a Replacement to the Financial Data Quality Management EBS Adapter
Document 1052154.1 How to Leverage Multiple FDM ERPi Adapters
Document 602380.1 Setup and Configuration for HFM Audit Intersection (DrillBack) into FDM
Document 981794.1 How to Configure and Setup DrillBack from Hyperion Enterprise (HE) into Hyperion Financial Data Quality Management (FDM)
Document 882510.1 Error: "The XML page cannot be displayed" After Clicking the Validate Fish Inside of Financial Data Quality Management (FDM)
Document 739664.1 Workbench Error "2037 - Database User ID and Password are Required" for Login During Application Logon
Document 968084.1 FDM URL Link from HFM causes FDM Window to Close Unexpectedly
Document 942561.1 Setting Up Conditional Maps in FDM
Document 1101084.1 How to Set Up Essbase Adapter's Calc Script to Prevent Delete for Previous Years
Document 1114660.1 Incorrect Date in the Period Field of the Check Report
Document 800476.1 Tips for FDM Registering with Shared Services
Document 1090074.1 Failure to Create New FDM Application on 64-bit Windows
Document 780874.1 How to Verify EBS Setup for DrillBack to EBS in FDM
Document 745230.1 How to Configure FDM to Authenticate on Shared Services

Error Messages/Bugs

Document 1065546.1 FDM Error "Index Was Out of Range" in User Maintenance When Pulling Users From Shared Services
Document 603191.1 Exporting Maps as Excel, Receive "Error: ActiveX component can't create object"
Document 840319.1 Periodic data export fails loading into HFM with "No Such Member PER"
Document 963032.1 Data Access Error or "There is Invalid Cell Data" in the Logic for the type 'Function' in Financial Data Quality Management 11.1.1.3.00
Document 852117.1 "Essbase API Procedure: [EsbInit] Threw code: 1030723" When Testing Financial Data Quality Management Integration into Essbase
Document 727112.1 User Unable to Load FDM Data into HFM, Receive "Could not Authenticate the Specified User. %0"
Document 880148.1 "Cannot Create ActiveX Component" Error When Configuring the FDM WebConfig Manager
Document 973722.1 "Type Mismatch - 13" Error When Logging into a Financial Data Quality Management Application Deployed Against SharedServices
Document 597376.1 FDM Integration with HFM Error: "Server/Cluster is incorrectly configured. Please reconfigure your Cluster or Server connection
Document 1132723.1 Export To Excel error "SaveAs method of Workbook class failed" in FDM 11.1.2
Document 1073992.1 Receive Error: "Unable to cast COM object of type 'System.__ComObject' to interface type 'HSVMETADATALib.HsvMetadata'" when Integrating with HFM and FDM Installed in a 64bit OS
Document 1179495.1 Error: "HTTP Error 500.0 - Internal Server Error" Unable to Run FDM and EPM Simultaeneously on IIS7 64bit Installation
Document 1229893.1 Error: "This application is not registered with Shared Services." when trying to add a newly provisioned user to FDM
Document 1151723.1 Error: "Unable to get the user named (xxxxx) on computer or domain named (xxxxxx)! Cannot create ActiveX Component" When Running the FDM Web Config Manager Windows 2008
Document 1195948.1 FDM Import Error "Error: Invalid Option Key: Fileprompt"
Document 1118753.1 FDM Validate Error "The stylesheet does not contain a document element"
Document 780239.1 Integrating with Hyperion HFM Returns "Error At Line: 45 [Inner Except]: [Stack Trace]"
Document 1139713.1 Shared Services Provisioning Fails Error "30:1101:JNDI"
Document 597518.1 FDM Receive "ERROR: Description [Script failure caused error]: Object doesn't support this property or method Procedure clsEventHandler.PobjAPI_ImportAction" During Import
Document 757127.1 FDM Error: "Run-Time error '91': Object variable or with block variable not set" When Trying to Import XML File Via Workbench
Document 760291.1 FDM XML Import Fails with Error "An Error Occurred Importing the File: Detail: Object Variable or With Block Variable Not Set"
Document 800406.1 Error at Line 45 Browsing to the Target System in the Financial Data Quality Management (FDM) Maps

Document 862633.1 FDM Error: "Object variable or With block variable not set" During Export to Excel and Creating Locations

Document 1213783.1 Error Logging into FDM Workbench "Invalid User Name or Password, No Permission to Create or Add a New FDM Application - 2653"

Document 1053623.1 FDM Adapter Configuration Error on 64 Bit Operating System
Document 599765.1 When Exporting a Grid in FDM to Excel Receive "ActiveX component can't create object"

General Information

Document 1080315.1 How Can IIS Be Enabled for 32 Bit Applications to Run FDM 11.1.1.3.0 on a 64 bit Operating System?
Document 966752.1 Message "DATABASE/SCHEMA ALREADY EXISTS" when Creating a new Financial Data Quality Management Application
Document 604711.1 How to Setup Sticky Server between HFM and FDM
Document 739174.1 How to export the Metadata of FDM to an XML file
Document 942558.1 Where is Table Editor in FDM 11.1.1.3.00?
Document 758003.1 How to Load PERIODIC Instead of YTD Data in FDM

EPM System Defects Fixed Finder Document 1292603.1
Installation and Configuration information Click Here

Related

Oracle Financial Services Analytical Applications (OFSAA) Product Documentation

2012-01-18T17:18:00.001+03:00

Oracle Financial Services Analytical Applications (OFSAA) Product Documentation [ID 1073394.1]

		Modified 20-DEC-2011 Type REFERENCE Status PUBLISHED

In this Document
Purpose
Scope
Oracle Financial Services Analytical Applications (OFSAA) Product Documentation

Applies to:

Oracle Financial Services Asset Liability Management - Version: 5.1 and later [Release: 5 and later ]
Oracle Financial Services Profitability Management - Version: 5.1 and later [Release: 5 and later]
Oracle Financial Services Funds Transfer Pricing - Version: 5.1 and later [Release: 5 and later]
Oracle Financial Services Analytical Applications Infrastructure - Version: 7.1 and later [Release: 7 and later]
Oracle Financial Services Profitability Analytics - Version: 5.1 and later [Release: 5 and later]
Information in this document applies to any platform.
OFSAA
OFSAAI

Purpose

Last Update: December 20, 2011

This note provides link to Oracle download site where you can find the latest installation and user guide documents for Oracle Financial Services Analytical Applications product suite.

Click link below to access the documents:
Documentation Library for Oracle's Enterprise Performance Management Suite for Oracle Financial Services Analytical Applications 5.2, Oracle Part Number E26650-01

If you are not directed to the documentation site from link above, please type in the following address to your browser:
http://download.oracle.com/docs/cd/E26650_01/homepage.htm

Scope

The link above include documentation for the following products:

Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Oracle Financial Services Profitability Management (OFSPM)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Balance Sheet Planning (BSP)
Oracle Financial Services Pricing Management, Transfer Pricing Component
Oracle Financial Services Profitability Analytics (PFTBI)
Oracle Financial Services Asset Liability Management Analytics (ALMBI)
Oracle Financial Services Data Warehouse (FSDW)

Oracle Financial Services Analytical Applications (OFSAA) Product Documentation

Oracle Financial Services Analytical Applications documents:

http://download.oracle.com/docs/cd/E26650_01/homepage.htm

Attachments

Migration45to72_UG_E26522_01_110911.pdf (396.59 KB)

OFSAACFE_E24987_01_090611.pdf (2,503.23 KB)

OFSAAI72Install_E22351_01_082911.pdf (8,412.42 KB)

OFSAAI Install Guide (6,990.64 KB)

OFSAAI_UG_72_E24199_01_112111.pdf (20,928.89 KB)

OFSAAI_UG_E16687_01_061311.pdf (13,755.19 KB)

OFS Asset Liability Management 5.2 (10,513.87 KB)

OFSAAPFTBI_UG_E23175_01.pdf (3,452.86 KB)

OFSAA_AddingCustomInstrumentTables_02082010.pdf (5,167.09 KB)

OFSAA_AddingCustomLeaf_02112010.pdf (5,255.25 KB)

OFSAA_CompareandMergeModels_02102010.pdf (3,478.72 KB)

OFSAA_DD_E16101_01_091610.pdf (2,099.65 KB)

OFSAA_DataMigration_E18045_01_072910.pdf (348.77 KB)

OFSAA Data Model Utilites (2,343.71 KB)

OFSAA_LookupTable_02162010.pdf (2,370.27 KB)

OFSFTP_UG_E17388_01_061711.pdf (9,226.48 KB)

OFSPM_UG_E25486_01_120111.pdf (9,263.61 KB)

User Defined Properties (50 KB)

Related

Hyperion Enterprise Performance Management Architect (EPMA) Failover Support

2012-01-18T17:15:00.001+03:00

Hyperion Enterprise Performance Management Architect (EPMA) Failover Support [ID 1313265.1]

		Modified 10-MAY-2011 Type WHITE PAPER Status PUBLISHED

In this Document
Abstract
Document History
Hyperion Enterprise Performance Management Architect (EPMA) Failover Support

Applies to:

Hyperion Planning - Version: 11.1.2.0.00 to 11.1.2.0.00 - Release: 11.1 to 11.1
Hyperion Essbase - Version: 11.1.2.0.00 to 11.1.2.0.00 [Release: 11.1 to 11.1]
Hyperion Profitability - Version: 11.1.2.0.00 to 11.1.2.0.00 [Release: 11.1 to 11.1]
Hyperion Financial Management - Version: 11.1.2.0.00 to 11.1.2.0.00 [Release: 11.1 to 11.1]
Information in this document applies to any platform.

Abstract

This article contains sample scripts for clustering Performance Management Architect Dimension Server for failover in an active-passive configuration. Please refer to the 11.1.2 Oracle Hyperion Enterprise Performance Management System High Availability and Disaster Recovery Guide for details on how to configure EPMA dimension server for failover. Please note that the scripts are just a sample and need to be modified for the target environment.

Document History

Author:
Create Date 13-Apr-2011
Update Date 13-Apr-2012
Expire Date 13-Apr-2013 (ignore after this date)

Hyperion Enterprise Performance Management Architect (EPMA) Failover Support

The information and scripts are attached to this article.

Attachments

Sample_EPMA_11.1.2_Failover_Scripts.zip (8.1 KB)

Related

Products

Middleware > Enterprise Performance Management > Planning > Hyperion Planning
Middleware > Enterprise Performance Management > Essbase > Hyperion Essbase
Middleware > Enterprise Performance Management > Profitability > Hyperion Profitability
Middleware > Enterprise Performance Management > Financial Management > Hyperion Financial Management

Keywords

ENTERPRISE PERFORMANCE MANAGEMENT; EPMA; FAILOVER

Rate this document

Utilities for Troubleshooting Oracle Hyperion Enterprise Performance Management 11.1.2.0 or 11.1.2.1

2012-01-18T17:09:00.000+03:00

Utilities for Troubleshooting Oracle Hyperion Enterprise Performance Management 11.1.2.0 or 11.1.2.1 [ID 1303200.1]

		Modified 18-JAN-2012 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution
References

Applies to:

Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Hyperion BI+ - Version: 11.1.2.0.00 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Hyperion Planning - Version: 11.1.2.0.00 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Hyperion Financial Management - Version: 11.1.2.0.00 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Hyperion BI+ - Version: 11.1.2.0.00 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Information in this document applies to any platform.
(1) \Oracle\Middleware\user_projects\epmsystem1\bin\ziplogs.bat|.sh
(2) \Oracle\Middleware\ohs\ccr\bin\
(3) \Oracle\Middleware\ohs\rda\rda.cmd
(4) \Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat|.sh
(5) \Oracle\Middleware\user_projects\epmsystem1\bin\validate.bat

Goal

This article aims to help users use various troubleshooting tools to validate or troubleshoot an installation of Oracle EPM 11.1.2.0. or 11.1.2.1

Solution

(1) A new troubleshooting tool introduced in Oracle EPM 11.1.2.1 is \Oracle\Middleware\user_projects\epmsystem1\bin\ziplogs.bat|.sh file. The output of this is generated in \Oracle\Middleware\user_projects\epmsystem1\diagnostics\ziplogs\EPM_logs__11.1.2.1.0.zip

(2) Oracle Configuration Manager (OCM) is an advanced tool which collects and evaluates settings from configuration files (but not Hyperion Registry) and stores them in a central database administered by Oracle. It was first introduced into EPM in version 11.1.2.0

(3) Remote Desktop Assistant (RDA) collects and zips up a large amount of information concerning the software and hardware environments of Oracle products. If Perl 5.005 or later is installed on the computer and accessible from the command line (test: perl -version), then run: \Oracle\Middleware\ohs\rda\perl rda.pl from the command line to access the RDA tool. Alternately, precompiled RDA executables are available for several platforms (rda.cmd, rda.sh, rda.bat). View an RDA webcast from the https://oracleaw.webex.com reference site listed below.

(4) Configuration settings have been moved from configuration files to a database repository associated with Shared Services. These may be extracted to an HTML formatted file by running \Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat|.sh without parameters from the command line. The output is generated to file \Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\registry.html The username/login/jdbc URL for the Hyperion/HSS registry are kept in \Oracle\Middleware\user_projects\epmsystem1\config\foundation\11.1.2.0\reg.properties file.

(5) A much enhanced validation tool is available in \Oracle\Middleware\user_projects\epmsystem1\bin\validate.bat. In EPM 11.1.2.1 the output files are of the form \Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\instance_report_20YYMMDD_######.html (where YY is the year, MM is the month, DD is the day, and ###### is a unique integer). It also runs the tool under (1) and gives the output of that tool.

(6) Individual log files may be found in subdirectories under (those 'starred' are not collected by ziplogs):
\Oracle\Middleware\user_projects\domains\EPMSystem\servers\\logs *
\Oracle\Middleware\logs *
\Oracle\Middleware\wlserver_10.3 *
\Oracle\Middleware\user_projects\epmsystem1\tmp *
\Oracle\Middleware\ohs\cfgtoollogs\opatch *
\Oracle\Middleware\EPMSystem11R1\diagnostics\logs
\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\
\Program Files\Oracle\Inventory\logs
C:\Users\\Oracle\oradiag_\diag\
C:\Users\\.oracle\logs\

(7) Some debug tools (*) can be activated if under http://:19000/workspace/index.jsp > Navigate > Administration > Workspace Server Settings > Client Debug Enabled: is set to Yes (then click 'OK' button, close all browser windows, and restart browser).
* http://hostname:19000/workspace/debug/configInfo.jsp
* http://hostname:19000/workspace/debug/userInfo.jsp
* http://hostname:19000/workspace/debug/userGroupQuery.jsp

Other tools are available at these URLs (largely derived from validate.bat output). A non-Error response indicates that the web service of each particular application is active.:
http://hostname:19000/workspace/status
http://hostname:19000/workspace/BPMContext
http://hostname:8600/mappingtool/faces/info.jspx
http://hostname:10080/easconsole/console.html
http://hostname:16000/WebAnalysis
http://hostname:6373/oracle-epm-fm-webservices/ApplicationService
http://hostname:8300/HyperionPlanning/
http://hostname:13080/aps/APS
http://hostname:8200/hr/status.jsp
http://hostname:19091/awb/conf/AwbConfig.xml
http://hostname:8500/calcmgr/index.htm

(8) Enterprise Manager is the standard Oracle graphic user interface debugging and configuration tool. Although advanced versions require extra cost licensing, there is a bundled version of Enterprise Manager available with EPM. Research the product starting with KM article 1302746.1. It is hoped that ECID (Execution Context ID) functionality will be widely incorporated with the 'Hyperion' product stack in EPM version 11.1.2.2.

Platform Desupport Notice Affecting EPM System Releases Beginning with Release 11.1.2

2012-01-18T17:08:00.001+03:00

Platform Desupport Notice Affecting EPM System Releases Beginning with Release 11.1.2 1

		Modified 05-NOV-2010 Type ANNOUNCEMENT Status PUBLISHED

In this Document
What is being announced?

Applies to:

Oracle Crystal Ball - Version: 11.1.1.0.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Hyperion Data Integration Management - Version: 11.1.1.0.00 to 11.1.1.1.00 [Release: 11.1 to 11.1]
Hyperion Strategic Finance - Version: 11.1.1.1.00 to 11.1.1.3.00 [Release: 11.1 to 11.1]
Hyperion Data Relationship Management - Version: 11.1.1.0.00 to 11.1.1.3.00 [Release: 11.1 to 11.1]
Hyperion Financial Data Quality Management - Version: 11.1.1.0.00 to 11.1.1.3.00 [Release: 11.1 to 11.1]
Information in this document applies to any platform.

What is being announced?

The following platform components will no longer be supported by Oracle Hyperion Enterprise Performance Management System subsequent to release 11.1.1.x. (Note: Not all individual Oracle Hyperion Enterprise Performance Management System release 11.1.1.x products are supported all platforms. For specific details, please refer to the applicableCertification Matrix.). Please refer to the Products section below for a full list of the affected Products.

SERVER OPERATING SYSTEMS
POWER AIX 5.2
PA-RISC HP-UX 11i (11.23)
Itanium-2 Windows 2003 SP1, Server Enterprise Edition for Itanium-based Systems

DATABASES (Repositories and Data Sources)
Oracle Database 10.1
IBM DB2 8.2 through 9.2
Microsoft SQL Server 2000

DATABASES (Data Sources only)
IBM DB2 7x for z/OS
Teradata (ODBC) V2R6.0.x
Teradata (ODBC) V2R5.1.x

WEB APPLICATION SERVERS
Oracle WebLogic Server 9.2
Oracle Application Server (all releases)
IBM WebSphere Application Server and IBM HTTP Server will not supported with the next release.

IDENTITY MANAGEMENT
Oracle Directory Services
- Oracle Virtual Directory 10.1.4.0.1
Access Management
- Oracle Access Manager 10.1.4.0.1
Oracle Identity Manager 10.1.4.0.1 and higher
Microsoft Active Directory 2000
IBM Tivoli Directory Server 6.1
Sun ONE LDAP 5.2

OTHER CLIENT SOFTWARE
Internet Explorer 6
Firefox 2

Where are Application Install Inventories Stored in Oracle EPM 11.1.2.1

2012-01-18T17:05:00.001+03:00

Where are Application Install Inventories Stored in Oracle EPM 11.1.2.1 [ID 1304532.1]

Applies to:

Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Hyperion Essbase - Version: 11.1.2.0.00 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Hyperion Planning - Version: 11.1.2.0.00 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Information in this document applies to any platform.

Goal

Identify the location of software inventories associated with Oracle EPM 11.1.2.1.

Solution

It is important to know where installation inventory lists are stored: to detect the completeness of an install, to determine whether a patch has been applied, or to delete as part of a reinstall.

\Oracle\Middleware\EPMSystem11R1\oraInst.loc points to the location of the central inventory. oraInst.loc may have been installed in a previous Oracle install on Unix in: /var/opt/oracle or /etc or $HOME (of the user installing Oracle software), preventing the 'reinstall' of OHS or other software.
\Program Files\Oracle\Inventory is typically the location of the central inventory (despite the name 'central inventory', there may exist mutually exclusive inventories generated with the install of other Oracle products). On Unix/Linux the central inventory is in the installer's 'home' directory.
A local inventory is typically found in \Oracle\Middleware\EPMSystem11R1\.oracle.products
A local pointer (.oracle.instances) to the instance(s) set by EPM 11.1.2.0 and EPM 11.1.2.1 (and referenced by EPM 11.1.2.1 Installer for 'Apply Maintenance Release' option) is put in C:\Users\\ Ensure the same user installs both versions.
\Oracle\Middleware\EPMSystem11R1\.oracle.products is used to recreate an inventory if need be (but a regeneration of an inventory will exclude service fixes/patches installed via OPatch. To recreate an inventory after one is corrupted...run \Oracle\Middleware\EPMSystem11R1\OPatch\createInventory.bat.)
\Oracle\Middleware\ohs\.patch_storage (holds records of previous OPatches)

A Unique Instance Name Is Required When Configuring A New Install Of EPM 11.1.2.1 In Distributed Environment

2012-01-18T17:04:00.001+03:00

A Unique Instance Name Is Required When Configuring A New Install Of EPM 11.1.2.1 In Distributed Environment [ID 1317679.1]

Applies to:

Hyperion Financial Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Hyperion Planning - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Profitability - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Strategic Finance - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Financial Data Quality Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Information in this document applies to any platform.

Goal

To install and configure Oracle EPM 11.1.2.1 in a distributed environment with a proper Instance name on each server

Solution

When configuring EPM 11.1.2.1 in a distributed environment, it is necessary to supply a new, unique Instance name on each server.

For example.

If using the default Instance name 'epmsystem1' on the first server, if you keep the same naming convention on subsequent servers, you will need to supply new, unique Instance names such as epmsystem2, epmsystem3, etc.

During Configuration each instance gets written to the EPM System Registry and the EPM System Configurator verifies that each instance name is unique. If you fail to provide a new unique instance name during the configuration process you will receive a message stating that the instance name is not valid. You will be forced to go back and enter a unique instance name.

Note: If you are applying the maintenance release (11.1.2 to 11.1.2.1), during the configuration process you select the first option "Modify existing instance" since the epmsystem1 instance name already exists and is shared by all servers in the distributed environment. Be sure not to delete or change the instance names during a maintenance release configuration as it will cause the configuration to change from a maintenance install to a new installation and will cause issues with the rest of the server deployments in the distributed environment.

Shared Application File System in R12 and 11i

2012-01-15T20:14:00.001+03:00

Shared Application File System in R12 and 11i

E-Business suites (EBS) 11i and R12 both support the sharing of the Applications Tier File System. Sharing a file system in EBS involves sharing a volume between 2 or more physical servers. In a shared Application Tier File System (ATFS) implementation, the application services can be configured to run (utilize CPU and memory) on any server sharing the ATFS simply by changing some context file variables via OAM, running Autoconfig and restarting the services. This process is detailed in the following notes:

R12: Note.384248.1: Sharing the Application Tier File System in Oracle E-Business Suite Release 12
11i: Note.233428.1: Sharing the Application Tier File System in Oracle Applications 11i

Some key concepts of sharing ATFS:

Each server sharing the ATFS will have its own context file
Certain context file variables dictate which application services start and run on which server(s)
Certain context file variables dictate how AD Utilities will behave on each server

The Unified Applications Tier File System (UATFS)

The term "Unified Applications Tier File System" (UATFS) came along with R12 as a new feature. Oracle Development decided it would be beneficial to always install all the files needed on every server in a given R12 installation, even if the server was only to host some of the Application services. Even though this term was coined for an R12 feature, it still applies to some 11i file systems. A Unified Applications File System essentially means that the file system contains all the files required to support all 4 base service groups in E-Business Suite:

Web
Forms
Admin (Not a true process or service as the other 3 are. The "admin" component dictates which server administers the application database objects and therefore has the needed files for that task.)
Concurrent Processing (Reports)

Again, all versions of R12 are always installed with UATFS as delivered by Rapid Install. However in 11i only single node-installations are unified at install time. In 11i in order to achieve a unified file system from a multi-node installation, a merge of the file systems must be performed. This is the only supported manner in which to achieve a unified file system from an installation which was originally multi-node. APPL_TOP Merging in 11i is accomplished by Note 233428.1, Section 4, "Merging existing APPL_TOPs into a single APPL_TOP". Because R12 is always unified there is not an APPL_TOP merge process in R12.

Some Non-Typical Scenarios for Shared File Systems in 11i

In 11i it is also possible to share an ATFS even if the file system is not unified or complete; i.e., it only supports 1, 2 or 3 of the 4 core services. For example 11i can have an ATFS which only has the files for Forms and Web. That ATFS can then be shared with another server for Forms / Web services only. The other core services, Admin and Concurrent would then have its own ATFS on another server or servers. This would be done for some advanced topology configurations like load-balancing or perhaps a standby Web / Forms server and would minimize the footprint of the ATFS. Because the ATFS in this example is not unified, the ATFS of the Forms/Web servers could never host the Concurrent Processing or Admin services without first being merged with an ATFS which has the necessary Concurrent Processing and Admin files. So while in 11i it is possible to share a non-unified ATFS, it would not be a typical configuration. A typical configuration is sharing 1 unified ATFS for amongst multiple servers. The advantages of this non-typical example would be:

Smaller Footprint for the ATFS on each volume/disk (however the overall combined footprint would be larger)
Better performance from the shared volume/disk, as there are 2 instead of 1

The disadvantages would be:

Must maintain multiple ATFS's
Patches have to be applied multiple times
Cloning is more difficult as 2 ATFS's must be cloned

For disk performance reasons, you could implement a similar strategy in R12, for example sharing 2 volumes (VOL1, VOL2) amongst 4 servers: 2 web/forms servers accessing only VOL1 and the 2 CCM/Admin servers accessing only VOL2. Those 2 disks would each have a unified ATFS in R12, where the same configuration in 11i the file systems could be partial or unified.

For more information please refer :

Explanation of Context Variables for Shared Application File System in R12 and 11i [ID 1070152.1]

References
NOTE:233428.1 - Sharing the Application Tier File System in Oracle Applications Release 11i
NOTE:384248.1 - Sharing The Application Tier File System in Oracle E-Business Suite Release 12
NOTE:406558.1 - Configuring Applications Node Services in Oracle E-Business Suite Release 12
NOTE:415385.1 - On a R12 Multi-Node Install -- Why do all Middle Tiers run all Services?

Shared Application File System in R12 and 11i

2012-01-15T20:14:00.000+03:00

Shared Application File System in R12 and 11i

R12: Note.384248.1: Sharing the Application Tier File System in Oracle E-Business Suite Release 12
11i: Note.233428.1: Sharing the Application Tier File System in Oracle Applications 11i

Some key concepts of sharing ATFS:

Each server sharing the ATFS will have its own context file
Certain context file variables dictate which application services start and run on which server(s)
Certain context file variables dictate how AD Utilities will behave on each server

The Unified Applications Tier File System (UATFS)

Web
Forms
Admin (Not a true process or service as the other 3 are. The "admin" component dictates which server administers the application database objects and therefore has the needed files for that task.)
Concurrent Processing (Reports)

Some Non-Typical Scenarios for Shared File Systems in 11i

Smaller Footprint for the ATFS on each volume/disk (however the overall combined footprint would be larger)
Better performance from the shared volume/disk, as there are 2 instead of 1

The disadvantages would be:

Must maintain multiple ATFS's
Patches have to be applied multiple times
Cloning is more difficult as 2 ATFS's must be cloned

Explanation of Context Variables for Shared Application File System in R12 and 11i [ID 1070152.1]

Financial Management Error "Unable to open file" When Previewing Or Printing A System Report [ID 1082720.1]

2012-01-13T10:33:00.000+03:00

Financial Management Error "Unable to open file" When Previewing Or Printing A System Report [ID 1082720.1]

		Modified 01-SEP-2011 Type PROBLEM Status PUBLISHED

In this Document
Symptoms
Cause
Solution

Symptoms

Previewing or printing Hyperion Financial Management (HFM) system reports returns error like this:

Unable to open file D:\Hyperion\products\FinancialManagement\Web\HFM\FileTransfer\{436ECBC0-5060-4B69-B599-1D481A5D5A86}.FTR\ICPReport2_867826759.
Show Details:
Error Reference Number: {E37C98DA-6D0D-4459-A7FF-1D41440AAEA9};User Name: admin@Native Directory
Num: 0x80040237;Type: 1;DTime: 12/2/2009 7:50:14 PM;Svr: ;File: HFMActionsExecution.cpp;Line: 2236;Ver: 11.1.1.2.0.2207;ExErr: It is an error to mix objects from different versions of MSXML.;
Num: 0x80040237;Type: 0;DTime: 12/2/2009 7:50:14 PM;Svr: ;File: HFMActions.cpp;Line: 72;Ver: 11.1.1.2.0.2207;

Cause

Incorrect NTFS permissions on the File Transfer folder will cause this issue. To check NTFS permissions on the File Transfer folder:

On the HFM web server, check the data value of FileTransferFolderPath value in the Windows Registry located:
HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Web
Right-click on the folder found in the above registry in Windows Explorer and select the Security tab.
The following NTFS permissions should be applied for the File Transfer folder:

Administrators - Full Control
IIS user (usually Internet Guest Account, IUSR_*): Full Control
ASP user (usually Launch IIS Process Account, IWAM_*): Full Control.
NETWORK SERVICE: Full Control
SYSTEM: Full Control.
Authenticated Users: Read&Execute, List Folder Contents, Read, Special Permissions
For HFM web servers deployed on Windows 2008, group IIS_IUSRS should have assigned Modify permission to the folder

Solution

The recommended way to set permissions is to run the EPM System Configurator on the HFM Web server as follows:

Run the "EPM System Configurator" (accessible at "Start" -> "All Programs" -> "Oracle EPM System" -> "Foundation Services")
Expand "Financial Management"
Check "Configure Web Server"
Complete the deployment process.

If this does not resolve the issue, apply manually required NTFS permissions for the File Transfer Folder (see point 3 in the Cause section above).

Related

How to Reregister an Existing Hyperion Product With Shared Services in Version 11.1.2

2012-01-13T10:32:00.001+03:00

How to Reregister an Existing Hyperion Product With Shared Services in Version 11.1.2 [ID 1175663.1]

		Modified 25-JUL-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution
References

Applies to:

Hyperion Essbase - Version: 11.1.2.0.00 to 11.1.2.0.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Goal

How to re-register an existing Hyperion product such as Essbase, Essbase Administration Services (EAS), with Shared Services in EPM version 11.1.2?

Solution

1. Locate the product_config_#.xml in the directory EPM_ORACLE_INSTANCE/config/foundation/11.1.2.0/product/product_name

For example; the Essbase product file is located in EPM_ORACLE_INSTANCE/config/foundation/11.1.2.0/product/Essbaseserver/11.1.2.0

2. Open the file product_config_#.xml and locate the line:

="hubRegistration">Configured

3. Change the status from Configured to Pending.

4. Rerun 'startconfigtool.bat' or 'startconfigtool.sh' or the EPM System Configurator again and select the product. This enables you to reregister the product with Shared Services

How To Implement Row Level Security in EPM 11.1.1.2.0 [ID 970369.1]

2012-01-13T10:31:00.000+03:00

How To Implement Row Level Security in EPM 11.1.1.2.0 [ID 970369.1]

		Modified 01-APR-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution

Applies to:

Hyperion BI+ - Version: 11.1.1.2.00 and later [Release: 11.1 and later ]
Information in this document applies to any platform.

Goal

Implement Row Level Security in EPM Interactive Reporting 11.1.1.2.

Solution

A) Set background resources for Row Level Security (RLS)
1. Create a database to hold the RLS tables,
2. Create an ODBC connection to the RLS DataBase using appropriate Merant Wire Protocol for your RDBMS.
3. Create an OCE file with ODBC/ODBC connection types and publish it to the workspace, call it RLS.
4. Open Row_Level_Security.BQY (i.e, for system 9 it’s located in %Hyperion_Home%\BIPlus\docs\en; not bundled with EPM 11.1.1.x) and select the RLS.OCE file created in the previous step and connect to RLS database.
5. If this is the first time to establish a connection to the RLS database you will be asked to create these tables first, click yes.
6. Enter the username and password then on Create, now you should have three tables created in your database:
7. Define the OCE connection in DAS using Local Services Configurator, and then restart all the services.
8. Configure RLS in workspace, Navigate > Administer > Row Level Security, check Enable Row Level Security and enter your details of RLS OCE.
9. Restart all the services to ensure changes take effect

B) Define Users and Groups for RLS
1. Click on Work with Users\Groups button and Create a group called it AMERICAS
2. Create a user called "process" and add it as a member in AMERICAS.
3. Create a user called "process" and in shared services (it’s very important to spell it identically to the user in the RLS tables with the same letter case otherwise RLS will not work).

C) Build your report and publish it to the workspace, edit the permission for this report and grant “Full Access” and “View and Process” permissions for user called “process”.

D) Define Restrictions
1. We need to hide the column called “STORE_KEY” in “SALES_FACT” table to prevent the employess from tying back the sales figures with the stores. We can hide the column by adding a row in BRIOSECR to restrict access for “PUBLIC” group as below:
2. Then override this restriction for “AMERICAS” group by adding a second restriction to the BRIOSECR as below:
3. Now, I f we run the report using “admin” which is not a member of “AMERICAS” group we will not be able to see “STORE_KEY”.
4. If we open the same report using “process” user we will be able to see the values in STORE_KEY
5. Now, we will add another constraint to restrict access of AMERICAS group to Sales amount to the store named ‘BMV Lyon’ and to hide other rows of data. This condition will be applied as an inner join constraint.
6. Run the report again, you get only sales amount of ‘BMV Lyon’ store.

For more information, please refer to IR_user.pdf. This contains the official documentation for Row Level Security. Check Chapter 22 "Row Level Security in Interactive Reporting" page 505.

Related

Products

Middleware > Business Intelligence > Hyperion Query & Reporting > Hyperion BI+

Keywords

ROW LEVEL SECURITY; SECURITY

Rate this document

How to Change IP Address in an Oracle Applications Environment

2012-01-12T12:16:00.000+03:00

How to Change IP Address in an Oracle Applications Environment

Print this post

1. Change the IP Address in the Server;

2. Verify the current ip address setup in the Oracle Applications environment. Connect as apps user into SQL*Plus and run:

select NODE_NAME, STATUS, NODE_MODE, NODE_ID,SERVER_ADDRESS, HOST, DOMAIN, WEBHOST, VIRTUAL_IP from fnd_nodes where node_name = upper('hostname');

3. Run the following command to remove the old ip address from the Oracle Applications tables:

perl $AD_TOP/bin/adgentns.pl appspass=apps contextfile=$APPL_TOP/admin/_hostname.xml -removeserver

replace _hostname.xml for the context file name under the $APPL_TOP/admin directory;

then connect to SQL*Plus as apps user and run:

begin
FND_NET_SERVICES.remove_server('', '');
end;
/
commit;
/

replace by the SID of the environment and by the hostname in the environment. Both must be entered in upper case.

4. Run autoconfig to populate the values using the new IP Address.

5. Confirm the ip address has been changed to the new value changed in the step 1:

select NODE_NAME, STATUS, NODE_MODE, NODE_ID,SERVER_ADDRESS, HOST, DOMAIN, WEBHOST, VIRTUAL_IP from fnd_nodes where node_name = upper('hostname');

How to Change IP Address in an Oracle Applications Environment [ID 553318.1]

2012-01-12T12:15:00.001+03:00

How to Change IP Address in an Oracle Applications Environment [ID 553318.1]

		Modified 25-FEB-2008 Type HOWTO Status MODERATED

In this Document
Goal
Solution

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

Applies to:

Application Install - Version: 11.5.9 to 11.5.10
Information in this document applies to any platform.

Goal

How to change the server IP Address in an Oracle Applications environment ?

Solution

Oracle Financial Services Analytical Applications (OFSAA) Product Documentation

2012-01-08T15:55:00.001+03:00

Oracle Financial Services Analytical Applications (OFSAA) Product Documentation [ID 1073394.1]

		Modified 20-DEC-2011 Type REFERENCE Status PUBLISHED

In this Document
Purpose
Scope
Oracle Financial Services Analytical Applications (OFSAA) Product Documentation

Applies to:

Purpose

Scope

Oracle Financial Services Analytical Applications (OFSAA) Product Documentation

Oracle Financial Services Analytical Applications documents:

http://download.oracle.com/docs/cd/E26650_01/homepage.htm

Attachments

Migration45to72_UG_E26522_01_110911.pdf (396.59 KB)

OFSAACFE_E24987_01_090611.pdf (2,503.23 KB)

OFSAAI72Install_E22351_01_082911.pdf (8,412.42 KB)

OFSAAI Install Guide (6,990.64 KB)

OFSAAI_UG_72_E24199_01_112111.pdf (20,928.89 KB)

OFSAAI_UG_E16687_01_061311.pdf (13,755.19 KB)

OFS Asset Liability Management 5.2 (10,513.87 KB)

OFSAAPFTBI_UG_E23175_01.pdf (3,452.86 KB)

OFSAA_AddingCustomInstrumentTables_02082010.pdf (5,167.09 KB)

OFSAA_AddingCustomLeaf_02112010.pdf (5,255.25 KB)

OFSAA_CompareandMergeModels_02102010.pdf (3,478.72 KB)

OFSAA_DD_E16101_01_091610.pdf (2,099.65 KB)

OFSAA_DataMigration_E18045_01_072910.pdf (348.77 KB)

OFSAA Data Model Utilites (2,343.71 KB)

OFSAA_LookupTable_02162010.pdf (2,370.27 KB)

OFSFTP_UG_E17388_01_061711.pdf (9,226.48 KB)

OFSPM_UG_E25486_01_120111.pdf (9,263.61 KB)

User Defined Properties (50 KB)

Related

Products

More Applications > Industry Solutions > Financial Services > Oracle Financial Services Asset Liability Management
More Applications > Industry Solutions > Financial Services > Oracle Financial Services Profitability Management
More Applications > Industry Solutions > Financial Services > Oracle Financial Services Funds Transfer Pricing
More Applications > Industry Solutions > Financial Services > Oracle Financial Services Analytical Applications Infrastructure
More Applications > Industry Solutions > Financial Services > Oracle Financial Services Profitability Analytics

Keywords

DATA DICTIONARY; DOCUMENTATION; INFRASTRUCTURE; INSTALLATION; OFSAA; OFSAAI; PROFITABILITY; USERS GUIDE

Rate this document

New OFSAAI 7.2.8 / OFSAA 5.5 Installation Steps On Red Hat Linux 5.3 [ID 1331600.1]

2012-01-08T15:48:00.000+03:00

New OFSAAI 7.2.8 / OFSAA 5.5 Installation Steps On Red Hat Linux 5.3 [ID 1331600.1]

		Modified 22-JUN-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution
References

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version: 7.2.8 and later [Release: 7 and later ]
Oracle Financial Services Funds Transfer Pricing - Version: 5.5 and later [Release: 5 and later]
Oracle Financial Services Profitability Management - Version: 5.5 and later [Release: 5 and later]
Oracle Financial Services Asset Liability Management - Version: 5.5 and later [Release: 5 and later]
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA) - Version 5.5

Goal

Are there any full installation kits available for Oracle Financial Services Analytical Applications Infrastructure (OFSAAI) 7.2.8 with Red Hat Linux 5.3 like there is for AIX 6.1? Or is it required to install OFSAAI 7.2.3 and install all patches to bring OFSAAI to 7.2.8 and then install the OFSAA 5.5 solutions?

Can OFSAA 5.5 be installed directly on top of OFSAA 5.2?

Solution

Yes, for a new installation on Red Hat Linux 5.3, there is no full installer kit for Infrastructure. OFSAA application service packs however are cumulative. OFSAA 5.5 can be installed directly on top of OFSAA 5.2 base installation. 5.2.1 and 5.2.2 service packs are not required to be installed if installing OFSAA 5.5.

This means that the following patches should be installed in order for new OFSAA installation on RedHat Linux 5.3:

1. E-Delivery Red Hat Linux 5.3 -- 7.2.3 Infrastructure full installer kit
2. E-Delivery OFSAA 5.2 base installer application kits
3. Infrastructure Service Packs -- Not cumulative:

Patch: 10348810 Oracle Financial Services Analytics Infrastructure Service Pack 6 (7.2.6)
Patch: 11810651 - ANALYTICAL APPLICATIONS INFRASTRUCTURE 7.2 SERVICE PACK #7 (7.2.7)
Patch: 12532784 Analytical Applications Infrastructure 7.2 Service Pack #8 (7.2.8)

4. Required pre-requisite patches for OFSAA 5.5:

Patch:12423916 - task selection: left shuttle box has restrictive paging (25/page + 'less/more')
Patch:11900691 - new table classification required for forward rate agreements
Patch:12349210 - new table classification required for swaps, capfloors and fx contracts

5. OFSAA 5.5 Application Patches:

Patch: 12529364: Asset Liability Management Service Pack 5.5
Patch: 12529459: Funds Transfer Pricing Service Pack 5.5
Patch: 12434987: Profitability Management Service Pack 5.5

References

NOTE:1273935.1 - OFSAAI 7.2 and OFSAA 5.2, 5.5 Service Packs Information

Related

Products

More Applications > Industry Solutions > Financial Services > Oracle Financial Services Analytical Applications Infrastructure
More Applications > Industry Solutions > Financial Services > Oracle Financial Services Funds Transfer Pricing
More Applications > Industry Solutions > Financial Services > Oracle Financial Services Profitability Management
More Applications > Industry Solutions > Financial Services > Oracle Financial Services Asset Liability Management

Keywords

INFRASTRUCTURE; INSTALL; INSTALLATION; INSTALLER; KIT; OFSAA; OFSAAI; PATCH

Rate this document

OFSAA Installation Steps

2012-01-08T15:46:00.001+03:00

OFSAA Installation Steps

Install Oracle Database
Create database user to store OFSAA configuration
SQL> create user configuser identified by welcome1;
Grant privileges to user created in previous step by running privileges_config_user.sql
SQL>@privileges_config_user.sql
SQL>grant unlimited tablespace to configuser;
Install JDK 1.6.0_17
Install WebLogic Server 10.3.1 (If you are installing weblogic with 64 bit JDK then follow steps mentioned here )
Create weblogic domain by running config.sh (For steps on how to create domain in weblogic click here )
Create JDBC in domain with JNDI as jndi/FICMASTER (For steps on how to create/configure JDBC in WebLogic click here
Fill value in file OFSAAI_InstallConfig.xml file (Use configuration guide embedded under installation guide for parameter and value )
Install OFSAA by running Setup.sh GUI (This script will use OFSAAI_InstallConfig.xml as parameter file). If you hit error regarding elif then add below entry at top of file
#!/bin/bash
Create EAR & WAR file by running $OFSAA_HOME/ficweb/ant.sh
Deploy EAR/WAR file created in previous step on WebLogic Server
(For steps on how to deploy application is weblogic server click here )
Start deployed application from WebLogic console
Test OFSAA application

Utilities for Troubleshooting Oracle Hyperion Enterprise Performance Management 11.1.2.0 or 11.1.2.1

2012-01-06T11:06:00.001+03:00

Utilities for Troubleshooting Oracle Hyperion Enterprise Performance Management 11.1.2.0 or 11.1.2.1 [ID 1303200.1]

		Modified 23-DEC-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution
References

Applies to:

Goal

This article aims to help users use various troubleshooting tools to validate or troubleshoot an installation of Oracle EPM 11.1.2.0. or 11.1.2.1

Solution

(1) A new troubleshooting tool introduced in Oracle EPM 11.1.2.1 is \Oracle\Middleware\user_projects\epmsystem1\bin\ziplogs.bat|.sh file. The output of this is generated in \Oracle\Middleware\user_projects\epmsystem1\diagnostics\ziplogs\EPM_logs__11.1.2.1.0.zip

(2) Oracle Configuration Manager (OCM) is an advanced tool which collects and evaluates settings from configuration files (but not Hyperion Registry) and stores them in a central database administered by Oracle. It was first introduced into EPM in version 11.1.2.0

(3) Remote Desktop Assistant (RDA) collects and zips up a large amount of information concerning the software and hardware environments of Oracle products. If Perl 5.1 or later is installed on the computer and accessible from the command line (test: perl -version), then run: \Oracle\Middleware\ohs\rda\rda.cmd from the command line to access the RDA tool. Alternately, precompiled RDA executables are available for several platforms.

(4) Configuration settings have been moved from configuration files to a database repository associated with Shared Services. These may be extracted to an HTML formatted file by running \Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat|.sh without parameters from the command line. The output is generated to file \Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\registry.html The username/login/jdbc URL for the Hyperion/HSS registry are kept in \Oracle\Middleware\user_projects\epmsystem1\config\foundation\11.1.2.0\reg.properties file.

(5) A much enhanced validation tool is available in \Oracle\Middleware\user_projects\epmsystem1\bin\validate.bat. In EPM 11.1.2.1 the output files are of the form \Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\instance_report_20YYMMDD_######.html (where YY is the year, MM is the month, DD is the day, and ###### is a unique integer). It also runs the tool under (1) and gives the output of that tool.

(6) Individual log files may be found in subdirectories under (those 'starred' are not collected by ziplogs):
\Oracle\Middleware\user_projects\domains\EPMSystem\servers\\logs *
\Oracle\Middleware\logs *
\Oracle\Middleware\wlserver_10.3 *
\Oracle\Middleware\user_projects\epmsystem1\tmp *
\Oracle\Middleware\ohs\cfgtoollogs\opatch *
\Oracle\Middleware\EPMSystem11R1\diagnostics\logs
\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\
\Program Files\Oracle\Inventory\logs
C:\Users\\Oracle\oradiag_\diag\
C:\Users\\.oracle\logs\

(7) Some debug tools (*) can be activated if under http://:19000/workspace/index.jsp > Navigate > Administration > Workspace Server Settings > Client Debug Enabled: is set to Yes (then click 'OK' button, close all browser windows, and restart browser).
* http://hostname:19000/workspace/debug/configInfo.jsp
* http://hostname:19000/workspace/debug/userInfo.jsp
* http://hostname:19000/workspace/debug/userGroupQuery.jsp

Other tools are available at these URLs (largely derived from validate.bat output). A non-Error response indicates that the web service of each particular application is active.:
http://hostname:19000/workspace/status
http://hostname:19000/workspace/BPMContext
http://hostname:8600/mappingtool/faces/info.jspx
http://hostname:10080/easconsole/console.html
http://hostname:16000/WebAnalysis
http://hostname:6373/oracle-epm-fm-webservices/ApplicationService
http://hostname:8300/HyperionPlanning/
http://hostname:13080/aps/APS
http://hostname:8200/hr/status.jsp
http://hostname:19091/awb/conf/AwbConfig.xml
http://hostname:8500/calcmgr/index.htm

(8) Enterprise Manager is the standard Oracle graphic user interface debugging and configuration tool. Although advanced versions require extra cost licensing, there is a bundled version of Enterprise Manager available with EPM. Research the product starting with KM article 1302746.1. It is hoped that ECID (Execution Context ID) functionality will be widely incorporated with the 'Hyperion' product stack in EPM version 11.1.2.2.

References

Related

Products

Middleware > Enterprise Performance Management > Essbase > Hyperion Essbase
Middleware > Business Intelligence > Hyperion Query & Reporting > Hyperion BI+
Middleware > Enterprise Performance Management > Planning > Hyperion Planning
Middleware > Enterprise Performance Management > Financial Management > Hyperion Financial Management
Middleware > Business Intelligence > Hyperion Query & Reporting > Hyperion BI+

Keywords

CONFIGURATION; CONFIGURATION FILE; DEBUGGING; DIAGNOSTICS; ENTERPRISE MANAGER; ENTERPRISE PERFORMANCE MANAGEMENT; LOG FILE; PERFORMANCE MANAGEMENT; PERL; RDA; TROUBLESHOOT

ORACLE® HYPERION FINANCIAL MANAGEMENT

2012-01-06T10:47:00.001+03:00

ORACLE® HYPERION FINANCIAL MANAGEMENT

Frequently Asked Questions: 64-Bit Environments

• What is 64-bit Financial Management?

o This is the 64-bit port of Financial Management. It is functionally identical to 32-bit Financial Management and uses the same code base. The first version of 64-bit Financial Management is 11.x.

• Which Operating Systems are supported?

o The x86-64 versions of Microsoft Windows are supported. On the application server, this includes Windows 2003 and later. On the client side, the x86-64 versions of Windows XP and Vista are supported.

• Which CPUs are supported?

o The x86-64 architecture is supported. This includes the AMD64 and Intel 64 (formerly EM64T) processors. The Itanium processor (IA-64 architecture) is currently NOT supported.

• How does one migrate from 32-bit to 64-bit Financial Management? Will 64-bit Financial Management work with an application created under 32-bit Financial Management?

o The upgrade path from a previous release running 32-bit to 64-bit Financial Management is similar to an ordinary version upgrade. When upgrading from a previous release of Financial Management, use the Schema Upgrade Utility to upgrade the database schema to support the new version of Financial Management (11.x or newer), schema upgrade is not required when moving from 11.x or newer 32-bit to 64-bit of the same release.

• Which components of the system need to be 64-bit? In particular, does the relational database need to be 64-bit?

o The database can be either 32-bit or 64-bit as long as it is a supported DBMS type and version.

o Financial Management consists of tiers: Application Server, Database Server, Web Server, remote client. The tiers can be mixed and matched as required. 32-bit clients and web servers can connect to a 64-bit application server (and vice-versa) just as the 64-bit application server can connect to either a 32-bit or 64-bit DBMS.

o Considerations need to be made for third-party and extending software. By default, the Financial Management installation software will only install 64-bit software on a 64-bit operating system (this will be addressed in future releases). This means that only the 64-bit client components will be installed on a Financial Management application server. When 32-bit connectivity is required (as is required by Financial Data Management and other systems), they may not function unless the 32-bit client software is installed on the 64-bit application server. Please refer to the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide for more information. If this is an issue, contact the Support group for steps to resolve this.

• What are the benefits of 64-bit Financial Management?

o The main benefit of 64-bit Financial Management is the ability to hold substantially more data in memory at one time. Depending on the size of the application, and its usage profile, the extra memory can lead to significant speed improvements, while simultaneously reducing the load on the relational database.

• What are the memory limitations of 64-bit Financial Management?

o The limit of virtual address space is dictated by MS Windows and is 8 TB (8192 GB), compared to a maximum of 3 GB in 32-bit Windows. Since the physical memory in almost any current computer is far smaller than 8 TB, the implication is that, in practical terms, 64-bit Financial Management is limited by physical memory, rather than virtual memory. In other words, 64-bit Financial Management can take advantage of all available physical memory once the proper memory parameter adjustments are made (see below).

• Are there any memory settings that need to be tuned for 64-bit Financial Management?

o Yes. Financial Management’s default memory settings are appropriate for a small to medium size application in a 32-bit environment. To take advantage of the extra memory in a 64-bit environment we recommend the following settings for a monthly application. The relevant registry settings are NumDataRecordsinRAM and MaxDataCacheSizeinMB which need to be created or changed in [HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Server] on each application server’s Windows registry. The following table contains suggested values for these parameters depending on available memory. This is done with the assumption that Financial Management is the only memory-intensive process running on the machine and running only a single Financial Management application. If multiple Financial Management applications will be active, then divide the Total physical Memory installed on the server by the number of Financial Management applications to arrive at the “Available Physical Memory” for each application.

Available Physical Memory

NumDataRecordsinRAM

MaxDataCacheSizeinMB

4 GB

4,000,000

500

8 GB

10,000,000

1500

16 GB

30,000,000

4500

32 GB

60,000,000

9000

For a weekly application, divide the NumDataRecordsinRAM by 4, without changing the value in the last column.

• What kind of applications will see the most benefit?

o Applications with large memory requirements will see the most benefit. This includes applications with one or more of the following characteristics:

􀂃 Large scenarios (millions of records per year),

􀂃 Dense applications (many large subcubes)

􀂃 Large memory footprint as a result of many scenarios being accessed concurrently.

􀂃 Weekly applications.

• What kind of applications will see the least benefit?

o Small applications, where the total memory footprint of the application, even under load, can fit comfortably in the 32-bit memory space.

Cold-backup scripts for Oracle E-Business Suite R11&R12

2012-01-05T11:41:00.000+03:00

Cold-backup scripts for Oracle E-Business Suite R11&R12

In this article; i will explain how we can take backup wiht using scriptsMany Oracle Forum users ask question in OTN as ” where we can find scripts for backup”. I want to share some sample script code for can take Oracle E-Business Suite.

Before start please change related information wiht yours instead of in sample code

1. Cold backup script:

BKUP_DATE=`date +%d%m%Y`
export BKUP_DATE

BKUP_LOG_FILE=/xx/log_backup_”$BKUP_DATE”.log
export BKUP_LOG_FILE

echo “##########STOPPING ORACLE SERVICES################” >> $BKUP_LOG_FILE
/xx/oraclectl.sh stop >> $BKUP_LOG_FILE
echo “##########DONE Stopping Oracle Services###########” >> $BKUP_LOG_FILE
sleep 60
echo “##########COPYING DATABASE DIRECTORIES############” >> $BKUP_LOG_FILE
/xx/backup_to_disk.sh
echo “##########DONE Copying Database Directories#######” >> $BKUP_LOG_FILE
sleep 120
echo “##########STARTING ORACLE SERVICES################” >> $BKUP_LOG_FILE
/xx/oraclectl.sh start >> $BKUP_LOG_FILE
echo “##########DONE Starting Oracle Services###########” >> $BKUP_LOG_FILE

echo “##########DELETE OLD BACKUP LOGS #################” >> $BKUP_LOG_FILE
find . -name ‘log_backup*’ -mtime +3 -exec rm -f {} \; >> $BKUP_LOG_FILE
echo “##########DONE Delete Old Backup Logs ############” >> $BKUP_LOG_FILE

/bin/mailx -s “XX company ORACLE DB COLD BACKUP LOG – ” abc@xx.com < $BKUP_LOG_FILE

As you can see we are using oraclectl.sh for can stop/start services.

The details of this sh is:

ORA_OWNER_DB=oraprod
ORA_SID_DB=PROD
ORA_HOSTNAME=xx
ORACLE_HOME=/xx/PROD/proddb/9.2.0

ORA_OWNER_APP=applprod
COMMON_TOP=/xx/PROD/prodcomn

SID_HOST=PROD_xx

case “$1″ in
‘start’) # Start the Oracle e-Business Suite Services
su – $ORA_OWNER_DB -c “$ORACLE_HOME/appsutil/scripts/$SID_HOST/addbctl.sh start”
su – $ORA_OWNER_DB -c “$ORACLE_HOME/appsutil/scripts/$SID_HOST/addlnctl.sh start $ORA_SID_DB”
su – $ORA_OWNER_APP -c “$COMMON_TOP/admin/scripts/$SID_HOST/adstrtal.sh apps/apps”
;;
‘stop’) # Stop Oracle e-Business Suite Services
su – $ORA_OWNER_APP -c “$COMMON_TOP/admin/scripts/$SID_HOST/adstpall.sh apps/apps”
sleep 240
su – $ORA_OWNER_DB -c “$ORACLE_HOME/appsutil/scripts/$SID_HOST/addlnctl.sh stop $ORA_SID_DB”
su – $ORA_OWNER_DB -c “$ORACLE_HOME/appsutil/scripts/$SID_HOST/addbctl.sh stop immediate”
;;
esac

As you can see we are using backup_to_disk.sh for can copy process

#Delete first previous cold backup

rm -rf /xx/backup/offline_backup/*

#Start to copy process for cold backup

cp -rf /xx/PROD/proddata /xx/backup/offline_dbbckp

cp -rf /xx/PROD/proddb /xx/backup/offline_dbbckp

After edit and replace your system’s exact informations(like user,path etc.) instead of my information which i have used for my script than you can use it with crontab future and can schedule for your cold backup

Tablespace check script for Oracle E-Business Suite R11&R12

2012-01-05T11:40:00.000+03:00

Tablespace check script for Oracle E-Business Suite R11&R12

In this article, i will explain how we can check tablespace size wiht scriptsAs i Dba or Apps Dba, we should check tablespace size to dont have any issue when they reach %100 usage. Here is the sample for make automatic check for tablespace usage

First of all; we will create custom env file for my script. I like to create env file because i can use same env(after edit) for other clients.

Here is my env file:

CUSTOMER=ABC
USER=oravis
ORACLE_SID=VIS
ORACLE_HOME=/u01/VIS/visdb/10.2.0
SID_HOST=”$SID”_test
ALR_DATE=`date +%d%m%Y`
ALR_LOG_FILE=/u02/alert_errors_”$ALR_DATE”.log
DBA=”erp@xxx.com”

export CUSTOMER USER SID ORACLE_HOME SID_HOST ALR_DATE ALR_LOG_FILE DBA

As you can notice, this env uses for our ABC compan my dbtier owner is oravis, my SID is VIS,my linux machine hostname is test.You can change those information wiht yours

Tablespace check script:

Before start script please be notice i put my.env file under /u01 mount point

#My env file is set here

. /u01/my.env
ps -ef | grep -v grep | grep ora_pmon_$ORACLE_SID | wc -l | while read CONTROL
do

if [ "$CONTROL" -gt 0 ] ; then

sqlplus -s < tablespace.tmp
/bin/mailx -s “TABLESPACE ALERT for ${ORACLE_SID}” erp@xxx.com < tablespace.alert
fi
else
/bin/mailx -s “DB ALERT- ${ORACLE_SID} KAPALI” erp@xxx.com< message.txt
fi
done

If i put this script to my crontab it will run and check tablespace usage. If size become %80 then it will send me e-mail. You can change ROUND ((F.FREE_SPACE/T.TOTAL_SPACE)*100)) <=20 parameter for your need. I mean if you need alert for usage become %95, than put 5 instead of 20.

FDM: How To Register The Essbase Adapter and Troubleshoot Common Issues in 11.1.2.1

2012-01-02T10:41:00.000+03:00

FDM: How To Register The Essbase Adapter and Troubleshoot Common Issues in 11.1.2.1 [ID 1345340.1]
Modified 03-NOV-2011 Type TROUBLESHOOTING Status PUBLISHED
In this Document
Purpose
Last Review Date
Instructions for the Reader
Troubleshooting Details
What are the prerequisites in Essbase?
How to register the Essbase Adapter
Troubleshooting
References

Applies to:

Hyperion FDM Essbase Adaptor - Version: 11.1.2.0.00 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Purpose

This will detail how to register the Essbase Adapter for FDM version 11.1.2.1 in 32bit and 64bit operating systems and how to troubleshoot common issues.
Last Review Date

August 10, 2011
Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.
Troubleshooting Details

What are the prerequisites in Essbase?

-Ensure that the Essbase 32bit Runtime Client is installed on the FDM Application Server. FDM is a 32bit product and so the 32bit Runtime client is required even on a 64bit Operating System

-Check that the Essbase pathing variables are set up correctly. These are different for 32bit and 64bit machines. Both options are shown in the steps below.

1. From My Computer, right-click and select Properties. The System Properties dialog box is displayed.
2. Select the Advanced tab.
3. Click Environment Variables. The Environment Variables screen is displayed.

If this is a maintenance installation then there might still be User Variables called ESSBASEPATH and ARBORPATH- these can be deleted.

4. In the System Variables Portion of the window (bottom).
5. Select the variable name "ESSBASEPATH" and click Edit. If this variable doesn't exist then create it by selecting the New button.
6. In the Variable Value field enter the path \common\EssbaseRTC\11.1.2.0 and click OK e.g.
Oracle\Middleware\EPMSystem11R1\common\EssbaseRTC\11.1.2.0
7. Select the variable name 'Path' and click Edit
8. At the start of the path add the following value depending on the operating system
On 32bit systems
%ESSBASEPATH%\bin
On 64bit system
\bin-32;%ESSBASEPATH%\bin;\Products\Essbase\EssbaseClient-32\bin

How to register the Essbase Adapter

1) Copy the appropriate FDM Essbase adapter .exe file (e.g. ES11xG4H.exe) to the \common\EssbaseRTC\11.1.2.0\bin
2) Launch the FDM Workbench and log in
3) Choose File/Register Adapter and browse to the \common\EssbaseRTC\11.1.2.0\bin folder and select the es11xg4h.exe file and click "open" to register the adapter.

Troubleshooting

If any of the steps above have been missed, then there are various errors that can occur.

Error
When exporting from FDM to Essbase receiving the error
Error: Export failed.
Detail: File not found: esbapin.DLL
At Line: 128

Resolution
The esbapin.dll file is located in the \common\EssbaseRTC\11.1.2.0\bin folder. In order that FDM can locate this, the Essbase Adapter must be registered from this folder. Please see the section on how to register the adapter above.

Error
When browsing to the target system from mapping tables receiving the error
"Error: File not found ESBAPIN.DLL

Resolution
The 32bit client is not installed
To resolve this see KM Document 948857.1

Error
When browsing to the target receiving the error
"Procedure :[EsbInit] Threw Code : 1030803 AT Line 124."

Resolution
The pathing is not correct, see above or KM Document 1342362.1

References

NOTE:1342362.1 - Unable To Connect To Essbase From Fdm Version 11.1.2.1
NOTE:948857.1 - File Not Found Esbapin.dll When Attempting to Connect to Essbase From FDM

Related
Products
Middleware > Enterprise Performance Management > Financial Data Quality Management > Hyperion FDM Essbase Adaptor
Keywords
32BIT; 64BIT; ADAPTER; ESSBASE; FDM; FILE NOT FOUND ESBAPIN.DLL; INSTALL & CONFIGURE; RUNTIME

Back to top

Hyperion Queries

2011-12-21T14:37:00.001+03:00

Hyperion Queries -

SELECT username, password FROM DBA_USERS;

SELECT name,password FROM SYS.USER$ WHERE password is not null;

desc CSS_USERS;

select NAME ,PASSWORD,DESCRIPTION, FIRSTNAME,LASTNAME from EPMSS.CSS_USERS;

select UPDATEDBY,CREATEDBY,ACCOUNTSTATUS,DESCRIPTION,LASTNAME,FIRSTNAME,PASSWORD,NAME from EPMSS.CSS_USERS;

Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone

2011-12-08T14:58:00.000+03:00

Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone [ID 559518.1]

		Modified 17-OCT-2011 Type WHITE PAPER Status PUBLISHED

Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone

Last Updated: Oct. 20, 2010

This document describes the process of using the Oracle Applications Rapid Clone utility to create a clone (copy) of an Oracle E-Business Suite Release 12 system that utilizes the Oracle Database 10g Real Application Clusters feature.

The resulting duplicate Oracle Applications Release 12 RAC environment can then be used for purposes such as:

Patch testing
User Acceptance testing
Performance testing
Load testing
QA validation
Disaster recovery

The most current version of this document can be obtained in OracleMetaLink Note 559518.1.

There is a change log at the end of this document.

In This Document

Note: At present, the procedures described in this document apply to UNIX and Linux platforms only, and are not suitable for Oracle Applications Release 12 RAC-enabled systems running on WIndows.

A number of conventions are used in describing the Oracle Applications architecture:

Convention	Meaning
Application tier	Machines (nodes) running Forms, Web, and other services (servers). Also called middle tier.
Database tier	Machines (nodes) running the Oracle Applications database.
oracle	User account that owns the database file system (database ORACLE_HOME and files).
CONTEXT_NAME	The CONTEXT_NAME variable specifies the name of the Applications context that is used by AutoConfig. The default is [SID]_[hostname].
CONTEXT_FILE	Full path to the Applications context file on the application tier or database tier.
APPSpwd	Oracle Applications database user password.
Source System	Original Applications and database system that is to be duplicated.
Target System	New Applications and database system that is being created as a copy of the source system.
ORACLE_HOME	The top-level directory into which the database software has been installed.
CRS_ORACLE_HOME	The top-level directory into which the Cluster Ready Services (CRS) software has been installed.
ASM_ORACLE_HOME	The top-level directory into which the Automatic Storage Management (ASM) software has been installed.
RMAN	Oracle's Recovery Manager utility, which ships with the 10g Database.
Image	The RMAN proprietary-format files from the source system backup.
Monospace Text	Represents command line text. Type such a command exactly as shown.
[ ]	Text enclosed in square brackets represents a variable. Substitute a value for the variable text. Do not type the square brackets.
\	On UNIX, the backslash character is entered at the end of a command line to indicate continuation of the command on the next line.

Section 1: Overview, Prerequisites and Restrictions

1.1 Overview

Converting Oracle E-Business Suite Release 12 from a single instance database to a multi-node Oracle Real Application Clusters (Oracle RAC) enabled database (described in OracleMetalink Note 388577.1) is a complex and time-consuming process. It is therefore common for many sites to maintain only a single system in which Oracle RAC is enabled with the E-Business Suite environment. Typically, this will be the main production system. In many large enterprises, however, there is often a need to maintain two or more Oracle RAC-enabled environments that are exact copies (or clones) of each other. This may be needed, for example, when undertaking specialized development, testing patches, working with Oracle Global Support Services, and other scenarios. It is not advisable to carry out such tasks on a live production system, even if it is the only environment enabled to use Oracle Real Application Clusters.

The goal of this document (and the patches mentioned herein) is to provide a rapid, clear-cut, and easily achievable method of cloning an Oracle RAC enabled E-Business Suite Release 12 environment to a new set of machines on which a duplicate RAC enabled E-Business Suite system is to be deployed.

This process will be referred to as RAC-To-RAC cloning from here on.

1.1.2 Cluster Terminology

You should understand the terminology used in a cluster environment. Key terms include the following.

Automatic Storage Management (ASM) is an Oracle database component that acts as an integrated file system and volume manager, providing the performance of raw devices with the ease of management of a file system. In an ASM environment, you specify a disk group rather than the traditional datafile when creating or modifying a database structure such as a tablespace. ASM then creates and manages the underlying files automatically.
Oracle Cluster File System (OCFS2) is a general purpose cluster file system which can, for example, be used to store Oracle database files on a shared disk.
Certified Network File Systems is an Oracle-certified network attached storage (NAS) filer: such products are available from EMC, HP, NetApp, and other vendors. See the Oracle Release 10g Real Application Clusters installation and user guides for details on supported NAS devices and certified cluster file systems.
Cluster Ready Services (CRS) is the primary program that manages high availability operations in an Oracle RAC environment. The crs process manages designated cluster resources, such as databases, instances, services, and listeners.
Oracle Real Application Clusters (Oracle RAC) is a database feature that allows multiple machines to work on the same data in parallel, reducing processing time. Of equal or greater significance, depending on the specific need, an Oracle RAC environment also offers resilience if one or more machines become temporarily unavailable as a result of planned or unplanned downtime.

1.3 Prerequisites

This document is only for use in RAC-To-RAC cloning of a source Oracle E-Business Suite Release 12 RAC System to a target Oracle E-Business Suite RAC System.
The steps described in this note are for use by accomplished Applications and Database Administrators, who should be:
- Familiar with the principles of cloning an Oracle E-Business Suite system, as described in OracleMetaLink Note 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone.
- Familiar with Oracle Database Server 10g, and have at least a basic knowledge of Oracle Real Application Clusters (Oracle RAC).
- Experienced in the use of of RapidClone, AutoConfig, and AD utilities, as well as the steps required to convert from a single instance Oracle E-Business Suite installation to a RAC-enabled one.
The source system must remain in a running and active state during database Image creation.
The addition of database RAC nodes (beyond the assumed secondary node) is, from the RapidClone perspective, easily handled. However, the Clusterware software stack and cluster-specific configuration must be in place first, to allow RapidClone to configure the database technology stack properly. The CRS specific steps required for the addition of database nodes are briefly covered further in Appendix A however the Oracle Clusterware product documentation should be referred to for greater detail and understanding.
Details such as operating system configuration of mount points, installation and configuration of ASM, OCFS2, NFS or other forms of cluster file systems are not covered in this document.
Oracle Clusterware installation and component service registration are not covered in this document.
Oracle Real Application Clusters Setup and Configuration Guide 10g Release 2 (10.2) is a useful reference when planning to set up Oracle Real Application Clusters and shared devices.

1.4 Restrictions

Before using RapidClone to create a clone of an Oracle E-Business Suite Release 12 RAC-enabled system, you should be aware of the following restrictions and limitations:

This RAC-To-RAC cloning procedure can be used on Oracle Database 10g and 11g RAC Systems.
The final cloned RAC environment will:
- Use the Oracle Managed Files option for datafile names.
- Contain the same number of redo log threads as the source system.
- Have all datafiles located under a single "DATA_TOP" location.
- Contain only a single control file, without any of the extra copies that the DBA typically expects.
During the cloning process, no allowance is made for the use of a Flash Recovery Area (FRA). If an FRA needs to be configured on the target system, it must be done manually.
At the conclusion of the cloning process, the final cloned Oracle RAC environment will use a pfile (parameter file) instead of an spfile. For proper CRS functionality, you should create an spfile and locate it in a shared storage location that is accessible from both Oracle RAC nodes.
Beside ASM and OCFS2, only NetApp branded devices (certified NFS clustered file systems) have been confirmed to work at present. While other certified clustered file systems should work for RAC-To-RAC cloning, shared storage combinations not specifically mentioned in this the article are not guaranteed to work, and will therefore only be supported on a best-efforts basis.

Section 2: Configuration Requirements for the Source Oracle RAC System

2.1 Required Patches

Please refer to OracleMetaLink Note 406982.1, "Cloning Oracle Applications Release 12 with Rapid Clone" to obtain the latest required RapidClone Consolidated Update patch number. Download and apply the latest required RapidClone Consolidated Update patch at this time.

Warning: After applying any new Rapid Clone, AD or AutoConfig patch, the ORACLE_HOME(s) on the source system must be updated with the files included in those patches. To synchronize the Rapid Clone and AutoConfig files within the RDBMS ORACLE_HOME using the admkappsutil.pl utility, refer to OracleMetaLink Note 387859.1, Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12, and follow the instructions in section System Configuration and Maintenance, subsection Patching AutoConfig

2.2 Supported Oracle RAC Migration

The source Oracle E-Business Suite RAC environment must be created in accordance with OracleMetalink Note 388577.1, Using Oracle 10g Release 2 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12. The RAC-To-RAC cloning process described here has only been validated for use on Oracle E-Business Suite Release 12 systems that have been converted to use Oracle RAC as per this note.

2.3 AutoConfig Compliance on Oracle RAC Nodes

Also in accordance with OracleMetalink Note 388577.1, AutoConfig must have been used during Oracle RAC configuration of the source system (following conversion).

2.4 Supported Datafile Storage Methods

The storage method used for the source system datafiles must be one of the following Oracle 10g RAC Certified types:

NFS Clustered File Systems (such as NetApp Filers)
ASM (Oracle Automatic Storage Management)
OCFS2 (Oracle Cluster File System V2)

2.5 Archive Log Mode

The source system database instances must be in archive log mode, and the archive log files must be located within the shared storage area where the datafiles are currently stored. This conforms to standard Oracle RAC best practices.

Warning: If the source system was not previously in archive log mode, but it has recently been enabled, or if the source system parameter ARCHIVE_LOG_DEST was at some point set to any local disk directory location, you must ensure that RMAN has a properly maintained list of valid archive logs located exclusively in the shared storage area.

To confirm RMAN knows only of your archive logs located on the shared disk storage area, do the following.

First, use SQL*Plus or RMAN to show the locations of the archive logs. For example:

SQL>archive log list

If the output shows a local disk location, change this location appropriately, and back up or relocated any archive log files to the shared storage area. It will then be necessary to correct the RMAN archive log manifest, as follows:

RMAN>crosscheck archivelog all;

Review the output archive log file locations and, assuming you have relocated or removed any locally stored archive logs, you will need to correct the invalid or expired archive logs as follows:

RMAN>delete expired archivelog all;

It is essential to carry out the above steps (if applicable) before you continue with the Oracle E-Business Suite Release 12 RAC cloning procedure.

2.6 Control File Location

The database instance control files must be located in the shared storage area as well.

Section 3: Configuration Requirements for the Target RAC System

3.1 User Equivalence between Oracle RAC Nodes

Set up ssh and rsh user equivalence (that is, without password prompting) between primary and secondary target Oracle RAC nodes. This is described inOracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide 10g Release 2 (10.2), with the required steps being listed in Section 2.4.7, "Configuring SSH on All Cluster Nodes".

3.2 Install Cluster Manager

Install Oracle Cluster Manager, and update the version to match that of the source system database. For example, if the original source system database is 10.2.0.3, Cluster Manager must also be patched to the 10.2.0.3 level.

Note: For detailed instructions regarding the installation and usage of Oracle's Clusterware software as it relates to Oracle Real Applications Clusters, see the following article: Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide10g Release 2 (10.2).

3.3 Verify Shared Mount Points or Disks

Ensure that all shared disk sub-systems are fully and properly configured: they need to have adequate space, be writable by the future oracle software owner, and be accessible from both primary and secondary nodes.

Note: For details on configuring ASM, OCFS2, and NFS with NetApp Filer, see the following articles:

Oracle Database Administrator's Guide 10g Release 2(10.2) contains details on creating the ASM instances. For ASM best practices, refer toAutomatic Storage Management Technical Best Practices.
Oracle Cluster File System User's Guide contains details on installing and configuring OCFS2. For OCFS best practices, refer to Linux OCFS - Best Practices.
Linux/NetApp RHEL/SUSE Setup Recommendations for NetApp Filer Storage contains details specific to Linux NFS mount options and please see Configuring Network Appliance's NetApp To Work With Oracle for details on where to find NetApp co-authored articles related to using NetApp-branded devices with Oracle products.

Note: For ASM target deployments, it is strongly recommended that a separate $ORACLE_HOME be installed for ASM management, whatever the the location of your ASM listener configuration, and it is required to change the default listener configuration via the netca executable. The ASM default listener name (or service name) must not be of the form LISTENER_[HOSTNAME]. This listener name (LISTENER_[HOSTNAME]) will be specified and used later by AutoConfig for the RAC-enabled Oracle E-Business Suite database listener.

3.4 Verify Network Layer Interconnects

Ensure that the network layer is properly defined for private, public and VIP (Clusterware) Interconnects. This should not be a problem if runcluvfy.sh from the Oracle Clusterware software stage area was executed without error prior to CRS installation.

Section 4: Preparing the Source Oracle RAC System for Cloning

4.1 Update the File System with the latest Oracle RAC Patches

The latest RapidClone Consolidate Update patch (with the post-patch steps in its README) and all pre-requisite patches should have already been applied above from Section 2 of this note. After patch application, adpreclone.pl must be re-executed on all the application tiers and database tiers. For example, on the database tier, the following command would be used:

$ cd $ORACLE_HOME/appsutil/scripts/[context_name]
$ perl adpreclone.pl dbTier

After executing adpreclone.pl on all all the application and database tiers, perform the steps below.

4.2 Create Database Image

Note: Do NOT shut down the source system database services to complete the steps on this section. The database must remain mounted and open for the imaging process to successfully complete. RapidClone for RAC-enabled Oracle E-Business Suite Release 12 systems operates differently from single instance cloning.

Login to the primary Oracle RAC node, navigate to [ORACLE_HOME]/appsutil/clone/bin, and run the adclone.pl utility from a shell as follows:

perl adclone.pl \
java=[JDK 1.5 Location] \
mode=stage \
stage=[Stage Directory] \
component=database \
method=RMAN \
dbctx=[RAC DB Context File] \
showProgress

Where:

Parameter	Usage
stage	Any directory or mount point location outside the current ORACLE_HOME location, with enough space to hold the existing database datafiles in an uncompressed form.
dbctx	Full Path to the existing Oracle RAC database context file.

The above command will create a series of directories under the specified stage location.

After the stage creation is completed, navigate to [stage]/data/stage. In this directory, you will find several 2GB RMAN backup/image files. These files will have names like "1jj9c44g_1_1". The number of files present will depend on the source system configuration. The files, along with the "backup_controlfile.ctl", will need to be transferred to the target system upon which you wish to creation your new primary Oracle RAC node.

These files should be placed into a temporary holding area, which will ultimately be removed later.

4.3 Archive the ORACLE_HOME

Note: The database may be left up and running during the ORACLE_HOME archive creation process.

Create an archive of the source system ORACLE_HOME on the primary node:

$ cd $ORACLE_HOME/..
$ tar -cvzf rac_db_oh.tgz [DATABASE TOP LEVEL DIRECTORY]

Note: Consider using data integrity utilities such as md5sum, sha1sum, or cksum to validate the file sum both before and after transfer to the target system.

This source system ORACLE_HOME archive should now be transferred to the target system RAC nodes upon which you will be configuring the new system, and placed in the directory you wish to use as the new $ORACLE_HOME.

Section 5: RAC-to-RAC Cloning

5.1 Target System Primary Node Configuration (Clone Initial Node)

Follow the steps below to clone the primary node (i.e. Node 1) to the new target system.

5.1.1 Uncompress ORACLE_HOME

Uncompress the ORACLE_HOME archive that was transferred from the source system. Choose a suitable location, and rename the extracted top-level directory name to something meaningful on the new target system.

$ tar -xvzf rac_db_oh.tgz

5.1.2 Create pairsfile.txt File for Primary Node

Create a [NEW_ORACLE_HOME]/appsutils/clone/pairsfile.txt text file with contents as shown below:

s_undo_tablespace=[UNDOTBS1 for Initial Node]
s_dbClusterInst=[Total number of Instances in a cluster e.g. 2]
s_db_oh=[Location of new ORACLE_HOME]

5.1.3 Create Context File for Primary Node

Execute the following command to create a new context file, providing carefully determined answers to the prompts.

Navigate to [NEW_ORACLE_HOME]/appsutil/clone/bin and run the adclonectx.pl utility with the following parameters:

perl adclonectx.pl \
contextfile=[PATH to OLD Source RAC contextfile.xml] \
template=[NEW ORACLE_HOME]/appsutil/template/adxdbctx.tmp \
pairsfile=[NEW ORACLE_HOME]/appsutil/clone/pairsfile.txt \
initialnode

Where:

Parameter	Usage
contextfile	Full path to the old source RAC database context file.
template	Full path to the existing database context file template.
pairsfile	Full path to the pairsfile created in the last step.

Note: A new and unique global database name (DB name) must be selected when creating the new target system context file. Do not use the source system global database name or sid name during any of the context file interview prompts as shown below.

You will be present with the following questions [sample answers provided]:

Target System Hostname (virtual or normal) [kawasaki] [Enter appropriate value if not defaulted] Do you want the inputs to be validated (y/n) [n] ? : [Enter n] Target Instance is RAC (y/n) [y] : [Enter y] Target System Database Name : [Enter new desired global DB name, not a SID; motoGP global name was selected here] Do you want the target system to have the same port values as the source system (y/n) [y] ? : [Select yes or no] Provide information for the initial RAC node: Host name [ducati] : [Always need to change this value to the current public machine name, for example kawasaki] Virtual Host name [null] : [Enter the Clusterware VIP interconnect name, for example kawasaki-vip ] Instance number [1] : 1 [Enter 1, as this will always be the instance number when you are on the primary target node] Private interconnect name [kawasaki] [Always need to change this value; enter the private interconnect name, such as kawasaki-priv] Target System quorum disk location required for cluster manager and node monitor : /tmp [Legacy parameter; just enter /tmp] Target System cluster manager service port : 9998 [This is a default port used for CRS ] Target System Base Directory : [Enter the base directory that contains the new_oh_loc dir] Oracle OS User [oracle] : [Should default to correct current user; just hit enter] Oracle OS Group [dba] : [Should default to correct current group; just hit enter] Target System utl_file_dir Directory List : /usr/tmp [Specify an appropriate value for your requirements] Number of DATA_TOP's on the Target System [2] : 1 [At present, you can only have one data_top with RAC-To-RAC cloning] Target System DATA_TOP Directory 1 : +APPS_RAC_DISK [The shared storage location; ASM diskgroup/NetApps NFS mount point/OCFS2 mount point] Do you want to preserve the Display [null] (y/n) ? : [Respond according to your requirements] New context path and file name [/s1/atgrac/racdb/appsutil/motoGP1_kawasaki.xml] : [Double-check proposed location, and amend if needed]

Note: It is critical that the correct values are selected above: if you are uncertain, review the newly-written context file and compare it with values selected during source system migration to RAC (as per OracleMetalink Note 388577.1).

When making comparisons, always ensure that any path differences between the source and target systems are understood and accounted for.

Note: If the most current AutoConfig Template patch as listed in OracleMetalink Note 387859.1 has already been applied to the source system, it is necessary to edit the value of the target system context variable "s_db_listener" to reflect the desired name for the tns listener. The traditionally accepted value is "LISTENER_[HOSTNAME]" but may be any valid value unique to the target host.

5.1.4 Restore Database on Target System Primary Node

Warning: It is NOT recommended to clone an E-Business Suite RAC enabled environments to the same host however if the source and target systems must be the same host, make certain the source system is cleanly shutdown and the datafiles moved to a temporarily inaccessible location prior to restoring/recovering the new target system.

Failure to understand this warning could result in corrupt redo logs on the source system. Same host RAC cloning requires the source system to be down.

Warning: In addition to same host RAC node cloning, it is also NOT recommended to attempt cloning E-Business Suite RAC enabled environments to a target system which can directly access source system dbf files (perhaps via an nfs shared mount). If the intended target file system has access to the to the source dbf files, corruption of redo log files can occur on the source system. It is also possible that corruption might occur if ANY dbf files exist on the new intended target file system which match the original source mount point [i.e. /foo/datafiles]. If existing datafiles on the target are in a file system location as is present on the source server [i.e. /foo/datafiles], shutdown the database which owns these datafiles.

Failure to understand this warning could result in corrupt redo logs on the source system or any existing database on the target host, having a mount point the same as the original and perhaps unrelated source system. If unsure, shutdown any database which stroes datafiles in a path which existed on the source system and in which datafiles were stored.

Restore the database after the new ORACLE_HOME is configured.

5.1.4.1 Run adclone.pl to Restore and Rename Database on New Target System

Navigate to [NEW_ORACLE_HOME]/appsutil/clone/bin and run Rapid Clone (adclone.pl utility) with the following parameters:

perl adclone.pl \
java=[JDK 1.5 Location] \
component=dbTier \
mode=apply \
stage=[ORACLE_HOME]/appsutil/clone \
method=CUSTOM \
dbctxtg=[Full Path to the Target Context File] \
rmanstage=[Location of the Source RMAN dump files... i.e. RMAN_STAGE/data/stage] \
rmantgtloc=[Shared storage loc for datafiles...ASM diskgroup / NetApps NFS mount / OCFS mount point]
srcdbname=[Source RAC system GLOBAL name] \
pwd=[APPS Password] \
showProgressode

Where:

Parameter	Usage
java	Full path to the directory where JDK 1.5 is installed.
stage	This parameter is static and refers to the newly-unzipped [ORACLE_HOME]/appsutil/clone directory.
dbctxtg	Full path to the new context file created by adclonectx.pl under [ORACLE_HOME]/appsutil.
rmanstage	Temporary location where you have placed database "image" files transferred from the source system to the new target host.
rmantgtloc	Base directory or ASM diskgroup location into which you wish the database (dbf) files to be extracted. The recreation process will create subdirectories of [GLOBAL_DB_NAME]/data, into which the dbf files will be placed. Only the shared storage mount point top level location needs be supplied.
srcdbname	Source system GLOBAL_DB_NAME (not the SID of a specific node). Refer to the source system context file parameter s_global_database_name. Note that no domain suffix should be added.
pwd	Password for the APPS user.

Note: The directories and mount points selected for the rmanstage and rmantgtloc locations should not contain datafiles for any other databases. The presence of unrelated datafiles may result in very lengthy restore operations, and on some systems a potential hang of the adclone.pl restore command .

Running the adclone.pl command may take several hours. From a terminal window, you can run:

$ tail -f [ORACLE_HOME]/appsutil/log/$CONTEXT_NAME/ ApplyDatabase_[time].log

This will display and periodically refresh the last few lines of the main log file (mentioned when you run adclone.pl), where you will see references to additional log files that can help show the current actions being executed.

5.1.4.2 Verify TNS Listener has been started

After the above process exits, and it has been confirmed that no errors were encountered, you will have a running database and TNS listener, with the new SID name chosen earlier.

Confirm that the TNS listener is running, and has the appropriate service name format as follows:

$ ps -ef | grep tns | awk '{ print $9}'

The output from the above command should return a string of the form LISTENER_[hostname]. If does not, verify the listener.ora file in the $TNS_ADMIN location before continuing with the next steps: the listener must be up and running before executing AutoConfig.

5.1.4.3 Run AutoConfig

At this point, the new database is fully functional. However, to complete the configuration you must navigate to [ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME] and execute the following command to run AutoConfig:

$ adautocfg.sh appspass=[APPS Password]

5.2 Target System Secondary Node Configuration (Clone Additional Nodes)

Follow the steps below to clone the secondary nodes (for example, Node 2) on to the target system.

5.2.1 Uncompress the archived ORACLE_HOME transferred from the Source System

Uncompress the source system ORACLE_HOME archive to a location matching that present on your target system primary node. The directory structure should match that present on the newly created target system primary node.

$ tar -xvzf rac_db_oh.tgz

5.2.2 Archive the [ORACLE_HOME]/appsutil directory structure from the new Primary Node

$ cd [ORACLE_HOME]
$ zip -r appsutil_node1.zip appsutil

5.2.3 Copy appsutil_node1.zip to the Secondary Target Node

Transfer and then expand the appsutil_node1.zip into the secondary target RAC node [NEW ORACLE_HOME].

$ cd [NEW ORACLE_HOME]
$ unzip -o appsutil_node1.zip

5.2.4 Update pairsfile.txt for the Secondary Target Node

Alter the existing pairsfile.txt (from the first target node) and change the s_undo_tablespace parameter. As this is the second node, the correct value would be UNDOTBS2. As an example, the [NEW_ORACLE_HOME]/appsutils/clone/pairsfile.txt would look like:

s_undo_tablespace=[Or UNDOTBS(+1) for additional Nodes]
s_dbClusterInst=[Total number of Instances in a cluster e.g. 2]
s_db_oh=[Location of new ORACLE_HOME]

5.2.5 Create a Context File for the Secondary Node

Navigate to [NEW_ORACLE_HOME]/appsutil/clone/bin and run the adclonectx.pl utility as follows:

perl adclonectx.pl \
contextfile=[Path to Existing Context File from the First Node] \
template=[NEW ORACLE_HOME]/appsutil/template/adxdbctx.tmp \
pairsfile=[NEW ORACLE_HOME]/appsutil/clone/pairsfile.txt \
addnode

Where:

Parameter	Usage
contextfile	Full path to the existing context file from the first (primary) node.
template	Full path to the existing database context file template.
pairsfile	Full path to the pairsfile created on last step.

Several of the interview prompts are the same as on Node 1. However, there are some new questions which are specific to the "addnode" option used when on the second node.

Note: When answering the questions below, review your responses carefully before entering them. The rest of the inputs (not shown) are the same as those encountered during the context file creation on the initial node (primary node).

Host name of the live RAC node : kawasaki [enter appropriate value if not defaulted] Domain name of the live RAC node : yourdomain.com [enter appropriate value if not defaulted] Database SID of the live RAC node : motoGP1 [enter the individual SID, NOT the Global DB name] Listener port number of the live RAC node : 1548 [enter the port # of the Primary Target Node you just created] Provide information for the new Node: Host name : suzuki [enter appropriate value if not defaulted, like suzuki] Virtual Host name : suzuki-vip [enter the Clusterware VIP interconnect name, like suzuki-vip.yourdomain.com] Instance number : 2 [enter the instance # for this current node] Private interconnect name : suzuki-priv [enter the private interconnect name, like suzuki-priv] Current Node: Host Name : suzuki SID : motoGP2 Instance Name : motoGP2 Instance Number : 2 Instance Thread : 2 Undo Table Space: UNDOTBS2 [enter value earlier added to pairsfile.txt, if not defaulted] Listener Port : 1548 Target System quorum disk location required for cluster manager and node monitor : [legacy parameter, enter /tmp]

Note: At the conclusion of these "interview" questions related to context file creation, look carefully at the generated context file and ensure that the values contained therein compare to the values entered during context file creation on Node 1. The values should be almost identical, a small but important exception being the local instance name will have a number 2 instead of a 1.

5.2.6 Configure NEW ORACLE_HOME

Run the commands below to move to the correct directory and continue the cloning process:

$ cd [NEW ORACLE_HOME]/appsutil/clone/bin
$ perl adcfgclone.pl dbTechStack [Full path to the database context file created in previous step]

Note: At the conclusion of this command, you will receive a console message indicating that the process exited with status 1 and that the addlnctl.sh script failed to start a listener named [SID]. That is expected, as this is not the proper service name. Start the proper listener by executing the following command:

[NEW_ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]/addlnctl.sh start LISTENER_[hostname].

This command will start the correct (RAC-specific) listener with the proper service name.

5.2.7 Source the new environment file in the ORACLE_HOME

Run the commands below to move to the correct directory and source the environment:

$ cd [NEW ORACLE_HOME]
$ ./[CONTEXT_NAME].env

5.2.8 Modify [SID]_APPS_BASE.ora

Edit the [SID]_APPS_BASE.ora file and change the control file parameter to reflect the correct control file location on the shared storage. This will be the same value as in the [SID]_APPS_BASE.ora on the target system primary node which was just created.

5.2.9 Start Oracle RAC Database

Start the database using the following commands:

$ sqlplus /nolog
SQL> connect / as sysdba
SQL> startup

5.2.10 Execute AutoConfig

Run AutoConfig to generate the proper listener.ora and tnsnames.ora files:

$ cd $ORACLE_HOME/appsutil/scripts/$CONTEXT_NAME
$ ./adautocfg.sh appspass=[APPS Password]

5.3 Carry Out Target System (Primary Node) Final Oracle RAC Configuration Tasks

5.3.1 Recreate TNSNAMES and LISTENER.ORA

Login again to the target primary node (Node 1) and run AutoConfig to perform the final Oracle RAC configuration and create new listener.ora and tnsnames.ora (as the FND_NODES table did not contain the second node hostname until AutoConfig was run on the secondary target RAC node).

$ cd $ORACLE_HOME/appsutil/scripts/[CONTEXT_NAME]
$ ./adautocfg.sh appspass=[APPS Password]

Note: This execution of AutoConfig on the primary target RAC Node 1 will add the second RAC Node connection information to the first node's tnsnames.ora, such that listener load balancing can occur. If you have more than two nodes in your new target system cluster, you must repeat Sections 4.2 and 4.3 for all subsequent nodes.

Section 6: RAC to Single Instance Cloning

It is now possible to clone from a RAC enabled E-Business Suite (source) environment to a Single Instance E-Business Suite (target) environment following nearly the same process detailed above in Section 5.

To clone from a RAC source environment to a Single Instance target, the image creation process as noted in Section 4 remains unchanged. On the target host system however, while working through Section 5, the context file creation (step 5.1.3 above) should be done as in the case of Single Instance cloning. All other primary target restore tasks remain the same from Section 5 in the case of Single Instance Restore. Disregard any references to secondary nodeconfiguration (starting at step 5.2) as it would not apply here.

For example:

Target Instance is RAC (y/n) [y] : [Enter n]

Because we are cloning the context file from a RAC enabled source system, the interview question above pre-selects a default value of being a RAC Instance. Be certain to select "N" for the above question. By creating a context file with without RAC attributes present, Rapid Clone will configure and convert the RDBMS Technology Stack and its binaries on the target system such that a Single Instance restore can be performed.

The Rapid Clone command to restore the database on the target system (step 5.1.4) remains the same whether the target is to be RAC or Single Instance.

Note: In a RAC to Single Instance Cloning scenario, there are no data structure changes to the database in regards to UNDO tablespaces or REDO log groups or members. These data structures will remain as were present in the source system RAC database. In some use cases, it might be advisable for the DBA to reduce the complexity carried over from the source RAC environment.

Section 7: Applications Tier Cloning for RAC

The target system Applications Tier may be located in any one of these locations:

Primary target database node
Secondary target database node
An independent machine, running neither of the target system RAC nodes
Shared between two or more machines

Because of the complexities which might arise, it is suggested that the applications tier should initially be configured to connect to a single database instance. After proper configuration with one of the two target system RAC nodes has been achieved, context variable changes can be made such that JDBC and TNS Listener load balancing are enabled.

7.1 Clone the Applications Tier

In order to clone the applications tier, follow the standard steps for the applications node posted on Sections 2 and 3 from OracleMetalink Note 406982.1,Cloning Oracle Applications Release 12 with Rapid Clone. This includes adpreclone steps, copy the bits to the target, configuration portion, and finishing tasks steps.

Note: On the applications tier, during the adcfgclone.pl execution, you will be asked for a database to which the applications tier services should connect to. Enter the information specific to a single target system RAC node (such as the primary node). On successful completion of this step, the applications node services will be started, and you should be able to log in and use the new target system Applications system.

7.2 Configure Application Tier JDBC and Listener Load Balancing

Reconfigure the applications node context variables such that database listener/instance load balancing can occur.

Note: The following details have been extracted from OracleMetalink Note 388577.1 for your convenience. Consult this note for further information.

Implement load balancing for the Applications database connections:

Run the context editor (through Oracle Applications Manager) and set the value of "Tools OH TWO_TASK" (s_tools_two_task),"iAS OH TWO_TASK"(s_weboh_twotask) and "Apps JDBC Connect Alias" (s_apps_jdbc_connect_alias).
To load-balance the Forms-based Applications database connections, set the value of "Tools OH TWO_TASK" to point to the [database_name]_balance alias generated in the tnsnames.ora file.
To load-balance the self-service Applications database connections, set the value of iAS OH TWO_TASK" and "Apps JDBC Connect Alias" to point to the [database_name]_balance alias generated in the tnsnames.ora file.

Execute AutoConfig by running the command:

cd $ADMIN_SCRIPTS_HOME; ./adautocfg.sh

After successful completion of AutoConfig, restart the Applications tier processes via the scripts located in $ADMIN_SCRIPTS_HOME.
Ensure that value of the profile option "Application Database ID" is set to dbc file name generated at $FND_SECURE.

Section 8: Advanced Cloning Scenarios

8.1 Cloning the Database Separately

In certain cases, customers may require the RAC database to be recreated separately, without using the full lock-step mechanism employed during a regular E-Business Suite RAC RapidClone scenario.

This section documents the steps needed to allow for manual creation of the target RAC database control files (or the reuse of existing control files) within the Rapid Clone process.

Unless otherwise noted, all command are specific to the primary target database instance.

Follow ONLY steps 1 and 2 in Section 2: Cloning Tasks of OracleMetalink Note 406982.1, then continue with these steps below to complete Cloning the Database Separately.

Log on to the primary target system host as the ORACLE UNIX user.
Configure the [RDBMS ORACLE_HOME] as note above in Section 5: RAC-to-RAC Cloning: execute ONLY steps 5.1.1, 5.1.2 and 5.1.3
Create the target database control files manually (if needed) or modify the existing control files as needed to define datafile, redo and archive log locations along with any other relevant and required setting.

In this step, you copy and recreate the database using your preferred method, such as RMAN restore, Flash Copy, Snap View, or Mirror View.
Start the new target RAC database in open mode.
Run the library update script against the RAC database.

$ cd [RDBMS ORACLE_HOME]/appsutil/install/[CONTEXT_NAME] $ sqlplus "/ as sysdba" @adupdlib.sql [libext]
Where [libext] should be set to 'sl' for HP-UX, 'so' for any other UNIX platform, or 'dll' for Windows.
Configure the primary target database
The database must be running and open before performing this step.
$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
$ perl adcfgclone.pl dbconfig [Database target context file]
Where Database target context file is: [RDBMS ORACLE_HOME]/appsutil/[Target CONTEXT_NAME].xml.
Note: The dbconfig option will configure the database with the required settings for the new target, but it will not recreate the control files.
When the above tasks (1-6) are completed on the primary target database instance, see "5.2 Target System Secondary Node Configuration(Clone Additional Nodes)" to configure any secondary database instances.

8.2 Additional Advanced RAC Cloning Scenarios

Rapid Clone is only certified for RAC-to-RAC and RAC-to-Single Instance Cloning at this time. Addition or removal of RAC nodes during the cloning process is not currently supported.

For complete details on the certified Rapid Clone scenarios for E-Business Suite Cloning, please refer to Document 783188.1 available in OracleMetaLink.

Appendix A: Configuring Oracle Clusterware on the Target System Database Nodes

Associating Target System Oracle RAC Database instances and listeners with Clusterware (CRS)

Add target system database, instances and listeners to CRS by running the following commands as the owner of the CRS installation:

$ srvctl add database -d [database_name] -o [oracle_home]
$ srvctl add instance -d [database_name] -i [instance_name] -n [host_name]
$ srvctl add service -d [name] -s [service_name]

Note:For detailed instructions regarding the installation and usage of Oracle Clusterware software as it relates to Real Applications Clusters, see the following article:

Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide10g Release 2 (10.2)