OK, so there are a ton of things to do right after a fresh R12 install. And before anyone says anything, I know each of my steps has multiple steps; I though 6 things made a simpler blog title, that’s all.
Nevertheless, below are the major tasks I think every Apps DBA should do right away before letting anyone log in. I call these out for two reasons. First because they’re invasive and tough to do once people start logging in and using the system. And second, some are security-related, so it’s good to get them done right away.
There are many security precautions that should be applied to a fresh install, but these should be done immediately before allowing anyone to log in. A fresh install is basically a wide open portal complete with known passwords (APPS/APPS, SYSTEM/MANAGER) so until some of these steps are taken, your new system is extremely vulnerable. In no particular order:
Change all the standard database and application passwords. All of them. Except APPLSYSPUB because you’ll end up handing it out anyway. Set up auditing (love the syslog feature). Lock down the listener with a password. Drop unneeded DB links. Set up node validation checking if you can. If you have developers or others connecting via sqlplus and you can’t consolidate them onto a Terminal Services box or similar, then you won’t be able to do this. 2. Clean up the database.
The default database has all the data, but it’s woefully lacking in structure. I see MANY systems that years later still have the same structure set by rapidwiz. At a minimum:
Spread out the control files. Put one copy on at least two separate devices. Multiplex the online redo log groups and spread them out over separate devices as well. Enable Oracle Managed Files (OMF). Huge convenience factor, so I do it whenever possible. This step is optional, though. Convert to ASM if possible. ASM provides a lot of benefits and is getting better with every release. Create a flash recovery area, then enable archiving and flashback. Even if you don’t want to back up the environment, set RMAN up to clean up the archive logs periodically and keep your database archiving. Flashback is incredibly valuable in a test environment and archiving is required for flashback. Set up a password file. Set up the SPFILE. 3. Set up a custom tablepsace and application top.
Even if you have no stated need for a custom application top, build one. When you or your customer needs it, you’ll want it right away. Having it available will prevent you from taking shortcuts and placing files and objects where they don’t belong out of expediency.
Create a custom tablespace. Create a custom application top with OAM so it’s in the context file. Register the application top in the application. Set up custom environment variables in $APPL_TOP/APPS${CONTEXT_NAME}.env 4. Clean up the users.
Set up custom profiles and assign them to all users. You can’t really set standard accounts to expire, but you can create profiles that require password complexity and prevent password reuse. Nothing should use the DEFAULT profile; take control of system access before it becomes too big of a pain.
Lock unneeded user accounts. If people need APPS account access, set up proxy users. Create some roles for named accounts. If people need to connect directly to the database, don’t try to manage all the privileges individually. Make sure to use your custom tablespace as the default tablespace for all named accounts. Set up a different tablespace if you like, just don’t use a standard application tablespace. Change all the passwords (see step 1 above). 5. Patch it up.
Before anyone gets in, lift the entire system to the highest possible rev. Once users and developers dig in, they aren’t going to want to make any fundamental changes, so patch your new system as high as you can right away. Core tech especially. Iin no particular order:
Latest CPU patches for all tiers Java server version Desktop JRE Patchsets for technology components, e.g. 11.1.0.6 to 11.1.0.7, 10.1.3.0 to 10.1.3.4, etc. Follow the certification matrix on Metalink for certified combinations. Updated family packs (Financials, HRMS, etc) Individual product updates Latest AD patchset Latest Autoconfig templates 6. Back it all up and create a gold copy.
Once you’ve done all this work, create a cold backup. Next time you need a clean environment, just restore your gold copy. Sounds basic, but I’m amazed at how many people don’t back up an environment they really want to live with going forward; why repeat all of this work?
Of course there are many other steps – security, OS management, monitoring, ongoing backups, etc. But the steps above will get your users set up nicely so they won’t be bugging you and you won’t have to bug them any more than necessary while you all get your feet wet in your shiny new R12 environment
R12 - Cloning from an RMAN backup using duplicate database Since most DBA's are using rman for their backup strategy I thought I would put together the steps to clone from an rman backup. The steps you follow are pretty much the same as described in Appendix A: Recreating the database control files manually in Rapid Clone in Note 406982.1 - Cloning Oracle Applications Release 12 with Rapid Clone.
Here are the steps:
Execute preclone on all tiers of the source system. This includes both the database and application tiers. (For this example, TEST is my source system.)
For the database execute: $ORACLE_HOME/appsutil/scripts//adpreclone.pl dbTier Where context name is of the format _
For the application tier: $ADMIN_SCRIPTS_HOME/adpreclone.pl appsTier
Prepare the files needed for the clone and copy them to the target server.
Take a FULL rman backup and copy the files to the target server and place them in the identical path. ie. if your rman backups go to /u01/backup on the source server, place them in /u01/backup on the destination server. To be safe, you may want to copy some of the archive files generated while the database was being backed up. Place them in an identical path on the target server as well.
Application Tier: tar up the application files and copy them to the destination server. The cloning document referenced above ask you to take a copy of the $APPL_TOP, $COMMON_TOP, $IAS_ORACLE_HOME and $ORACLE_HOME. Normally I just tar up the System Base Directory, which is the root directory for your application files. Database Tier: tar up the database $ORACLE_HOME.
ex. from a single tier system. The first tar file contains the application files and the second is the database $ORACLE_HOME
[oratest@myserver TEST]$ pwd /u01/TEST [oratest@myserver TEST]$ ls apps db inst [oratest@myserver TEST]$ tar cvfzp TEST_apps_inst_myserver.tar.gz apps inst . . [oratest@myserver TEST]$ tar cvfzp TEST_dbhome_myserver.tar.gz db/tech_st
Notice for the database $ORACLE_HOME I only added the db/tech_st directory to the archive. The reason is that the database files are under db/apps_st and we don't need those. Copy the tar files to the destination server, create a directory for your new environment, for example /u01/DEV. (For the purpose of this article I will be using /u01/DEV as the system base for the target envrionment we are building and myserver is the server name.)
Extract each of the tar files with the command tar xvfzp
Ex. tar xvfzp TEST_apps_inst_myserver.tar.gz
Configure the target system.
On the database tier execute adcfgclone.pl with the dbTechStack parameter.
For example. /u01/DEV/db/tech_st/10.2.0/appsutil/clone/bin/adcfgclone.pl dbTechStack
By passing the dbTechStack parameter we are tell the script to configure only the necessary $ORACLE_HOME files such as the init file for the new environment, listener.ora, database environment settings file, etc. It will also start the listener.
You will be prompted the standard post cloning questions such as the SID of the new environment, number of DATA_TOPS, Oracle Home location, port settings, etc.
Once this is complete goto /u01/DEV/db/tech_st/10.2.0 and execute the environment settings file to make sure your environment is set correctly.
[oradev@myserver 10.2.0] . ./DEV_myserver.env
Duplicate the source database to the target.
In order to duplicate the source database you'll need to know the scn value to recover to. There are two wasy to do this. The first is to login to your rman catalog, find the Chk SCN of the files in the last backupset of your rman backup and add 1 to it.
Ex. Output from a rman> List backups . . List of Datafiles in backup set 55729 File LV Type Ckp SCN Ckp Time Name ---- -- ---- ---------- --------- ---- 7 1 Incr 5965309363843 15-JUN-09 /u02/TEST/db/apps_st/data/owad01.dbf . . So in this case the SCN we would be recovery to is 5965309363843 + 1 = 5965309363844.
The other method is to login to the rman catalog via sqlplus and execute the following query:
select max(absolute_fuzzy_change#)+1, max(checkpoint_change#)+1 from rc_backup_datafile;
Use which ever value is greater.
Modify the db_file_name_convert and log_file_name convert parameters in the target init file. Example:
Verify you can connect to source system from the target as sysdba. You will need to add a tns entry to the $TNS_ADMIN/tnsnames.ora file for the source system.
Duplicate the database. Before we use rman to duplicate the source database we need to start the target database in nomount mode.
If there are no connection errors duplicate the database with the following script:
run { set until scn 5965309363844; allocate auxiliary channel ch1 type disk; allocate auxiliary channel ch2 type disk; duplicate target database to DEV }
The most common errors at this point are connection errors to the source database and rman catalog. As well, if the log_file_name_convert and db_file_name_convert parameters are not set properly you will see errors. Fix the problems, login with rman again and re-execute the script.
When the rman duplicate has finished the database will be open and ready to proceed with the next steps.
Execute the library update script:
cd $ORACLE_HOME/appsutil/install/DEV_myserver where DEV_myserver is the of the new environment.
sqlplus "/ as sysdba"@adupdlib.sql
If your on linux replace with so, HPUX with sl and for windows servers leave blank.
Configure the target database
cd $ORACLE_HOME/appsutil/clone/bin/adcfgclone.pl dbconfig
Where is $ORACLE_HOME/appsutil/DEV_myserver.xml
Configure the application tier.
cd /u01/DEV/apps/apps_st/comn/clone/bin perl adcfgclone.pl appsTier
You will be prompted the standard cloning questions consisting of the system base directories, which services you want enabled, port pool, etc. Make sure you choose the same port pool as you did when configuring the database tier in step 3.
Once that is finished, initialize your environment by executing
. /u01/DEV/apps/apps_st/appl/APPSDEV_myserver.env
Shutdown the application tier.
cd $ADMIN_SCRIPTS_HOME ./adstpall.sh apps/
Login as apps to the database and execute:
exec fnd_conc_clone.setup_clean;
I don't believe this step is necessary but if you don't do this you will see references to your source environment in the FND_% tables. Every time you execute this procedure you need to run autoconfig on each of the tiers (db and application). We will get to that in a second.
Change the apps password. Chances are you don't want to have the same apps password as the source database, so its best to change it now while the environment is down.
With the apps tier environment initialized:
FNDCPASS apps/ 0 Y system/> SYSTEM APPLSYS
Run autoconfig on both the db tier and application tier.
db tier: cd $ORACLE_HOME/appsutil/scripts/DEV_myserver ./adautocfg.sh
Application Tier cd $ADMIN_SCRIPTS_HOME ./adautocfg.sh
If there are no errors with autoconfig start the application. Your already in the $ADMIN_SCRIPTS_HOME so just execute:
./adstrtal.sh apps/
Login to the application and perform any post cloning activities. You may want to override the work flow email address so that notifications goto a test/dev mailbox instead of users. We always change the colors and site_name profile options, etc. More details can be found in Section 3: Finishing tasks of the R12 cloning document referenced earlier.
Thats it, hopefully now you have successfully cloning an EBS environment using rman duplicate.
Step 1. Create get_pwd package specification, as shown below. CREATE OR REPLACE PACKAGE get_pwd AS FUNCTION decrypt ( KEY IN VARCHAR2 ,VALUE IN VARCHAR2 ) RETURN VARCHAR2; END get_pwd; / Step 2. Create get_pwd package body, as shown below. CREATE OR REPLACE PACKAGE BODY get_pwd AS FUNCTION decrypt ( KEY IN VARCHAR2 ,VALUE IN VARCHAR2 ) RETURN VARCHAR2 AS LANGUAGE JAVA NAME 'oracle.apps.fnd.security.WebSessionManagerProc.decrypt(java.lang.String,java.lang.Stri ng) return java.lang.String'; END get_pwd; / Step 3. Query to get password for apps user. SELECT (SELECT get_pwd.decrypt (UPPER ((SELECT UPPER (fnd_profile.VALUE ('GUEST_USER_PWD')) FROM DUAL)), usertable.encrypted_foundation_password) FROM DUAL) AS apps_password FROM fnd_user usertable WHERE usertable.user_name LIKE UPPER ((SELECT SUBSTR (fnd_profile.VALUE ('GUEST_USER_PWD') ,1 , INSTR (fnd_profile.VALUE ('GUEST_USER_PWD'), '/') - 1 ) FROM DUAL)) Step 4. Query to get password for any application user. SELECT usertable.user_name , (SELECT get_pwd.decrypt (UPPER ((SELECT (SELECT get_pwd.decrypt (UPPER ((SELECT UPPER (fnd_profile.VALUE ('GUEST_USER_PWD')) FROM DUAL)), usertable.encrypted_foundation_password) FROM DUAL) AS apps_password FROM fnd_user usertable WHERE usertable.user_name LIKE UPPER ((SELECT SUBSTR (fnd_profile.VALUE ('GUEST_USER_PWD') ,1 , INSTR (fnd_profile.VALUE ('GUEST_USER_PWD'), '/') - 1 ) FROM DUAL)))) ,usertable.encrypted_user_password) FROM DUAL) AS encrypted_user_password FROM fnd_user usertable WHERE usertable.user_name LIKE UPPER ('&username'
How to Locate the Security Role List for Performance Scorecard [ID 1060911.1] Modified 26-OCT-2010 Type HOWTO Status PUBLISHED
In this Document Goal Solution
Applies to: Hyperion Performance Scorecard - Version: 9.3.0.0.00 to 11.1.1.3.00 - Release: 9.3 to 11.1 Information in this document applies to any platform. Goal
How to find the detailed security roles that are associated with Scorecard Permission, Measure Permission, Initiative Permission and Web Page Restriction.
Solution
Take the following steps:
1. Log into Scorecard as Admin.
2. Go to the Object view.
3. Select and expand Security from the left pane.
4. Expand Security Role List.
Right mouse click on the Permission and Restriction options as required and click 'Add':
Applies to: Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ] Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later] 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] 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
Applies to: Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later ] 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.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 in EPM 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: \Oracle\Middleware\user_projects\domains\EPMSystem\servers\\logs \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
Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement Rate this document Article Rating Rate this document Excellent Good Poor
Did this document help you? Yes No Just browsing
How easy was it to find this document? Very easy Somewhat easy Not easy Comments Provide feedback for this article. Please use 'Contact Us' for other feedback. Important Note: this feedback may be anonymously visible to other customers until processed by Oracle Support.
In this Document Goal Solution 1. Putting Applications in Read-Only Mode. 2. Stopping Each Application. 3. Complete Shutdown of Essbase Server. 4. Exporting the Database 5. Using the internal backup functionality in EAS. References
Applies to: Hyperion Essbase - Version: 6.5.4.0.00 to 11.1.1.3.00 - Release: 6.5 to 11.1 Information in this document applies to any platform.
Goal How to backup Essbase Databases How to create a backup of Essbase
Backup of Essbase Databases Create Essbase Backups Backing up Essbase Essbase Server backup
Solution There are several different options for preparing your Essbase server and applications for backup. It is very important that the files be in the proper mode before backups are performed.
There have been instances where the backup utility has corrupted one or more of the files used for storing data. In these cases it was necessary to delete the files dbname.esm, dbname.ind, dbname.tct, ess0000*.ind, and ess0000*.pag on all volumes for the specific database and then reload the database or restore from backup.
These five files work together to make up the data in the database. Once one of these files gets corrupted, your entire database is corrupted.
Three methods for preparing your database for tape backup or backup to a different file system are listed below. They are intended to give a general idea about the structure of your ESSCMD script.
1. Putting Applications in Read-Only Mode. The BEGINARCHIVE and ENDARCHIVE needs to be done on each database that you wish to backup. This is a good method if your business is 24x7. The drawback is that it will need to be updated every time a new database is added.
1) Set the database in read-only mode: LOGIN "Servername" "Username" "Password";BEGINARCHIVE "AppName" "DbName" "filename";LOGOUT;EXIT; 2) Run Backup Utility. 3) End the read only mode on the database. LOGIN "Servername" "Username" "Password";ENDARCHIVE "AppName" "DbName";LOGOUT;EXIT;
2. Stopping Each Application. This ensures the files are not in use. Applications will load when a user logs in to them and starts accessing data. This method is useful as it allows the Essbase server to remain running. If you have users who might be logging in while the backup is running you need to disable logins or shutdown the server.
Note: Oracle recommends that you do shutdown the Essbase server at least once a month to purge any garbage that might have collected in memory.
1) To unload an Application from memory: LOGIN "Servername" "Username" "Password"; UNLOADAPP "AppName" LOGOUT; EXIT; 2) Run Backup Utility.
Be aware that an Essbase Application is started as soon as a user logs on to it. Stopping it from running will not prevent this.
3. Complete Shutdown of Essbase Server. Drawback: Need to restart Essbase server when finished with backup. This method will prevent people logging in and starting applications while the backup procedure is running.
1) Shut down the Essbase Server. SHUTDOWNSERVER "Servername" "Username" "Password"; 2) Run Backup Utility.
You can add bells and whistles to the basic ESSCMD script examples.
LOGOUTALLUSERS or DISABLELOGIN are commonly used. The syntax for LOGOUTALLUSERS is:
LOGOUTALLUSERS "" "";
It affects all users on the server except for the user issuing the command and other Administrators. These commands will not work if there is a process running such as a calculation.
OUTPUT is also a useful command to use in your ESSCMD scripts as is the Error Handling as described in the Database Administrator's Guide.
When you run your backup utility it is important to make backups of the Application and Database directories as well as the Essbase.sec and Essbase.bak files from the Essbase\bin directory. The Essbase server must be stopped to successfully back up the .sec and .bak files.
The files that are necessary for the database to run are:
dbname.db (dbname.dbb is a backup of this file created upon successful startup of the database) dbname.otl dbname.ind dbname.esm ess0000*.ind (This will exist only if there is data in the database) ess0000*.pag (This will exist only if there is data in the database) dbname.tct
If Essbase is spanning drives it is necessary to make a backup of the ess0000*.* files on the other volumes.
ESSCMD scripts can be called from other batch scripts. To do this put a line like the following in a .bat file to call ESSCMD:
%ARBORPATH%\BIN\ESSCMD \SCRIPT.TXT
4. Exporting the Database Another option for backing up your data that works best with databases smaller than approximately 2GB is the Export command. This is implemented through Essbase Administration Services (EAS) or ESSCMD. The export file is limited to 2GB and must be written to one volume on the server (unless you do a parallel export - in that case multiple export files will be created). Once the export file grows beyond 2GB a new export file will be created.
The export file cannot be spanned to multiple volumes.
The advantage of the export file is that in addition to creating a good backup file, it also checks for data integrity while performing the export because it checks every block to see if the corresponding page and index files match. The disadvantage of the export file is that because it goes through every block (page and index files), it does take more time than just running tape backup software or copying the files.
A good approach that many companies employ is to run the export file once a week/month. In the event of corruption, restore from the last good export and reload any data that was loaded since the export was created.
Export has three different ways to export data. All data, Input level data, or Level 0 data. The determination of Level 0 and input is based upon the sparse dimensions. For example, if you choose Level 0 data for export, you may have data at upper level dense member combinations. (i.e. Using Sample Basic as an example, a block made up from New York -100-10 may contain QTR1 data inside of it.) The export files are text files that can be used to restore the database by reloading through ESSCMD or EAS. Export files can only be reloaded if members are not removed from the outline.
All Data Export: This is the most comprehensive and also most expensive in terms of space/size for your export file. Using this will not only give the largest export file, but it will also take the longest to run. If your total size of your database is small (2G or less), then you can use this method. Restoring from this method will not require recalculation since all the information is present in the export file.
Input Level Export: If you input your data in different sparse levels (sparse parent blocks " Level 0 Blocks), this is the method that you would want to employ. If you have a database that is over 2G when fully calculated, this will enable you to bring the size of the export file under the 2GB maximum. Another advantage is that if the corruption lies in a non-input block that exists as a result of a calculation (of the input blocks), you will be cleansing your database of the corruption by exporting the good blocks. Restoring from this export method will require recalculation to build upper level blocks that exist as a result of the input blocks being calculated.
Level 0 Export: If you only load at 0 level sparse blocks (All block combinations are Level 0 sparse members) and/or if you have a large database, this is probably the best method to use for exporting. This, like the previous export method will allow you to reduce your export file by not exporting calculated blocks. Just as in the previous example, if corruption exists in upper level blocks, it will not be a problem, since the export file will not contain the upper level blocks that may contain the corruption. Restoring from this export method requires recalculation to build the upper blocks that come into existence as a result of the Level 0 blocks being calculated.
If you are using export to backup your data, you need to be sure to make copies of the other important files on your system. These files include calc scripts (.csc), rules files (.rul), outline files (.otl), report scripts (.rep), ESSCMD scripts, and security files (...\Essbase\bin\Essbase.sec and Essbase.bak). Essbase must be shut down to successfully back up the security files.
5. Using the internal backup functionality in EAS. In version 11.1.1.x and later, EAS contains a backup functionality for the data within Essbase. A right click on the database node and selecting "ARCHIVE DATABASE" will create a complete backup of the database in a combined file that can be specified by the user.
References NOTE:583342.1 - Restore an Essbase Application From Backup http://download.oracle.com/docs/cd/E12825_01/epm.111/epm_backup_recovery.pdf
Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement Rate this document Article Rating Rate this document Excellent Good Poor
Did this document help you? Yes No Just browsing
How easy was it to find this document? Very easy Somewhat easy Not easy Comments Provide feedback for this article. Please use 'Contact Us' for other feedback. Important Note: this feedback may be anonymously visible to other customers until processed by Oracle Support.
Modified 08-FEB-2011 Type REFERENCE Status PUBLISHED
In this Document Purpose Scope How to Start and Stop Financial Management (HFM) Server Windows Processes What are the main Windows processes of an HFM application server? What happens when I start the HFM Windows Service? What happens when I stop the HFM Windows Service? Why should I use the HFM Windows Service? When should I not use the HFM Windows Service? Allowing HFM to start and stop as needed. Why do I see multiple HsvDataSource.exe processes on an HFM application server? When does the HsvDataSource.exe process stop itself? Why might the HsvDataSource.exe not stop by itself? What is the CASSecurity.exe process? In what order should the HFM processes be stopped?
Applies to: Hyperion Financial Management - Version: 1.0.0.0.00 to 11.1.2.0.00 - Release: 1.0 to 11.1 Information in this document applies to any platform.
Purpose This document describes the starting and stopping of the main Windows processes that are seen in the Windows Task Manager of a HFM application server.
Scope This document is intended for use by Hyperion Financial Management administrators with a good understanding of the Windows Task Manager, in particular the Processes tab.
How to Start and Stop Financial Management (HFM) Server Windows Processes What are the main Windows processes of an HFM application server? The main Windows processes of a HFM application server are HsxService.exe, HsxServer.exe, CASSecurity.exe and HsvDatasource.exe.
What happens when I start the HFM Windows Service? Oracle's Hyperion Financial Management can be started by starting the Windows Service "Hyperion Financial Management - Management Service". When this service is started, a process called HsxService.exe will become visible in the Windows Task Manager, and will remain running until the Windows Service is stopped. The HsxServer.exe, CASSecurity.exe and HsvDataSource.exe processes are also started.
What happens when I stop the HFM Windows Service? When the Hyperion Financial Management Windows service is stopped, the HsxService.exe process will be stopped along with the HsvDataSource.exe, CASSecurity.exe and HsxServer.exe processes.
Why should I use the HFM Windows Service? Oracle typically recommends that customers use the Windows Service approach only when their individual applications within their HFM database are known to take several minutes to start up. By starting the Windows Service, the application server will pre-launch each application, which will then be "active" and already started when the first user attempts to connect to the application. In this way, the user will not experience any "delay" while logging in, due to application startup time.
Applications may take longer to start up when their metadata dimensions are very large, when an application server or database is under heavy load, or when the rules file of the application contains a slow performing "NoInput" rules section. This section may take longer to execute if it contains many loop statements through many different metadata Point of View (POV) members. Care should be taken when designing metadata and NoInput rules routines to reduce the start up time of an individual application.
When should I not use the HFM Windows Service? A potential disadvantage of using the Windows Service approach is that all applications are started, regardless of the true requirement and usage of the end users. If there are many applications that exist in the HFM database, unnecessary memory and CPU cycles may be used launching applications which are not needed by the end users. For this reason, Oracle recommends that customers not keep unused HFM applications in production environment HFM databases, or to not use the HFM Windows Service approach if there are known unused HFM applications in the database.
Allowing HFM to start and stop as needed. If the HFM Windows Service is not being used as above, Financial Management will start itself when end users attempt to log on to an HFM application. When any end user connects to HFM for the first time on a particular application server, the process HsxServer.exe will be started. This process builds connections to the HFM database repository, authenticates the user connecting, and returns a list of available HFM applications within the database. There will only be one HsxServer.exe process on each application server. If the end user who connected to the HFM application server then proceeds to select an HFM application name to open, the HsxServer.exe process will then launch the HsvDataSource.exe Windows process to start that application. The HsxServer.exe process will remain running until there are no users logged on to that application server and all HsvDataSource.exe processes have also stopped.
Why do I see multiple HsvDataSource.exe processes on an HFM application server? Hyperion Financial Management opens one HsvDataSource.exe (HSVDAT~1.EXE) process on the HFM server per active application. Connections are application specific. If multiple applications are opened, multiple HsvDataSource.exe processes will be launched.
When an application is opened, a database connection pool is created between the application process and the relational database (SQL Server / Oracle / DB2 etc). However, connections are not released on an application basis - they are released on an application server basis. All connections are not released until the application server has no Financial Management users accessing any application.
When does the HsvDataSource.exe process stop itself? When an application server determines that all users of a particular application on that application server have correctly logged off or timed out (e.g. web time out), then it sends a signal to the HsvDataSource.exe process running that application to stop itself.
When all HsvDataSource.exe processes on a particular application server have stopped themselves, then the HsxServer.exe and CASSecurity.exe processes will also be stopped. After a short delay, under normal circumstances, all HFM processes will stop themselves. Only when all HFM processes on all HFM application servers have been stopped is it safe to make changes to the relational database for example, copying applications, taking or restoring backups of the database or powering down the database. Changes to the database should NOT be made while any HsvDataSource.exe process is seen running in the Windows Task Manager.
Why might the HsvDataSource.exe not stop by itself? If end users log off incorrectly, their sessions may not have stopped. Hyperion Reports, Financial Reporting, Web Analysis, Financial Data Quality Management, Shared Services task flows or other modules may be holding open connections to Financial Management applications. All other Hyperion processes and services which may be connecting to Financial Management should be stopped first. Financial Management administrators may like to use the "Users on System" module of Financial Management to stop end user connections. When Financial Management decides that all connections have stopped, it should proceed to shut itself down automatically.
What is the CASSecurity.exe process? Another Windows process is CASSecurity.exe. This is a process that manages the interface between Financial Management and Hyperion Shared Services modules. It handles some of the authorization and authentication processes of HFM, as well as security related features while the application is running. Important Note: Any change in the Shared Services external provider configuration REQUIRES the CASSecurity.exe process to be recycled in order gain access to the provider changes. Follow the "In what order should the HFM processes be stopped" section.
In what order should the HFM processes be stopped? If Financial Management appears to have frozen / crashed it may be necessary to stop the processes. Processes should be stopped in the following order:
The Hyperion Financial Management Windows Service (HsxService.exe) should be stopped via the Windows Services if it seen to be running. The HsvDataSource.exe for each application should be shut down. Ideally it should be observed that the HsvDataSource.exe is using 00% CPU in the Windows Task Manager before it is stopped using "End Process". Care should be taken when stopping running processes. Any CASSecurity.exe process which is still running in the Windows Task Manager should be stopped using "End Process" If any HsxServer.exe process is still running, it should be stopped using "End Process"
CAUTION: In a multi-server environment where multiple application servers are connecting to the same relational database, the process of stopping HFM should be repeated on ALL HFM application servers before attempting to restart any HFM processes or "bring up" the applications once again. It is not recommended to stop and start any one server independently but instead to stop the whole environment and then bring it back up.
Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement Rate this document Article Rating Rate this document Excellent Good Poor
Did this document help you? Yes No Just browsing
How easy was it to find this document? Very easy Somewhat easy Not easy Comments Provide feedback for this article. Please use 'Contact Us' for other feedback. Important Note: this feedback may be anonymously visible to other customers until processed by Oracle Support.
What Order Should Hyperion Services be Started, so that Hyperion Planning will Work Properly [ID 738471.1] Modified 10-JAN-2011 Type HOWTO Status PUBLISHED In this Document Goal Solution
Applies to:
Hyperion Planning - Version: 9.3.1.0.00 to 9.3.1.0.00 - Release: 9.3 to 9.3 Information in this document applies to any platform. Goal
To provide the order in which the application services should be started so that Planning will work properly.
Solution
The following Hyperion product services and processes are listed in their recommended startup order. The names of the Services are given as they appear in the Windows 'Services' list after a standard installation:
1. Hyperion S9 OpenLDAP 2. Hyperion S9 Shared Services 3. Hyperion S9 BI+ 9.3 Core Services 1 4. Hyperion S9 EPM Architect Process Manager which also starts the following: 5. Hyperion S9 EPM Architect Engine Manager 6. Hyperion S9 EPM Architect Job Manager 7. Hyperion S9 EPM Architect Event Manager 8. Hyperion S9 BI+ Analytic Services 9.3.1 — hypservice 9. Hyperion S9 Administration Services ATS5 10.Essbase Integration Server (this service might not exist) 11.Hyperion S9 Provider Services ATS5 12.Hyperion S9 BI+ 9.3 Interactive Reporting Service 1 (this service might not exist) 13.Hyperion S9 BI+ 9.3 Workspace 14. IIS: IIS Admin Service 15. HTTP SSL 16. World Wide Web Publishing Service 17. Hyperion S9 Apache 2.0 18. Hyperion S9 BI+ 9.3 Web Analysis (this service might not exist) 19. Hyperion S9 EPM Architect Web ATS5 20. Hyperion S9 EPM Architect Data Synchronization ATS5 21. Hyperion S9 Planning 22. HyperionRMIRegistry
Oracle HTTP Server Install Fails During EPM 11.1.2 install [ID 1302850.1] Modified 14-MAR-2011 Type PROBLEM Status REVIEWED In this Document Symptoms Cause Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.0.00 and later [Release: 11.1 and later ] Information in this document applies to any platform. Symptoms
In the installation GUI, the install of Oracle HTTP server is failing. All the other products get installed properly with the status of "completed".
The following error is seen in the install log file - [2011-03-09T09:53:01.142-05:00] [EPMINS] [ERROR] [EPMINS-00583] [oracle.EPMINS] [tid: 13] [SRC_CLASS: com.hyperion.install.util.OracleUtil] Thread has been interrupted: [[ oracle.sysman.oii.oiii.OiiiInstallInventoryReadException: OUI-10039:Unable to read install inventory /app/oraInventory on this system. Please check if you have the proper permissions to read/write to the inventory. at oracle.sysman.oii.oiii.OiiiInstallAreaControl.initAreaControl(OiiiInstallAreaControl.java:1816) at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:292) at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:231) ...................................
Cause
When EPM is being installed as a user who does not have access to the central inventory (oraInventory), the Oracle HTTP server install fails.
It is documented in the epm_install.pdf that on UNIX machines, for all Oracle products, the user that will be installing must be part of the same group; the group must have write permission to the central inventory (oraInventory).
Solution
Make sure that the user (or the group that user is in) installing EPM 11.1.2 has write permissions to the central inventory (oraInventory). OR Make sure that the /var/opt/oracle directory has the right permissions. Then create another oraInst.loc(located in the /var/opt/oracle directory) file and point this to a new location for the oraInventory location for the EPM 11.1.2 software.
EPM Configurator: "\Oracle\Middleware\oracle_common\modules\oracle.jmx_11.1.1\jmxframework.jar not exists" [ID 1108192.1] Modified 20-JUL-2010 Type PROBLEM Status PUBLISHED In this Document Symptoms Cause Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.0.00 and later [Release: 11.1 and later ] Microsoft Windows (32-bit) Symptoms
You have just installed EPM System 11.1.2. You experience the following issues:
You start EPM System Configurato in the Microsoft Windows GUI environment. It does not come up.
You start EPM System Configurator from the command line. You see a long list of messages that many *.jar files are missing, including the following message: "\Oracle\Middleware\oracle_common\modules\oracle.jmx_11.1.1\jmxframework.jar not exists".
\Oracle\Middleware\oracle_common, a directory of over 900mb in size, is missing.
Cause
You did not install in a certified version of the Microsoft Windows environment.
Solution
Upgrade to Microsoft Windows SP2/R2 and verify that ALL the environmental prequisites for the operating system have been met.
Ensure Virtual memory Control Panel > System > Advanced > Performance section Settings button > Advanced Change button is set to "recommended" for system.
Control Panel > System > Advanced > Environment Variables > set TMP and TEMP in User and System variables where at least one gigabyte of memory is available.
Clear the Central Inventory by modifying inventory.xml and set the type for EPMSYSTEM to “T”. The central inventory is normally under c:\program files\oracle.
Remove all the currently installed files by taking the following steps: Delete the installed files. You may have to stop some already-running processes on Windows. Note especially “Hyperion Integration Services” service and olapisvr.exe. Remove the InstallShield files from C:\Program Files\common files\InstallShield (or at least the vpd files). 4. Reinstall with V20843-01"Oracle Hyperion Enterprise Performance Management System Additional Content Release 11.1.2.0.0" and reconfigure.
EPM v11.1.2 Configuration Tool Does Not Launch Because Of Missing Jar Files [ID 1088031.1] Modified 19-APR-2011 Type PROBLEM Status PUBLISHED In this Document Symptoms Cause Solution References
Applies to:
Hyperion Essbase - Version: 11.1.2.0.00 and later [Release: 11.1 and later ] Information in this document applies to any platform. Symptoms
When you launch the EPM v11.1.2 Configuration Utility on a new installation, the configuration tool will produce the following errors and shutdown:
ERROR: E:\Oracle\Middleware\oracle_common\modules\oracle.odl_11.1.1\ojdl.jar not exists; file depth: 2; referenced from E:\Oracle\Middleware\EPMSystem11R1\common\jlib\11.1.2.0\epm_j2se.jar referenced from E:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.jar
ERROR: E:\Oracle\Middleware\oracle_common\modules\org.apache.commons.beanutils_1.6.jar not exists; file depth: 1; referenced from E:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.jar
ERROR: E:\Oracle\Middleware\oracle_common\modules\oracle.jmx_11.1.1\jmxframework.jar not exists; file depth: 2; referenced from E:\Oracle\Middleware\EPMSystem11R1\common\jlib\11.1.2.0\epm_soa.jar referenced from E:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.jar
ERROR: E:\Oracle\Middleware\oracle_common\modules\oracle.dms_11.1.1\dms.jar not exists; file depth: 2; referenced from E:\Oracle\Middleware\EPMSystem11R1\common\jlib\11.1.2.0\epm_j2se.jar referenced from E:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.jar
ERROR: E:\Oracle\Middleware\oracle_common\modules\oracle.http_client_11.1.1.jar not exists; file depth: 2; referenced from E:\Oracle\Middleware\EPMSystem11R1\common\jlib\11.1.2.0\epm_soa.jar referenced from E:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.jar
FATAL ERROR: Jars manifest check failed with message "Some referenced jars do not exist"
You will see errors when you click on the individual products in the EPM System Installer similar to:
EPMINS-01045: One or more required assemblies are missing; cannot install one or more selected components. See the Troubleshooting Guide for more information.: EPMINS-01047: The staticContent assembly is missing. The assembly is required in order to install a selected component. Cause
There are several possible causes for these errors:
1. The static content assembly has not been downloaded. 2. Swap Space Issue. 3. Permission on the oraInventory directory for EPM user. Solution
Static Content: In addition to the standard 'Hyperion Enterprise Performance Management System Foundation Services Release 11.1.2.0.0' Assemblies, you must also download the Assembly containing the static files used during installation and configuration.
You must download and unzip into your Assemblies folder the following component:
Swap Space: If the swap space is inadequate then OHS will not fully install. The Oracle Universal installer checks if you have more than 500MB of swap space. If you are using a server that has the virtual memory system managed then create a page file on the local drive to get the OHS universal installer to pass the swap space check.
If the OHS install fails then the oracle_common directory may be missing as a result. This will prevent the system configurator from launching. Make sure you rename the existing Oracle Inventory directory if you hit this problem so that it can create a new one during the re-install.
Permission on oraInventory Directory If the oraInventory directory already exists under a different user, the EPM user will need to have write permission to it or it will not be able to install some of the OHS components.
Note: If you do not install to the default location (/Oracle/Middleware) the installation logs may not get generated. This can make it difficult to diagnose any problems with the installation you may run in to.
Doing a Clean Uninstall of EPM 11.1.2 on Microsoft Windows [ID 1140553.1] Modified 07-JUL-2010 Type HOWTO Status PUBLISHED In this Document Goal Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.0.00 and later [Release: 11.1 and later ] Information in this document applies to any platform. Goal
Perform a clean uninstall of EPM 11.1.2.
Solution
Uninstall of EPM 11.1.2 is covered in the document "Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide" in Chapter 10 (page 219) "Uninstalling EPM system". This document can be accessed from the following link: http://download.oracle.com/docs/cd/E17236_01/nav/portal_1.htm.
The following steps will help: Stop all EPM (Hyperion and Oracle*) services. Follow the steps in Chapter 10 in the above document. Uninstall using the same user account who made the installation. Note: EPM uninstaller only uninstalls Middleware_Home\EPMSystem11R1. It does not uninstall Middleware_Home items like WL (weblogic), OHS (Oracle HTTP Server), JDK, jRockit, oracle_common, modules. This is because Middleware_Home is shared with other products. Uninstall the following only when no other use remains: Run WL uninstaller separately. Run OHS uninstaller separately. Run Oracle Application Developer uninstaller separately. Post-uninstallation checks: After uninstalling, please check in the start-all programs whether the Hyperion programs/shortcuts have been removed. Check under Windows registry in HKEY_LOCAL_MACHINE > Software and HKEY_CURRENT_USER > Software whether the Brio > Hyperion > Oracle keys have been removed correctly. Also confirm deletion of the following environment variables: ARBORPATH EPM_ORACLE_HOME ESSBASEPATH HYPERION_HOME As these were created when EPM was installed, they should be removed either by the uninstaller or they need to be removed manually.
Check the PATH variable and delete any portions that need to be removed.
Manually check the file system to see if any files or folders have been left behind. If any of these are left behind, they need to be removed manually. Ensure that \Documents and Settings\\.oracle.instance file has been deleted. Ensure that .oracle.products file in Middleware_Home\EPMSystem11R1 has been deleted. Remove any files left in your existing HYPERION_HOME, if you plan to re-use that location. Delete any BEA folder on the file system. Delete or rename installer records in C:\Program Files\common files\InstallShield\* if no other programs installed by this tool remain. C:\Program Files (x86)\Oracle\ or C:\Program Files\Oracle\inventory Clean up any remaining Hyperion-related files and directories under the user's install home or C:\Windows Registry keys which should be deleted: HKEY_LOCAL_MACHINE\software\wow6432node\oracle\ Delete any additional 'dds_proxy' settings in the registry. Delete any additional 'arborpath' entries in the registry. Delete any additional 'hyperion' entries in the registry.
Utilities for Troubleshooting Oracle Hyperion Enterprise Performance Management 11.1.2.1 [ID 1303200.1] Modified 20-APR-2011 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 ] 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.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 in EPM 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: \Oracle\Middleware\user_projects\domains\EPMSystem\servers\\logs \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
How May You Create Native Users in EPM 11.1.2 Using Lifecycle Management (LCM)? [ID 1173716.1] Modified 18-AUG-2010 Type HOWTO Status PUBLISHED In this Document Goal Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.0.00 and later [Release: 11.1 and later ] Information in this document applies to any platform. Goal
How may you create native users in version 11.1.2 using the LCM utility?
Solution
1. Create a user 'test' in the HSS. 2. Run the LCM migration and export the users to the FileSystem. 3. Find the Users.csv file, which will be created under MIDDLEWARE_HOME/user_projects/epmsystem1/import_export/admin@NativeDirectory. It will contain the details of the users 'admin' and 'test'. 4. Modify the Users.csv file to add new users. Enter new user names and Copy the remaining details of the user 'test' to the new users in the file. 5. Save the Users.csv file. 6. Execute the migration to import the users to HSS web application using the updated Users.csv file in the FileSystem.
After the migration is complete, newly added users in Users.csv file can be found in the HSS native directory console.
A Unique Instance Name Is Required When Configuring A New Install Of EPM 11.1.2.1 In Distributed Environment [ID 1317679.1] Modified 10-MAY-2011 Type HOWTO Status PUBLISHED In this Document Goal Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ] Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later] 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] 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.
Where are Application Install Inventories Stored in Oracle EPM 11.1.2.1 [ID 1304532.1] Modified 20-APR-2011 Type HOWTO Status PUBLISHED In this Document Goal Solution
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)
Error: "Error 404" After Configuration "Set up Shared Services and Registry Database Connection" in EPM 11.1.2.1 [ID 1303661.1] Modified 20-APR-2011 Type PROBLEM Status PUBLISHED In this Document Symptoms Cause Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ] Information in this document applies to any platform. Symptoms
When the Shared Services URL (http://:19000/interop) is accessed, an Error-404 error will appear.
A run of netstat would not show port 28080 (for Shared Services would not stay up due to lack of relational database repository). Cause
When 'Next' is clicked after the 'Set up Shared Services and Registry Database Connection...' page is configured, the EPM System Configurator tool immediately attempts to write HSS_COMPONENT_* and CSS_* tables (and ESS_CLUSTER_SERVER_MAPPING) to the relational database schema described on that page. However when the 'Back' button is clicked on the following page and new connectivity information is entered on the 'Set up Shared Services and Registry Database Connection...' page, the newly configured database will lack those tables. Without those repository database tables Shared Services will not run. Solution
Workaround:
(1) Delete the Hyperion Shared Services database repository tables ('old' Shared Services repository tables are not reused from 9.2.1 or 9.3.3 or 11.1.1.3 in any case...their data is extracted and reimported).
(2) Delete \Oracle\Middleware\user_projects\epmsystem1\config\foundation\11.1.2.0\reg.properties or create a new instance name, (to some name other than the default, 'epmsystem1') such as \Oracle\Middleware\user_projects\epmsystem2
Exporting Financial Reporting (FR) 11.1.2.1 Reports to Excel Does Not Open in Excel, but in an Internet Explorer Tab or Page [ID 1333633.1] Modified 29-JUN-2011 Type PROBLEM Status PUBLISHED In this Document Symptoms Cause Solution References
Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ] Information in this document applies to any platform. Symptoms
When users in Workspace 11.1.2.1, export a Financial Reporting report in "Query Ready mode" or "Fully Formatted", the export process opens in an Internet Explorer tab or in a new Internet Explorer page and not in Excel Workbook. Cause
This is an expected behavior under 11.1.2.1. The report opens correctly in Internet Explorer instead of Excel as there have been code changes in this area between system 9.3.1 and 11.1.2.1 Solution
To have the export open in Excel directly :
- Go to My Computer > Tools > Folder Option > File Types > Select XLS and click on advanced button. Un-check "Browse in Same window".
- Export a Financial Reporting report, it will be exported in Excel.
Internet Explorer 7 (IE7) and Internet Explorer 8 (IE8) Recommended Settings for Oracle Hyperion Products [ID 820892.1] Modified 02-MAY-2011 Type HOWTO Status PUBLISHED In this Document Goal Solution
Applies to:
Hyperion Financial Management - Version: 9.2.1.0.00 to 11.1.2.0.00 - Release: 9.2 to 11.1 Information in this document applies to any platform. Goal
Following settings should be applied in order for Oracle Hyperion Products to work correctly with Internet Explorer 7 (IE 7) and Internet Explorer 8 (IE 8). IE 8 is supported with versions 11.1.2 and 9.3.3 of Oracle Hyperion Products. For version 11.1.1.3 it is supported only for: Shared Services, Performance Management Architect, Calculation Manager, Planning, Financial Management, EPM Workspace with Patch:9314073, Financial Reporting with Patch:9657652, Interactive Reporting, Web Analysis, FDM.
For more details about supported software versions visit Oracle Enterprise Performance Management Products Supported Platforms Matrices. Solution
1. Configure browser to check for new version every time user visits a page
Open Internet Explorer Go to Tools > Internet options > General
In 'Browsing history' section select 'Every time I visit the webpage'
Click Ok, then Apply. 2. Disable default pop-up blocking
Open Internet Explorer Go to Tools > Internet options > Privacy tab
Uncheck 'Turn on Pop-up Blocker' 3. Add workspace URL to trusted sites
Open Internet Explorer Go to Tools > Internet options > Security tab
Select Trusted sites from Select a zone to view or change security settings.
Type your workspace URL in form http://workspaceserver:portnumber in 'Add this website to the zone' Uncheck 'Require server verification (https:) for all sites in this zone' Click Add, then Close. Click Ok and Apply. 4. Minimize security setting for trusted sites
Open Internet Explorer Go to Tools > Internet options > Security tab Select Trusted Sites from select a zone to view or change security settings
Select custom level
From Reset to list select Low Click Ok Click Apply, then Ok 5. Customize security settings
Open Internet Explorer Go to Tools > Internet options > Security Tab > Custom Level In 'Miscellaneous' section enable the option "Allow script-initiated windows without size or position constraints" In 'ActiveX controls and plug-ins' section enable “Run ActiveX controls and plug-ins” and “Script ActiveX controls marked safe for scripting.” 6. Enable option "Always allow session cookies".
Open Internet Explorer Go to Tools > Internet options > Privacy Tab > Advanced > Check the "Override automatic cookie handling" and accept the first and third party cookies and check the "Always allow session cookies" option. 7. Disable option "Enable Native XMLHTTP".
Open Internet Explorer Go to Tools > Internet options > Advanced Tab > Uncheck the option "Enable Native XMLHTTP".
In which location shall the FR Print server 11.1.2.1 component be installed? [ID 1322103.1] Modified 23-MAY-2011 Type HOWTO Status PUBLISHED In this Document Goal Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ] Information in this document applies to any platform. Goal
In which location should the FR Print server 11.1.2.1 component be installed?
Solution
The Financial Reporting Studio 11.1.2.1 component should be installed separate from the Oracle home directory where the EPM System 11.1.2.1 product suite has been installed. Most of EPM System 11.1.2.1 is installed under the Middleware folder (e.g., C:\Oracle\Middleware...), but in order for the Print Server to be able to access the relevant libraries, it should be installed under a separate subfolder (e.g., C:\Oracle\FinancialReportingStudio).
Stop And Start Scripts Are Not Available For The Financial Reporting (FR) Print Service In 11.1.2.1 [ID 1324483.1] Modified 25-MAY-2011 Type HOWTO Status PUBLISHED In this Document Goal Solution References
Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ] Information in this document applies to any platform. Goal
You've installed Financial Reporting Print Service 11.1.2.1 but there are no stop or start scripts for it in the Oracle\Middleware\user_projects\epmsystem1\bin folder. All other EPM services have scripts stored here. Solution
Because the FR Print Server is now recommended to be installed on a separate machine from the rest of Financial Reporting, the stop and start scripts for Print Service were intentionally discontinued.
Per unpublished Bug 12431736, these scripts will return in 11.1.2.2.
Number of Users Connected with Oracle Apps/Count Concurrent_users in Oracle Apps
How do we know how many users are connected to Oracle Applications?
1st Method :
1. Enable Profile Option "Sign-On Audit" at "Form" level. 2. Run "Purge Signon Audit" request. 3. Security:Users -> Monitor" option
2nd Method :
select distinct fu.user_name User_Name,fr.RESPONSIBILITY_KEY Responsibility from fnd_user fu, fnd_responsibility fr, icx_sessions ic where fu.user_id = ic.user_id AND fr.responsibility_id = ic.responsibility_id AND ic.disabled_flag='N' AND ic.responsibility_id is not null AND ic.last_connect like sysdate;
Count Number of concurrent_users in Oracle apps?
select count(distinct d.user_name) from apps.fnd_logins a, v$session b, v$process c, apps.fnd_user d where b.paddr = c.addr and a.pid=c.pid and a.spid = b.process and d.user_id = a.user_id and (d.user_name = 'USER_NAME' OR 1=1);
Where are Application Install Inventories Stored in Oracle EPM 11.1.2.1 [ID 1304532.1] Modified 20-APR-2011 Type HOWTO Status PUBLISHED In this Document Goal Solution
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)
Oracle Hyperion Enterprise Master Note [ID 1292930.1] Modified 08-JUL-2011 Type DIAGNOSTIC TOOLS Status PUBLISHED In this Document
Purpose --- --- Oracle Hyperion Enterprise Master Note --- Still Have Questions?
Applies to:
Hyperion Enterprise - Version: 5.0.1.0.00 and later [Release: 5.0 and later ] Information in this document applies to any platform.
Purpose ---
The purpose of this document is to act as a quick reference for Hyperion Enterprise.
--- Oracle Hyperion Enterprise Master Note ---
The following links will offer specific target articles on the corresponding topics for Enterprise.
Link to Enterprise Documentation Click Here
General
Document 1287179.1 Does Upgrading to Oracle's Enterprise Performance Management (EPM) 11.1.2.1 Impact the Current Installation of Oracle's Hyperion Enterprise.
Document 1294646.1 Which Versions of Hyperion Enterprise and Hyperion Enterprise Reporting Are Compatible with Windows 7?
Document 1287788.1 Hyperion Enterprise Client Crash In Windows XP.
Document 588620.1 List of settings/recommendations to avoid corruption.
Document 1137585.1 The Files and Their Purposes in Hyperion Enterprise.
Document 1100507.1 Best Practice For Hyperion Enterprise Backup and Virus Scanning.
Document 581499.1 How To Set Up Hyperion Retrieve With User Specific Or Multiple HPAPP.DAT Files In A Citrix Environment.
Document 581367.1 Information About the Locking Account in Hyperion Enterprise.
Document 588126.1 Performance Factors For Oracle's Hyperion Enterprise.
Document 582320.1 Converting An Enterprise Application Using The Conversion Utility.
Document 1064821.1 How To Rebuild A Hyperion Enterprise Application.
Document 583610.1 Rebuild A Data Category In An Enterprise Application.
Document 980282.1 Where To Get The Oracle Enterprise Performance Management System Documentation?
Troubleshooting
Document 589479.1 Error: "Class not registered" when Going into Database and Data Entry Module.
Document 595489.1 Unable to Print or Preview Any Reports.
Document 581128.1 Restrict Access to Entity in Retrieve.
Document 844378.1 Understanding and Troubleshooting Chappfile and LockfileEx Errors in Hyperion Enterprise.
Still Have Questions?
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the Hyperion Enterprise Community .
REM DBAToolZ NOTE: REM This script was obtained from DBAToolZ.com REM It's configured to work with SQL Directory (SQLDIR). REM SQLDIR is a utility that allows easy organization and REM execution of SQL*Plus scripts using user-friendly menu. REM Visit DBAToolZ.com for more details and free SQL scripts. REM REM REM File: REM a_conc_cleanup.sql REM REM APPS_CONC_MAN REM REM Author: REM Vitaliy Mogilevskiy (www.dbatoolz.com) REM REM Purpose: REM REM Resets concurrent managers/processes. REM Use if you killed any of the FND processes. REM REM REM Usage: REM a_conc_cleanup.sql REM REM Example: REM a_conc_cleanup.sql REM REM REM History: REM 11-24-2001 VMOGILEV Created REM REM
prompt "*** WARNING ***" prompt "This script will re-set conc managers as if they were never started" accept dummy prompt "press Enter to continue or CTL-C to exit"
spool a_conc_cleanup.log set verify off set lines 132 set trims on set pages 60 set feedback on
col CONCURRENT_QUEUE_ID format 9999 Heading "QUEUE Id" col CONCURRENT_QUEUE_NAME format a10 trunc Heading "QUEUE Code" col USER_CONCURRENT_QUEUE_NAME format a25 trunc Heading "Concurrent Queue Name" col MAX_PROCESSES format 999 Heading "Max" col RUNNING_PROCESSES format 999 Heading "Act" col running format 999 Heading "Run"
prompt CONCURRENT MANAGER CLEANUP prompt ========================== prompt UPDATING fnd_concurrent_queues (setting RUN and MAX to 0) ... select q.CONCURRENT_QUEUE_ID , q.CONCURRENT_QUEUE_NAME , q.USER_CONCURRENT_QUEUE_NAME , q.MAX_PROCESSES , q.RUNNING_PROCESSES , running.total running from (select /*+ ORDERED */ count(*) total , prc.CONCURRENT_QUEUE_ID from apps.fnd_concurrent_processes prc , apps.FND_CONCURRENT_REQUESTS req where req.phase_code='R' and req.controlling_manager = prc.concurrent_process_id group by prc.CONCURRENT_QUEUE_ID) running , apps.fnd_concurrent_queues_vl q where q.CONCURRENT_QUEUE_ID = running.CONCURRENT_QUEUE_ID(+) order by DECODE(q.application_id,0,DECODE(q.CONCURRENT_QUEUE_ID,1,1,4,2)) , sign(q.max_processes) desc , q.CONCURRENT_QUEUE_NAME , q.application_id;
update fnd_concurrent_queues set running_processes=0, max_processes=0 where (running_processes != 0 or max_processes != 0);
prompt UPDATING fnd_concurrent_processes (setting ACTIVE to K) ... select CONCURRENT_PROCESS_ID FROM fnd_concurrent_processes WHERE process_status_code not in ('K', 'S');
UPDATE fnd_concurrent_processes SET process_status_code = 'K' WHERE process_status_code not in ('K', 'S');
prompt UPDATING fnd_concurrent_queues (setting CONTROL CODE to NULL) ... SELECT concurrent_queue_name FROM fnd_concurrent_queues WHERE control_code not in ('E', 'R', 'X') AND control_code IS NOT NULL;
UPDATE fnd_concurrent_queues SET control_code = NULL WHERE control_code not in ('E', 'R', 'X') AND control_code IS NOT NULL;
prompt UPDATING fnd_concurrent_requests (setting PHASE=C, STATUS=X) ... col oracle_process_id format a9 heading "ORA Pid" select req.request_id , req.oracle_process_id , req.logfile_name log , req.outfile_name out from apps.fnd_concurrent_requests req where req.phase_code='R';
update fnd_concurrent_requests set phase_code='C' , status_code='X' where phase_code='R';
spool off
prompt "For safety reasons manually commit or rollback your changes"
Troubleshoot long running Concurrent Request in Apps 11i/R12 Troubleshoot long running Concurrent Request in Apps 11i/R12
This post covers overview of How to troubleshoot long running concurrent request in Oracle Apps 11i/R12
Step 1 : Check Concurrent Request ID of long running concurrent request from front end Step 2 : Find SID, SERIAL# and SPID by running SQL (given below) Step 3 : Enable event 10046 trace with level 12 using oradebug ( for 15-20 minute) Step 4 : Disable trace (once you are happy with trace size) Step 5 : Convert raw trace to TKPROF using various sort options like fchela, prsela, execpu Step 6 : Check TKPROF out file to find root cause of slow concurrent request
.
Step 1 : Check Request ID from Find Concurrent request screen (In my case Request ID is 2355)
Step 2 : Run below command to find SPID, provide concurrent request ID (2355 in my case) when prompted
SELECT a.request_id, d.sid, d.serial# ,d.osuser,d.process , c.SPID FROM apps.fnd_concurrent_requests a, apps.fnd_concurrent_processes b, v$process c, v$session d WHERE a.controlling_manager = b.concurrent_process_id AND c.pid = b.oracle_process_id AND b.session_id=d.audsid AND a.request_id = &Request_ID AND a.phase_code = ‘R’;
Step 6 : Check TKPROF file to find root cause of slow concurrent requet
.
SQL Script to Troubleshoot a long-running concurrent request .
set term on set feedback on set echo on set arraysize 4 set linesize 200 set pages 9999 set underline =; column username format A15 column sid format 9990 heading SID column type format A4 column lmode format 990 heading 'HELD' column request format 990 heading 'REQ' column id1 format 9999990 column id2 format 9999990 column sql_text format a100 column name format a80 break on id1 skip 1 dup undefine v_request_id define v_request_id undefine v_spid define v_spid undefine v_sid define v_sid spool vj_concurrent_monitor.lst
Prompt Enter the concurrent_request_id Accept v_request_id prompt checking requests select oracle_process_id from fnd_concurrent_requests where request_id='&v_request_id';
Prompt Enter the operating system oracle process id for this concurrent request accept v_spid Prompt Getting the sid SELECT SID,SERIAL#,LOGON_TIME FROM V$SESSION WHERE PADDR IN (SELECT ADDR FROM V$PROCESS WHERE SPID='&v_spid');
prompt Enter the session id for this concurrent request accept v_sid prompt memory usage for this session SELECT A.SID,A.USERNAME,B.VALUE,c.name FROM V$SESSION a,V$SESSTAT B,V$STATNAME C WHERE A.SID=B.SID AND B.STATISTIC#=C.STATISTIC# AND C.NAME like'%memor%' and a.sid='&v_sid';
prompt resource usage for this session SELECT A.SID,A.USERNAME,B.VALUE,c.name FROM V$SESSION a,V$SESSTAT B,V$STATNAME C WHERE A.SID=B.SID AND B.STATISTIC#=C.STATISTIC# and a.sid='&v_sid' order by b.value;
prompt this session waited on select sid,event,wait_time,state from v$session_wait where sid='&v_sid' order by wait_time;
prompt current sql executing by this session select a.sid,b.sorts,b.executions,b.loads,b.parse_calls,b.disk_reads, b.buffer_gets,b.rows_processed,C.sql_text from v$session a,v$sqlarea b,V$SQLTEXT C where a.sql_address=b.address and b.address=c.address and a.sid='&v_sid';
prompt sql which is taking more than 3mb in shared pool prompt nosql should take morethan 1mb in shared pool. prompt please ask the developers to tune the following sql statements select name, namespace,type,sharable_mem/(1024*1024) sharablemem,loads,executions,locks,pins,kept from v$db_object_cache where SHARABLE_MEM>3000000;
prompt sort segments using by this session SELECT s.username,s.sid,s.osuser,s.process,s.machine,u.extents, u.blocks,u.tablespace FROM v$session s, v$sort_usage u WHERE s.saddr=u.session_addr order by extents; and s.sid='&v_sid';
prompt current temp segments free in this instance SELECT tablespace_name, extent_size, total_extents, used_extents, free_extents, max_used_size FROM v$sort_segment;
prompt total system events at this time select event,total_waits waits, total_timeouts timeouts, time_waited total_time from v$system_event order by total_waits;
prompt latch contention if thery is any SELECT latch#, name, gets, misses, sleeps FROM v$latch WHERE sleeps>0 ORDER BY sleeps ;
prompt the latch which is sleeping select name, sleeps,latch# from v$latch_children where sleeps>4 order by sleeps;
How to stop concurrent requests How to Terminate running Concurrent Requests->
Set Terminating or Running to Completed/Terminated UPDATE fnd_concurrent_requests SET phase_code = 'C', status_code = 'X' WHERE status_code ='T' OR phase_code = 'R'
commit
How to set pending jobs on Hold->
Place Pending/(Normal/Standby) to On Hold UPDATE fnd_concurrent_requests SET hold_flag = 'Y' WHERE phase_code = 'P' AND status_code in ('Q','I')
commit
The above two queries are generally used if you don't want to run the requests which are copied from source system to target system during cloning. The above can be executed before making the CM up.
