Filter
Top Products
Resolution: Check that the table exists in the schema and that the db_convert_collect_info utility has
been run recently. The empty table scripts pull their information about which schema to use from the
text file /var/hpss/convert/6.2/Convert.DB.Names, created by running db_convert_collect_info. Enter
the appropriate schema name for the global database (which will be used for all databases) when
rerunning db_convert_collect_info. This could also mean that the tablespace that the unemptiable
tables exist under has quiesced to EXCLUSIVE mode (i.e. there is a lock on the tablespace). Look at
the tablespaces using the DB2 control center utility or issue “list tablespaces” on the DB2 CLI . If
the tablespace mode is EXCLUSIVE, use the CLI to issue the “quiesce tablespaces for table ****
reset” for each table that exists in the tablespace to free the lock and rerun the conversion program.
An error occurred, not all subsystem tables emptied in global, under schema hpss. => This error
is explaining that an error has occurred on one or more 'delete from ????' operations, where ???? is a
schema and table name.
Resolution: Verify that the table exists in the schema and that the db_convert_collect_info utility
has been run recently. The empty table scripts pull their information about which schema to use from
the text file /var/hpss/convert/6.2/Convert.DB.Names, created by running db_convert_collect_info.
Enter the appropriate schema name for the global database (which will be used for all databases)
when rerunning db_convert_collect_info. This could also mean that the tablespace that the
unemptiable tables exist under has quiesced to EXCLUSIVE mode (i.e. there is a lock on the
tablespace). Look at the tablespaces using db2's control center utility or issue “list tablespaces” on
the DB2 CLI. If the tablespace mode is EXCLUSIVE, use the CLI to issue the “quiesce tablespaces
for table **** reset” for each table that exists in the tablespace to free the lock and rerun the
conversion program.
Error: Cannot open file '/var/hpss/convert/6.2/sample' => The conversion program cannot access
the text file that maps DB Names to SubsysIds, or SSIds to CoreIds, or NSIds to CoreIds.
Resolution: Verify that the pathname of the text file that it is trying to access hasn't been modified in
the running script. If not, rerun the db_convert_collect_info utility because the text file was never
created or has been modified.
Error: Key '8cf7-754d66-7652cb3-21' not found in /var/hpss/convert/6.2/Convert.SS.Server.Ids
=> In this case, the conversion program is attempting to map an HPSS 4.5 Storage Server id to a new
HPSS 6.2 Core Server id, and it cannot find an entry in the text file, Convert.SS.Server.Ids, under
/var/hpss/convert/6.2. This text file is created after running db_convert_collect_info and results from
reading the general and specific config entries for all storage servers in the HPSS 4.5 system.
Therefore, if both a general and specific configuration record for this storage server does not exist,
either create the storage server this conversion program is trying to find, or delete the offending
metadata (i.e. orphaned storage segments). The conversion programs have a force option (-force) that
allows the conversion programs to output an error and continue the conversion process after finding
orphaned metadata entries; however, we strongly recommend that you contact your HPSS customer
support representative before using the force option, as converting essential metadata could be
skipped.
Resolution: Fix the HPSS configuration for the incomplete or missing 4.5 server or contact your
HPSS customer support representative and run the conversion with the force option to skip possible
orphaned metadata entries.
Error: /.:/encina/sfs/hpss/nsobjects is not in subsystem 1 => The program is attempting to
convert the "nsobjects" SFS file and discovered that the filename differs from your HPSS systems
specific configuration file NSObjFileName for subsystem 1.
HPSS Installation Guide July 2008
Release 6.2 (Revision 2.0) 229