
The first thing I did was run the pre-requisites check. There will be two phases to the install: a prerequisites check followed by the real installation. While I tried to include as many screenshots as possible, I did omit several steps where I simply chose the default settings proposed by the wizard. When you launch this process, a host of options will be presented each option will include an installation wizard to guide you along the way. SAP Installation will begin by launching the install process from within the SWPM. …and based on the SAP Note, I changed it to this: compatible ='12.1.0.2' Mine looked like this: compatible ='11.2.0'

Mine was located here: D:\app\\product\12.1.0\dbhome_1\dbsĮdit the file using Notepad and find the existing ‘compatible’ parameter. In Windows Explorer, navigate to the the ‘dbs’ folder to locate your init.ora file.

Reviewing this page, I reviewed the ‘INIT.ORA’ file. However, when I installed client 12.1 I received an error during Database creation indicating that the Oracle ‘Compatible’ parameter was not valid. I had run into an issue later on in the process: The Software Provisioning Manager (SWPM 1.0) prompted me that Oracle client 11.2 was not acceptable it was looking for 12.1. STEP 17: CHANGE ORACLE “COMPATIBLE” PARAMETER

However, I ran into some compatibility messages when doing the SAP install.

If you check out the packages you downloaded from SAP, you’ll notice that it calls for ORACLE 11.2 RDBMS. Now that our VM is configured, it’s time to put some meat on the bones.
