PWD50 or xxx00 library and file_list_type

• Article Type: General
• Product: Aleph
• Product Version: 19.01

Description:
Our prof_library file for PWD50 was set to ADM, and because of that, I think, new lines were added to its file_list by Upgrade Express - like z07p and z13u.

For instance, we see the following errors in the 1002.log:

Modifying data_root/file_list: add z13u in all libraries according to Z00
A_WARNING: z13u was not added to file_list under pwd50
Updating data_scratch/file_list for all libraries...

Building data_scratch/file_list for all libraries...
Modifying data_root/file_list: add z13u_id in all libraries according to Z00_ID
A_WARNING: z13u_id was not added to file_list under pwd50
...
...
A_ERROR: cannot find data in file_list in pwd50
A_ERROR: The table z13u does not exist in pwd50.
Insert data of USER-DEF fields 1 - 5 from Z13 to Z13U

Inserting data to z13u from z13 in lib: PWD50
A_ERROR: Cannot move data from z13 to z13u
Error from Oracle:
DBD::Oracle::db do failed: ORA-00942: table or view does not exist (DBD ERROR: error possibly near <*> indicator at char 18 in 'insert into PWD50.


When I look at the default file_list.PW, it is quite different.

Should the prof_library for our PWD50 be changed to
setenv file_list_type PW
?

And then UE (during our STP run next week) will not try to create a Z13u table and indexes, right?

Note: the name of the library in question may be pwd00 or sys00 or xxx00 rather than pwd50.

Resolution:
Since pwd50 is not just the $pw_library but also the $usr_library and the $z105_library at your site, you do not want to specify the file_list_type as PW.

As described in KB's 8192-3719 and 8037, you should specify file_list_type NONE (-- which is a special value indicating PW + USR +Z105). The distributed usr00 prof_library has file_list_type NONE.

• Article last edited: 10/8/2013