Hot answers tagged

3

We're now looking for a way to monitor the replication; mostly to verify that the slave server is still up-to-date. For monitoring replica lag, there are several ways that give slightly different answers, depending on which version of Postgres you are using. A simple query that can be done directly on the standby is: SELECT (CASE WHEN ...


3

I would suggest Transactional Replication. This will be more of a "Real-Time" copy of the data than the one refresh per day that you have now. You can add new tables into the database without affecting the replicated tables.


2

https://dev.mysql.com/doc/refman/5.7/en/replication-features-differing-tables.html describes the supported variations in table definitions. For one, it appears that this is supported with statement-based replication: When using statement-based replication, a simple rule of thumb to follow is, “If the statement run on the master would also execute ...


2

After much frustration and fruitless googling, I finally figured out the problem. It was not that the accounts for the 'SQL Server' and 'SQL Server Agent' services did not have access to the directory. The problem was that the account for the 'Log Reader Agent' did not have access. Should have been obvious from the error message, but I just didn't get it... ...


2

Is it possible to take their suggestions and incorporate them into your main database; or are the additions very client specific? You could ask them for scripts to run post restore. If you go down the replication road then see Chad's answer. Some warnings with transactional replication though are that if your subscriber fails, you might fill your ...


1

There are couple of options -- I would not suggest to go with replication as you are making schema changes and it will require to reinitialize the whole replication with a snapshot. Logshipping with standby option: Cheap and effective. Works great and less overhead of maintenance. Things to look out : If an adhoc log backup is taken, it will break ...


1

If both the servers showing same server-id, you can set this to some other value and check again. On Master: server-id = 1 On Slave: server-id = 2 Make sure that, while giving change master settings, give the host name as ip address of the master server. This should work, check again and see if the same issue exists. I hope this will help you.


1

Did I understand this correctly that your customer has MSSQL Server? Source Database MSSQL or other You have two options: Script your own replication Use Oracle Golden Gate to stream the data to your Oracle Database. Golden Gate supports "zero downtime" migration. Source Database Oracle Additionally to the options mentioned in "Source Database MSSQL ...


1

OS error 23 is "Data error (cyclic redundancy check)." you can check those by running executing on the command prompt net helpmsg 23, this basically means that you have a serious error on your disk. As the database is running what you need to to is to DONT PANIC Find your backups Script your replication setup Do a tail-of-the-log backup to have a ...


1

The second option should be the fastest. It was made for this. Also it should have no bugs since it is used a lot and already for a long time. If you go for this then you do not even need to use a composite primary key. In my opinion the only reason to use the first option is if you need a numbering starting from 1 per client.


1

You can use Replication Management Objects. You can interrogate them locally or remotely (the better option). The DLLs should be on some systems. If you still have known SQL 2000 instances please test them as it's unclear if modern versions of RMO will still talk down to SQL 2000 instances; 2005 and above should be more reliable. ...


1

By Default cql will convert the table/keyspace/column name in lowercase. If you have table/keyspace/column in uppercase you have to enclose it in double quotes. alter KEYSPACE "HiveMetaStore" with replication = {'class': 'NetworkTopologyStrategy', 'DCassandra1': 1}; Opscenter handled it for you:) CQL UpperCase/lowercase


1

Answer to 2) question - Most probably you had some minor version upgrade for your master 5.5 MySQL server. There is a bug for 5.0 - Bug #50876 and according to my experience, the same bug exists in 5.5


1

For trans rep to work one server needs to be able to see the other - and for FTP snapshots to work it has to be that the subscriber can see the publisher and that you set up a pull subscription. A push subscription is set up on the publisher and that's where the jobs run. A pull subscription is set up in the subscriber and that's where (some of) the jobs ...


1

This issue has been addressed (KB3155209) in SQL Server 2012 SP2 CU12



Only top voted, non community-wiki answers of a minimum length are eligible