I am running OrientDB 2.2 Community Edition and I have already used teleporter to import a SQL database consisting of 22 tables and 11 million records. I dropped a vertex class as I needed to change something and when i went to reimport a table using teleporter i got this message...
ERROR: Synchronization not allowed in OrientDB CE. Execution will be terminated
Is there a way i can import this table and join it to the corresponding vertex classes already in the orientdb database without dropping the whole database and reimporting everything from scratch (which took about 5 hours)
Thanks :)
Synchronisation is not allowed in OrientDB Community Edition, but it is in OrientDB Enterprise Edition. Thus you just have 2 choices:
try the OrientDB Enterprise Edition (45 days trial) and exploit the synch feature. Download link: http://orientdb.com/orientdb-enterprise/
drop the old database and migrate you relational database again from scratch.
I Hope I was helpful.
Related
There are several ways to upgrade from V8 what I read on several fora.
One of the methods is do exports of "main tables"
Which tables? And it only works good with smaller DB's.
And how big is big ? I have only Accounting , CRM, and Website modules on my Odoo 8 and I am self employed, not an enterprise.
I know that you can easily upgrade from 8 - > 10 .
If I use the OpenUpgrade software, does it make a new DB which can then be used with a new instance of Odoo with V12? Or does it migrate the complete instance db + software?
If I downgrade modules in V10, will the upgrade to V12 be easy. Or are there special tables written in the DB who can block the migration from V10 -> V12 ?
Migrations are tricky. The basic process will be:
Make a copy of your database and ship it to a separate environment
Run OpenUpgrade V9.0 with the --upgrade=all flag on the database
If you come across any errors, handle them individually by looking at the error and making the necessary changes to your modules
Once the upgrade completes, you can move forward and do the same for OpenUpgrade V10.0, V11.0 and V12.0
Copy your database back to production
Currently we are using microstrategy as a reporting tool 11.1 version and using Oracle DB - micro strategy metadata, Statistics , history all installed in Oracle
now we are planning to move Db from Oracle to Postgres. just wanted to check if microstrategy support Potgres DB
Here is the list of certified and supported versions: Repositories
From personal experience I can say PostgreSQL v9,v10 and v11 runs fine as metadata repository. Tested v9-v12 as DWH too, all working without problems.
As far as I remember they didn't deliver the bundled driver in one of the MSTR-versions (2019-something), but that seems to have changed in MSTR-2020 again. Not a showstopper, but something to be aware of.
I am also running PG-11 as repo for History List too, but you definitely won't get help from support for this. OT: They even made me switch from MariaDB to MySQL for a support case (don't really blame them though, it's not certified and that's that).
My last attempt at running Statistics-Repo with PG is a long while ago and it didn't really work out of the box. Don't know what the situation is there. You might have to consider moving to PlatformAnalytics and/or MySQL(/MariaDB) for this too. EM only receives bugfixes from MSTR-2020 onwards, so this seems to be future-proof (EM discontinued from 2020 onwards?)
This mostly reflects our experience, the only certified PG version for MSTR 11.1 is PG-9 and only for the MD-Repo!
I trying to connect to DB2 database through SQL Developer. I followed following steps create connection:
1. Open SQL Developer
2. Go to Tools > Preferences > Database > Third Party JDBC Drivers.
3. I added third-party JDBC driver path entries (db2jcc.jar and db2jcc_license_cu.jar)
As soon as I try to create connection I get below error
Oracle SQL-Developer Version 17.2 works fine for me with Db2 Version 11 for Linux x64 and I am using a recent Type-4 jdbc (db2jcc4.jar) driver from IBM.
You question shows that your Db2 jdbc driver version is very old (Version 9.7 fixpack 5) and out of support, so you should upgrade to the latest available Db2 client for your (unspecified) operating-system. Also you should ensure you are using the latest release of the Oracle-SQL-Developer for your operating system.
As your question gives no facts about your versions of Oracle or Db2 products or operating systems, this is the best advice that is possible.
I got the same problem, it turned out SQL Developer doesn't display tables for DB2, but still allows to perform SQL queries. If you know table names, you will be able to select data from those tables if you have enough permissions to do so.
You can test ability to perform SQL queries by selecting DB2 version (SQL below is valid for DB2 12.0)
SELECT GETVARIABLE('SYSIBM.VERSION') AS VERSION FROM SYSIBM.SYSDUMMY1;
Make sure you don't forget to specify schema while selecting data from your tables!
select * from schema.table_name;
We are currently re-engineering our system (Documents Management System) and we are moving from MySQL to use OrientDB, we are creating the migration tool, but we are faced with the problem of moving the data from RDMS mysql to orientDB, my question is: Is there any tool to easily migrate from MySQL to OrientDB and yes we are using orientDB as graphDB, my orient is v 2.2.10 (i have recently updated from 2.2.6)
You can use teleporter. It is compatible with MySQL.
OrientDB Teleporter is a tool that synchronizes a RDBMS to OrientDB database. You can use Teleporter to:
Import your existing RDBMS to OrientDB
Keep your OrientDB database synchronized with changes from the RDBMS. In this case the database on RDBMS remains the primary and the database on OrientDB a synchronized copy. Synchronization is one way, so all the changes in OrientDB database will not be propagated to the RDBMS
Teleporter is fully compatible with several RDBMS that have a JDBC driver: we successfully tested Teleporter with Oracle, SQLServer, MySQL, PostgreSQL and HyperSQL. Teleporter manages all the necessary type conversions between the different DBMSs and imports all your data as Graph in OrientDB.
NOTE: This feature is available only in the OrientDB Enterprise Edition. If you are interested in a commercial license look at OrientDB Subscription Packages.
I want to use Embedded FireBird with .NET 3.5. I have few queries:
(1) Are there any new developments done on the embedded version by the FireBird community?
(2) Are there any database file repair & optimize (shrink etc.) features in it?
(3) Does it supports Triggers, Foreign Keys, PL/SQL type of things etc.?
(1) Are there any new developments
done on the embedded version by the
FireBird community?
Yes, both the embedded and the client-server version are very active projects.
Using the same embedded version dll for ADO.NET for example, you can use the most recent version of the firebird engine dlls, even if the ADO.NET Firebird provider is not build for that version, but for a previous.
Check the issue tracker here: http://tracker.firebirdsql.org/secure/Dashboard.jspa
(2) Are there any database file repair
& optimize (shrink etc.) features in
it?
Yes, as described here: http://www.firebirdfaq.org/faq324/. You need to install the client-server version of firebird to use GFIX and GBAK from the command line. It is just a few megabytes.
Firebird does not have a "Compacting" feauture to shrink the database. You need to backup and then restore the database to do this. However you can use a firebird database for years without backup/restore (if you are lucky and the hard disk does not die). The only thing that you might need to do is to recalculate all indeces selectivity as described here: http://www.firebirdsql.org/dotnetfirebird/blog/2005/03/improving-query-performance-through.html
(3) Does it supports Triggers, Foreign
Keys, PL/SQL type of things etc.?
Yes. The 2.5 version of the embedded engine also supports accessing the same database file from different proccess at the same time.
Answering your questions:
The Embedded version is like a normal Firebird but encapsulated in a DLL and with some minor limitations. The Firebird Team just released some days ago the 2.5 version of SuperServer, Classic and Embedded flavors. More info at Embedded Firebird Server and Firebird website.
There are tools to repair and optimize databases. Check How to repair a corrupt Firebird database
Firebird is SQL:2003 conformant as stated in Firebird: SQL Conformance. It has triggers, foreiggn keys and stored procedures.
Hope that helps