I have a question, about a question, that is part of the 70-462 Microsoft exam.

I had this question today, and I'm not completely sure of the correct answer. While I did pass the exam, I would like to understand the correct solution given this situation.

If I recall the question correctly, you administer a 2012 SQL Server, the requirements are to offload up to the minute reporting, for an OLTP database, to another server, and also be able to add indexes to the secondary database.

The answers for the question were along the lines of:

1. Two servers, different data center. AG group with synch commit. Active secondary.
2. Two servers, same subnet. AG group with synch commit.
3. Two servers, log shipping every 10 minutes.
4. A couple diffrent answers with a-synch commit.
5. SQL Server that includes application database configured to perform transactional replication.
6. SQL Server that includes application database configured to perform snapshot replication.
7. Two servers in a windows failover cluster. SQL Server configured as clustered instance.

Initially I ruled out the a-synch commit options (latency), the synch commit AG group in different data centers (latency?), log shipping (delay), and snapshot replciation options.

This left me with the synch commit AG group on the same subnet, or SQL server with transactional replication.

Based on https://msdn.microsoft.com/en-us/library/ff878253.aspx, I read that if you want indexing on your active secondaries, you have to create them in your primary. I interpreted the question as requiring to be able to create indexes on the seconday, that do not exist on the primary (covering indexes for reporting, or what not).

The other answer, refers to SQL Server singularly, which doesn't sound like we're adding "another server" to offload the work to.

Have I misinterpreted the question/requirements? What should the correct answer/solution be?

I am Using the Domino Designer 9.0, FP 8 and I can't sync my Gitrepositry with my Java Code on my Database. Sometimes it works just fine, but most of the time the Designer shows me the Sync Conflict window. For my files I always select Use "On-Disk Project Version". The Window closes and opens up again.

When I open a file which should have changed,edit and save it, the "Sync Conflict" window opens up again. So i assume the designer knows the different files but can't write into my database(?).

What I have tried to fix to problem so far: -Deleting local replica and create a new local replica -Remove database from Designer and reassociate the git with the database -changing the properties of the Java files (Prohibit reffresh or replace to modify) -rebuild, refresh etc.

I'm new to MySQL and have set up MySQL master-master replication according this tutorial:https://support.rackspace.com/how-to/mysql-master-master-replication/

I have created some test users on the first DB and would like to know how can I replicated those users to the second master DB.

As far as I understood the administrative database, which is called 'mysql' must be replicated, so the users will be replicated.

Is it enough if I add the line below into my.cnf?

replicate-do-db mysql

Are there any other possibilities to replicated users?

The closest answer I found was mysql-db-in-replication-but-users-created-on-master-are-not-replicating-on-slave

Any help would be appreciated.

I have a master/slave replication setup based on statement based replication. On master database named DB1, I have 5 tables and I want to replicate only two table on slave's database named DB2.

Also, I want to change the database name on my slave end.

So my configuration file on Slave end look like this and replication filtering is this:

   replicate-rewrite-db="DB1->DB2"
   replicate-do-table=DB2.table4
   replicate-do-table=DB2.table5

Also I have tried below filtering as well:

   replicate-rewrite-db="DB1->DB2"
   replicate-do-table=DB1.table4
   replicate-do-table=DB1.table5

But in both case records not getting replicated , also no error is reporting.

As per MySQL documentation , replicate-rewrite-db doesn't work with replicate-do-table.

Any method to resolve this? Or is this not possible?

I'm using MySQL 5.6 community edition on Linux server.

I haven't made any changes to master end as it is on customer side.

I have a MongoDB in a ReplicaSet with 3 members, and last week the primary node got corrupted somehow and stopped. I had to resync the data from the other nodes.

It has been a week but I was checking this morning and the databases looks different somehow between the primary (that crashed) and the two secondary that were used for resync the data.

PRIMARY (after crash)

Secondary

I've seen other questions similar to this one but at the end the databases had the same amount of objects, however, my scenario it isn't the same.

Any idea? Or does it look ok?

Basic master-slave MySQL configuration has been done on Windows machine. Master and slave servers are running on localhost with different ports.

Now when executing update or insert in master server, slave server getting stopped after that event. Once restarting slave server and check updates then update/insert is successfully executed in slave through replication setup.

What could be the possible root cause of this issue?

Log of show slave status\G :

 *************************** 1. row ***************************

Slave_IO_State: Waiting for master to send event
              Master_Host: 127.0.0.1
              Master_User: masteradmin
              Master_Port: 3307
            Connect_Retry: 60
          Master_Log_File: USERMAC38-bin.000007
      Read_Master_Log_Pos: 840
           Relay_Log_File: USERMAC38-relay-bin.000004
            Relay_Log_Pos: 290
    Relay_Master_Log_File: USERMAC38-bin.000007
         Slave_IO_Running: Yes
        Slave_SQL_Running: Yes
          Replicate_Do_DB:
      Replicate_Ignore_DB:
       Replicate_Do_Table:
   Replicate_Ignore_Table:
  Replicate_Wild_Do_Table:
   Replicate_Wild_Ignore_Table:
               Last_Errno: 0
               Last_Error:
             Skip_Counter: 0
      Exec_Master_Log_Pos: 840
          Relay_Log_Space: 467
          Until_Condition: None
           Until_Log_File:
            Until_Log_Pos: 0
       Master_SSL_Allowed: No
       Master_SSL_CA_File:
       Master_SSL_CA_Path:
          Master_SSL_Cert:
        Master_SSL_Cipher:
           Master_SSL_Key:
    Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
            Last_IO_Errno: 0
            Last_IO_Error:
           Last_SQL_Errno: 0
           Last_SQL_Error:
Replicate_Ignore_Server_Ids:
         Master_Server_Id: 1
              Master_UUID: 63ac2f83-44ac-11e5-bafe-d43d7e3ca358
         Master_Info_File: mysql.slave_master_info
                SQL_Delay: 0
      SQL_Remaining_Delay: NULL
  Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
       Master_Retry_Count: 86400
              Master_Bind:
  Last_IO_Error_Timestamp:
 Last_SQL_Error_Timestamp:
           Master_SSL_Crl:
       Master_SSL_Crlpath:
       Retrieved_Gtid_Set:
        Executed_Gtid_Set:
            Auto_Position: 0

Error log of slave before it got stopped :

'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port= 3307, master_log_file='USERMAC38-bin.000008', master_log_pos= 123, master_bind=''. New state master_host='127.0.0.1', master_port= 3307, master_log_file='USERMAC38-bin.000013 [truncated, 295 bytes total]
Storing MySQL user name or password information in the master.info repository is not secure and is therefore not recommended. Please see the MySQL Manual for more about this issue and possible alternatives.
Slave I/O thread: connected to master 'masteradmin@127.0.0.1:3307',replication started in log 'USERMAC38-bin.000013' at position 498
Slave SQL thread initialized, starting replication in log 'USERMAC38-bin.000013' at position 498, relay log '.\USERMAC38-relay-bin.000001' position: 4

General log of slave before it got stopped :

150819 11:04:44    10 Query stop slave
150819 11:04:45     8 Query SHOW GLOBAL STATUS
150819 11:04:48     8 Query SHOW GLOBAL STATUS
150819 11:04:51     8 Query SHOW GLOBAL STATUS
10 Query    CHANGE MASTER TO MASTER_HOST = '127.0.0.1' MASTER_USER = 'masteradmin' MASTER_PASSWORD = <secret> MASTER_PORT = 3307 MASTER_LOG_FILE = 'USERMAC38-bin.000013' MASTER_LOG_POS = 498
150819 11:04:54     8 Query SHOW GLOBAL STATUS
150819 11:04:55    10 Query start slave
11 Connect Out  masteradmin@127.0.0.1:3307
150819 11:04:57     8 Query SHOW GLOBAL STATUS
150819 11:05:00     8 Query SHOW GLOBAL STATUS
150819 11:05:02    10 Query show slave status
150819 11:05:03     8 Query SHOW GLOBAL STATUS
150819 11:05:06     8 Query SHOW GLOBAL STATUS
150819 11:05:09     8 Query SHOW GLOBAL STATUS
150819 11:05:12     8 Query SHOW GLOBAL STATUS
150819 11:05:15     8 Query SHOW GLOBAL STATUS
150819 11:05:18     8 Query SHOW GLOBAL STATUS
150819 11:05:21     8 Query SHOW GLOBAL STATUS
150819 11:05:24     8 Query SHOW GLOBAL STATUS
150819 11:05:27     8 Query SHOW GLOBAL STATUS
150819 11:05:30     8 Query SHOW GLOBAL STATUS
150819 11:05:33     8 Query SHOW GLOBAL STATUS
150819 11:05:37     8 Query SHOW GLOBAL STATUS
150819 11:05:40     8 Query SHOW GLOBAL STATUS
150819 11:05:43     8 Query SHOW GLOBAL STATUS
150819 11:05:46     8 Query SHOW GLOBAL STATUS
150819 11:05:49     8 Query SHOW GLOBAL STATUS
150819 11:05:52     8 Query SHOW GLOBAL STATUS
150819 11:05:55     8 Query SHOW GLOBAL STATUS
150819 11:05:58     8 Query SHOW GLOBAL STATUS
150819 11:06:01     8 Query SHOW GLOBAL STATUS
150819 11:06:04     8 Query SHOW GLOBAL STATUS
150819 11:06:07     8 Query SHOW GLOBAL STATUS
150819 11:06:10     8 Query SHOW GLOBAL STATUS
150819 11:06:13     8 Query SHOW GLOBAL STATUS
150819 11:06:16     8 Query SHOW GLOBAL STATUS
150819 11:06:18    12 Query BEGIN
12 Query    COMMIT /* implicit, from Xid_log_event */
150819 11:06:19     8 Query SHOW GLOBAL STATUS

Error log after restarting slave :

You need to use --log-bin to make --log-slave-updates work.
You need to use --log-bin to make --binlog-format work.
Plugin 'FEDERATED' is disabled.
2015-08-19 12:11:26 150 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: CPU does not support crc32 instructions
InnoDB: Initializing buffer pool, size = 165.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 8556085
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 8556558
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
2015-08-19 12:11:27 1f64  InnoDB: Warning: table 'mysql/innodb_index_stats'
InnoDB: in InnoDB data dictionary has unknown flags 50.
2015-08-19 12:11:27 1f64  InnoDB: Warning: table 'mysql/innodb_table_stats'
InnoDB: in InnoDB data dictionary has unknown flags 50.
InnoDB: 1.2.10 started; log sequence number 8556558
Server hostname (bind-address): '127.0.0.1'; port: 3309
- '127.0.0.1' resolves to '127.0.0.1';
Server socket created on IP: '127.0.0.1'.
2015-08-19 12:11:27 150  InnoDB: Warning: table 'mysql/slave_worker_info'
InnoDB: in InnoDB data dictionary has unknown flags 50.
Recovery from master pos 2235 and file USERMAC38-bin.000013.
Storing MySQL user name or password information in the master.info repository is not secure and is therefore not recommended. Please see the MySQL Manual for more about this issue and possible alternatives.
Slave I/O thread: connected to master 'masteradmin@127.0.0.1:3307',replication started in log 'USERMAC38-bin.000013' at position 2235
Event Scheduler: Loaded 0 events
E:\2-Softwares\mysql-5.6.10-winx64\bin\mysqld.exe: ready for connections.
Version: '5.6.10-log'  socket: ''  port: 3309  MySQL Community Server (GPL)
Slave SQL thread initialized, starting replication in log 'USERMAC38-bin.000013' at position 2235, relay log '.\USERMAC38-relay-bin.000011' position: 4

I've recently started working with database read replicas. One of the projects I'm working on has an AWS RDS PostgreSQL setup where there's one write-database and multiple read-replicas. Sometimes, the replica lags a lot and applications querying for information which was just written do not find it in the replicas.

One solution I was considering was using something like Freno - which, from what I gather, is a tool that throttles your writes on MySQL while your replicas are lagging.

Is there any such tool for PostgreSQL?

All suggestions are welcome! (possible Freno alternative for PostgreSQL; strategies for this situation; general replica-lag-related for this situation advice; etc.) Thank you.

When we first set up our multi-region Mongo infrastructure up we didn't add any security and are using unencrypted transport connections for replication over the public internet. We need to switch to use encrypted connections for the replication, but are worried that switching this will break the current replication. We have a couple of TB of data and it is very difficult to force a resync if things get out of sync.

What is the recommended process to switch to encrypted transports in this situation?

Thanks in advance,

Ian

How to replicate - Create User, Procedure and Tablespace using Oracle GoldenGate.

I am able to replicate DDL under schema, however above is not getting replicated i.e. when I create an user, procedure or tablespace.

GoldenGate Version - 12.2.0.1 Database Version - 11.2.0.4

Extract Conf:

GGSCI (sourceGG) 36> view params ext4

extract ext4
userid ogguser, password ogguser
exttrail /u01/app/oracle/product/11.2.0.4/oggsrc/dirdat/mt
DDL INCLUDE ALL
table ogguser.*;

GGSCI (sourceGG) 37>

Dump Conf:

GGSCI (sourceGG) 37> view params dpump2

extract dpump2
userid ogguser, password ogguser
rmthost targetGG, mgrport 7809
rmttrail /u01/app/oracle/product/11.2.0.4/oggtrg/dirdat/pt
passthru
DDL INCLUDE ALL
table ogguser.*;

GGSCI (sourceGG) 38> 

Replicat Conf:

GGSCI (targetGG) 37> view params rep4
replicat rep4
assumetargetdefs
handlecollisions
userid ogguser, password ogguser
DDL INCLUDE ALL
DDLERROR DEFAULT IGNORE RETRYOP
map ogguser.*, target ogguser.*;

GGSCI (targetGG) 38> 

Thanks!

I was trying to implement Master-Slave Database Replication on two systems.
I followed the steps from the following links
https://www.youtube.com/watch?v=DmQWcU2INqQ
and
Master Slave Replication

But in both cases, I ended up with

Slave_IO_Running: Connecting
Slave_SQL_Running: Yes

I've tried to check the network connection between the machines and they're able to ping each other successfully.
Disabled the antiviruses and Firewalls on both systems
Added an alias for the slave to access the master machine, Working.
Both machines using 3306 port for mysql.

Last_IO_error: error connecting to master 'user01@192.168.2.46:3306' -- retry-time 60 retries: 1

Just wondering if SQL Server use different technology for Transactional Replication and Alwayson High Availability or is it same behind the scene. Basically I need to know if SQL Server use same or different technology(protocol/process) for Replication and Synchronizing the secondary replicas in High Availability in SQL Server 2016. Thanks in advance.

I have moved into RDS MYSQL 5.6 and now I have a problem. I have 5 read replicas and a/z master.

I am trying to alter a table and want to change a column value and also on some tables I want to add a new column. Although this operation is non blocking on MYSQL 5.6 but when it gets replicated to the slaves it causes slaves to lag for entire duration of it, I cannot afford slave lag as we are 24/7 operations.

I tried doing SET sql_log_bin = 0; to skip the query to the slave but RDS do not allow this, otherwise I could have done slave (one each) --> master approach and eventually changing on master.

Anyone has any advise how to go on about this in RDS MYSQL 5.6

I've never setup streaming replication before and was unsure if the following setup is possible with the latest postgres:

• I have two data centers, with two dedicated database servers in each.
• One data center is the main center and runs all our applications, this is where we want Postgres running with synchronous streaming replication between master and slave.
• The remote data center exists for disaster recovery, and we want the main data center Postgres instances to asynchronously replicate to the remote data center.

Is the above scenario possible? Having Master1 and Slave1 replicate synchronously in one data center, and then having Asynchronous replication between Master1 and Slave2/Slave3 which are hosted in a remote data center?

(Hi; sorry for my English) My question is: how can I restart MySQL replication on a slave server. At first sight everything seems to be normal but when I check with

SHOW SLAVE STATUS\G

besides Relay_Log_Space, Read_Master_Log_Pos and Seconds_Behind_Master which continue to increase. Other data remain fixed for several days. I tried STOP/START SLAVE; but nothing has changed.

root@localhost [mysql]> SHOW SLAVE STATUS\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: x.x.x.x
                  Master_User: slave_replicator
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000103
          Read_Master_Log_Pos: 197827259
               Relay_Log_File: mysql-relay-bin.000002
                Relay_Log_Pos: 149672940
        Relay_Master_Log_File: mysql-bin.000029
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table:
                   Last_Errno: 0
                   Last_Error:
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 305160334
              Relay_Log_Space: 65277287216
              Until_Condition: None
               Until_Log_File:
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File:
           Master_SSL_CA_Path:
              Master_SSL_Cert:
            Master_SSL_Cipher:
               Master_SSL_Key:
        Seconds_Behind_Master: 1724670
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error:
               Last_SQL_Errno: 0
               Last_SQL_Error:
  Replicate_Ignore_Server_Ids:
             Master_Server_Id: 3464562
                  Master_UUID: 727b7e74-325f-11e6-9b54-faa1cd739fa9
             Master_Info_File: /var/lib/mysql/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Reading event from the relay log
           Master_Retry_Count: 86400
                  Master_Bind:
      Last_IO_Error_Timestamp:
     Last_SQL_Error_Timestamp:
               Master_SSL_Crl:
           Master_SSL_Crlpath:
           Retrieved_Gtid_Set:
            Executed_Gtid_Set:
                Auto_Position: 0

I recently installed two identical default installations of MySQL 5.7 under Ubuntu Server 16.04, and configured them to do a binary log replication. Until now this has been working fine, but suddenly the replication stops continuing and the slave query thread runs at 100% CPU without doing any work.

After some searching I found that the slave status tells that it is way behind master. Using mysqlbinlog on the binlog file indicated by Relay_Master_Log_File and position Exec_Master_Log_Pos, I found out that the statement executed at this position is:

SET @@SESSION.GTID_NEXT= 'ANONYMOUS';

Somehow the slave hangs when trying to execute this statement, sending the CPU load to 100% (which is how I discovered the situation in the first place).

Except by having the slave skip that statement using SET GLOBAL sql_slave_skip_counter=1 it is unclear to me what is the actual cause of this issue, and how I should solve this.

Any help would be really appreciated!

While replicating from Mariadb 10.1 to MySQL (5.0, 5.1, 5.5) or Mariadb (5.2, 5.5) lower versions, if master's binlog_format is set to row, the replication failure occurs with the following message at slave (show slave status \G;):

Last_Error: Table definition on master and slave does not match: Column 18 type mismatch - received type 19, rtmariadb10.empdetails has type 11

Here

Master: Mariadb 10.1,binlog_format: row ; 
Slave : Mysql 5.1, binlog_format=statement/row/mixed(any one of these) 

Can someone please help to solve this issue?

I've setup a virtual machine on Azure with Ubuntu 16.10 and Mysql 5.7 for a database replication Master/Slave from another server.

I followed this article: https://www.opsdash.com/blog/mysql-replication-howto.html

All seems to works correctly, replication works but I've serious problems with the use of DATA LOAD INFILE. If I use this command, the replication doesn't works.

I tried with relative varible "slave_load_tmpdir", creating a new directory '/var/slavetmp' and updating my.cnf with these values, but this is the error in mysql with "SHOW SLAVE STATUS":

Unable to use slave's temporary directory /var/slavetmp - Can't read dir of '/var/slavetmp/' (Errcode: 13 - Permission denied)

Have any ideas?

Thanks in advance

My idea is to use user session and transaction id to have a Unique id that stores each action performed by user in to a temporary object . when exception occurs during this session we will log these actions else temporary object will be discarded

By this famous guestbook example:

https://github.com/kubernetes/examples/tree/master/guestbook

It will create Redis master/slave deployment and services. It also has a subfolder named redis-slave which used for create a docker image and run Redis replication command.

• Dockerfile
• run.sh

The question is, if deployed the Redis master and slave to the k8s cluster. Then how to run that command? Deploy a new container? That will not relate to the slave container already deployed.

Is there a better way to do Redis repliaciton between master and slave running in k8s cluster?

My company is trying to implement a MySQL failover mechanism, to achieve higher availability in our webservices tier - we commercialize a SaaS solution. To that end we have some low-end VMs scattered through different geographical locations, each containing a MySQL 5.5 server with several DBs, that for the time being are merely slave-replicating from the production server - the objective up until now was just checking the latency and general resilience of MySQL replication.

The plan however is to add a Master-Master replication environment between two servers in two separate locations, and these two instances would handle all the DB writes. The idea wouldn't necessarily imply concurrency; rather the intention is having a single one of the instances handling the writes, and upon a downtime situation using a DNS Failover service to direct the requests to the secondary server. After the primary comes back online, the b-log generated in the meantime in the secondary would be replicated back, and the DNS Failover restored the requests back to the first one.

I am not an experienced administrator, so I'm asking for your own thoughts and experiences. How wrong is this train of thought? What can obviously go wrong? Are there any much better alternatives? Bash away!

Thanks!