Metadata Conversion Troubleshooting Procedures; Hpss Installation Guide July; Hpss 4.5 To 6.2 Conversion Utility Errors And Warnings; 1.Db_Convert_Collect_Info Errors - IBM High Performance Storage System HPSS Installation Manual

the "PRE62_". Next, beginning with step 4, follow the procedures in Section 6.3.24.1: Revert the
HPSS 6.2 System to Version 4.5 on page 225. The site will also have to revert the operating system
software and any other upgraded software back to the HPSS 4.5 prerequisite versions so that the
HPSS 4.5 code is not running on unsupported software.

6.4. Metadata Conversion Troubleshooting Procedures

This section provides troubleshooting procedures for common errors that may occur during a
metadata conversion from HPSS 4.5 or HPSS 5.1 to HPSS 6.2. This file does not contain all error
messages that a failed conversion might output but does discuss the more common errors.
If a DB2 or SQL error message is not found in this section, use DB2's CLI to obtain more
information about the error. For example:
$ db2 ? SQL0100W
This will show more details about SQL warning message 100. Another reference that will help in
determining actions upon receiving DB2 or SQL error messages, is the DB2 Message Reference. This
guide has a list of every message DB2 can produce and recommended actions for fixing the problem.
In the following sections, the error text in displayed in bold type followed by a "=>" then an
explanation of the error. The corresponding "Resolution:" paragraph(s) detail the recommended
course of action to correct the problem and then continue with the conversion.

6.4.1. HPSS 4.5 to 6.2 Conversion Utility Errors and Warnings

This section provides troubleshooting procedures for errors that occur during a metadata conversion
from 4.5 to 6.2. This file does not contain all error messages that a failed conversion might output but
does provide some of the more common errors a user might see. It is helpful to keep in mind that the
SFS (HPSS 4.5) metadata is only being read and then modified in memory and inserted into a DB2
table. So, even with the worst of error conditions, a user could empty all DB2 tables using the
db_*_convert_empty utilities provided, and start the conversion over from scratch with no harm to
the metadata, DB2 or SFS.I
6.4.1.1. db_convert_collect_info Errors
Error: Could not open file /var/hpss/convert/6.2/Convert.DB.Names => The program was unable
to open a text file for writing in /var/hpss/convert/6.2 directory.
Resolution: Check to make sure the directory exists and that write permissions are set properly.
Error: DB2 Database Descriptive Name must be no more than 32 characters long. => The
descriptive name entered for the DB that is longer than the allowed 32 character string size.
Resolution: Rerun db_convert_collect_info and choose a name that is no more than 32 characters
long.
Error: Must enter different DB Name for each subsystem. => The same database name for
multiple subsystems was entered. Only one subsystem can share the same database as the global
database, all other subsystems must have their own database.
Resolution: Create a different database, each with a unique database name, for each subsystem to be
converted. Rerun the db_convert_collect_info utility and provide a unique database name for each
subsystem.
HPSS Installation Guide July 2008
Release 6.2 (Revision 2.0) 227