4
5/22/2018 536954_OSDatainClusterEnvt.-slidepdf.com http://slidepdf.com/reader/full/536954os-data-in-cluster-envt 1/4 16.09.2009 Page 1 of 4  SAP Note 536954 - OS data in a cluster environment for OS07  Note Language: English Version: 13 Validity: Valid Since 12.09.2006 Summary Symptom OS07: You are unable to display the hardware information in the cluster. OS07: You are unable to display the OS syslog in the cluster. OS07: You are unable to display the operating system data for the database. Previously, if you wanted to display operating system data in a cluster environment, you had to install saposcol and rfcoscol (for Windows, see Note 114287). With rfcoscol, the operating system data was transferred to the SAP system. As of Release 4.6B with the Support Packages specified below, you can install a sapccmsr agent (instead of rfcoscol), which corrects errors with the hardware information and the OS syslog display, among other things. To do so, you require at least sapccmsr Version 2003/6 (see related notes).  More Terms OS07, ST06, hardware information, OS syslog, saposcol, problems with rfcoscol Cause and Prerequisites . Solution Windows platforms: 1. Delete the old entries In transaction AL15, delete the following saposcol destinations:  - SAPOSCOL_<virtual_DB_hostname>  - SAPOSCOL_<virtual_R3_hostname> In transaction SM59, delete the following destinations:  - SAPOSCOL_<vir tual_DB_host name>  - SAPOSCOL_<vir tual_R3_host name> You no longer require the SAPOSCOL_<virtual_R3_hostname> destination. To view the operating system data of the central instance, use either transaction ST06 if you are logged on directly, or transaction OS07 -> <virtual_R3_hostname>_<SID>_<system number>. Instead of the SAPOSCOL_<virtual_R3_hostname> destination, now use the following destination: SAPCCMSR.<virtual_DB_hostname>.99 This destination is created when the agent is installed. 2. Install the SAPCCMSR agent: The SAPCCMSR agent is installed to allow you to display operating system data for the database of the cluster installation in transactions RZ20 and OS07. For this, the SAPCCMSR agent is registered in the local system and is always started together with the database resources of the cluster (if you also want to monitor the cluster using a central CCMS system, you can specify the central CCMS as a second central system when you register the agent). o Log on to the physical host on which the database is currently running.

536954_OS Data in Cluster Envt

Embed Size (px)

DESCRIPTION

536954_OS data in cluster envt.

Citation preview

  • 5/22/2018 536954_OS Data in Cluster Envt.

    1/4

    16.09.2009 Page 1 of 4

    SAP Note 536954 - OS data in a cluster environment forOS07

    Note Language: English Version: 13 Validity: Valid Since 12.09.2006

    Summary

    Symptom

    OS07: You are unable to display the hardware information in the cluster.

    OS07: You are unable to display the OS syslog in the cluster.

    OS07: You are unable to display the operating system data for the database.

    Previously, if you wanted to display operating system data in a cluster

    environment, you had to install saposcol and rfcoscol (for Windows, see

    Note 114287).

    With rfcoscol, the operating system data was transferred to the SAP system.

    As of Release 4.6B with the Support Packages specified below, you can

    install a sapccmsr agent (instead of rfcoscol), which corrects errors with

    the hardware information and the OS syslog display, among other things. To

    do so, you require at least sapccmsr Version 2003/6 (see related notes).

    More TermsOS07, ST06, hardware information, OS syslog, saposcol, problems with

    rfcoscol

    Cause and Prerequisites

    .

    Solution

    Windows platforms:

    1. Delete the old entries

    In transaction AL15, delete the following saposcol destinations:

    - SAPOSCOL_ - SAPOSCOL_

    In transaction SM59, delete the following destinations:

    - SAPOSCOL_

    - SAPOSCOL_

    You no longer require the SAPOSCOL_ destination.

    To view the operating system data of the central instance, use either

    transaction ST06 if you are logged on directly, or transaction OS07 ->

    __.

    Instead of the SAPOSCOL_ destination, now use the

    following destination:

    SAPCCMSR..99

    This destination is created when the agent is installed.

    2. Install the SAPCCMSR agent:

    The SAPCCMSR agent is installed to allow you to display operating

    system data for the database of the cluster installation in

    transactions RZ20 and OS07. For this, the SAPCCMSR agent is registered

    in the local system and is always started together with the database

    resources of the cluster (if you also want to monitor the cluster

    using a central CCMS system, you can specify the central CCMS as a

    second central system when you register the agent).

    o Log on to the physical host on which the database is currentlyrunning.

  • 5/22/2018 536954_OS Data in Cluster Envt.

    2/4

    16.09.2009 Page 2 of 4

    SAP Note 536954 - OS data in a cluster environment forOS07

    o Copy the SAPCCMSR agent from SAP Service Marketplace (-> Note

    209834). The CCMS agent must be located on a shared disk, so that

    the cluster administrator software can start the service later.

    o Generate a profile for the agent (sapccmsr.pfl) in the directory

    into which you have copied the sapccmsr agent. The profile must

    contain the following entries:

    SAPLOCALHOST=

    DIR_PERF=

  • 5/22/2018 536954_OS Data in Cluster Envt.

    3/4

    16.09.2009 Page 3 of 4

    SAP Note 536954 - OS data in a cluster environment forOS07

    The SAPCCM4X. service is generated during

    registration. During registration, select sapservice as the

    service user and "manual" as the start type.

    o Add the sapccm4x service SAPCCM4X. to the SAP

    group in the cluster administrator.

    o The current node has now been fully installed.

    Start the SAPCCM4X. service from the cluster

    administrator.

    o To be able to start the SAPCCM4X. service on the

    second node during a failover, you must still install the service

    there using:

    ntscmgr install SAPCCM4X. -b -p "-Service pf="

    Header Data

    Release Status: Released for Customer

    Released on: 12.09.2006 13:34:11

    Master Language: German

    Priority: Correction with medium priority

    Category: Program error

    Primary Component: BC-CCM-MON Monitoring

    Valid Releases

    Software Component Release From

    Release

    To

    Release

    and

    Subsequent

    SAP_BASIS 46 46B 46D X

    SAP_BASIS 60 610 640

    SAP_BASIS 70 700 700

    Support Packages

    Support Packages Release Package Name

    SAP_BASIS 46B SAPKB46B54

    SAP_BASIS 46C SAPKB46C45

    SAP_BASIS 46D SAPKB46D34

    SAP_BASIS 610 SAPKB61036

    SAP_BASIS 620 SAPKB62027

    Related Notes

  • 5/22/2018 536954_OS Data in Cluster Envt.

    4/4

    16.09.2009 Page 4 of 4

    SAP Note 536954 - OS data in a cluster environment forOS07

    Number Short Text

    657999 Installing a Standalone Gateway in an MSCS Environment

    584136 CCMS agents and kernels: Patches 2003 (composite note)

    209834 CCMS agent technology (composite SAP Note)

    Attributes

    Attribute Value

    Freigabezeitpunkt

    2006091213363

    SP Patch Level

    Software Component Version Support Package SP Patch

    Level

    SAP KERNEL 7.00 32-BIT SP137 000137

    SAP KERNEL 7.00 32-BIT UNICODE SP137 000137

    SAP KERNEL 7.00 64-BIT SP137 000137

    SAP KERNEL 7.00 64-BIT UNICODE SP137 000137

    SAP KERNEL 4.6D 32-BIT SP2356 002356

    SAP KERNEL 4.6D 64-BIT SP2356 002356

    SAP KERNEL 4.6D 64-BIT SP2364 002364

    SAP KERNEL 4.6D_EXT 32-BIT SP2356 002356

    SAP KERNEL 4.6D_EXT 32-BIT SP2364 002364

    SAP KERNEL 4.6D_EXT 64-BIT SP2356 002356

    SAP KERNEL 4.6D_EXT 64-BIT SP2357 002357

    SAP KERNEL 4.6D_EXT 64-BIT SP2364 002364