30 4. Set the environment variable PLUGIN_HOME to <%MIDDLEWARE_HOME%>/plugins/oracle.sysman.emas.oms.plugin_ Installation To install the patch, follow these steps: Note: In case of a multi-oms environment, after you perform these steps on the first OMS host, repeat the same steps for each of the other OMSes. 1. Maintain a location for storing the contents of the patch ZIP file. In the rest of the document, this location (absolute path) is referred to as <PATCH_TOP_DIR>. 2. Extract the contents of the patch ZIP file to the location you created in Step (1). To do so, run the following command: $ unzip -d <PATCH_TOP_DIR> p _121020_generic.zip 3. Navigate to the <PATCH_TOP_DIR>/ directory: $ cd <PATCH_TOP_DIR>/ Install the patch by running the following command: On Unix: $ opatch napply -oh $PLUGIN_HOME On Windows: opatch napply -oh %PLUGIN_HOME% 5. Start the OMS by running the following command: $ emctl start oms 5. Management Agent patch : ==================================== It is a pre-requisite to apply a patch for (BP1) on the agent before you apply this patch. To apply an agent patch, follow these steps: 1. In Cloud Control, from the Enterprise menu, select Patching and Provisioning, and then click Patches and Updates. 2. On the Patches and Updates page, in the Patch Search Region, enter the available in the readme, and click Search. 3. Select the patch, and from the context menu click Add to a Plan, and select Add to New. 4. In the Add Patch to Plan dialog box, enter a unique name for the plan, and click the search icon to view the list of targets reporting to the OMS running on your host. From the list, select the agent targets (or group of targets) that need to be patched. Ensure that you add at least one target of type agent, and then click Create Plan. 5. On the Patches and Updates page, in the Plans region, click the Patch Plan you created in the previous step. Alternatively, select the Patch Plan, and from the context menu, click View. 6. In the Create Plan wizard, on the Plan Information page, in the Overview section, enter the Patch Plan name. You can choose to edit it if you want. (Optional) Only to communicate with other adminstrators, you may enter your intended deployment date or time, and a short description. 7. Click Next. 8. On the Patches page, review the patches added to the Patch Plan.

31 9. Click Next. 10. In the Deployment Options page, retain the default location (%emd_emstagedir%) available on the target machine, or edit the Stage Location to provide a new location for staging the Agent patches. In the Credentials section, select Oracle Home Preferred Credentials if you have already set them earlier. You can otherwise click Override Oracle Home Preferred Credentials to set the Normal Oracle Home Credentials and Privileged Oracle Home Credentials, to access the Oracle home of the target. 11. Click Next. 12. On the Validation page, click Analyze to check for conflicts. If there are conflicts, then review the issues, and resolve it according to the correspnding solutions available on the page. After resolving the issue, click Re-Analyze. 13. Click Next. 14. On the Review & Deploy page, review the details you have provided for the patch plan, then click Deploy. Note: If the automated patching process fails, then to recover from the failure, you can manually apply the patch. #!/bin/bash # Script: /OraBase/Software/oracle/GridControl/cc_patches_2012_08/AGENT/install_patch.sh AGENT_BASE_DIR=/OraBase/agent/agent12c AGENT_HOME=${AGENT_BASE_DIR}/core/ AGENT_INSTANCE_HOME=${AGENT_BASE_DIR}/agent_inst export ORACLE_HOME=${AGENT_HOME} export PATH=${AGENT_INSTANCE_HOME}/bin:$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH unzip -o -d $ORACLE_HOME /OraBase/Software/oracle/GridControl/cc_patches/p _111000_Linux-x86-64.zip /OraBase/agent/agent12c/agent_inst/bin/emctl stop agent cd /OraBase/Software/oracle/GridControl/cc_patches_2012_08/AGENT/ opatch napply -skip_subset -skip_duplicate -silent -ocmrf /OraBase/Software/oracle/GridControl/cc_patches_2012_08/ocm.rsp /OraBase/agent/agent12c/agent_inst/bin/emctl start agent # End Script Ausführung: if [! -f /OraBase/Software/oracle/GridControl/cc_patches_2012_08/AGENT/install_patch.sh ]; then mount /OraBase/Software fi /OraBase/Software/oracle/GridControl/cc_patches_2012_08/AGENT/install_patch.sh umount /OraBase/Software

43 to be Privilege propagating group. User creating Privilege propagating group must have full privileges on member targets. Alternatively, it is possible to create regular groups that are not Privilege propagating. Privilege propagation groups enable administrators to grant privileges to other administrators in a manner where new administrators get the same privileges as its member targets. For example, granting Operator privilege on a Group to an Administrator will grant him Operator privilege on its member targets as well. Privilege Propagating Groups can contain individual targets. Target Privilege Grant: Connect Target Read-Only

p^db=`oj===pìééçêíáåñçêã~íáçå= Error: "Could not connect to the SQL Server Instance" or "Failed to open a connection to the database." When you attempt to launch ACT! by Sage or ACT by Sage Premium for

Exercise (Part XI) Notes: The exercise is based on Microsoft Dynamics CRM Online. For all screenshots: Copyright Microsoft Corporation. The sign ## is you personal number to be used in all exercises. All

Version: 00; Status: E Seite: 1/6 This document is drawn to show the functions of the project portal developed by Ingenics AG. To use the portal enter the following URL in your Browser: https://projectportal.ingenics.de

Exercise (Part II) Notes: The exercise is based on Microsoft Dynamics CRM Online. For all screenshots: Copyright Microsoft Corporation. The sign ## is you personal number to be used in all exercises. All

Exercise (Part I) Notes: The exercise is based on Microsoft Dynamics CRM Online. For all screenshots: Copyright Microsoft Corporation. The sign ## is you personal number to be used in all exercises. All

PTC X32plus Licensing Guide This guide provides information on the installation of license management software and request for license keys required to execute software. Select this link for the English

English Deutsch English After a configuration change in the windows registry, you have to restart the service. Requirements: Windows XP, Windows 7, SEP 12.1x With the default settings an event is triggered