As far as scenery goes, this is the most distracting run I’ve ever done. I found it impossible to focus on running. Savannah is a beautiful city. It is small, yet packed with life and activity from the touristy bits to family life and business.
For a better write-up about Savannah Squares than this post, read this; an eloquent intro to the squares.
Because I will have to do this again in no time, here I jot down the quickest way for me to install 12c. This is the usual series of following steps, running into an error, searching for a fix, lather, rinse repeat.
Step One – Install oracle-rdbms-server-12cR1-preinstall.
Step Two – …gets us all the way here – [FATAL] PRVF-0002 : Could not retrieve local nodename
Step Three - … cannot write oradata change to /home/oracle/oradata
Step Four – Swapfile … I used 10000
Step Five – Then I see installer is bent on putting oradata directory in /home. Just revise to suit your install.
This one got me for a loop. It just so happens that both the h2 browser AND the play app should run from the same console. Otherwise, you end up running app and its database as one instance and new instance of ‘a’ database in another instance.
Do as I say and not as I do!
1. From shell, start play app. Do NOT type ‘play run’, just ‘play’.
2. Type ‘h2-browser’ next, The H2 Console should load up in the browser.
3. Now, type ‘run’ (or ‘~run’ for compile on save) to start your app.
Bingo! You should be able to now see your database.
In the spirit of my previous runaround post, I decided to do the same for my latest long run.
This time I ran in Brooksville, FL instead. The combination of week 7 of training plan (Disney here I come!), the kid’s school camping trip and the opportunity to run in a new place warranted this post.
Call me weird, planning the run was half the fun. Between Google Maps and Garmin Connect, I was able to plot a route around our camping site that lined up with planned run.
The only thing I did not plan was the expected humidity. According to NOAA’s site, average humidity was 69. That is a lot of water in the air. Thankfully, it was cold enough that it was not a bother. Accordingly, however, my printed route paper was completely wet 2 minutes after I took it out of pack!
One of the few frustrating experiences learning VMware Hypervisor has been loosing my server! At install time, I must have defaulted to automatically getting an IP Address from DHCP. Twice now, I’ve attempted to login thru vSphere and my server is nowhere to be found. The hosted VMs are all accessible. Its just VMware that goes M.I.A leading me to the suspicion that I did something wrong.
My usual fix is to scan my network for devices.
After figuring out which IP Address is my server at now, I proceeded to the servers configuration page on the right and selected networking from the mid-left pane.
Selecting properties from the rightmost panel brings up the networking details for the server. Here, I can see my new IP Address as well.
Selecting Management Network from the left pane and pressing the edit button brings up the network properties where I can change the IP Address.
Easy enough, I changed my settings to statically set my IP Address. Done!
One missing feature of the wonderful free version of VMware vSphere Hypervisor is the auto-magic way of cloning a VM. Nothing I could find at least on this. There are features for managing snapshots of VMs, for taking snapshots and related tasks, however, to backup/clone a VM, you have to take matters into your own hands.
Before you follow this steps, ensure the VM you’re about to clone is off.
First step, on your VMWare GUI, from Storage section, right click/browse the datastore where your VM image is stored.
On the Datastore Browser, create a new folder. This directory will shortly become your cloned VM directory.
Having created a directory for the VM (to be cloned), click on the folder of the VM you want to clone now. From the contents of this directory, select all the files, skip the logs and right-click copy. Notice screen-grab shows .ldk and .vswp files. The existence of these is because I grabbed the image from a running VM. Remember the VM to be cloned should be shutdown. These files should not be part of copy/paste steps.
Having copied all the files, go back to the newly created directory and right-click paste these previously copied items.
From all the copied files, right-click the file with the vmx extension and select ‘Add to Inventory’.
Select a name for your newly created VM
Finally, select the location of new VM. Here you can see me place all ‘Base’ VMs in their own ‘Resource Pool’. I am only doing this to group together copies I make of any VM I configure. I haven’t even looked up why I want to use a resource pool for its intended purpose.
As mentioned at the beginning of this post, there may be an official way of creating/cloning VMs in VMware vSphere Hypervisor but I do not yet know how. This, however, works like a charm, enjoy. Thanks for reading.