Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia

Upgrading SSH Tectia Manager (Oracle)

Starting from version 2.3, SSH Tectia Manager no longer uses Openlink ODBC drivers when connecting to an Oracle server. Instead, an internal Oracle client is used to connect to the Oracle server. When upgrading an existing installation with Openlink ODBC driver to SSH Tectia Manager 2.3 and later, no special actions are needed. The SSH Tectia Manager will switch from Openlink to internal Oracle driver automatically and when the upgrade has been successfully completed, Openlink software is no longer needed and can be uninstalled.

To upgrade SSH Tectia Manager that is using the Oracle database, follow the instructions below:

  1. Stop the Management Server:

    # /etc/init.d/ssh-mgmt-server stop
  2. Upgrade the Management Database.

  3. Upgrade the Management Server.

    1. On Linux: To upgrade from a previous version of the Management Server, run the following command as root:

      # rpm --upgrade ssh-mgmt-server-<v>-linux-x86.rpm

      In the command, <v> is the current release version of the Management Server (for example Restart the server:

      # /etc/init.d/ssh-mgmt-server restart

    2. On Solaris: To upgrade the Management Server, copy the package to the hard disk to a temporary directory of your choice, uncompress the package, and run the upgrade. Run the following commands as root:

      # cp /cdrom/install/solaris/ssh-mgmt-server-<v>-sparc-solaris8-9.pkg.Z .
      # uncompress ssh-mgmt-server-<v>-solaris-8-10-sparc.pkg.Z
      # pkgrm SSHmgmtse
       ... answer "yes" to any questions displayed
      # pkgadd -d ssh-mgmt-server-<v>-solaris-8-10-sparc.pkg all
       ... answer "yes" to any questions displayed

      In the commands, <v> is the current release version of the Management Server (for example Restart the server:

      # /etc/init.d/ssh-mgmt-server restart

      The Management Server installation package includes the installation packages for the Management Agents for all supported platforms. There is no need to import them separately to the Management Server machine. You should be able to login to the administration interface in a moment.

  4. In case of problems, check the syslog for possible error messages. An environment that is running correctly should always have the Management Database process and the Management Server processes (ssh-mgmt- server and ssh-mgmt-engine) running. Note specifically that all the modules should be started using the startup script provided, since running the binaries directly will cause the paths and environment to be set incorrectly.

  5. Upgrade the Management Agents to new versions remotely at Software → Management Agent.

  6. Check that all hosts are correctly upgraded to the new version at Reports → Standard reports → Tectia management system reports → Tectia Management Agent versions.


Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more