| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
|
| The Ingres system catalogs are not fully carried forward in a reloaded database - the bit that tells the database that Replication is being used is missing. We do the following when reloading a database: A. sql +U B. insert into iidbcapabilities (cap_capability, cap_value) values ('REP_CATALOG_LEVEL','00200'); We are using Ingres 2.6, there is a chance that the value '00200' could be changed in later releases of Ingres. When this row is inserted, then Replicator commands like "repmgr" will work. Hope this solves your problem. Eric Mischke -----Original Message----- From: info-ingres-admin-at-cariboulake.com [mailto:info-ingres-admin-at-cariboulake.com] On Behalf Of anupamshriwatri-at-gmail.com Sent: Wednesday, January 04, 2006 10:33 AM To: info-ingres-at-cariboulake.com Subject: [Info-ingres] restart replication after reload of database hello all, we had to destroy a database and had to create it back again due to some problems. now how to start replication again for that database. we have successfully loaded tables into the database, with their data. the dd_ tables are also there in the database with the previous information.....but still repmgr will not start. what do we have to do start replication on the database? or it has to be reconfigured again for replication? expecting replies.... thanks Anupam _______________________________________________ Info-ingres mailing list Info-ingres-at-cariboulake.com http://mailman.cariboulake.com/mailm...py/info-ingres |
![]() |
| Thread Tools | |
| Display Modes | |