DataBase - Replication Cold Start
Asked By Asphalt Blazer
11-Mar-10 09:08 AM
I have 2 databases in two different instances that I am doing one-way
replication to. I will be cold starting the replication when I first
initialize it. But I do not want the target table to be refreshed. I
have sychronized the capture side and apply side tables using export-
import and then changed some column values on the target side after
this export-import. I do not want these values to be overwritten. I
just want the capture and apply to proceed from the current point on a
cold start. Is there any way to do this?
TIA.
Mannepalli
(1)
Shashi
(1)
Ibm.swg.im.iis.repl.qrepl.doc
(1)
Infocenter
(1)
Databases
(1)
Regardin
(1)
PRUNCTL
(1)
Db2luw
(1)
whatever replied to Asphalt Blazer
You have not mentioned whether this is SQL or Q Replication.
If it is SQL Replication...once u do a COLD START of the capture ..you
have to do a FAKE FULL REFRSH.
Basically u have to update ASN.IBMSNAP_REGISTER SET DISABLE_REFRESH =3D
1 and also PRUNCTL Table.
You have to change tables in the APPLY Side also.
There should be lots of documentation regardin this in the info
center..Pls check
Cheers...
Shashi Mannepalli
Asphalt Blazer replied to whatever
This is Q-Replication.
I have done the disable refresh already. But on starting the apply,
replication is not working. Is there any particular documentation
regarding this you can point me to?Thank you.
whatever replied to Asphalt Blazer
a
http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=3D/com=
.ibm.swg.im.iis.repl.qrepl.doc/topics/iiyrqcapcmtncold.html
Look for
Considerations for using the cold start mode
cheers...
Shashi Mannepalli
blazer462 replied to Asphalt Blazer
Make sure your queue is empty before doing the cold start. This would
be the most common reason why applier would'nt start after the cold
start.
this question, but I drew blanks last time. Now assuming I have several referenced (library?) databases in my main database, how do I get the names of all the forms in your way of working is a little different from mine, though we both use reference databases. This is what I do: Each user application is a user database with a reference user applications. When these changes have their effect on the (standarized) forms in the user databases, than the forms can be updated with one click of a button. In this concept of n text - Hi Phil, The best way to test the principle of the referenced databases is to make a production environment on a different computer, but with exactly the same me starting from Access 97, for many applications. It works the same way, whether the databases are compiled or uncompiled. However, when compiled, BOTH the databases must be deployed at the same time. App.Mde does not work with any other all possible locations for the components, which is why I would never put any library databases anywhere except in the same folder as the front end. In my opinion, all the application components belong there, including your front end, your temp database and any library databases. Supposedly references that are broken but can be resolved by looking in the same folder
to be loaded and compared. The JET engine behind Access is not suited to handle databases beyond stamp collection size and lacks most features of a "real" database management system. Consider Ace, you should restrict your post to the dotnet / csharp newsgroups, so those in comp.databases.ms-access who _do_ know about Jet and Ace will not see and correct your SQL server. Basically your advice comes down to not knowing much of anything about = 20 databases, not understanding computer architecture, and your response = can = 20 simply can be summed up as in a position to criticize an important MVP like you. Maybe this source is: http: / / databases.aspfaq.com / database / what-are-the-limitations-of-ms-acc = ess.html. I would like Microsoft's knowledge base articles that make clear why JET is crap, i.e. MDB databases going corrupt, which is unacceptable even if you merely store your stamp collection in it I *do* have some experience with JET and it should be legitimate even in comp.databases.ms-access to criticize it. Heck, I have no problems whatsoever with Access, only with 20 pointing out it is a bad assumption on your part. legitimate even in comp.databases.ms-access to criticize it. Heck I have no problem to the criticisms, but not long after MSDE and SQLServer Express showed up. And why not - database servers and embedded databases really targets different usage scenarios. There can be many reasons for that. It is not
I have no idea if this is possibe. Suppose I have 2 separate front end databases called AFe.accdb and BFe, both with respective back end databases ABe, accdb and BBe.accdb. Both these FE databases have some common forms and associated Vb. For example they both have a form called for displaying the respective menus. The data for these menus is supplied from the BE databases. What I want to do is have yet another database called say Menus.accdb which and BFe.accdb. Then somehow I want to set a reference in those Front End databases back to Menu.accdb so that those forms still appear still to be there. That refenence. 3 Are there likely to be clashes with the same function defined in both databases. 4 What other problems are there likely o be Thanks Phil Access Discussions Visual Studio Business Solutions", published by Wiley Access newsgroup support is alive and well in USENET comp.databases.ms-access You probably need to use code to link your tables anyhow. Relink Access in yet another BE database with the information on what the paths are for BE databases for each organisation. The other scenario is for a totally different FE / BE database arrangement
STMM as a way to convince customer executives that DB2 needs less expertise than other databases because it is self-tuning (or at least a lot less expertise than needed by worthless anyway and I recommend that it be turned off (default is on for new databases). If you do use STMM, and end up in a mental institution, do not blame the memory model and the fact that it works across instances really helps us consolidate databases and get the most out of our servers." - Canadian Department of National Defence customers throw know many DBAs that will devote hours and hours to optimally configure some of their databases and yet, for their test environments, they are happy to let STMM do the heavy That being said, some of these same DBAs have enabled STMM on their most critical databases and found that its tuning outperformed their hand tuned configuration. I'd be interested to necessary precautions. You can read more about the precautions here: http: / / publib.boulder.ibm.com / infocenter / db2luw / v9r7 / topic / com.ibm.db2.luw.admin.perf.doc / doc / c0023815.html That is trying to get STMM to work on a critical database server with multiple instances and databases, we gave up and just hard-coded the memory values. It was not very difficult STMM has had problems in the past with being to manage a large number of databases with multiple instances, especially under Linux. IBM support flat out told us that automatic instance
tables from one database to another database that was created around the same time. These databases are copy / pasted into a new folder and renamed each year (in MyComputer) and the I tried running the macros from another person's pc who has access to these databases and it did not work on his pc either. . . got all the same messages. I was kind of hoping it was just my pc, but apparently not. These databases are very important at this time of year, as they are for the company budget tables from one database to another database that was created around the same time. These databases are copy / pasted into a new folder and renamed each year (in MyComputer) and the I tried running the macros from another person's pc who has access to these databases and it did not work on his pc either. . . got all the same messages. I was kind of hoping it was just my pc, but apparently not. These databases are very important at this time of year, as they are for the company budget supported for this type of object. Macros have been enabled on both pc's, both databases. About the only solution we have not tried yet is to modify the sandbox setting supported for this type of object. Macros have been enabled on both pc's, both databases. About the only solution we have not tried yet is to modify the sandbox setting