Linux Mint Debian Edition (LMDE) is a derivative of the Debian distro, jollied along with some visual polish, lots of ‘ease of use’ and a useful mix of desktop software. It is not updated as frequently as the more-mainstream Linux Mint distro (which is Ubuntu-based), and the software repositories are not as well-maintained as for its mainstream cousin, so it’s generally regarded as a stable, slightly boring platform for people who know what they’re doing with Linux, rather than complete novices.
If you are reading this page, be aware that it specifically and exclusively deals with running Atlas (and Oracle 12c) on LMDE. If you’re using the ‘standard’ version of Linux Mint, you should be reading this other page instead!
Atlas (and Oracle 12c!) runs fine on LMDE version 2 (“Betsy”).
As is the case with all Atlas/Oracle installs, your server needs to be built with at least 5GB RAM and at least a 40GB hard disk.
Please watch the generic Atlas videos here, here and here to get an idea of how Atlas works in general. The generic documentation (including those videos) are available from this page. Below are LMDE-specific notes.
2.0 What’s been tested?
- LMDE 2 (‘Betsy’), in both Cinnamon and MATE flavours
3.0 Operating System media
LMDE is available in different forms, depending on what desktop environment you want to use. There are separate ISOs for Cinnamon and MATE desktops, for example. See the project’s download page for details of the latest versions available, and the flavours they come in.
The screenshots shown here indicate that I downloaded and installed from the MATE 64-bit ISO, but the choice of desktop environment is irrelevant to Atlas.
4.0 Operating System installation issues
LMDE boots as a ‘live’ distro (i.e., it’s fully usable, directly off the installation DVD or USB image). A desktop icon gives you the chance to install it onto a hard disk in the traditional way, so that it thereafter acts as a ‘normal’ operating system.
There are no deviations from the ‘accept the defaults’ approach when installing the operating system.
At one point during the install, though, you are asked to supply a hostname. You should supply one that is fully-qualified (i.e., with a domain name component), as I am doing here:
Here, I’m claiming ‘dizwell.home’ as my domain name: if you don’t have a domain name in your environment, make one up. It is quite common to use .localdomain for example, which is nicely functional but meaningless.
Other than that, the O/S installation is almost always a case of clicking [Next] (or [Forward] as the mood takes the installer!)
5.0 Running Atlas
I had no problems getting my LMDE 2 (MATE) VM displaying large screen resolutions. I specifically didn’t have to install any of the ‘guest additions’ to get it displaying at comfortably large resolutions, no matter what virtualization solution I was using (but, for the record, I used VirtualBox for the screenshots shown below).
Note that LMDE comes with wmctrl installed already, so I didn’t even have to do anything to make that Atlas prerequisite come about!
Immediately after the first post-install reboot, therefore, I was able to do the standard:
wget http://bit.do/dizatlas -O atlas.sh chmod +x atlas.sh ./atlas.sh
…after which, I simply followed the prompts.
6.0 Installing Oracle 12c
The Oracle 12c installation will start by claiming that your environment does not meet minimum standards:
That dialog box can be dismissed by clicking [Yes] -and don’t worry about it, because your environment is actually just fine!
After that, however, the installation is entirely straightforward: there are no linking errors or anything else that requires your attention, other than the (routine) requirement to run two root scripts part-way through:
Since there are no linking errors, Atlas will have created a post-install script in the oracle user’s Documents directory which you can (optionally) run once the Oracle installation completes successfully. Since I am my own oracle user, the following screenshot shows me checking the contents of my own Documents directory:
Note that the file is already executable: Atlas created it that way. You can therefore run that script now, as yourself, using the following command:
Do that as yourself, not as root. The command will not appear to have done anything at all, and you’ll merely return to the next line on the command prompt. Nevertheless, it will actually have altered some of the interface settings for the command-line SQL*Plus tool so that its query results are presented more sensibly than they are by default:
The default SQL*Plus settings would have resulted in that query’s return being broken up into a fairly illegible mess. Nevertheless, it’s up to you whether to run the post-install script: it is entirely optional to do so.
Incidentally: the command you see me typing in that last screenshot (“sql“) is the alias of the full command (“sqlplus / as sysdba“). It is aliased with a reference to the rlwrap utility, so that if you get into SQL*Plus using it, you can press the up and down cursor keys to retrieve and scroll through any previous SQL commands you’ve typed. If you ever need the vanilla, un-rlwrapped version of SQL*Plus, however, then just type the full-blown sqlplus command and you’ll be running the exact same program as before but without a command line history.