Rally - On-premises: Database hostname error when migrating to v2.0
search cancel

Rally - On-premises: Database hostname error when migrating to v2.0

book

Article ID: 129994

calendar_today

Updated On:

Products

CA Agile Central On Premise (Rally) CA Agile Central SaaS (Rally)

Issue/Introduction

During the database migration process, the error "Could not resolve hostname" is seen and the migration fails
[[email protected] ~]$ caac migration /tmp/directory-2019-03-25-02-00-05-dp.tgz
Warning: This will migrate data from version 2018.1 backup, and cannot be used if the backup is from any other version. [Y/N] Y
Migration confirmed. Input was Y .
Mon Mar 25 19:20:12 2019: Moving backup 2018.1 file - to /tmp/directory-2019-03-25-02-00-05-dp.tgz inside a container.
Mon Mar 25 19:20:19 2019: Start extracting directory-2019-03-25-02-00-05-dp.tgz.
Mon Mar 25 19:20:19 2019: tmp/directory-2019-03-25-02-00-05-dp.dmp
Mon Mar 25 19:21:08 2019: opt/RallyOnPrem/lib/onprem-lib.conf
Mon Mar 25 19:21:08 2019: opt/RallyOnPrem/web/var/www/html/announcements.html
Mon Mar 25 19:21:08 2019: Archive was extracted, continue...
Mon Mar 25 19:21:08 2019: 2018.1 dump (/tmp/tmp/directory-2019-03-25-02-00-05-dp.dmp) is present, continue...
Mon Mar 25 19:21:08 2019: DUMP_STRING = "SYSTEM"."SYS_EXPORT_SCHEMA_02" x86_64/Linux 2.4.xx f4wp1 12.02.00.01.00 001:001:000001:000001 HDR>T<? u80+;ts . Continue.
Mon Mar 25 19:21:08 2019: Dump file is from 2018.1 on-prem version. Oracle v.12.02.00.01.00. Continue.
Mon Mar 25 19:21:15 2019: === Starting restore DB process.
Mon Mar 25 19:21:15 2019: Have DB host '<database_hostname>'
Mon Mar 25 19:21:15 2019: Copying restore script to Oracle VM...
Mon Mar 25 19:21:20 2019: ssh: Could not resolve hostname <database_hostname>: Try again
Mon Mar 25 19:21:20 2019: lost connection

 

Environment

Release:
Component: ACPREM

Resolution

This is caused by the import process not being able to resolve the hostname of the database server.

There are two resolutions
  1. Include the hostname of the server in the /etc/hosts file.  Be sure to include long and short names.
  2. Update the database connection string in the dashboard so that it points to a hostname that the server is able to resolve, or use the IP address of the database server.