I'm currently experimenting van different versions of Data Pump. (Oracle)
We have a bunch of dev oracle servers at work. Versions 11, 12, 18 and 19.
If I recall correctly, Oracle 19 should be backwards compatible with 18, 12 and 11.
I can successfully connect to the Oracle 12 server using the Oracle 19 client, but when I try to do a export using Datapump I get the following error:
Any ideas? Shouldn't Data Pump also be backwards compatible?
Thanks in advance.
Generally speaking, you should
export data using the lowest data pump export utility version involved (12c in your case)
import data using the target database version's data pump import utility
For more info, see My Oracle Support (e.g. Export/Import DataPump Parameter VERSION - Compatibility of Data Pump Between Different Oracle Versions (Doc ID 553337.1)
Related
I want to use offline and locale data base and when network is available, send data to the server. What are solutions ?
Server is linux running postgresql 9.5 or higher. Local and offline data base is Libreoffice 6.2.7 or OpenOffice for WINDOWS7 and WIndows10 64bits
I think about sql code to do the task but I never found how to deal with two database in an sql code.
It is like INSERT ... TO ... database.table ...
I'm hoping this question is appropriate for here, but, I'm running out of options.
I have come across a Sybase 8 database from c. 2000. I'm being asked to get it up and running; however, even using Sybase Anywhere 16 won't allow me to connect to the .db file.
My experience with Sybase is from a long time ago. Can anyone suggest or know of a way to get it up and running or even get it upgraded? Ideally I'd like to export the database and get it out of Sybase and into another DBMS.
Thanks in advance.
Databases from version 9 or older of SQL Anywhere must be reloaded in order to be use with SQL Anywhere 10 or higher. You will need to use the dbunload utility to reload the database into a new database and then you can use it with SQL Anywhere 16.
You can do something like: dbunload -c uid=myuser;pwd=mypassword;dbf=old.db -an new.db to create a new database from the old one. There are other dbunload switches for dealing with page size, encryption, and other options.
Disclaimer: I work for SAP in SQL Anywhere engineering.
I am using SQL Anywhere 17, but I believe you can do the same in Sybase Central 16.
I want to import an existing FilemakerPro (local, no server version) database into PostgreSQL. I have configured my two ODBC drivers for FMP and PostgreSQL. The two appear in the ODBC Manager and they are connected properly. Now my problem: I don't find any comprehensible explanation how to import the database in Postgre! I imagine that I need to write a bit of SQL-code but I didn't find any commented one.
I have seen a lot of inormation like this: "I suggest looking at FileMaker ODBC to extract data, or using Postgres ODBC driver and insert data from FileMaker with "Execute SQL" script step into PostgreSQL tables." But nothing that explained more precisely.
Could anybody help me by telling what to do inside PostgreSQL to import the database?
Thanks a lot for your help!
I want to import data from a Postgres database to a SQL Server database.
The Postgres database is using SQL-ASCII encoding because the databse was migrate from old ISAM database.
So, if I want to Import the data into SQL Server I have two problems:
Characters like ä,ü,ö are not supported
Numeric Default type not supported too.
For Dataimport I use Postgres SQL Native Provider in Microsoft Integration Services.
To convert the data about dataconverting in Microsoft Integration Services not running.
To try convert data directly in postgres - Example:
convert_to(lieferanten.lief02::text, 'UTF8'::name) AS convert_to
--> Result in SQL Server is --> can not Import!
So I don't know how I can solve this Problem. Anybody have idea or can help me?
Fix the data in PostgreSQL first.
There may be several different character-sets and encodings mixed up in the database (since SQL-ASCII makes no guarantees about the data).
It can be as simple as dumping the database and running iconv against it, or it can be a tedious semi-manual process of correcting value-by-value.
Once you can import it into PostgreSQL as UTF-8 (or ISO-whatever) then you can transfer it to SQL Server.
I'm being demanded to develop a new software that must be built over SharePoint and use Microsft SQL Server 2012.
I have a DB in Postgres, and some of its tables will be used in this new project, so I must import these tables, everyday. I'd like to use WebService to do it, but they want it to be done DB-to-DB directly.
Postgres-to-Postgres is already done and it "works", but importing to Microsoft is being troublesome.
Does anybody know some MSSQL tool that can connect to Postgres and do the import?
Typically for this sort of situation (assuming that it'll be a process that's repeated on a regular basis) you'd use SSIS (comes with most versions of MS SQL Server). Have a look at the first several hits on this Google search, especially the first one.
Another option is to connect to the Postgres database directly from your application via ODBC, and eliminate the redundant copy of the data - and get real-time updates instead of having to wait for the next execution of the SSIS job.