This way you can be sure that the right version will be installed, and they will also upgrade together if needed. So the name of the game is to use same version for the packages, possibly use the same repository as well, preferably your distribution's repos. After installation you possibly need to
otherwise you may still get configuration errors in VirtualBox settings. Besides virtualbox-ext-pack I have virtualbox, virtualbox-dkms, and virtualbox-qt packages installed, a bunch of gvfs packages, and of course dkms.
(You'd want to go to a PPA and fiddle around yourself only if your distribution's offered packages are missing some features and the PPA would offer a later version with those fatures. But then I'd advise to use the PPA for all virtualbox packages and don't mix and match.)
It is important that the extension pack match the version of VirtualBox installed. If VirtualBox gets updated via a ppa or however, you need to remove the old extension pack, download the new one, and install it.
We currently have a need to know what computers have an extension pack installed as part of oracle. Having a hard time finding a good way to do this. Was wondering if anybody had any experience with thi.
On a 10.13.3 host, I installed VirtualBox 5.2.8. I opened Composer and created a new package using Normal Snapshot, let the first half finished, then installed the current version of the Extension Pack, then completed the snapshot in Composer.
Upon inspection there's a file, ExtPack.xml, located at /Applications/VirtualBox.app/Contents/MacOS/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/ - so should be easy enough to create an extension attribute either checking for the existence of this file, grepping the Version revision string, etc.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
In my case deleting the previous virtualbox-ext-oracle build directory, to start fresh was all that was needed.
It was trying to build using the old, existing PKGBUILD rather than overwriting it with the new one. Check the PKGBUILD before the building to verify version is pkgver=7.0.8 rather than pkgver=7.0.6.
I don't think Oracle makes a difference betwwen dev, test and production. If you use it for business purposes, even while developing, they might have the right to send a bill depending on the jurisdiction you're in.
There is a good chance that whomever is using VirtualBox in this application may be using it as part of an automated test setup. I use it to test software on multiple operating systems. I can control the VM through VBoxManage and then run all the tests via SSH. The whole thing is orchestrated automatically via a bash script.
None of that requires the VirtualBox Extension Pack however, which adds some rather niche features, mainly related to USB device pass through. The problem in this case is with the VB EP, which you can download from the VB web site, but only for personal use and evaluation.
This has been a problem for oracle customers for decades. It was possible for a DBA to implement high availability features the customer hadn't licenced for years. Normally the manager responsible for the budget wouldn't be aware of it until either the annual lice bill suddenly leapt up or the got a call from Oracles Compliance team that would normally be followed up by a compulsory software audit if you wanted to avoid the bill.
In some cases the unfortunate DBS had embedded useful but expensive features so deep in the infrastructure that they couldn't be unpicked, in that case Oracle would usually make a 'special arrangement' if you committed to licencing the additional tools they would graciously apply your normal account discounts (90% in my case) but there was usually a bit of leverage applied to try and replace some non Oracle product with Oracles at the same time. I never fell foul of this issue personally as I was forewarned before moving into a tech management role and I briefed my DBA's but since going independent I've come across plenty of DBA's who have fallen down that particular pit. When I first stared working with oracle there was no competing product for High volume transaction processing other than DB2. I've always liked the product but always disliked the company. it seems endemic in the software industry, Microsoft tried to charge me for 1000 copies if windows because I had got rid of the boxes of floppy disks, Computer Associates tried to double the cost of my disk compression software when they bought the company. I found in all cases that if you had a corporate relationship with the company and your organisation had some industry visibility you could stand your ground and get it sorted out but I would have hated to be in that position in a smaller company.
One of IBM's gimmicks with Informix is to push it for embedded systems so there are ARM ports. A bit of scratching around shows there's also a PHP module. Hmmm. A Pi Nextcloud server running on Informix? If I ever have a spare week to play with that...
From my reading of the Oracle DB license: if you are virtualizing Oracle DB installs, Virtualbox is pretty much your only option if you want to have your Hyper-threads not count as full cores are far as licensing is concerned.
I won't have MySQL, Virtual Box, Java or any of their rubbish. But loads of stuff requires it, I've had a look at some open source projects but had to bin them straight away because they use Virtual Box to run an emulator. So many online project use it for VMs. It's possible employees are downloading it to play with stuff.
Oracle licencing terms are licencing terms, not law. If you don't use their software, they don't apply to you. If you use their software without agreeing to them, they still don't apply to you, but they might be able to sue for copyright violation.
"ORACLE DATABASE STANDARD EDITION - NAMED USER PLUS 3 YEAR" plus software updates/support. 20 named users (wouldn't recommend this config for an DB running an internet facing app), was $6,300 at the time. I was (and still sort of am) unsure how many named users I needed, I probably could of gotten away with maybe 2 or 3 given that really nothing other than vCenter (which had 2 DBs one for vCenter itself one for VMware Update manager - so 2 named users?) and nightly datapump job for backups. But I saw the cost of 20 and just said screw it license it for a bit more just in case.
I'm sure our license was too small for Oracle to care, they contacted me at least once or twice a year trying to upsell something. I explained what we use Oracle for and there wasn't any opportunities for upsell in this environment. They always understood(sometimes it took some additional explaining) in the end and left me alone for another 6-12 months.
One crazy bit is for a while they were pestering me about renewing support, support that didn't expire for another 2 years. I never understood that. I see emails from last year reminding me my support is expiring in 2020 and the cost to renew the support is .."USD $3.15" .. eventually those emails stopped.
I haven't dug into Oracle's licensing recently but several years ago standard edition could run on unlimited cores and you generally paid per socket(max of 4 I think). vs the enterprise which has the funky per-core licensing. I think Oracle SE even included RAC licensing at one point anyway.
I went through two Oracle audits with a company back in 2006(happened just as I joined the company) and again in 2008. Boss ignored my advice to change to standard edition in 2006 (they were originally licensed for "Standard edition one" if that version still exists, for a DB on an internet facing social media site). They had Enterprise edition installed.
They paid hefty fines and were assured everything was OK after the audit in 2006 so my boss ignored my advice. Auditors came around again in 2008 and found lots of new violations, this time they accepted my advice and I went through the process of migrating everything to standard edition(found it ironic the Oracle staff were not aware of the per socket licensing advantages to Oracle SE vs per-core licensing on Oracle Enterprise), even changing the CPUs from dual core (optimal for per-core licensing on fast cores) to quad core (better for standard edition more power). HP found out the DL380s they sold us as quad core capable ended up not being quad core capable they had to replace the motherboards (some time later they updated their docs reflecting some early boards could not do quad core processors).
The migration from Oracle EE to Oracle SE at that company was pretty painless, I mean no app changes, I did all the work. We had a Oracle consulting company that helped manage things and their custom monitoring app required partitions, so it was their standard practice to install Oracle EE with partitioning ($$$), so they had to change their shit around, but they realized they should do that anyway.
At least with Oracle 10g which is what we had at the time I think, we were still able to leverage Oracle enteprise manager with the performance packs and stuff (against the license), it was easy to wipe the installation from the DB when it came time for the next audit, no issues(semi regularly wiped the config for that anyway due to problems, didn't care about data retention on that stuff). Newer Oracle I noticed it didn't seem possible to install things that way anymore. Really missed the performance packs, I'm not a DBA but it was just amazing to see how quickly anyone could track stuff down, vs MySQL even in 2019 is nowhere close to it(and the way things have progressed in mysql over the past decade MySQL will probably never get to where Oracle was 10-15 years ago).
d3342ee215