The following articles will help resolve issues with HFM and Shared Services:
Configuration
- Document 1345635.1 How to Use Remote Diagnostic Agent (RDA) to Gather Diagnostic Information On Oracle Hyperion Shared Services Servers to Help Resolve Service Requests Faster
- Document 820892.1 Internet Explorer (IE7, IE8 and IE9) Recommended Settings for Oracle Hyperion Products
- Document 1355997.1 Troubleshooting Life Cycle Management Problems with Hyperion Financial Management
- Document 1109448.1 Identifying LISTEN Ports for Hyperion Services
- Document 989574.1 Starting and Stopping of HFM Server Windows Processes
- Document 851731.1 Error "404 Page not found" In Assign Access Control Module In Shared Services When Accessing Financial Management Application
- Document 1109543.1 How to Automate Financial Management Consolidation Process Using Taskflow Automation
- Document 1132263.1 Financial Management Error "Object doesn't support this property or method" or a Blank Page is Displayed When Clicking Taskflow POV Selector
- Document 961143.1 Financial Management Taskflows Run One Hour Later Than Scheduled
- Document 1069389.1 Financial Management Taskflows Fail When Sending Email Notification
- Document 871044.1 Financial Management Error "500 Internal Server Error" When Selecting Point of View in Taskflows
Oracle Hyperion Planning and Shared Services
The following article will help locate information on Hyperion Planning related to Shared Services. Doc ID 763342.1 FAQ About Shared Services and Planning Related issues
Doc ID 1212454.1 How to Update Database Connection in Shared Services Registry Using the EPMSYS_REGISTRY.bat Utility
Doc ID 801405.1 Unable to open Shared Services User Interface Error:" Failed to get Registry Instance! DB Connection is not existing for SharedService. Check registry for SharedService."
Doc ID 741599.1 Shared Services Does not Start After Rebooting the Server
Doc ID 1158016.1 How to change the Shared Services Logging Level in 11.1.2
Doc ID 1153027.1 Master Note for Hyperion Shared Services
Doc ID 976279.1 How To Change Shared Services Database Repository in EPM 11
EPM System Defects Fixed Finder Document 1292603.1
| Shared Services OpenLDAP FAQ - Common Errors, Backup Techniques, Advanced Usage [ID 763771.1] | |||||
| Modified 01-SEP-2011 Type FAQ Status PUBLISHED | |||||
In this Document
Purpose
Questions and Answers
Fundamentals
What is OpenLDAP?
What does Shared Services store in OpenLDAP ?
Which version of OpenLDAP is shipped with Shared Services?
Where can I find any documentation on OpenLDAP?
What is BDB and why it is also included with SharedServices ?
Maintenance
Is it really necessary to backup OpenLDAP ?
Can I run a "hot" backup, without stopping the service ?
How can you create a back up?
How can you restore a back up?
Can I delete all those "logfiles" ?
Common Errors
Service fails to start with error code 21
Advanced configuration
How to reset OpenLDAP without losing registration information.
Applies to:
Hyperion Financial Management - Version: 4.1.1.0.00 to 11.1.1.1.00 - Release: 4.1 to 11.1Hyperion Planning - Version: 4.1.0.0.00 to 11.1.1.1.00 [Release: 4.1 to 11.1]
Hyperion Essbase - Version: 9.0.0.0.00 to 11.1.1.1.00 [Release: 9.0 to 11.1]
Hyperion BI+ - Version: 9.0.0.0.00 to 11.1.1.1.00 [Release: 9.0 to 11.1]
Information in this document applies to any platform.
Purpose
Since the very first release of Hyperion System 9, the Shared Services product has used an OpenLDAP instance for rapid storage and retrieval of provisioning information. This document will try to clarify what this means, which problems it might involve, how you can perform common maintenance tasks and advanced configuration.Questions and Answers
Fundamentals
What is OpenLDAP?
LDAP is an acronym for the Lightweight Directory Access Protocol, a network standard developed for managing large hierarchies (directories) of objects.
As defined on the main project page, OpenLDAP is "a robust, commercial-grade, fully featured, and open source LDAP suite of applications and development tools. The project is managed by a worldwide community of volunteers".
What does Shared Services store in OpenLDAP ?
All the provisioning information related to Roles is stored in OpenLDAP. All products contact this service at authentication time to define which roles are assigned to the user. If the OpenLDAP service is not available, users cannot log on to any product.
"Native Directory" users' information is also entirely stored in OpenLDAP.
Which version of OpenLDAP is shipped with Shared Services?
Shared Services ships with a pre-configured version of OpenLDAP release 2.3.7
Where can I find any documentation on OpenLDAP?
See the extensive OpenLDAP Administrator Guide
What is BDB and why it is also included with SharedServices ?
Oracle Berkeley DB is "the industry-leading open source, embeddable database engine that provides developers with fast, reliable, local persistence". OpenLDAP uses BDB for data persistence in its default configuration.
Maintenance
Is it really necessary to backup OpenLDAP ?
Yes. OpenLDAP is an essential service for Hyperion System 9, and it's required by any System 9 version, up to and including the 9.3.x release. A corrupted repository will mean the complete loss of all provisioning information. All Native Directory users will also be deleted and the content linked to them will be mostly unrecoverable.
Unfortunately, it's not uncommon for the repository to become corrupted following an unexpected (power loss etc) or forced shutdown. Often, a simple reboot will produce minor corruptions. For this reason, Oracle strongly recommends daily or weekly backups.
Can I run a "hot" backup, without stopping the service ?
You can do this, but you should keep in mind that what you will obtain from a "hot backup" is not a full snapshot, but rather an incremental backup. As described by the BDB documentation page on archiving and restoring, "a snapshot is a full backup, whereas the periodic archival of the current log files is an incremental backup. For example, it might be reasonable to take a full snapshot of a database environment weekly or monthly, and archive additional log files daily. Using both the snapshot and [all] the log files [archived since then], a catastrophic crash at any time can be recovered to the time of the most recent log archival; a time long after the original snapshot."
How can you create a back up?
The easiest way to perform a backup is simply to copy the entire $HYPERION_HOME/SharedServices/9.x.x/OpenLDAP folder. However, this will not perform BDB transaction-log trimming, so you will end up with an ever-growing folder and increased risks of repository corruption.
The best way to create a backup is by following this procedure:
- Create a folder where you want to store your backup, e.g. C:\my_hss_backup
- Stop the SharedServices web application
- Stop the OpenLDAP service.Note: this will mean that nobody can log on any System9 product.
- Open a shell or command prompt
- Navigate to $HYPERION_HOME/SharedServices/9.x.x/server/scripts, for example:
cd C:\Hyperion\SharedServices\9.x.x\server\scripts - execute the backup.bat / backup.sh script, passing as parameter the location of the previously created empty folder, e.g.:
backup.bat C:\my_hss_backup - Restart the OpenLDAP instance
- Restart the Shared Services web application
By following this procedure, you will end up with a full backup of your configuration in the specified folder (C:\my_hss_backup in the example), ready to be used for recovery. This backup procedure will also trim the BDB transaction logs to free up space.
Note that the provided scripts are just running standard BDB tools available in $HYPERION_HOME\SharedServices\9.x.x\OpenLDAP\bdb, pointing them at the repository files under $HYPERION_HOME\SharedServices\9.x.x\OpenLDAP\var\openldap-data. You can fine tune them, or build your own scripts, by following the instructions on the BDB documentation page on archiving and restoring.
How can you restore a back up?
Assuming you created a cold backup as specified in the previous question, you can simply follow this procedure:
- Stop Shared Services web application
- Stop the OpenLDAP service. If the service is already stopped, make sure that you don't have any "slapd" processes still running (in Windows by using Task Manager, in Unix environments with PS or similar), by killing them if necessary.
- Navigate to $HYPERION_HOME/SharedServices/9.x/server/scripts, for example:
cd C:\Hyperion\SharedServices\9.x\server\scripts - execute the recover.bat / recover.sh script, passing as parameter the location of the previously created backup, e.g.:
recover.bat C:\my_hss_backup - Restart the OpenLDAP instance
- Restart the Shared Services web application
If you did not take a cold backup at any point in time, you cannot use the provided recovery script.
If you did take a old backup at some point in time, and hot backups after that, you can restore that backup with this script, and then apply the following backups in the original sequence by following the instructions on the BDB documentation page on archiving and restoring.
Can I delete all those "logfiles" ?
No! Those are transaction logs produced by BDB, and are necessary to maintain repository integrity. Do not delete them manually. Perform a cold backup as specified above, and they will be automatically discarded.
Common Errors
Service fails to start with error code 21
This is the most common error, due to minor corruptions in the repository structure, usually following forced or unexpected system shutdown. Follow this procedure to attempt a simple recovery:
- Make sure that you don't have any "slapd" processes still running (in Windows by using Task Manager, in unix environments with ps or similar), by killing them if necessary.
- Open a shell or Command Prompt
- Navigate to $HYPERION_HOME/SharedServices/9.x/OpenLDAP/var/openldap-data, e.g.:
cd C:\Hyperion\SharedServices\9.x\OpenLDAP\var\openldap-data - launch db_recover like this:
..\..\bdb\bin\db_recover - If you receive an error message reporting a version mismatch, it means that db_recover found some files to be still in use by a process, killed that process, but couldn't execute the full procedure. Launch it again and again until the message stops appearing.
The BDB documentation page on Recovery contains further details and procedures to attempt.
Advanced configuration
How to reset OpenLDAP without losing registration information.
The quickest way to get back to a new blank openLDAP repository is to reset all the OpenLDAP data to the way it was just after the installation of Shared Services. At the end of this procedure, only the admin user will be available, but so long as you registered your products with the admin user and your Shared Services relational database is not touched, you will not have to reregister the products.
- Stop the openLDAP service
- Remove all files under $HYPERION_HOME/SharedServices/9.x.x/openLDAP/var/openldap-data
- Run $HYPERION_HOME/SharedServices/9.x.x/openLDAP/ConfigureHubLDAP.bat
- Start the OpenLDAP service and the Shared Services web application
- Log into Shared Services and select Administration -> Sync Native Directory
This comment has been removed by a blog administrator.
ReplyDeleteThis comment has been removed by a blog administrator.
ReplyDeleteThis comment has been removed by a blog administrator.
ReplyDelete