NO.
Daniel my friend, repeating the exact same question doesn't help anyone. Please clarify in more detail what you are trying to accomplish best as you can. Before doing sure to review the Replicate documentation best you can, to at least get an idea of the terminology/language used for the various action and components.
Tell us where the (change) data is coming from, where it is going, and perhaps some special requirements.
Most importantly tell us which SOURCE ENDPOINT is considered and carefully read up on the PREREQUISITES for that source endpoint in the Replicate documentation.
I can tell you already though that the answer is NO. Somebody, probably a DBA or perhaps yourself, probably needs to maak some preparations on the source. Read, and be the judge yourself.
Typically a (often privileged) username/password needs to be set up and access to the transaction log provided (WAL, REDO, T-LOG, whatever it is called for the desired source). And often the source DB has to be told to log more than the minimum information, or retain it longer. Replicate can handle the table actions - provided the right privileges are in place. It's all in the books.
There are some exceptions where little or no action is needs - they are sort of non-CDC CDC solutions: ODBC-CDC, Files.
hth,
Hein.
