Prepare the input file for the Entity Move/Rename utility

The input file for the Entity Move/Rename utility can be in CSV or Unicode tab delimited format. You can use any editor to create the input files. Included in the utility installation folder is a sample Unicode text file (.txt format).
Important: On Linux®, the text input file must be saved or converted to be encoded in UCS-2 Little Endian and have Linux end of line (LF) characters.
Tip: If you are using Microsoft Excel, you must save the spreadsheet as a CSV or tab delimited file.

The input file must have the following five columns of data:

Table 1. Columns in the input file

Column Name

Description

Sample Value

Source entity location

The entity on which the operation is run.

/The Bank/USA/North East/Providence

Target entity location
The new parent entity for move and move and rename operations only.
Note:
  • For Oracle rename operations only (no move), the value must be - (dash).
  • For Db2® rename operations only (no move), the value must be blank.

For move and move and rename operations:

/Worldwide/Americas/USA/NE

Run as user

Application user name, whose identity is used to run the operation.

OpenPagesAdministrator

New entity name
The new name after the operation for rename and move and rename operations only.
Note:
  • For Oracle move operations only (no rename), the value must be - (dash).
  • For Db2 move operations only (no rename), the value must be blank.

For rename and move and rename operations: Boston

Execution order
Establishes the operation execution order as follows:
  • Operations that specify the execution order are run before operations that do not.
  • Operations that have a numeric value in the execution order column are run in regular ascending ordering.

If set, the value must to be a valid number; Otherwise, leave the field blank.

1

The following is a short description of the data in the sample .txt file that is included in the utility directory.

  • The first line illustrates moving entity /The Bank/USA/North East/Providence to new location /Worldwide/Americas/USA/NE. Operation is to be run as the user SOXAdministrator. This operation is run first in the batch.
  • The second line illustrates in place rename of the entity /Worldwide/Americas/USA/NE/Providence. Entity name changes to Boston. Target location does not apply and is set to -. This entry has a dependency on the previous move operation and has higher number in the execution order column. Also, it references to the new entity location that will be in effect after the first operation completes.
  • If the first operation fails for any reason, this operation fails as well and the entity location would be incorrect.
  • The third line illustrates simultaneous move of the entity /The Bank/USA/Midwest/Chicago to new location /Worldwide/Americas/USA/MW and rename to Detroit. This operation has no dependencies and will be run after the first two complete.

If you have an Oracle database with the 32-bit SQL*Loader utility in a Linux environment, see the topic: Avoid error 0509-036 when you use the 32-bit Oracle SQL*Loader. Otherwise, run the IBM OpenPages® with Watson™ Entity Move/Rename utility.