Tips & Tricks : Update of the MaxDB engine for EDW 5.0

Size: px

Start display at page:

Download "Tips & Tricks : Update of the MaxDB engine for EDW 5.0"

Rhoda Strickland
6 years ago
Views:

1 Tips & Tricks : Update of the MaxDB engine for EDW 5.0 Always read the stand alone part of this document to understand the upgrade process. Take care that a rollback is not possible (making a snapshot is recommended). Contents Why upgrading MaxDB engine?... 2 General things to be careful of... 3 Update MaxDB engine stand alone server... 4 Update MaxDB engine Load Balancing architecture... 5 Update MaxDB engine Cluster architecture... 6 Download links

2 Why upgrading MaxDB engine? In some cases, ITS can advice an upgrade of the MaxDB engine for EDW 5.0 (on Windows 2003 or 2008). For example, when running EDW 5.0 on Windows /64 bits with an antivirus software (e.g. Mcafee 8.5 and 8.7 or Trend Micro OfficeScan v10), you can face great performance issues: When opening the Esker administrator (MMC), it takes 1 or 2 minutes just to open an empty queue. The traces are full of long request warning. To fix this, an update of MaxDB from version (the one installed with EDW 5.0) to version is needed. Also, for specific database issues, SAP can advice this upgrade. 2

General things to be careful of On Windows 2008, when

administrator: Be sure to be logged with an administrator

administrator At the end of the MaxDB setup, we noticed on

3 General things to be careful of On Windows 2008, when launching a command prompt, be sure to do it as an administrator: Be sure to be logged with an administrator account Be sure to launch MAXDB setup file as an administrator At the end of the MaxDB setup, we noticed on Windows 2008 that there is a crash. This happens after the upgrade thus you can omit this crash. 3

4 Update MaxDB engine stand alone server Using Esker administrator (MMC), stop All Esker services (right click on Server node) Stop IIS (iisreset /stop) Using the services MMC (services.msc), stop LDAP service, Log & SNMP service and XServer service Using database manager, put the database offline Close all opened MMC and database softwares Using Process Explorer, be sure there is no handle on any file located in the MaxDB folder (look for handle with keyword sapdb for this). On windows 2008, if process rhs.exe is handling a file, it s normal and you don t have to take care of this Launch the MaxDB setup file (run the command x_cons EDP350 show version to determine if you need 32 or 64bits setup file). o Select that it s an upgrade o Server + client o Important Select: Install software + Upgrade of the existing database o Enter ESKDBADM credential and follow setup screens At the end of the MaxDB setup, we noticed on Windows 2008 that there is a crash. This happens after the upgrade thus you can omit this crash. Once setup is finished, restart IIS, Log &SNMP and the LDAP services. Also restart Xserver service (if needed) Then start Esker administrator (MMC) and browse the queues to be sure you can see elements and get their xml. Using Esker administrator (MMC), restart all services. 4

5 Update MaxDB engine Load Balancing architecture On each slave server, stop everything: o IIS o Using Esker administrator (MMC): all Esker services o Using services MMC: LDAP and Log&SNMP On the master server, stop everything: o IIS o Using Esker administrator (MMC): all Esker services o Using services MMC: XServer, LDAP and Log&SNMP o Using database manager, put the database offline On the master server: Using Process Explorer, be sure there is no handle on any file located in the MaxDB folder (look for handle with keyword sapdb for this). On windows 2008, if process rhs.exe is handling a file, it s normal and you don t have to take care of this On the master server: close all opened MMC and database softwares On the master server: Launch the MaxDB setup file o Select that it s an upgrade o Server + client o Important Select: Install software + Upgrade of the existing database o Enter ESKDBADM credential and follow setup screens At the end of the MaxDB setup, we noticed on Windows 2008 that there is a crash. This happens after the upgrade thus you can omit this crash. On the master server starts XServer service (if needed) On the master server: restart IIS, the Log &SNMP and LDAP services. Then start Esker administrator (MMC) and browse the queues to be sure you can see elements and get their xml. On the master server: Using Esker administrator (MMC), restart all services. On each slave server: restart IIS, the Log &SNMP and LDAP services. Then start Esker administrator (MMC) and browse the queues to be sure you can see elements and get their xml. On each slave server: Using Esker administrator (MMC), restart all services. 5

6 Update MaxDB engine Cluster architecture Node 1 is referring the Active node, i.e. the node that holds the shared drive and thus sees it as a local drive. Node 2 is referring the passive node. On both nodes, stop IIS. Using the cluster administrator, in the Esker Group, take offline all resources except o Disk resources o IP resources o DTC resources o File share resources o Network name resources Make sure Node 1 and Node 2 group are offline (should be as the group are also resources in the Esker Group) On node 1: Using database manager, check that database if well offline. On node 1: Using Process Explorer, be sure there is no handle on any file located in the MaxDB folder (look for handle with keyword sapdb for this). On windows 2008, if process rhs.exe is handling a file, it s normal and you don t have to take care of this On node 1: Launch the MaxDB setup file (run the command x_cons EDP350 show version to determine if you need 32 or 64bits setup file). o Select that it s an upgrade o Server + client o Important Select: Install software + Upgrade of the existing database o Enter ESKDBADM credential and follow setup screens At the end of the MaxDB setup, we noticed on Windows 2008 that there is a crash. This happens after the upgrade thus you can omit this crash. 6

7 On node 1: using services MMC (services.msc), check that both services MAXDB: EDP350 and XServer are stop and set to manual. If this is not the case stop them and/or modify them. If the Xserver service has been removed : o Run the following command : sc \\localhost create xserver binpath= <local install path>\sapdb\indep_prog\pgm\serv.exe ( /!\ There is a space after binpath=) On node 1: During database registering "dbmcli -R "H:\Esker\sapdb\depend" inst_reg -k M760603", an additional resource will appear in the failover cluster manager in the Esker group (.M or.m760610), this resource can be removed from the failover cluster manager, but the associated service in the services.msc must not be changed. On node 1: Use specific Serv.exe for cluster architecture o Backup "<INDEP_PROG_DIR_On_LOCALDisk>\pgm\serv.exe e.g. C:\Program Files\sapdb\indep_prog\pgm o Take "<DEPEND_DIR_ On_SHAREDDisk>\Cluster\serv_clu.exe e.g. H:\esker\sapdb\depend\cluster o Copy it to "<INDEP_PROG_DIR_On_LOCALDisk>\pgm\ rename it to serv.exe Move the group ESKERGROUP to node 2 On node 2, using Process Explorer, check again that no process lock MaxDB files and launch the MaxDB setup. On node 2: Launch the MaxDB setup file o Select that it s an upgrade o Server + client o Important Select: Install software + Upgrade of the existing database o Enter ESKDBADM credential and follow setup screens At the end of the MaxDB setup, we noticed on Windows 2008 that there is a crash. This happens after the upgrade thus you can omit this crash. On node 2: Use specific Serv.exe for cluster architecture o Backup "<INDEP_PROG_DIR_On_LOCALDisk>\pgm\serv.exe e.g. C:\Program Files\sapdb\indep_prog\pgm o Take "<DEPEND_DIR_ On_SHAREDDisk>\Cluster\serv_clu.exe e.g. H:\esker\sapdb\depend\cluster 7

$o Copy it to "<INDEP_PROG_DIR_On_LOCALDisk>\pgm\ rename it to serv.exe On node 2: Use specific Service.exe for cluster architecture o Backup "<DEPEND_DIR_ On_SHAREDDisk>\pgm\service.exe e.g. H:\esker\sapdb\depend\pgm o Take "<DEPEND_DIR_ On_SHAREDDisk>\Cluster\ service_clu.$

8 o Copy it to "<INDEP_PROG_DIR_On_LOCALDisk>\pgm\ rename it to serv.exe On node 2: Use specific Service.exe for cluster architecture o Backup "<DEPEND_DIR_ On_SHAREDDisk>\pgm\service.exe e.g. H:\esker\sapdb\depend\pgm o Take "<DEPEND_DIR_ On_SHAREDDisk>\Cluster\ service_clu.exe e.g. H:\esker\sapdb\depend\cluster o Copy it to "<DEPEND_DIR_ On_SHAREDDisk>\pgm\ rename it to service.exe On node 2: Use specific Dbmsrv.exe for cluster architecture o Backup "<DEPEND_DIR_ On_SHAREDDisk>\pgm\dbmsrv.exe e.g. H:\esker\sapdb\depend\pgm o Take "<DEPEND_DIR_ On_SHAREDDisk>\Cluster\dbmsrv_clu.exe e.g. H:\esker\sapdb\depend\cluster o Copy it to "<DEPEND_DIR_ On_SHAREDDisk>\pgm\ rename it to dbmsrv.exe Using a command prompt, register database (ONLY ON NODE 2) In the last command, use the proper path for <DEPEND_DIR_ On_SHAREDDisk> 8

9 On 64 bits OS ONLY: Using a command prompt, register ODBC driver (ONLY ON NODE 2) "<EDPDIR>\Program\ODBC\odbcreg.exe" "MaxDB (Unicode)" -i -p "<EDPDIR>\Program\ODBC" - d sqlod32w.dll Be careful, the command is case sensitive, also register sqlod32w.dll and NOT sqlod32.dll ( w for Unicode!) On node 2: using services MMC (services.msc, check that both services MAXDB: EDP350 and XServer are stop and set to manual. If this is not the case stop them and/or modify them) Start IIS on both nodes Using Cluster administrator put online all the resources and checks that all is working fine. Using Cluster administrator, move the owner of the Esker Group and then check again that both nodes are working ok (Esker administrator (MMC), processing). 9

10 Download links Please get Process Explorer from Sysinternal web site The MAXDB upgrade setup is retrievable here: (run the command x_cons EDP350 show version to determine if you need 32 or 64bits setup file) 64 bits version: 32 bits version: 10

Resolution: The DataChannel servlet no longer stops working, regardless of the state of the DataChannel extension.

Resolution: The DataChannel servlet no longer stops working, regardless of the state of the DataChannel extension. Hotfix version 1 Build 4.5.3.1026 McAfee epolicy Orchestrator 4.5 This document is a supplement to the McAfee epolicy Orchestrator 4.5 Patch 3 Release Notes in the release package, and details fixes included