When “repair using” is issued on a file with wildcards where the source database has sequences conforming to those wildcard entries, the following messages are observed in sp_ctrl session that issued the command:
sp_ctrl>repair using <file_name>
Cannot repair "OWNER"."SEQUENCE_NAME"
Source table is not in database
Here are the contents of the file file_name:
datasource:o.source_SID
expand OWNER.% OWNER.% targetserver@o.target_SID
The command “repair using” does not parse the conforming objects to eliminate the sequences from the list of objects. This results in issuance of repair for tables as well as sequences. The repair succeeds on tables but the error message is displayed for sequences as below:
Cannot repair "OWNER"."SEQUENCE_NAME"
Source table is not in database
One can simply ignore those error messages (or notices) as they will not do any harm although they may be an annoyance. If the messages are not desired, then one may want to create explicit entries for the tables in the file used in the “repair using” or use exclusion clauses for sequences so that the command does not pick up sequences.
