In my previous post I shared some findings on migrating user and application data between platforms with different endianness, focusing on problems with reducing downtime.
Today I’ll talk more about the complexity of chosen method. It’s not only about complexity per se, it’s rather about the possibility to automate as much as possible in order to allow efficient migration of a big number of databases.
Continue reading “Cross-endian Oracle migration – moving user data – part II”
One can find a lot of sources and materials regarding migrating Oracle databases between platforms having different endianness, even though the choice of possible methods is limited in this case. On paper (slides?) everything looks fine, but then you hit bugs or environment-specific problems. Moreover, in real life the situation is always more complex than moving just one tablespace with just one datafile as shown in many places as an example. Today I would like to add my 2 cents into this topic, focusing on moving user and application data.
Continue reading “Cross-endian Oracle migration – moving user data – part I”
Recently I was working on migrating Oracle 188.8.131.52 database running on Windows, to new hardware infrastructure on Linux. This Oracle version is with us for quite a long time, plus migration from Windows to Linux is quite common (fortunately in that direction…;)), so when I got an error while trying to use Active Duplicate feature to create a standby database, I was quite sure I’ll be able to quickly find the solution either in MOS or elsewhere. Indeed, I found several blog posts with exactly the same error, but solution mentioned there was not working for me.
Continue reading “Migrating from Windows to Linux with Active Duplicate for standby – problem with 184.108.40.206”
If you have performance problems after migrating your BI databases from 220.127.116.11 to 18.104.22.168 or any other performance issue, you should not underestimate SQL Plan Notes, which can point you to the right direction or just let you understand what exactly is going on with your queries. Please check below how SQL Plan Notes helped me to investigate problem I recently encountered.
Continue reading “BI jobs performance degradation after Oracle 22.214.171.124 to 126.96.36.199 migration”