surdabhi wrote:hey, there's no need to be rude, if i ask you something..
I don't think he/she meant that as bad as you're taking it. I would probably of commented on the training aspect as well.
Anyway, the question is very general and may be hard to answer.
As you know, WTX (Mercator) is used to build maps that translate data from one format to another. Once the map is tested, it is implemented into a system file, and deployed to the machine that runs "launcher".
As for common errors, they may spawn from different WTX processes.
Like Map failures. All the possible errors would be in the "Map Designer Reference" guide, in the documentation that comes with the product. Most of the errors you'll see, will be "One or more inputs Invalid" or "Input Type contains errors" (the second is warning, not an error), both pointing to a problem with the data being validated. Other errors include stuff like "Target Not Available", where the output location for the map is not available, for reasons such as the network is down, the ID running the map does not have access to the output directory, or the FTP log in is incorrect.
For errors like the FTP login incorrect, the map will return a "Target Not Available", and you'll have to turn on the trace file for the FTP adapter and see the information inside. The same thing if your output adapter is a message queue. The map will return "Target Not Available", then you turn on the trace file and view it, and it should have the specific MQ error message, like 2085 - unknown object name". Same thing with the email adapter, etc.
Most shops using WTX will have a system dedicated to reading the Audit log from all systems and alerting people, usually through the email adapter, that the return code was not equal to 0 and should be looked at.
Does that help at all?
I believe knowledge is all about sharing rather than being very possessive and obnoxious about it. 
