When an existing U2 account is copied as the O/S level into another account there are a number of adjustments that need to be made in the new account if the source account had the Kourier software installed. These changes are focused on full path names embedded in VOC entries, indexes and other Kourier control records.
warningWidgetWarningThe steps outlined below should be completed when there are no users logged into the new account.
If you have pointed the KT_IOTEMP or KT_MESSAGE files to a different file system, you must correct the paths in these VOC items to point to their new location.
The data sources used in Kourier services will have UNC’s (full pathnames) pointing to specific systems/resources. These UNC’s need to be corrected so that they point at the proper locations associated with the new account.
If you are using Kourier to export information from ODBC data sources,you will need to correct the ODBC Connection record to point at the correct Window’s ODBC data source.
Kourier relies on an O/S level index named KCL_INDEX to track Net Change. If you are running the UniVerse database you must adjust the full path name to the index file stored in the file header of each file that has an index. If you are running UniData you can skip this task.
Use the SET.INDEX command to view index information and to fix errors:
Example of good index (if logged into the LVN account and GL is local to that account)
>SET.INDEX GL
Indices for file "GL" reside in "E:/UV/Accounts/LVN/GL/I_GL".
Example of bad index (if logged into the POR account and GL is local to that account)
>SET.INDEX GL
Indices for file "GL" reside in "E:/UV/Accounts/LVN/GL/I_GL".
In the second example, the file path incorrectly points to the LVN account when it should be pointing to the POR account.
How to fix a bad index (if logged into the POR account)
>SET.INDEX GL TO E:/UV/Accounts/POR/GL/I_GL
The current indices for file "GL" are at path
"E:/UV/Accounts/LVN/GL/I_GL"
to be changed to path
"E:/UV/Accounts/POR/GL/I_GL"
Do you wish to make this change (Y/N)? Y
File header block up dated.
In the second example, the file path incorrectly points to the LVN account when it should be pointing to the POR account.
Kourier includes a program named KT.FIXINDEXPATH that will implement all of the steps outlined above. You should use caution with running this command.
Kourier relies on an O/S level index named KCL_INDEX to track net change. Note that the full-path name to the KT_CHGLOG file in the display below includes a full-path name that points to the source account.
LIST.INDEX GL KCL_INDEX
Alternate Key Index Summary for file GL
File........... GL
Indices........ 1 (0 A-type, 0 C-type, 0 D-type, 1 I-type, 0 SQL, 0 S-type)
Index Updates.. Enabled, No updates pending
Index name Type Build Nulls In DICT S/M Just Unique Field num/I-type
KCL_INDEX I Not Reqd No No S L N SUBR('KCL.UPDATE
LOG','E:\UV\Acco
unts\LVN/KT_CHGL
OG/GL',@ID)
Use the KCL.REMOVEINDEX command to remove all Kourier Net Change indexes.
Once you have removed all the Kourier net change indexes, run KT.SETUPNETCHG to restore net change.
When using Kourier to export data into SQL, the staging area associated
with the source account should be copied to a new directory associated with the
target account. The following directories should be cleared in that new
directory:
In the Config folder, you should adjust any database or full path
reference in the dtsConfig file associated with the target database.
The first time you build SSIS packages for the exports that send data to
SQL in the new account, make sure to you correct all database and path
references in the Generate Packages screen.