Upgrade DPA 9.1.85 to DPA 10.0.352, 9.1.8510.0.352

Upgrade DPA 9.1.85 to DPA 10.0.352, 9.1.8510.0.352

The upgrade of SolarWinds DPA is actually very simple. Here we will introduce the process of upgrading from DPA 9.1.95 to DPA 10.0.352. Why upgrade? The emails sent by DPA to users have been clearly written (as shown below). DPA 10.0 has started to support MySQL, and it has fixed some bugs, performance improvement.

Our records indicate that you might haveDatabase Performance Analyzer (DPA) 9.0Installed and licensed. If you have upgraded all your DPA servers to a later version (v9.1, 9.2, or 10.0), please ignore this email.

While SolarWinds transitioned Confio MERs to a new licensing model in August 2014, it delayed the enforcement of core licenses for Oracle, DB2 and Sybase until November 10,201 5. if you are using DPA 9.0 with core licenses for Oracle, DB2 or Sybase, you shoshould upgrade all your DPA servers to the latest version available inCustomer Portal Before November 10,201 5. This will ensure that DPA can be configured to monitor all the databases that are licensed.

What will happen if I don't upgrade?

DPA will start technically enforcing licenses for Oracle, DB2 and Sybase on November 10,201 5. If you are under your license limit, DPA will continue to collect data from all licensed database instances.If you have exceeded your licensing limit, DPA will unlicense all registered databases and stop monitoring them, and you will have to select which databases you want to monitor up to your licensing limit.

How many licenses will I have once I upgrade to a later version?

• If you purchased Oracle, DB2 or Sybase licenses before August 1, 2014 and have not purchased more licenses since that time, your licenses were core-based. core-based licenses have been converted to instances at a ratio, and the new license keys in your Customer Portal reflect this converted amount.
• If you initially purchased or bought additional licenses after August 1, 2014, your licenses are instance-based. The new license keys in your Customer Portal will reflect the purchased amount.

What shoshould I do?

We recommend that you upgrade to the latest version of DPA available in yourCustomer PortalAnd activate your license keysBefore November 10,201 5. This will correctly align product enforcement with the licenses you purchased.

Are there other benefits to upgrading?

Yes, DPA has made a lot of progress since 9.0 was released:

• 9.1 added support for Amazon RDS databases, excluding SQL Statements from trend graphs and event annotations
• 9.2 added integration with Orion
• 10.0 added MySQL support
• Bug fixes, security updates, and speed improvements

If you have any questions or concerns, pleaseContact customer serviceAt your earliest convenience. We apologize for the inconvenience and look forward to helping you quickly through this final transition of DPA licensing.

 

Upgrade procedure:

 

1: First, you must go to the official website to download the installation file through your account. It provides two versions: Windows and Linux. I downloaded the solar Installation File solarwinds-dpa-v10.0.352-sr1--linux-unix.tar.gz.

2: Decompress the installation package of solarwinds-dpa-v10.0.352-sr1--linux-unix.tar.gz, and view readme.txt. You will see the following upgrade instructions. Before strongly recommended UPGRADE, check upgrade instructions in reade.txt.

3: We recommend that you adjust the steps in the Guidance Document. First, stop the DPA service and disable any cron jobs about SolarWinds DPA.

[root@lnxmonitor ~]# cd /home/solarwinds/dpa_9_1_85/

[root@lnxmonitor dpa_9_1_85]# ls

iwc  license.txt  shutdown.sh  SolarWindsEula.rtf  startup.sh

[root@lnxmonitor dpa_9_1_85]# ./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_9_1_85/iwc/jre_linux

PATH IS SET TO /home/solarwinds/dpa_9_1_85/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 -Xss256k -Xms256m -Xmx1024m -Djsse.enableCBCProtection=false -XX:MaxPermSize=192m -Dcom.sun.management.jmxremote -Djava.net.preferIPv4Stack=true -Dnet.sf.ehcache.skipUpdateCheck=true

Using CATALINA_BASE:   /home/solarwinds/dpa_9_1_85/iwc/tomcat

Using CATALINA_HOME:   /home/solarwinds/dpa_9_1_85/iwc/tomcat

Using CATALINA_TMPDIR: /home/solarwinds/dpa_9_1_85/iwc/tomcat/temp

Using JRE_HOME:        /home/solarwinds/dpa_9_1_85/iwc/jre_linux

Using CLASSPATH:       /home/solarwinds/dpa_9_1_85/iwc/tomcat/bin/bootstrap.jar:/home/solarwinds/dpa_9_1_85/iwc/tomcat/ignite_config

**************************************************************************

*

*  DPA is shutting down. 

*

***************************************************************************

Exiting script after webserver stopped.

[root@lnxmonitor dpa_9_1_85]# 

4. Install the new DPA application.

./Dpa_10_0_352_x64_installer.sh the installation process is as follows:

5: Copy/Move some files or folders to the new installation directory.

[root@lnxmonitor ~]# 

[root@lnxmonitor ~]# cd /home/solarwinds/

[root@lnxmonitor solarwinds]# ls

dpa_10_0_352  dpa_10_0_352_x64_installer  dpa_9_1_85

[root@lnxmonitor solarwinds]# cp -fr /home/solarwinds/dpa_9_1_85/iwc/tomcat/ignite_config/* /home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/idc/system.properties'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/idc/repo.properties'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/idc/server.properties'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/properties/sqlformat.properties'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/properties/connection.pool.properties'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/properties/mail.properties'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/analysis/analysis.properties'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/analysis/wait_parameters.xml'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/readme.txt'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/iwc/security/sqlauth.xml'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/oracle_config/name_config_readme.txt'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/registration/massreg_sql_server_template.csv'? y

cp: overwrite `/home/solarwinds/dpa_10_0_352/iwc/tomcat/ignite_config/registration/massreg_oracle_template.csv'? y

[root@lnxmonitor solarwinds]# cp -rf /home/solarwinds/dpa_9_1_85/iwc/tomcat/logs/* /home/solarwinds/dpa_10_0_352/iwc/tomcat/logs/ 

[root@lnxmonitor solarwinds]# mv /home/solarwinds/dpa_9_1_85/iwc/tomcat/licensing/ /home/solarwinds/dpa_10_0_352/iwc/tomcat/

If you use SSL or LDPAS, or modify the default DPA port number. You must refer to the document to copy the following configuration documents. Because the upgrade cases here do not involve this, they are skipped (in fact, it is also very simple) Here. For more information, see.

If you are:

   - using LDAPS, or 

   - using SSL, or

   - have 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. If you changed default port values or if you are using SSL on 9.1.x or

      bellow, open server.xml from both the old and the new installation

      directories and then manually copy over the appropriate values. Make

      sure that ports on the HTTP and HTTPS connector are not conflicting.

      The files are located at:

          - <OLD_home>/iwc/tomcat/conf/server.xml

          - <NEW_home>/iwc/tomcat/conf/server.xml

6. Delete the installation file.

[root@lnxmonitor solarwinds]# rm SolarWinds-DPA-v10.0.352-SR1--Linux-Unix.tar.gz 

rm: remove regular file `SolarWinds-DPA-v10.0.352-SR1--Linux-Unix.tar.gz'? y

[root@lnxmonitor solarwinds]# rm -rf dpa_10_0_352_x64_installer/

7: Start the DPA service.

./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.

**************************************************************************

atalog exists...

ound java 1.6 or 1.7

AVA HOME IS SET TO /home/solarwinds/dpa_10_0_352/iwc/jre_linux

ATH 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

he server port is 8127

he HTTP port is 8123

he HTTPS port is 8124

PA is not running.

he port 8123 is open

he port 8124 is open

he port 8127 is open

tarting DPA

TACK_SIZE OVERRIDE = 

IN_HEAP_MEMORY OVERRIDE = 

AX_HEAP_MEMORY OVERRIDE = 

DDITIONAL_JVM_OPTION = 

BM Jvm Is Set To NO

etting the -server option for JVM

AVA_OPTS is  -server -Xss264k -Xms256m -Xmx1024m -XX:MaxPermSize=192m -Dcom.sun.management.jmxremote -Djava.net.preferIPv4Stack=true -Dnet.sf.ehcache.skipUpdateCheck=true

aiting 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.

**************************************************************************

xiting script after webserver launched.

Then, when logging on to the system from the browser, you may need to wait a moment, and DPA will also upgrade some scripts in the database. Generally, you will see the following: the time is short. After the upgrade is complete, it will jump to the logon page. So far, the DPA upgrade process has been completed.