I have an Oracle Enterprise Linux server 7.8 and I am accessing it through putty software from my PC running Windows 10 OS. I have installed the same version of SQL Server on both the Linux server and my Windows PC.
What I am trying to do is a transactional replication where I want to set Linux server as both distributor and publisher and Windows PC SQL Server instance as subscriber.
So, my question is whether this is possible or not?
Because I have tried all possible way of my knowledge and still I was not able to configure replication successfully....
Related
I want to work with Mongo Compass running in Windows and connect to MongoDb server in WSL2.
Both MongoDb services are working fine (I can connect from Windows to MongoDb server on Windows and from WSL2 to MongoDb server on WSL2).
Windows build 19042.
Thanks!
Unless you are running a pretty old build (from 2018 or earlier) WSL includes a feature known as Localhost Forwarding, which should automatically allow you to use localhost in Mongo Compass in Windows to connect to the database running under WSL.
However, sometimes that features "breaks", especially if you hibernate or turn on Windows with the Fast Startup feature enabled (which is the default).
If this is the case, try wsl --shutdown and restart WSL. Then disable Fast Startup. If you do need to hibernate, remember that you may need to wsl --shutdown again to restore the forwarding mechanism.
See this answer for some additional details.
As far, as I understood, to access something running on WSL from you host-machine(Windows) you need to manually map host:port of your WSL MongoDB server to localhost.
This link describes the topic, I hope:
https://learn.microsoft.com/en-us/windows/wsl/networking#accessing-a-wsl-2-distribution-from-your-local-area-network-lan
After mapping your port you probably will connect to your MongoDB server via Compass with mapped address and port.
Hi I want to connect to remote MongoDB server without using SSH tunneling(Both the client and server systems will run on windows OS). Is there any way to connect.
I am trying to set up a server in a virtual machine using the Oracle VirtualBox. I use Ubuntu 18.04 LTS in the VirtualBox. I use PostgreSQL as my database.
In my Tomcat, I have a property file where I provide the database URL and password. I want the tomcat that is set up in the VirtualBox to be able to access a local database that is set up using PGAdmin in my Windows machine in which the VirtualBox is installed.
Is it possible to do that?
When connecting to a SQL server DB running on my host machine from a VM, I use the IP address to connect.
You can run ipconfig (or your OS's equivalent) to find the IP address of the machine serving the DB, then try to connect from your host machine via that IP address instead of the machine name.
There might be some VM-specific settings you need to tweak to allow network access between the VM and host, refer to this post for more info. Usually I have to set my VirtualBox network mode to bridged adapter.
Database server os = Ubuntu 16.04
client machine= Windows os 8.
we are not able to connect database server from pagAdmin which I have installed on my laptop (while its prompting for password).
Have you configured "pg_hba.conf" file in the server for remote access? IF not, you need to add following in the file
# vi /var/lib/pgsql/data/pg_hba.conf
host all all 192.168.101.20/24 trust
192.168.101.20/24 is just an example, you need to write clients IP and port.
I have a perl script running on a Debian virtual machine on VMWare. This script is supposed to connect to a DB2 database running on my Windows 7. When I try to connect with that string:
my $dbh = DBI->connect("dbi:DB2:DATABASE='nmap'; HOSTNAME='192.168.252.167'; PORT='50000'; PROTOCOL=TCPIP; UID='db2admin'; PASSWORD='password'";
The program returns an error and it says that db2 is not installed on Debian. How can I tell my script that the DB is running on a different machine? The virtual machine has a bridged connection with 192.168.252.178 as IP address.
You need the DBD::DB2 package installed on the client machine (your Debian VM in this case) if you want to connect to a DB2 database with DBI.