When you copy a Session task, the Copy Wizard looks for the database connections and associated mappings in the target folder. If the mapping or connection does not exist, you can select a new mapping or connection. If the target folder has no mappings, you must first copy a mapping to the target folder in the Designer before you can copy the session.
When you copy a session, you might encounter the following copy conflicts:
Duplicate name.
A session with the same name exists in the target folder. You can rename the existing session, reuse the session in the target folder or replace it. If you rename or replace the session use the default mappings and connections. Otherwise, you may need to choose the connections and mappings after you copy the session.
Cannot find connection.
The connection object for this session does not exist in the target.
Cannot find mapping.
The associated mapping is not in the target folder. You can select an available mapping in the target folder. If you have no mappings in the target, you must cancel the session copy.
Cannot find database connections.
A database connection object does not exist in the target repository. Select connections from the target repository.