JRE PLUGIN FOR EBS AND ESSBASE CONSOLE

Use jre-8u101-windows-i586 in IE 11 for ebs 12.2 console jre-7u25-windows-x64 for ESSBASE CONSOLE Find the Java Control Panel » Windows » Mac OS X Add a URL • Click on the Edit Site List button. • Click the Add in the Exception Site List window. • Click in the empty field under Location field to enter the URL. URL should begin with http:// or https:// eg. http://myexample.com or https://myexample.com • Click OK to save the URL that you entered. If you click Cancel, the URLs are not saved. • Click Continue on the Security Warning dialog.

Oracle Apps R12 Startup Shutdown Scripts

Please click the blog below and subscribe . http://madhanappsdba.blogspot.qa/2013/12/output-post-processor-opp-in-oracle.html Start-up Shutdown Scripts in Oracle Apps R12 June 10, 2007 / r12 / By Atul Kumar / 54 COMMENTS This Post covers Start-up Shutdown scripts in Oracle Applications Release 12, If you wish to know more about Startup/Shutdown scripts in Oracle Apps 11i click here Order of Startup Shutdown ————————————– As in Oracle Apps 11i order for startup is A) Start Database Tier Services –Start Database Listener –Start Database Then B) Start Application/Middle Tier Services — adstrtal.sh Order for shutdown in Oracle Apps R12 is A) Stop Application/Middle Tier Services — adstpall.sh Then B) Stop Database Tier Services –Stop Database –Stop Database Listener Database Tier Scripts in R12 ————————————– For Database tier you need to start database and database listener. Scripts are located in Database_Install_Dir/db/tech_st/10.2.0/appsutil/scripts/$CONTEXT_NAME– For Database Use script addbctl.sh – For Database Listener Use script addlnctl.sh or alternatively you can use lsnrctl startstop listener_name (For Database Listener) sqlplus “/as sysdba” SQL> startup shutdown immediate Middle/Application Tier Scripts in R12 ————————————————- Scripts for Application Tier services in R12 are located in “Install_base/inst/apps/$CONTEXT_NAME/admin/scripts“ where CONTEXT_NAME is of format SID_HOSTNAME i) adstrtal.sh Master script to start all components/services of middle tier or application tier. This script will use Service Control API to start all services which are enabled after checking them in context file (SID_HOSTNAME.xml or CONTEXT_NAME.xml) ii) adstpall.sh Master script to stop all components/services of middle tier or application tier. iii) adalnctl.sh Script to start / stop apps listener (FNDFS and FNDFS). This listener will file will be in 10.1.2 ORACLE_HOME (i.e. Forms & Reports Home) listener.ora file will be in $INST_TOP/apps/$CONTEXT_NAME/ora/10.1.2/network/admin directory (Mostly similar to one in 11i with only change in ORACLE_HOME i.e. from 8.0.6 to 10.1.2 ) iv) adapcctl.sh Script to start/stop Web Server or Oracle HTTP Server. This script uses opmn (Oracle Process Manager and Notification Server) with syntax similar to opmnctl [startstop]proc ohs like opmnctl stopproc ohs . (In 11i this script directly used to call apachectl executable but now calls opmnctl which in turn calls apachectl. In 11i web server oracle home was 1.0.2.2.2 but in R12 its 10.1.3) v) adcmctl.sh Script to start / stop concurrent manager, Similar to one in 11i. (This script in turn calls startmgr.sh ) vi) adformsctl.sh Script to start / stop Forms OC4J from 10.1.3 Oracle_Home. This script will also use opmnctl to start/stop Forms OC4J like opmnctl stopproc type=oc4j instancename=forms vii) adformsrvctl.sh This script is used only if you wish to start forms in socket mode. Default forms connect method in R12 is servlet. If started this will start frmsrv executable from 10.1.2 Oracle_Home in Apps R12 viii) adoacorectl.sh This script will start/stop oacore OC4J in 10.1.3 Oracle_Home. This scripts will also use opmnctl (similar to adapcctl & adformsctl) to start oacore instance of OC4J like opmnctl startproc type=oc4j instancename=oacore ix) adoafmctl.sh This script will start/stop oafm OC4J in 10.1.3 Oracle_Home. This scripts will also use opmnctl (similar to above) to start oacore instance of OC4J like opmnctl startproc type=oc4j instancename=oafm x) adopmnctl.sh This script will start/stop opmn service in 10.1.3 Oracle_Home. opmn will control all services in 10.1.3 Oracle_Home like web server or various oc4j instances. If any services are stopped abnormally opmn will/should start them automatically. xi) jtffmctl.sh This script will be used to start/stop one to one fulfilment server. xii) mwactl.sh To start / stop mwa telnet server where mwa is mobile application. Log File Location for Startup Shutdown Services in R12 ———————————————————————- Log files for startup/shutdown scripts for application/mid tier in R12 are in $INST_TOP/apps/$CONTEXT_NAME/logs/appl/admin/log (adalnctl.txt, adapcctl.txt, adcmctl.txt, adformsctl.txt, adoacorectl.txt, adoafmctl.txt, adopmnctl.txt, adstrtal.log, jtffmctl.txt ) –Are you facing any issues in startup/shutdown scripts ? –Should Oracle Create single script which should start/stop entire application including database ?

EBS XML Publisher Request Fails Due to Output Post Processing Issue

Please refer and subscribe the blogger below . http://r12ebs.blogspot.qa/2014/10/xml-bi-publisher-concurrent-requests.html http://madhanappsdba.blogspot.qa/2013/12/output-post-processor-opp-in-oracle.html XML Publisher Request Fails Due to Output Post Processing Issue OPP Log file: To obtain the OPP log file, follow the bellow steps: § Select the System Administrator responsibility. § Navigate to Concurrentà ManageràAdminister. § Select the Output Post Processor Service. § Select the Processes button. § Select Manager Log. Issues: BI Publisher concurrent request completed with warning due to a timeout caused by the Output Post Processor (OPP). Given bellow the possible common errors may occur due to OPP issue: Issue 1. OPP No Response: +------------- 1) PUBLISH -------------+ The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status. Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary. +--------------------------------------+ Issue 2. OPP Process Timeout: +------------- 1) PUBLISH -------------+ The concurrent manager has timed out waiting for the Output Post-processor to finish this request. Check that there are enough Output Post-processor service processes running. More information may be found in the service process logfile. +--------------------------------------+ Issue 3. OPP No Response and OPP Process Timeout: +------------- 1) PUBLISH -------------+ The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status. Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary. +--------------------------------------+ Issue 4. The OPP is not running or does not pick up the request: +------------- 1) PUBLISH -------------+ Unable to find an Output Post Processor service to post-process request [request_id]. Check that the Output Post Processor service is running. +--------------------------------------+ Issue 5. OPP log contains error java.lang.OutOfMemoryError: Java heap space Cause: 1 1. OPP No Response: The concurrent manager process generates the XML data file. Upon completion it will trigger the OPP in order to merge the XML data file and the template which was selected on the Submit Request form. The number of concurrent requests that the OPP can handle in parallel depends upon: the number of Processes the number of Threads Per Process The default values are 2 Processes and 2 Threads per Process so a total of 4 reports can be processed in parallel. In case there are other concurrent requests running which have already invoked the OPP then it might happen that no additional requests can be picked up for a period of time. The pending request will be picked up as soon as one of the running jobs completes. By default a timeout will occur if it takes longer than 120 seconds (2 min.) for the Output Post Processor to pick up the request from the concurrent manager process. In that case, the concurrent request will complete with status Warning and the request log file will contain Error Message 1 (see above). 2. OPP Process Timeout: Once the OPP picks up the request, the BI Publisher engine is invoked to generate the final output file. The time that this takes will depends on various elements such as: size of the XML Data File complexity of the template performance of the server By default a timeout will occur if it takes longer than 300 seconds (5 min.) for the BI Publisher engine to generate the output file. The concurrent request will complete with status Warning and the request log file will contain Error Message 2. 3. OPP No Response and OPP Process Timeout: The OPP service is not picking up any new requests. The OPP JAVA process is still running, but it is unresponsive. This can be due to errors in previous requests or just to the amount of time the manager has been running. The OPP becomes unresponsive (stale) after running for more than one week. 4. The OPP is not running or does not pick up the request: The error generally occurs if the OPP service is not running or the OPP service is not active 5. OPP log contains error java.lang.OutOfMemoryError: Java heap space: Solution: Two profiles options actually control the timeouts of OPP. i. Concurrent:OPP Response Timeout ii. Concurrent:OPP Process Timeout OPP No Response: i. Increase the value (in seconds) for the profile option 'Concurrent:OPP Response Timeout'. If the current value is 120 then set it to 240. (Value *2) ii. Increase the number of processes or threads (or both) of the OPP via System Administrator iii. Stop and restart the OPP service OPP Process Timeout: Increase the value (in seconds) for the profile option 'Concurrent:OPP Process Timeout'. OPP No Response and OPP Process Timeout: i. Increase the value (in seconds) for the profile option 'Concurrent:OPP Response Timeout'. If the current value is 120 then set it to 240. (Value *2) ii. Increase the value (in seconds) for the profile option 'Concurrent:OPP Process Timeout' Note: Oracle recommends setting the profiles to the following values to minimize seeing the occurrence of the Warning in your log file, especially if you are submitting large reports: Concurrent: OPP Processing Timeout to 86400 (24 hours) Concurrent: OPP Response Timeout to 3600 (1 hour) iii. Bounce the concurrent managers and resubmit. 4. The OPP is not running or does not pick up the request: Insure the OPP manager is running. Note: If the OPP manager is not running then navigate to the Oracle Applications Manager responsibility - Concurrent Managers - Select Output Post Processor - View Details - Stop and then Start the Manager again. 5. OPP log contains error java.lang.OutOfMemoryError: Java heap space: Generic errors can be resolved by performing either of the following steps: § Log into the XML Publisher Administrator responsibility. § Navigate to Home – Administration – Configuration. § Under the General Properties select Temporary directory. § Select a temporary file location on your concurrent processing node. This should be at least 5Gb or 20 times larger than the largest XML data file you generate. OR § Get the heap size per OPP process is currently defined: SELECT developer_parameters FROM fnd_cp_services WHERE service_id = (SELECT manager_type FROM fnd_concurrent_queues WHERE concurrent_queue_name = 'FNDCPOPP' ); The default should be: J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m § Increase the Heap Space per Process to 1024: UPDATE fnd_cp_services SET developer_parameters ='J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m' WHERE service_id = (SELECT manager_type FROM fnd_concurrent_queues WHERE concurrent_queue_name = 'FNDCPOPP' ); § Bounce the Concurrent Manager Output Post Processor (OPP) in Oracle Applications R12 and 11i What is Output Post Processor? Concurrent Processing now uses the Output Post Processor (OPP) to enforce post-processing actions for concurrent requests.Post-processing actions are actions taken on concurrent request output. An example of a post-processing action is that used in Concurrent Processing support of XML Publisher. If a request is submitted with an XML Publisher template specified as a layout for the concurrent request output, then after the concurrent manager finishes running the concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output. OPP runs as a service that can be managed through Oracle Applications Manager (OAM) from the System Activity page (Navigation: Applications Dashboard > Applications Service (from the dropdown list) > Go). How to Increase the number of Output Post Processors? 1.Log on to Applications with “System Administrator” responsibility. 2.Navigate to Concurrent -> Manager -> Define. 3.Query for the “Output Post Processor” service. 4.Click on “Work Shifts” and increase the number of processes How to get OPP manager log file location? $APPLCSF/log//FNDOPP####.txt OR 1,System Administrator > Concurrent > Manager > Administer 2,Search for ‘Output Post Processor’ 3,Click the ‘Processes’ button . 4,Click the Manager Log button. This will open the ‘OPP’ Upload the OPP log file. In some cases, Output Post Processor is not start up and it shows Actual and Target are showing different values when we query for Output Post Processor. The log files shows that no error message.In this case apply the following possible solution for starting the OPP. 1. Shutdown the internal manager by using adcmctl.sh stop apps/apps 2. Make sure there is no FNDLIBR processe running: $ ps -ef| grep FNDLIBR OR ps -ef|grep applprod|grep FNDLIBR 3. If there is any FNDLIBR processe please kill it $ kill -9 pid 4. Run cmclean.sql script as document from Note 134007.1 5. Restart the internal manager by using adcmctl.sh start apps/apps or How to kill and start Output Post Processor (OPP) Background: This article explains how to kill OPP and restart the same Solution: 1,System Administator > Concurrent > Manager > Administer 2,Query "Output Post Processor" -> Processes button Get the sytem id of "Output Post Processor" 3,ps -ef|grep [system id] 4,kill -9 [system id] in Unix 5,System Administator > Concurrent > Manager > Administer 6,Query "Output Post Processor" -> Restart button Fixing Output Post-processor actions failed issues in EBS R12 Environment: Oracle EBS 12.1.3, Oracle Database 11gR2, RedHat Linux5 Symptoms: Users unable to open the out files. Concurrent requests failed with “Post-processing of request failed error message” One or more post-processing actions failed. Consult the OPP service log for details. No further attempts will be made to post-process this request. Cause: The concurrent manager process was able to successfully invoke the Output Post-Processor (OPP) but encountered a timeout as the OPP takes longer than the value assigned to complete the job. Solution: 1,Increase the value of profile Concurrent: OPP Response Timeout . Bounce Apache and retest. 2,If the issue still exists, perform the following steps. 3,Increase the number of Output Post Processors as follows: 4,Increase the number of processes for Output Post Processor. 5,Additionally, ensure there is a setting of oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5 under Parameters. For more details Please check metalink I.E oracle.support Concurrent Requests Fail Due to Output Post Processing (OPP) Timeout [ID 352518.1] Ouput Post Processing Fails Due To java.lang.ThreadDeath [ID 427233.1] Why Does OPP Intermittently Completes With Warnings and Error 'java.lang.OutOfMemoryError'? [ID 978495.1] To know more this post is very nice http://knoworacleappsdba.blogspot.in/2012/07/all-about-output-post-processor-opp-in.html How to start the Output Post Processing (OPP) in 11i At least one OPP process active in the system. The concurrent processing uses the Output Post Processor (OPP) to enforce post-processing actions for concurrent requests. For example, post-processing action is that used in publishing concurrent requests with XML Publisher. Actually when you have submit a request with XML Publisher template specified as a layout for the concurrent request output. Once finishes the concurrent manager concurrent program, it will contact the OPP to apply the XML Publisher template and create the final output To activate the OPP follow these setps The Profile Option "Concurrent: GSM Enabled" must be set to Y Then: 1. Login to Apps with sysadmin responsibility 2. Navigate to: Concurrent -> Managers -> Define 3. Query for Manager = 'Output Post Processor%' or Short Name = FNDCPOPP 4. Check the checkbox "Enable" . 5. Click on 'Work Shifts button 6. see Work Shift of the OPP and Set Processes = 1 and Parameters = oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5 and Sleep Second = 30 7. Save How to restart Oracle Apps 11i OPP via non unix command It can be done using adcmctl.sh script only and there is no specific script for OPP. You can restart it from the application via (System Administrator responsibility > Concurrent > Manager > Administer), select "Output Post Processor" and click on the "Restart" button. OPP Issue while generating the XML Output in apps 11i Problem Description: 1, Few XML type concurrent programs taking long time and completed with warning OPP log file registered below error Caused by: java.lang.ThreadDeath 2, CPU utilization taking 100% constantly while running the concurrent programs. Cause The java.lang.ThreadDeath error indicates that the Output Post Processor has reached its processing timeout. Solution The following configuration changes are recommended to optimize the environment for these type of reports: 1. Increase the value of the Concurrent: OPP Timeout profile option to 10800 seconds. 2. Enable the scalability feature of XML Publisher: 1. Login as SYSADMIN 2. Responsibility: XML Publisher Administrator 3. Function: Administration 4. Set the following properties: 5. Temporary Directory 6. Use XML Publisher's XSLT processor: True 7. Enable scalable feature of XSLT processor: True -- By default it’s false 8. Enable XSLT runtime optimization: True > After changing the value also the problem still exist. As per the SR suggestion, we increased the java heap size from 1024M to 2048M. a. Bring down the concurrent managers. b. Use the Update statement below, for example: update FND_CP_SERVICES set DEVELOPER_PARAMETERS = 'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx2048m' where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = 'FNDCPOPP'); c. Bring concurrent managers up again Please check below note's from oracle support 427233.1 :Output Post Processing Fails Due To java.lang.ThreadDeath 1268217.1: Output Post Processor (OPP) Log Contains Error “java.lang.OutOfMemoryError: Java heap space" 1266368.1: Output Post Processor (OPP) Log Contains Error "java.lang.OutOfMemoryError" 978495.1: Why Does OPP Intermittently Completes With Warnings and Error 'java.lang.OutOfMemoryError'? 352518.1 :Concurrent Requests Fail Due to Output Post Processing (OPP) Timeout 364547.1 :Troubleshooting Oracle XML Publisher For The Oracle E-Business Suite

easconsole not working in browser

Everything is working fine, but when i try to access easconole..am not able see the console .thought it is working for my colleagues. I was having java 8 ..uninstalled this version and installed (7 update 25) j7 upaate 25 ..it worked for me :-) Link to download jre 7 update 25 is below http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html https://blogs.oracle.com/proactivesupportEPM/entry/java_update_alert_java_1 Java update alert: issue with EAS 11.1.2.3 By Lia Nowodworska -Oracle on Oct 24, 2013 (in via Nancy) Customers using EPM 11.1.2.3 and a web browser to launch the Essbase Administration Services Console will lose the ability to launch EAS Console via the Web URL if they apply Java 1.7 build 45. Development is currently investigating this issue. Workaround: If Java 1.7 Update 45 has been installed, it will need to be uninstalled and a previous version will need to be installed. Older versions of Java are available in the Java Archive Note: Though it may work, Java 1.7 is not supported in previous versions of EAS. (Exception for PSU 11.1.2.2.104 which introduced JRE 1.7 support in the 11.1.2.2 code line) Customers running a version of EAS Console prior to 11.1.2.3 need to install the supported version of JRE. Please follow this also in the Oracle Community

Fails to Apply ADF Patch 18277370 on Solaris 64bit (Doc ID 2038297.1)

Click to add to Favorites OUD11gR2PS2: Fails to Apply ADF Patch 18277370 on Solaris 64bit (Doc ID 2038297.1) To BottomTo Bottom In this Document Symptoms Cause Solution References APPLIES TO: Oracle Unified Directory - Version 11.1.2.2.0 to 11.1.2.2.2 [Release 11g] Information in this document applies to any platform. SYMPTOMS Patch 18277370 is a ADF patch to support IE11 in ODSM. But when it is attempted to be applied using opatch, it fails on Solaris 64bit environment with UnsatisfiedLinkError as follows. $ export ORACLE_HOME=$MW_HOME/oracle_common $ $MW_HOME/oracle_common/OPatch/opatch apply java.lang.UnsatisfiedLinkError: /export/home/oracle/app/Middleware/oracle_common/oui/lib/solaris/liboraInstaller.so: ld.so.1: java: fatal: /export/home/oracle/app/Middleware/oracle_common/oui/lib/solaris/liboraInstaller.so: wrong ELF class: ELFCLASS64 (Possible cause: architecture word width mismatch) at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary1(ClassLoader.java:1965) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1890) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1851) at java.lang.Runtime.load0(Runtime.java:795) at java.lang.System.load(System.java:1062) at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.loadNativeLib(OiipuUnixOps.java:402) at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.(OiipuUnixOps.java:125) at oracle.sysman.oii.oiip.oiipg.OiipgEnvironment.ssgetUidux(OiipgEnvironment.java:528) at oracle.sysman.oii.oiix.OiixEnvironmentOps.ssgetUidux(OiixEnvironmentOps.java:159) at oracle.opatch.OUIReplacer.isRootAccess(OUIReplacer.java:832) at oracle.opatch.OPatch.main(OPatch.java:518) Exception in thread "main" java.lang.UnsatisfiedLinkError: no oraInstaller in java.library.path at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1886) at java.lang.Runtime.loadLibrary0(Runtime.java:849) at java.lang.System.loadLibrary(System.java:1088) at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.loadNativeLib(OiipuUnixOps.java:420) at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.(OiipuUnixOps.java:125) at oracle.sysman.oii.oiip.oiipg.OiipgEnvironment.ssgetUidux(OiipgEnvironment.java:528) at oracle.sysman.oii.oiix.OiixEnvironmentOps.ssgetUidux(OiixEnvironmentOps.java:159) at oracle.opatch.OUIReplacer.isRootAccess(OUIReplacer.java:832) at oracle.opatch.OPatch.main(OPatch.java:518) OPatch failed with error code 1 $ CAUSE Bug 21522623 - fails to run opatch on solaris 64bit SOLUTION Since this issue happens because '-d64' is missing in JRE_MEMORY_OPTIONS on $MW_HOME/oracle_common/oui/oraparam.ini, please add '-d64' option into JRE_MEMORY_OPTIONS on $MW_HOME/oracle_common/oui/oraparam.ini like as below. JRE_MEMORY_OPTIONS=" -d64 -mx512m -XX:MaxPermSize=256m"

After applying the 11.1.2.3.500 EPM System Patch Set Update (PSU): 17529887 which is a combined EPM patch that includes Planning 11.1.2.3.500,

Issues Using Hyperion Planning after Applying EPM System Patch Set Update (PSU) 11.1.2.3.500 (Doc ID 1640411.1) To BottomTo Bottom In this Document Symptoms Cause Solution References APPLIES TO: Hyperion Planning - Version 11.1.2.3.000 and later Information in this document applies to any platform. SYMPTOMS After applying the 11.1.2.3.500 EPM System Patch Set Update (PSU): 17529887 which is a combined EPM patch that includes Planning 11.1.2.3.500, the following issues have been observered: Planning cannot be accessed via Workspace and the following error is found in the Planning0.log file: <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1402564062723>

not able to delete oci.dll

Download process explorer from MSDN. Find what has a lock on oci.dll (probably Distributed Transaction Coordinator). Stop the service. Delete the file. http://technet.microsoft.com/en-us/sysinte...s/bb896653.aspx svchost will be holding oci.dll

Perform a Clean Uninstall of EPM 11.1.2 on Microsoft Windows (Doc ID 1140553.1)

Perform a Clean Uninstall of EPM 11.1.2 on Microsoft Windows (Doc ID 1140553.1) /dhyp01/hyperion/Oracle/Middleware/wlserver_10.3/uninstall/uninstall.sh /dhyp01/hyperion/Oracle/Middleware/EPMSystem11R1/uninstall/uninstall.sh /dhyp01/hyperion/Oracle/Middleware/utils/uninstall/uninstall.sh How to Uninstall Hyperion Enterprise Performance Management (EPM) (Doc ID 1265740.1) To BottomTo Bottom In this Document Goal Solution References APPLIES TO: Hyperion Planning - Version 11.1.1.0.00 to 11.1.2.0.00 [Release 11.1] Information in this document applies to any platform. *may 18,2015* GOAL To completely uninstall Hyperion Enterprise Performance Management System SOLUTION On a Windows system: 1). Using the same user that installed EPM, uninstall the EPM suite by double clicking the 'uninstall.cmd' located in the %HYPERION_HOME%\uninstall folder. 2). Reboot the server (to remove the Windows 'Services') 3). Delete the %HYPERION_HOME% folder (and all it's sub-folders) 4). Open up the Windows registry with 'regedit' and delete the 'Hyperion Solutions' key under \\HKEY_LOCAL_MACHINE\SOFTWARE 5). In the registry, navigate to \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. There shouldn't be any services (see 2) prefixed 'HyS9', if there are then delete them. 6). Navigate to %DRIVE%\Documents and Settings\ and delete files '.oracle.products' and 'set_hyphome_1.bat' 7) Navigate to C:\Program Files\Common Files\InstallShield\Universal\common and delete the two folders 'Gen1' and 'oracle' 8). Right-click on 'My Computer' -> 'Properties' -> 'Advanced' -> 'Environment Variables' and remove the %HYPERION_HOME% variable and any Hyperion products on %PATH%. 9). Reboot - the server should now be in a state fit for an EPM re-installation. On a UNIX system: 1). Using the same user that installed EPM, uninstall the EPM suite by double clicking the 'uninstall.sh' located in the $HYPERION_HOME/uninstall directory. 2). Delete the $HYPERION_HOME directory and it's sub-directories. 3) Navigate to the $HOME directory of the user that installed Hyperion EPM and delete the files '.oracle..products' and '.hyperion.' Please see Note 1140553.1 for additional information pertinent to version 11.1.2. REFERENCES NOTE:1140553.1 - Perform a Clean Uninstall of EPM 11.1.2 on Microsoft Windows

Perform a Clean Uninstall of EPM 11.1.2 on Microsoft Windows (Doc ID 1140553.1)

Perform a Clean Uninstall of EPM 11.1.2 on Microsoft Windows (Doc ID 1140553.1) How to Uninstall Hyperion Enterprise Performance Management (EPM) (Doc ID 1265740.1) To BottomTo Bottom In this Document Goal Solution References APPLIES TO: Hyperion Planning - Version 11.1.1.0.00 to 11.1.2.0.00 [Release 11.1] Information in this document applies to any platform. *may 18,2015* GOAL To completely uninstall Hyperion Enterprise Performance Management System SOLUTION On a Windows system: 1). Using the same user that installed EPM, uninstall the EPM suite by double clicking the 'uninstall.cmd' located in the %HYPERION_HOME%\uninstall folder. 2). Reboot the server (to remove the Windows 'Services') 3). Delete the %HYPERION_HOME% folder (and all it's sub-folders) 4). Open up the Windows registry with 'regedit' and delete the 'Hyperion Solutions' key under \\HKEY_LOCAL_MACHINE\SOFTWARE 5). In the registry, navigate to \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. There shouldn't be any services (see 2) prefixed 'HyS9', if there are then delete them. 6). Navigate to %DRIVE%\Documents and Settings\ and delete files '.oracle.products' and 'set_hyphome_1.bat' 7) Navigate to C:\Program Files\Common Files\InstallShield\Universal\common and delete the two folders 'Gen1' and 'oracle' 8). Right-click on 'My Computer' -> 'Properties' -> 'Advanced' -> 'Environment Variables' and remove the %HYPERION_HOME% variable and any Hyperion products on %PATH%. 9). Reboot - the server should now be in a state fit for an EPM re-installation. On a UNIX system: 1). Using the same user that installed EPM, uninstall the EPM suite by double clicking the 'uninstall.sh' located in the $HYPERION_HOME/uninstall directory. 2). Delete the $HYPERION_HOME directory and it's sub-directories. 3) Navigate to the $HOME directory of the user that installed Hyperion EPM and delete the files '.oracle..products' and '.hyperion.' Please see Note 1140553.1 for additional information pertinent to version 11.1.2. REFERENCES NOTE:1140553.1 - Perform a Clean Uninstall of EPM 11.1.2 on Microsoft Windows