Hi Andy,
Andy K wrote:
I have an existing database (on a Linux Red Hat ES3) where the
replication function exists but does not work because the target
database has been shutdown months ago .
My question is what will happens if i start the target database ?
Nothing bad will happen by just starting the database. If you start the
apply-process and there is remaining (not pruned) data in the cd-tables,
this data will be applied.
Will there be problems with the source database or the target database
(decreasing performance or other kinds of problem )?
as usual...it depends (amount of data to be applied, other applications
running against the database)....
Was the capture-process on the source-database running all the time?
Then you should have a reasonable amount of data in the cd-tables. If
you have stopped the capture-process you would need to have all logfiles
written by the source database since capture has been shut down. Else,
capture will not work properly and you would need to do a
(manual/automatic) full refresh.
ps1 : is there any possibilities to setup a replication processus
without the DB2 control center ? (it seems to be no after the
documents I have read but who knows ... )
1. Learn by the scripts, Replication Center creates for you. You can
easily modify them or write your own wrappers around them.
2. "SQL-Replication Guide and Reference" is the source you are looking for.
3. short list of commands you need to look up to run replication from
the command-line: asncap, asnapply, asnacmd, asnccmd, asnanalyze.
ps2 : that control center seems to be quite annoying especially if the
linux server has been secured and doesn't allow graphical screening !
I understand you are running the control center on the server where the
database resides. This is not optimal in many ways.
If the Administration Server is running on the server you should be able
to run the graphical tools on your client without any X-forwarding at all.
Yes, control center _is_ annoying like any other graphical java
interface that I have seen so far, but it is getting better from release
to release . Fortunately there are many ways to run and monitor DB2 UDB
without running a gui at all. ;-)
regards,
Norbert