DSM/SCM User's Guide

Troubleshooting
DSM/SCM User’s Guide — 529846-014
13 - 11
Software Configuration Troubleshooting
INITENV then runs STARTSCM. If TCP/IP and its LISTNER process are not running,
STARTSCM indicates that you must start TCP/IP and its LISTNER process before
using the Planner Interface.
Software Configuration Troubleshooting
Migration Troubleshooting
Problem Recovery
A No Software for Target
warning window appears.
The
site ID in the target profile might not match the site ID on
the RVU.
1. Check the site ID. (
Checking the Site ID on page 5-3)
2. Check that the correct site ID is in the target
system
profile.
A failure occurs in
ST
ARTSCM when you try
to
run DSM/SCM from a
TSV other than the original
ZDSMSCM TSV.
The startup program cannot locate INITSTAT. If you send the
TSV to another disk, information created in the ZDSMSCM
subvolume by INITENV is not available.
Always run DSM/SCM from the original ZDSMSCM TSV from
which INITENV was run.
Problem Recov
ery
After you migrate between
R
VUs, ST
ARTSCM gives a
Pathway error that a cold
start is required.
Between certain RVUs, PATHMON requires a cold start of the
Pathway configurations:
1. Stop the $YPHI process.
2. Run PATHCOLD from the ZDSMSCM TSV
3. After PATHCOLD completes, run STARTSCM.
After you migrate, an SQL
IV
ARS error occurs when
you attempt
to start
DSM/SCM on the host for
the first time.
Before running STARTSCM, initialize SQL and run
PATHCOLD from the ZDSMSCM subvolume.
1. Before initializing SQL, save a copy of
$SYSTEM.SYSTEM.ZZSQLCI2.
2. Initialize SQL:
> SQLCI INITIALIZE SQL;EXIT
3. After SQL is initialized, rename the copy back to
$SYSTEM.SYSTEM.ZZSQLCI2 to ensure that DSM/SCM
recognizes it.
For more information, see the appropriate SQL installation
guide.