Using SQLite to Oracle conversion and synchronization tools.
When launching the DBConvert or DBSync application in GUI mode, it seamlessly guides you through the steps to initiate database migration or synchronization:
1. Connect to SQLite source database.
Specify the username/password and host/port parameters if your source database requires login credentials.
![Connect to SQLite source database from DBConvert]()
2. Connect to Oracle destination database.
Specify parameters for the destination database similar to the source, defining connection settings and username/password pairs.
![Connect to Oracle target database from DBConvert]()
NOTE #1: Each DBConvert or DBSync tool's name comprises two different databases, enabling any specified database to operate as the source or destination. Furthermore, the same type of database can function as both the source and destination.
NOTE #2:
Connections to cloud databases (e.g., Amazon RDS, Google Cloud, or Azure SQL) aren't explicitly specified in the user interface but use the same settings as traditional on-premises databases.
NOTE #3: Connections to source and target databases remain active until you close the DBConvert/DBSync application or reopen new connections.
Refer to our documentation for
specific source/ destination configurations for different
databases.
3. Configure database migration options.
Specify the tables, fields, indices, and views you want to transfer to the Oracle destination database by checking/unchecking the corresponding boxes.
Customize general database/ tables settings. Or configure specific table , field, index object individually when
migrating data.
Explore our articles in the user's manual about Configuring database migration options. for detailed information.
The screenshot below summarizes the general features available in DBConvert software.
4. Detection of potential database migration issues. Errors and Warnings
The database enforces certain relations on the data, and on the customization step, an intelligent error checker verifies all possible data integrity and referential integrity issues. It highlights any problems before migration starts.
By default, DBConvert attempts to automatically map the database types of the source SQLite database to the closest equivalent of the target Oracle
database types. However, you can manually change the data types for the entire database globally using the
"Global mapping" or individually for each field.
Explore the Intelligent error checker for more
information. on errors and warnings
5. Execution. The final stage of data migration.
Initiate the conversion or synchronization process after configuring source and destination databases in the previous steps.
Click the "Commit" button to start
conversion. Here, you can also monitor the migration/synchronization process.
Optionally save connection settings and configuration parameters into the session file to
schedule the launching of sync or migration jobs regularly.
![Execution step of DBConvert products]()
Explore more about the options available during the execution stage
Command line mode
Pass previously saved sessions as parameters to the Command-Line DBConvert Client. A session retains SQLite source and Oracle target database connection settings
with other specified options.
Example:
C:\Program Files\DBConvert\oracle2sqlitePro\oracle2sqlitePro_Cons.exe /Session:"Session_Name"
NOTE: First, run the software in GUI mode to create a session file with initial parameters.
Built-in scheduler.
Our applications include a built-in scheduler to run database migration and sync jobs at specified times. Set the scheduled date and time to execute job sessions automatically.
Find more Information about the built-in scheduler