I have installed Symmetric-ds-pro 3.12.2 on my 3 servers and configured multi-master replication among them. The node.properties file on my 1st server, created an entry auto.config.registration.svr.sql.script=/symmetric-config-multi-master.sql.
But nowhere I am able to find symmetric-config-multi-master.sql on my server. Where can i find it?
Related
I develop on a Mac (High Sierra) with MAMP (basic, not Pro), and I have several different Drupal sites in ~/Sites/<sitename>.
Currently, if I change Document Root to work on a different site, I get errors on the new site until I delete the database .frm and .ibd files, as well as the log/data files, and re-import the database from a SQL dump.
Errors are:
2019-11-04T20:01:50.231324Z 2 [Warning] InnoDB: Cannot open table
/cache_bootstrap from the internal data dictionary of InnoDB
though the .frm file for the table exists. Please refer to
http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for
how to resolve the issue.
Files I have to delete:
/Applications/MAMP/db/mysql57/<sitename>/ (entire contents)
ibdata1
ib_logfile0
ib_logfile1
Re-importing the SQL database each time I want to work on a different site is getting really old. It is not a crisis, since this is just local development and it's not impacting the server, but it is seriously annoying. Has anyone else seen this?
How to add new driver into database through KNIME preferences? Generally,
File-> Preferences -> Add File/ Add Directory
The files accepted are only of *.jar or *.zip.
MY QUESTION
I have installed ODBC64 into my PC. Now I need to add that file into knime preferences and use the Driver into Database Connector node.
How to add and use the file into my Knime?
And What is meant by Database URL jdbc:mysql://host:port/database_name
Host and port?
Can anyone please briefly explain and help me out?
I'm assuming based on your database URL of jdbc:mysql:// that you are wanting to connect to a MySQL database? Based on that, then there is a thread on the KNIME forum which explains pretty much all of your question, but the process is the same for any other sort of database. The steps are as follows:
Download the jdbc driver (e.g. from https://dev.mysql.com/downloads/connector/j/ for MySQL) - NB KNIME now comes bundled with several drivers already installed - MySQL is one of those - in the Database Connector node the drivers installed are listed.
In the database URL, you need to change those parts in <> - i.e. the hostname, port number and database name. Hostname may be localhost if it is a local database. The port number you will need to find from your database administrator, or will be what you set it up to be if you are running a local database (3306 is the default for MySQL), so for a database called 'myDB' on the default port on your local machine, the url should be jdbc:mysql://localhost:3306/myDB
For some of the shipped drivers, there are also connector nodes, e.g. MySQL Connector, SQLite Connector, PostgreSQL Connector etc, which still require the server name/port and database name, but take them as individual inputs rather than requiring editing of the URL
Recent versions of KNIME are based on Java 8, which dropped support for ODBC, so you should first find an alternative driver for your database and only after you can connect to that with KNIME as described on the KNIME documentation page for DB connectors.
You have several nodes which allow you to connect to a DB (especially MySQL).
I remember there was a dedicated MySQL node for connecting with the DB.
Just remember this: you have to input the IP adress : port, then insert credentials and point to the DB you want to open by default.
I have configured a FailOver Cluster Instance (ClusterDB) with two nodes for SQL Server 2014 on Windows 2008 R2 SP 1. It's my first cluster so I'm not very sure of a lot of things, this is new for me so keep this in mind.
I created a shared folder of my backups on the cluster and successfully accessed from my Test Server (Windows Server 2012 and in the same domain). But from a few days now I can't access to this folder, when I log in into my Test Server and try to access to \ClusterDB on windows explorer, throws me an error as it cannot find the machine.
The cluster has an internal IP and a external one for the Server and both are online, if put \InternalIP on my test server, it can connect, but this not shows the shared folder (I suppose it should be here but not sure why not).
From the nodes of the cluster (node 1 and node 2) I can connect to \ClusterDB and see the shared folder.
I checked the permissions for this folder and the main user (user which I log in on my test server) has permission to read this folder
Could anybody help me to fix this?
I know this is a really old post and some people might get upset that I'm posting to it, however this is the result that turns up in Google when searching for an answer to this issue.
In my case the problem was the drive letter of the shared drive was removed by the failover cluster. To see this open Failover Cluster Manager, click on the File Server role, and select the resources tab at the bottom. You should see a Storage category with the drive being used listed, right click on this and select change drive letter.
The drive letter needs to either match the drive letter listed in the shares tab or you need to adjust the shares listed in the shares tab to match the new drive letter you assign to it.
I'm not an expert with TSQL so have patience with me please. So recently I was doing a project in TSQL on my local server using SQL Server 2008 R2 Management Studio. I was reading my files from a temp file on my C: drive and bulk inserting them into tables at the time.
Then I went and moved to a regular server instead of my local server on my machine.
It took me a bit to realize that I no longer had access to my local machine folders and files, and that is causing me issues.
I've read that one solution is to create a mapped drive on the server, but this is not an option for me.
So my question is what are other options for me? Could I use UNC paths to access my files or anything else?
The files I want to access are regular text files that are comma-delimited and newline terminated.
(I saw somewhat similar questions to mine, but there's seemed server specific or specific to their particular issues. Also none of their questions were answered.)
Actually a mapped drive won't work either because the account SQL runs under by default (local system if I recall) will not have network access.
So, the more reliable way to do this is definitely with a UNC path BUT there is more! (I've done this several times when I've needed to move database backups and log backups across servers for mirroring).
How?
On the SQL server machine AND the other server that will host the share, create a new user (same username and password on both machines) - assuming your not using AD. The user needs not be in any groups at all other than the users group but it must be called the same in both servers and the password must match.
On the SQL server machine change the account that SQL SERVER is running under. This is done in the SQL server configuration tool. Do not try to do this yourself via windows services. Choose the user that you created in no 1 above. Note you have to enter the pw. Restart SQL after you've changed it and verify SQL still runs fine. It should run just as before but now is running as a particular user with all the permissions of that user (which actually are very limited anyhow, but at least the user can access network resources).
On the remote server, make sure the new user has NTFS permissions on the folders that will host your share. Read/write perhaps or just read if SQL is only reading data.
On the remote server, create a share pointing to the appropriate folder that you set permissions for above. Make sure if you're using share permissions that the new user also has permissions on the share (not just on NTFS on the drive).
Once all of this is setup, your SQL scripts simply use the UNC path that points to the remote share and since SQL is running "as" a user with access to that share, SQL will see the files just fine!
Example, I have 2 server, each server using a copy of linux cpanel.
I first install free trial script into subfolder reside in Server A.
eg:
sample.com/service/username1
sample.com/service/username2
sample.com/service/username3
Then when people decided to upgrade, I gonna move all files to theirnewdomain.com, including database etc into Server B (another copy of cpanel).
In such case, what is the best suggestion to perform this kind of upgrade?
Move files from serverA to ServerB, possible to automate it? Zip it into a common place for Server B to pickup?
Moving mysql db created in ServerA's cpanel into ServerB's cpanel, best way? Recreate a copy into ServerB, then dump data into the fresh copy?
Seems like not possible to directly modify the db pointing in cpanel database, because its now 2 server, each server got a copy of cpanel. Things are separated.
Note, this process need a few task to be done in the process. Eg: update to centralized database of the file moving status, domain creation status, db creation status, and etc...
Any idea?
How actually other service that host in multi server work?
In general, you probably want to follow the pattern of running a backup script and then extracting it on the new server. You may find some hints in this description of a manual process.