There is this saying in the English language that something is “too big to fail”. It can refer to almost anything, a country, an initiative, a company, etc. What it tries to say is that, whatever the subject, is so big by now that there is simply no chance that it will ever go away again. You may have already heard this saying you may have not. However, I come across this phrase quite a bit in the IT world too. A technology is too big to fail or a company is too big to fail. And yet, the reality is that nothing is too big to fail!
Did you ever wonder or need to know which systems use big endian and which ones use little endian? Look no further, you can query it right out of the Oracle database:
SQL> SELECT platform_name, endian_format FROM V$TRANSPORTABLE_PLATFORM ORDER BY PLATFORM_NAME;
|AIX-Based Systems (64-bit)||Big|
|Apple Mac OS||Big|
|Apple Mac OS (x86-64)||Little|
|HP IA Open VMS||Little|
|HP Open VMS||Little|
|HP Tru64 UNIX||Little|
|HP-UX IA (64-bit)||Big|
|IBM Power Based Linux||Big|
|IBM zSeries Based Linux||Big|
|Linux IA (32-bit)||Little|
|Linux IA (64-bit)||Little|
|Linux x86 64-bit||Little|
|Microsoft Windows IA (32-bit)||Little|
|Microsoft Windows IA (64-bit)||Little|
|Microsoft Windows x86 64-bit||Little|
|Solaris Operating System (x86)||Little|
|Solaris Operating System (x86-64)||Little|
|Solaris[tm] OE (32-bit)||Big|
|Solaris[tm] OE (64-bit)||Big|
Just because you can doesn’t mean you should
I still see it happening that people put object, i.e. tables, etc. in the SYSTEM or SYSAUX tablespace. Sometimes it’s done deliberately, sometimes it happens automatically by creating a table in the SYS schema. Well, let me tell you, it’s a really bad idea. You should not put any kind of user object into those tablespaces. Even the Oracle Database Documentation warns you of doing so:
Run your Oracle database inside a Docker container
Oracle has released Docker build files for the Oracle Database on Github. With those build files one can go ahead and build his or her own Docker image for the Oracle Database. If you don’t know what Docker is you should go and check it out. It’s a cool technology based on the Linux containers technology that allows you to containerize your application, whatever that application may be. Naturally, it didn’t take long for people to start looking at containerizing databases as well which makes a lot of sense, especially for, but not only, development and test environments. Here is a detailed blog post on how to containerize your Oracle Database by using those build files that Oracle has provided.
Sometimes when I want to test something or write a prototype of some sort SELinux (Security-Enhanced Linux) kicks in and hinders me, given that it is enabled by default on OL 7 UEK 4. STOP! Before I let you continue to read take a mental note of my disclaimer: I am an advocate of having security turned on by default. It helps us provide better and obviously more secure systems which, in turn, helps the world save time and money. Security should never, ever be turned off for production systems!
With this being said, here are a couple of quick steps for how to get around it.
Here is also a short video on this topic: