Tag Info

New answers tagged

0

You are trying to execute SQL SERVER sql syntax in msaccess. Need to remove the nolock hints. The column and table alias need to b prefixed with AS. And more. Executing your query as a pass-through is probably a better option anyway.


0

Seconds_Behind_Master is the difference between the timestamps a statement was most recently downloaded by the IO_THREAD and when it was most recently executed. I'd highly recommend pt-heartbeat. pt-heartbeat is a two-part MySQL and PostgreSQL replication delay monitoring system that measures delay by looking at actual replicated data. This avoids ...


1

what will be the effect of this on fields of type "timestamp with timezone"? They're converted from their internal UTC representation to UTC-5 at the moment. They'll be converted using UTC+4 after. So applications will see a 9-hour time shift if they're ignoring the time zone. If they respect the time zone reported in the timestamp then there will ...


1

I have seen this since about 2002. Ignore it; it will go away. I have failed to find out what causes it, and it so elusive that I could not get anyone to look at as a "bug". I do not know if this will have any impact on innobackupex.


0

You need to look at the actual catalog/metadata table(s) and clean them up. The GUI and stored procedures often don't cleanup the underlying tables properly. So, after you have run the sp_dropsubscription SP run a select from MSsubscriptions and MSsubscriptions to see if there is any data referring to your unwanted subscriptions. See: ...


0

From "BOSPROD9", try to connect with the mongoshell to the other serves: $ mongo --host 10.235.96.12 --port 27017 $ mongo --host 10.235.96.13 --port 27017 (Telnet is not the same.) If this doesn't work, it might be firewall or BindIP. Check bind_ip (should be 0.0.0.0, change in mongodb.conf is it's 127.0.0.1): $ netstat -nap | grep :27017 | grep LISTEN ...


0

For anyone with a similar problem, I have ended up going with MariaDB, which supports multiple masters per node (connection_name variable when specifying CHANGE MASTER TO). MySQL supports this allegedly starting at 5.7, but we don't want to wait for that release.


2

Use the built-in bitwise operators to examine the column. For example select schema_option & 0x01 AS GeneratesObjectCreation, schema_option & 0x02 AS GenerateCustomSP, ... etc.


2

There are two ways to run a replica. You can use either, or both together: Streaming replication, where the replica makes a PostgreSQL protocol connection to the standby as configured with primary_conninfo in recovery.conf; or WAL shipping, where the replica runs a restore_command (set in recovery.conf that fetches WAL archives to replay. See ...


2

From your description, it sounds like you need something like Bucardo to try and merge data from multiple sources into one. Though you'll probably have to write some custom conflict handlers to deal with data that conflicts across B, B1, and B2. There are examples out there like this for custom conflict resolution: ...


0

I prefer using ucarp for VIP management in conjunction with DRBD I have some posts advocating MySQL, DRBD and ucarp Feb 10, 2014 : MySQL High Availability for InnoDB Oct 17, 2012 : Creating High Availability Cluster with PostgreSQL Dec 19, 2011 : Best way to setup master to multi master replication What might interest you the most is my old post ...


0

MULTIMASTER REPLICATION If you want to use Galera, just get Percona XtraDB Cluster. It comes right-out-of-the-box with Galera libraries wrapped up inside. Just put the wsrep options in my.cnf to to enable Galera. See the PXC Documentation for more info. If you have EC2, you can also use the PXC Setup Guide in EC2. MULTISOURCE REPLICATION multi-source ...


2

Yes, if you are using Peer2Peer replication between the primary and secondary servers which is an enterprise only feature I would personally use Mirroring/AlwaysOn for redundancy between primary and secondary sites as this includes ways to failover without changing the DNS records. Either by adding ';Failover Partner=PartnerServerName;' to the connection ...


0

How about using INSERT ... ON DUPLICATE KEY UPDATE or REPLACE INTO on master itself?


0

Yes you can run all the replication agents from the machine inside the firewall. After everything is setup normally, just disable the SQL Agent jobs that run the agents on the DMZ machine, then create the same jobs on the machine inside the network. Enable the jobs inside the network and start them. The push and pull terminology with SQL replication just ...


0

I am almost in the same situation to identify the best option for my DR. We are using hyper V replica and planning all database servers to be vitalized. But my biggest problem is we have an integrated SQL Server replication usage for our application load balancing and I am not sure whether it works with hyper V VMs. As per Microsoft it says "If multiple SQL ...


1

Not sure if you have checked this; but there is an option in sp_addarticle called @identityrangemanagementoption. If set to manual, then it "Marks the identity column using NOT FOR REPLICATION". Pls check if this is the case. Ref : https://msdn.microsoft.com/en-us/library/ms173857(v=sql.110).aspx


0

The only way I have found to do this so far is by using: On the Master B: SET SQL_LOG_BIN=0; ALTER DEFINER=user@localhost EVENT e_test ENABLE; SET SQL_LOG_BIN=1; This works, but as soon as I alter the Event on Master A, Master B goes back to Slaveside_disabled and I have to repeat this process. So not perfect by any means, as it relies on us remembering ...


0

Not strictly an answer, but perhaps a very long comment: MySQL is very similar to Mac OS X versioning. Mac OS X was first released in 2001. MySQL 5.0 in 2005. It would be just as unfair to compare OS X El Capitan to 10.0 as it would MySQL 5.7 to 5.0. The History: Version 6.0 of MySQL was canceled, and 7.x is the versioning scheme of MySQL Cluster, ...


0

If you mean is MySQL Replication supported between 5.1 and 5.6, I have a very strong warning !!! DATETIME in MySQL 5.6 now has microseconds represented. When it comes to MySQL Replication, row-based binary logging on 5.5 Master cannot be properly handled on a 5.6 Slave processing a DATETIME. I wrote about this and provided an error log that demonstrates ...


1

I've confirmed this is a bug with MySQL/Oracle Support. They will update the public tickets when the internal fixes are ready. To summarize: MySQL replication is only supported between one release level (the second digit) and the next; e.g. between MySQL 5.1 and 5.5; 5.5 and 5.6 but not between MySQL 5.1 and 5.6. The documentation is mistaken when it says ...


2

Original Answer (leaving for people that might hit this because of the simple explanation): The clusterAdmin role only applies when you authenticate against the admin database, so unless you specify the --authenticationDatabase option to be admin when you are running mongodump/mongorestore I suspect you are getting a lesser privilege when authing against ...


0

I would say Yes, it is a bad practice to keep master database in same server than replica database. I have good three(3) reasons why, but there are possible workarounds if you cannot acquire another DB Server. Before I discuss those reasons, have a look at a Pictorial Representation of the InnoDB Architecture (from Percona CTO Vadim Tkachenko) REASON #1 : ...


2

this could be because of openssl update. take a look at the following https://github.com/iuscommunity-pkg/mysql55/issues/4 a notable bug that occurs with the latest version of OpenSSL. This issue prevents secure connections from being made due to the default hardcoded cipher no longer being supported in the newer version of OpenSSL. Below is an ...


0

DISCLAIMER : I haven't tried this myself What you asking for is somewhat rare. Nevertheless, it is possible. Here is a link to Looker.com to explain how. Basically, you do the following: Create a read replica Create a Custom DB Parameter group Tweak the read_only setting in the Custom DB Parameter Group When replica has been created, ... you modify ...


1

To migrate data between different storage engines in MongoDB 3.0 you will need to perform an initial sync to the new replica set node or use mongorestore to seed a new replica set with your data. If you want to add a node with a new storage engine to a live production replica set, rs.add() is the correct approach. To ensure a smooth upgrade I would also ...


1

The MASTER_DELAY option is currently scheduled to be in MariaDB 10.1. There is an issue for the feature. Until that is added to MariaDB, your best option is pt-slave-delay from Percona. I've used it before and it is pretty easy to get going but since it isn't part of the mysql server, it's not as reliable.



Top 50 recent answers are included