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!
Related
I am trying to connect to a client's DB2 v7.2 database in Linux.
I am pretty new to DB2 and could not find 7.2 odbc driver in IBM site. The earliest is 9.1 odbc driver. Is this compatible with v7.2 ?
IBM does not make such old legacy drivers publicly available, for good reasons.
Genuine IBM customers always have a way to acquire legacy drivers however, although this is wholly dependent on who you know.
The v9.1 ODBC driver might have trouble accessing v7.2. It rather depends on which fixpacks are deployed (client and server), which operating-system (for client), and what authorization level you have for the target instance, and what rights you have at the workstation end, apart from the level of competence needed. This is not work for beginners.
Keep in mind that legacy drivers may not be able to install on modern workstation operating-system versions (for example , they might need the workstation operating system to be also a legacy version).
Another approach is to have a detailed understanding of exactly how (with which versions and tools) the client currently connects to that legacy database, and then seek to emulate that mix of versions, possibly by cloning.
This is not a programming question so stackoverflow may not be the correct forum. There are IBM specific forums run by IBM which may help.
Good day. I just finished upgrading my AWS RDS database engine from 9.6.22 to 10.17. I used these steps to make the upgrade using the AWS Console:
Create snapshot of target database to upgrade
Restore snapshot
Upgrade the restored snapshot's (which is now a new instance) DB Engine version.
After I did all of this, everything seems fine but when I access the database, this warning message appears
WARNING: psql major version 9.6, server major version 10.
Some psql features might not work.
I did not continue on my testing because I want to know what is the meaning of this first. Because I am fairly new in AWS as a whole. Thanks!
The meaning is that just because you are connecting to an upgraded database on some machine run by Amazon, the PostgreSQL installation on your local machine was not magically updated. psql from version 9.6 doesn't know what metadata tables were changed in v10, what features were removed and so on.
It would be a good idea to install a more recent version of PostgreSQL on your machine. By the way, upgrading to v10 was not the smartest move, as that version will go out of support in less than a year. You should upgrade to the latest version that your service provider offers.
The client program psql you are using to connect to the database is from an older version than the database it is connecting to. Some of the introspection features might not work. For example, psql from 9.6 won't know how to do tab completion for commands that were added to the server after 9.6.
This is generally not a major problem for psql (unless the server wants to use SCRAM authentication), but for optimal experience it would be good to install a newer client. Other tools like pg_dimp might not with at all against a server newer than they are.
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
This question might be slightly subjective, but I am unsure where else it would be better suited.
I have used Orchard on a number of projects where the server was Windows Server based - integrating with AD, SQL etc to provide a MVC based portal - like stealing candy from a toddler!
I have been exploring MonoTouch recently, and installed Orchard on OSX under ModMono as per http://docs.orchardproject.net/Documentation/Running-Orchard-on-Mono.
It all seems to run fine, and fast, but I am unsure whether to back this on a commercial venture. I have always used MySQL or MSSQL as the DB, whereas my current install is running PostgreSQL - something new (which is always good).
Does anyone know of any sites which use Orchard running on Mono, with ModMono (Apache2) and PostgreSQL?
I plan to deploy to a cloud server running CentOS and Mono to do further testing before going any further, but think it could be an exciting avenue to explore.
I can't say I know of any sites that run Orchard on Mono commercially but I do know of a lot of sites that use Mono, Postgresql and CentOS. But if it works on a Mac running Modmono and Postgresql then it should work on CentOS.
The only issues that you may face running on Linux is case sensitivity. If you do run in to case sensitivity issues when you are trying out Orchard on Linux then you may want to configure your site to use Mono IOMAP temporarily until you fix an issues with case sensitivity.
This is a very reliable and cost effective stack. It may take a bit of research and problem solving to get up and running initially but once it's running it should be very stable.
I am currently near the end of porting an application that is going to be using Mono, Postgresql and Ubuntu running on Amazon EC2. I believe that Ubuntu is better than CentOS when it comes to Mono as it is much easier to setup and seems to be better supported. You can use the badgerports repositories located here if you want to try out the latest version of Mono on Ubuntu.
I have installed Oracle 10g and now want to install 11g also...How can I do it?.. I know that ORACLE_HOME environment variable need to be configured for each "oracle"..
Can you describe me steps how to do this?
Thank you very much in previous.
Thank you It helped me so much...
The most important is that I should have chosen %ORACLE_HOME% like %ORACLE_BASE%...
Just %ORACLE_BASE% should be the same...And it works.
There's ususally not a lot of reasons why Oracle databases of different versions cannot run on the same machine, be it Windows or Linux/Unix. Reasons can be if you run Clustering software, which may not be of a lower version than any database version involved. Similar with Oracle Grid or Cloud. Other than that, I can't really think of reasons, but there may be excpetions, linked to specific OS. Usage of ORACLE_HOME's is how Oracle manages different databases and versions. The Oracle Homes should be different for each database, the Oracle Base should be the same, the central inventory must be shared, and the ownership (of Oracle Homes) may be shared or separated. Sharing Oracle Home is an option for advanced users only.