Siebel 26.1 RepositoryUpdate Issues
Hi Support,
We just ran into two new issues with RepositoryUpdate we have not seen before.
First we had three columns that errored with and Oracle database error that the value was too large. It finally hit us that for the previous Oracle client we had to set NLS_LANG in the registry to indicate that our database was Unicode. The new Siebel provided Oracle client is the Oracle Instant Client and as such does not have an Oracle home. We created a NLS_LANG environment variable and that seems to have fixed the issue.
The second issue looks like a plan bug. During the import of one of the first sifs (We are coming from 21.12) an EIM table referred to a column that was not present in a base table. We added this column and are retrying now and looks like our work around took care of this issue.