Changing a hostname after installation of CA Directory and Ingres
search cancel

Changing a hostname after installation of CA Directory and Ingres

book

Article ID: 54908

calendar_today

Updated On:

Products

CA Directory CA Security Command Center CA Data Protection (DataMinder) CA User Activity Reporting

Issue/Introduction

Description:

It occasionally becomes necessary to change a machine hostname after Directory is installed. There are two components involved: CA Directory and Ingres.

On UNIX
You will need to do the following

  • Run command "dxserver stop all" as user dsa

  • Run command "ingstop" as user ingres

eTrust Directory:

  • Change the hostname in the Knowledge files in the config ($DXHOME/config/knowledge) - for each DSA that access that machine (including DSAs on remote machines that connect to the machine being renamed).

Ingres:

  • Change the hostname where it appears in $II_SYSTEM/ingres/files/config.dat

  • Run command "ingsetenv II_GCNxx_LCL_VNODE <new_hostname>" as user ingres. (NOTE: the "xx" in the command is the Ingres installation code. You can run "ingprenv" command to see what the value of II_INSTALLATION is set to.)

  • Remove all files in $II_SYSTEM/ingres/files/name except for iiname.all

  • Edit the hostname in all remote machines that connect to Ingres through Ingres/Net. (Only applicable if you have this setup)

You can now start Ingres and dxservers by doing the following

  • Run command "ingstart" as user ingres

  • Run command "dxserver start all" as user dsa

On WINDOWS
You will need to do the following as a user with Administrative rights

  • Run command "dxserver stop all"

  • Stop the "Ingres Intelligent Database [EI]" service from the windows service manager

eTrust Directory:

  • Change the hostname in the Knowledge files in the config (%DXHOME%\config\knowledge) - for each DSA that access that machine (including DSAs on remote machines that connect to the machine being renamed).

Ingres:

  • Change the hostname where it appears in %II_SYSTEM%\ingres\files\config.dat

  • Run command "ingsetenv II_GCNxx_LCL_VNODE <new_hostname>" . (NOTE: the "xx" in the command is the Ingres installation code.You can run "ingprenv" command to see what the value of II_INSTALLATION is set to.)

  • Remove all files in %II_SYSTEM%\ingres\files\name folder except for iiname.all

  • Edit the hostname in all remote machines that connect to Ingres through Ingres/Net. (Only applicable if you have this setup)

You can now start Ingres and dxservers by doing the following

  • Start the "Ingres Intelligent Database [EI]" service from the windows service manager

  • Run command "dxserver start all"

Solution:

On UNIX
You will need to do the following

  • Run command "dxserver stop all" as user dsa

  • Run command "ingstop" as user ingres

eTrust Directory:

  • Change the hostname in the Knowledge files in the config ($DXHOME/config/knowledge) - for each DSA that access that machine (including DSAs on remote machines that connect to the machine being renamed).

Ingres:

  • Change the hostname where it appears in $II_SYSTEM/ingres/files/config.dat

  • Run command "ingsetenv II_GCNxx_LCL_VNODE <new_hostname>" as user ingres. (NOTE: the "xx" in the command is the Ingres installation code. You can run "ingprenv" command to see what the value of II_INSTALLATION is set to.)

  • Remove all files in $II_SYSTEM/ingres/files/name except for iiname.all

  • Edit the hostname in all remote machines that connect to Ingres through Ingres/Net. (Only applicable if you have this setup)

You can now start Ingres and dxservers by doing the following

  • Run command "ingstart" as user ingres

  • Run command "dxserver start all" as user dsa

On WINDOWS
You will need to do the following as a user with Administrative rights

  • Run command "dxserver stop all"

  • Stop the "Ingres Intelligent Database [EI]" service from the windows service manager

eTrust Directory:

  • Change the hostname in the Knowledge files in the config (%DXHOME%\config\knowledge) - for each DSA that access that machine (including DSAs on remote machines that connect to the machine being renamed).

Ingres:

  • Change the hostname where it appears in %II_SYSTEM%\ingres\files\config.dat

  • Run command "ingsetenv II_GCNxx_LCL_VNODE <new_hostname>" . (NOTE: the "xx" in the command is the Ingres installation code.You can run "ingprenv" command to see what the value of II_INSTALLATION is set to.)

  • Remove all files in %II_SYSTEM%\ingres\files\name folder except for iiname.all

  • Edit the hostname in all remote machines that connect to Ingres through Ingres/Net. (Only applicable if you have this setup)

You can now start Ingres and dxservers by doing the following

  • Start the "Ingres Intelligent Database [EI]" service from the windows service manager

  • Run command "dxserver start all"


Environment

Release: ESPDIR99000-8.1-Extended Support Plus-for CA Directory
Component: