DPA从DPA 10.0.352升级到DPA 11.0.373

1: 解压安装文件SolarWinds-DPA-11.0.373-64bit.tar.gz

[root@lnxmonitor tmp]# tar -xzvf SolarWinds-DPA-11.0.373-64bit.tar.gz 
DPAAdministratorGuide_11.0_RC.pdf
dpa_11_0_373_x64_installer/
dpa_11_0_373_x64_installer/dpa_11_0_373_x64_installer.sh
dpa_11_0_373_x64_installer/install.txt
dpa_11_0_373_x64_installer/readme.txt

 

2: 查看解压目录下的readme.txt,里面有升级DPA的处理步骤。

UPGRADE INSTRUCTIONS
---------------------------------------------------------------------------
 
Prerequisite: System has an existing installation.
 
1. Install the new version of SolarWinds DPA on your existing server.
 
2. Disable cron jobs set up for SolarWinds DPA.
 
3. Run the shutdown.sh command from the old installation directory.
 
4. Locate the directory created when you installed the new version:
    /home/dpa_10_1_xxx       <= old installation home (may be ignite_8_x_xxx or dpa_9_x_xxx)
    /home/dpa_10_2_xxx       <= new SolarWinds DPA home
 
5. Copy or move these directories from the old to the new installation directory:
 
    WARNING: Do not copy hotfix files.
 
    cp -fr <OLD_home>/iwc/tomcat/ignite_config/* <NEW_home>/iwc/tomcat/ignite_config/
    cp -fr <OLD_home>/iwc/tomcat/logs/* <NEW_home>/iwc/tomcat/logs/
    mv <OLD_home>/iwc/tomcat/licensing <NEW_home>/iwc/tomcat/
 
6. If you are:
    - using LDAPS,
    - using SSL, or
    - changed the default SolarWinds DPA ports,
 
    then also complete the following tasks:
 
    a. Copy the keystore to the new installation:
 
        cp -fr <OLD_home>/iwc/tomcat/conf/.keystore  <NEW_home>/iwc/tomcat/conf/
 
    b. Edit <NEW_home>/iwc/tomcat/ignite_config/idc/system.properties file as follows:
 
       If the "javax.net.ssl.trustStore" entry is present, make sure it refers
       to a key store file inside the new DPA installation directory structure
       if possible.
 
       If the "com.confio.security.trustStore" entry is present, make sure it
       refers to a trust store file inside the new DPA installation directory
       structure if possible.
       If the referenced trust store file is in the new DPA installation
       directory structure, make sure the path is relative to the
       <NEW_home>/iwc/tomcat directory. For example, the absolute path
       "/home/user/dpa_10_2_xxx/iwc/tomcat/conf/.keystore" should be represented
       as "conf/.keystore" in the "com.confio.security.trustStore" entry.
 
    c. If you changed default port values or if you are using SSL on DPA 9.1.x or
       earlier, open server.xml from the old and the new installation
       directories.
 
    d. Copy over the appropriate values. Make sure that ports on the HTTP and
       HTTPS connector do not conflict. The files are located at:
 
        - <OLD_home>/iwc/tomcat/conf/server.xml
        - <NEW_home>/iwc/tomcat/conf/server.xml
 
7. If you disabled a cron job, update the path in those scripts to the new directory
   name and re-enable the job.
 
8. The upgrade is complete. The next step is to start SolarWinds DPA (see
   the section on Startup Instructions).

 

3:授予dpa_11_0_373_x64_installer.sh执行权限,并执行脚本。

#chmod +x dpa_11_0_373_x64_installer.sh
 
#./dpa_11_0_373_x64_installer.sh

 

3: 禁用DPA相关的crontab作业。停止DPA服务(版本为DPA 10.0.352),

[root@lnxmonitor dpa_10_0_352]# ./shutdown.sh 
**************************************************************************
*
*  If this script fails you can manually stop the program by 
*  doing the following steps: 
*
*  1) Set the JAVA_HOME environment variable to your Java installation.
*  2) Add <JAVA_HOME>/bin to your PATH environment variable.
*  3) Go to the <DPA Home>/tomcat/bin directory. 
*  4) Run ./shutdown.sh 
*
*
***************************************************************************
Catalog exists...
Found java 1.6 or 1.7
JAVA HOME IS SET TO /home/solarwinds/dpa_10_0_352/iwc/jre_linux
PATH IS SET TO /home/solarwinds/dpa_10_0_352/iwc/jre_linux/bin:/usr/java/jdk1.7.0_25/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
IBM Jvm Is Set To NO
Setting the -server option for JVM
JAVA_OPTS is  -server -Xss264k -Xms256m -Xmx1024m -XX:MaxPermSize=192m -Dcom.sun.management.jmxremote -Djava.net.preferIPv4Stack=true -Dnet.sf.ehcache.skipUpdateCheck=true
Using CATALINA_BASE:   /home/solarwinds/dpa_10_0_352/iwc/tomcat
Using CATALINA_HOME:   /home/solarwinds/dpa_10_0_352/iwc/tomcat
Using CATALINA_TMPDIR: /home/solarwinds/dpa_10_0_352/iwc/tomcat/temp
Using JRE_HOME:        /home/solarwinds/dpa_10_0_352/iwc/jre_linux
Using CLASSPATH:       /home/solarwinds/dpa_10_0_352/iwc/tomcat/bin/bootstrap.jar:/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config
**************************************************************************
*
*  DPA is shutting down. 
*
***************************************************************************
Exiting script after webserver stopped.

 

4:拷贝相关文件,例如配置文件、日志文件、License文件

 

cp -fr <OLD_home>/iwc/tomcat/ignite_config/* <NEW_home>/iwc/tomcat/ignite_config/

cp -fr <OLD_home>/iwc/tomcat/logs/* <NEW_home>/iwc/tomcat/logs/

mv <OLD_home>/iwc/tomcat/licensing <NEW_home>/iwc/tomcat/

 

 
root@lnxmonitor solarwinds]# cp -fr /home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/* /home/solarwinds/dpa_11_0_373/iwc/tomcat/ignite_config/
[root@lnxmonitor solarwinds]# cp -fr /home/solarwinds/dpa_10_0_352/iwc/tomcat/logs/*  /home/solarwinds/dpa_11_0_373/iwc/tomcat/logs/
[root@lnxmonitor solarwinds]# mv /home/solarwinds/dpa_10_0_352/iwc/tomcat/licensing /home/solarwinds/dpa_11_0_373/iwc/tomcat/
[root@lnxmonitor solarwinds]# ls
dpa_10_0_352  dpa_11_0_373  dpa_9_1_85
[root@lnxmonitor solarwinds]# cd dpa_11_0_373/
[root@lnxmonitor dpa_11_0_373]# ls
iwc  license.txt  shutdown.sh  SolarWindsEula.rtf  startup.sh

 

5:如果你设置了SSL或修改了默认端口等,那么参考上面的第六条说明进行配置。此处由于不需要设置,那么略过。

 

6:启动DPA服务,访问页面,检查升级是否成功!

 
[root@lnxmonitor dpa_11_0_373]# ./startup.sh 
**************************************************************************
*
*  If this script fails you can manually start the program by 
*  doing the following steps: 
*
*  1) Set the JAVA_HOME environment variable to your Java installation.
*  2) Add <JAVA_HOME>/bin to your PATH environment variable.
*  3) Go to the <DPA Home>/tomcat/bin directory. 
*  4) Run ./startup.sh 
*  5) Bring up the link (http://machine Name:8123 
*     or http://machine IP:8123) in your browser.
*
*
***************************************************************************
Catalog exists...
Found java 1.8
JAVA HOME IS SET TO /home/solarwinds/dpa_11_0_373/iwc/jre_linux
PATH IS SET TO /home/solarwinds/dpa_11_0_373/iwc/jre_linux/bin:/usr/java/jdk1.7.0_25/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
The server port is 8127
The HTTP port is 8123
The HTTPS port is 8124
DPA is not running.
The port 8123 is open
The port 8124 is open
The port 8127 is open
Starting DPA
STACK_SIZE OVERRIDE = 
MIN_HEAP_MEMORY OVERRIDE = 
MAX_HEAP_MEMORY OVERRIDE = 
ADDITIONAL_JVM_OPTION = 
IBM Jvm Is Set To NO
Setting the -server option for JVM
JAVA_OPTS is  -server -Xss300k -Xms256m -Xmx1024m -Djava.net.preferIPv4Stack=true -Dnet.sf.ehcache.skipUpdateCheck=true
Tomcat started.
 
Waiting on initialization...please be patient
 
**************************************************************************
*
*  DPA has been launched, wait one minute then bring up 
*  one of the following links in your browser:
*
*  http://<Machine Name>:8123 or http://<Machine IP>:8123
*  https://<Machine Name>:8124 or https://<Machine IP>:8124
*
*  If the link does not work, check <iwc_dir>/tomcat/logs
*  and make sure a firewall is not running on this machine.
*
***************************************************************************
Exiting script after webserver launched.

 

如果监控了较多的数据库服务器,则打开DPA时有可能需要等待一小段时间,如下所示。另外,如果一个License Key被拆分到两个DPA服务器,则启动DPA的时候,需要激活License,如果你服务器可以访问外网,那么就可以在线激活License,如果不能访问外网,只能使用离线激活方式。如果不激活License,则Upgrade则会受阻,无法继续进行!

 

参考资料:

https://support.solarwinds.com/Success_Center/Database_Performance_Analyzer_(DPA)/DPA_Admin_Guide/060_Upgrade_DPA/020_Upgrade_DPA_on_Linux

 

时间: 2024-09-10 10:23:03

DPA从DPA 10.0.352升级到DPA 11.0.373的相关文章

枫树浏览器v1.6.2.0 for Windows(基于Chromium 11.0.696.77)

枫树浏览器是基于谷歌http://www.aliyun.com/zixun/aggregation/33824.html">Chrome浏览器的极速双核安全浏览器.具备谷歌浏览器所有特性的同时,枫树浏览器还增加了隐私数据保护.鼠标手势.IE标签.广告过滤.老板键.代理设置.常用下载工具支持.超级拖拽等增强功能.枫树浏览器完全免费,您可以任意使用. 枫树浏览器V1.6.2.0 for Windows (基于Chromium 11.0.696.77)更新日志:a [修正] IE模式右键菜单项&

oracle9i从9.2.0.4升级到9.2.0.6(64位)报ORA-00600: [19004]的解决方法

在升级山东PDA数据库从oracle 9.2.0.4-64位升级到9.2.0.6-64位报ORA-00600: [19004]在网上找到正解,转载在此供以后参考.ORA-00600: 内部错误代码, 参数: [19004], [], [], [], [], [] --ORACLE 10.1 OR 10.2中所有平台都存在该问题. <问题现像> 在进行多表关联复杂查询时出现 ORA-00600: 内部错误代码, 参数: [19004], [], [], [], [], [], [], [] 错误

支付宝9.0怎么升级 iphone支付宝9.0升级方法

1.我们在iphone桌面点击appstore 然后我们点击"更新"如果有支付宝,你会看到有 支付宝9.0更新了,点击后面的"更新",如下图所示. 2.好了更新好了,就会弹出提示了,现在我们只要点击好即可,如下图所示. 3.在这个过程中我们只要一直等待更新完成就可以了. 更新完成后,你的支付宝9.0就升级成功了,之后我们就可以体验新功能了. 好了上面是一个支付宝8与支付9的图对比了,希望对各位有帮助了.

PATCHSET 10.1.0.3&amp;amp;amp;9.2.0.5

patchset  3761843   for   oracle 10.1.0.3  升级10.1.0.2 到10.1.0.3   patchset  3501955   for   oracle  9.2.0.4  升级到 9.2.0.5  不过升级后还是要打和alert#68 相关的那个PATCH 3811906  这样才完整文件名称为10.1.0.3  p3761843_10103_LINUX.zip  551M9.2.0.5   p3501955_9205_LINUX.zip   313

DPA 9.1.85 升级到DPA 10.0.352流程

 SolarWinds DPA的升级其实是一件非常简单的事情,这里介绍一下从DPA 9.1.95升级到 DPA 10.0.352版本的流程.为什么要升级呢? DPA给用户发的邮件已经写的非常清楚了(如下所示),DPA 10.0这个版本已开始支持MySQL了,另外它解决了一些Bug,在性能上有所改进.提升. Our records indicate that you might have Database Performance Analyzer (DPA) 9.0 installed and l

Linux下Oracle 10.2.0.1升级到10.2.0.4总结

最近部署测试环境时,将测试环境ORACLE数据库从10.2.0.1升级到了10.2.0.4,顺便整理记录一下升级过程. 实验环境: 操作系统:Oracle Linux Server release 5.7 数据库:Oracle 10.2.0.1 下载解压补丁包 1: [oracle@DB-Server tmp]$ unzip p6810189_10204_Linux-x86-64.zip 2:  3: [oracle@DB-Server Disk1]$ ls 4: 10204_buglist.h

Oracle RAC 10.2.0.1 升级 10.2.0.5

Oracle RAC 10.2.0.1 升级  10.2.0.5 1.crs和rdbms的升级包是一个,升级时先升级crs,再升级rdbms,最后升级库2.最权威的文档在,10205的补丁中,有个readme. 一.停止数据库相关进程 分别在两台机器上停止数据库 sqlplus "/as sysdba"; sql>shutdown immediate lsnrctl stop 也可以用srvctl工具在一个节点上完成 $ORA_CRS_HOME/bin/srvctl stop s

Oracle 10.2.0.1 升级到 10.2.0.4

--********************************* -- Oracle 10.2.0.1 升级到 10.2.0.4 --*********************************     数据库升级并不难,只要遵循其步骤,一般问题不大.但是升级失败的情况也是屡见不鲜,尤其是生产数据库的升级,搞不定的时候甚至要创建SR.   下面描述基于Linux(Oracle Linux 5.4/2.6.18-164.el5PAE)平台下Oracle 10.2.0.1 升级到 10.

Windows 平台10.2.0.1 升级到10.2.0.4 报msvcr71.dll错误解决

Windows 平台10.2.0.1 升级到10.2.0.4 报msvcr71.dll错误解决    问题分析: 肯定是因为MSVCR71.dll文件占用所致. 故需要检查服务和进程是否完全正常关闭. 问题解决思路: 通过检查所有的Oracle服务是否关闭. 找到MSVCR71.dll被哪个进程所占用,将其停止. 参考如下: MSVCR71.DLL 更新时在使用 找到用该DLL的进程,具体方法如下: MSVCR71.DLL is in use during Oracle patch instal