Table of Contents

Search

  1. Preface
  2. Client Messages
  3. Informatica Administrator Messages
  4. A Message Codes
  5. B Message Codes
  6. C Message Codes
  7. D Message Codes
  8. E Message Codes
  9. F Message Codes
  10. H Message Codes
  11. I Message Codes
  12. J Message Codes
  13. L Message Codes
  14. M Message Codes
  15. N Message Codes
  16. O Message Codes
  17. P Message Codes
  18. R Message Codes
  19. S Message Codes
  20. T Message Codes
  21. U Message Codes
  22. V Message Codes
  23. W Message Codes
  24. X Message Codes

Message Reference

Message Reference

REP_ 57169

REP_
57169

Multiple connections of different types have the same name, and some sessions and/or transformations contain this name without a type prefix (such as “Relational:”) as connection information. This ambiguity must be resolved by prefixing those connection information.
The specified database connection name exists as both a relational and application connection. You entered the database connection name for the Stored Procedure or Lookup transformation location in the session properties, but you did not specify Relational: or Application: before the connection name.
Enter Relational: or Application: before the connection name for the Stored Procedure or Lookup transformation location in the session properties.
The database connection name in the From field in the Replace Connections dialog box exists as both a relational and application connection. You entered the database connection name in at least one session or transformation, but you did not specify Relational: or Application: before the connection name.
Enter Relational: or Application: before the connection name in all transformation properties and session properties that specify this database connection name.

0 COMMENTS

We’d like to hear from you!