Running an agent on a different machine is no more complex than copying binaries to the new machine and running a single executable file.
Firstly, you need to run the Omni Loader executable. On Windows, that's a file named OmniLoader.exe, while on Linux, it’s simply OmniLoader. Running Omni Loader requires just a single parameter and that's the port where it should listen as a local web server. Omni Loader has a whole web server built in, used for a web application with a user interface for the Omni Loader.
To make it as simple as possible, we also provide a simple batch file called run-standalone.bat which starts Omni Loader listening on a default port of 5000. When you head over to the browser after you have started Omni Loader and type in localhost:5000, you will be presented with a modern and very easy-to-use web application where you can control all aspects of your migration.
When you want to shut Omni Loader down, you need to stop the console process that you have started earlier.
Cluster Mode is only slightly more complex than Standalone. The process itself is virtually the same, but you need to run separate agents that connect to Omni Loader over a network. Omni Loader acts as an orchestrator to the agents. You can run a single agent on the same machine where the orchestrator is but do not run more than one as that would not result in higher performance.
Omni Loader Cluster is designed to run on as many machines as you have available for the migration. The process of running Omni Loader as an orchestrator is the same as running it in a standalone mode, but you need to supply an additional parameter --cluster. When you go to add more machines, the process of deploying the agents is equivalent.
Run the Omni Loader agent executable (OmniLoaderAgent.exe on Windows, or OmniLoaderAgent on Linux) and give it a single parameter, the IP:port of the Omni Loader orchestrator.
To run Omni Loader in Console Mode, simply supply the -job parameter. This parameter should specify the full or relative path to the JSON job descriptor file. Omni Loader will run through the whole migration after which you can examine the logs to ensure that everything went as expected.
One of the log files is a detailed JSON log file designed for machine consumption.
Ready to get started?
We support over 20 databases at this point and are very likely to support yours. Take a look at the whole list on our databases page.
Omni Loader easily migrates absolutely huge databases. Our competitors either require a lot of time-consuming setup time or the performance is not suitable for very large databases.
Please contact us and we will discuss your needs.
We will gladly organize a demo of Omni Loader for you. Please reach out by filling out the form at Spectral Core and provide your work email address (not an anonymous one). We can only work with you if your budget is at least $30,000 per year.
If you would like a demo of Full Convert, we can't accomodate that as Full Convert is a low-cost tool. Instead, please use its free trial to ensure it works for your specific needs.
Please write to email@example.com.
At this time we do not offer phone support. With customers in 98 countries we've been doing customer support for 20 years and phone support does not work well for anyone. Instead, please use email to open a support ticket by writing to firstname.lastname@example.org. One of our developers will make sure your issue is taken care of.
For on-premises installation please contact us to obtain a license. Once you do, you will get native executables for Windows and Linux. Run as many agents as your license allows to scale to the perfromance levels you need.
Absolutely - that's the core functionality of Omni Loader.
CDC is available for Oracle, SQL Server, and MySQL/MariaDB source databases. All target databases automatically support data ingestion from CDC-enabled sources.