DIET errors when the username is not "sa" on Oracle databases (Article # 353)
View products that this article applies to.
Problem:
When using DIET on Oracle databases, and the username is not SA, then errors can occur, such as:
Unique field 'login_name' not specified
Resolution:
DIET queries directly against the user_indexes and user_ind_columns views. Those are the only queries using the user_ views. These queries will only return data if the DIET login is the owner of these indexes. By default, this is the SA user. If "sa" owns these indexes, then that user would have to be used.
Expected:
DIET would use the all_indexes and all_ind_columns views.
There is not currently a workaround. The SA user must be used.
A Change Request has been opened so that all_indexes and all_ind_columns are used instead. This would allow a user other than SA to be used.
Applies To:
-
ArchiveManager – Dovetail ArchiveManager (formerly Data Import Export Tool)