Friday, November 9, 2012

Google CHROME SSL Certificate Issue

I decided to give the Google Chrome browser a try. After installing I found that I could not connect to Google Drive and other Google sites.  I kept getting the red-box error:


"The site's security certificate is not trusted!..."

The biggest problem was there was just a single "BACK" button in the red-box there was no option to proceed anyway like in Firefox or IE.  Basically if I couldn't get to Google apps online Chrome would be useless to me.

So I googled away at the issue and could not get a clear answer even from Google Groups etc.  All the answers ran the gamut of sites being hijacked to my system being infected.  I knew there was no problem with my system since I had no issues reaching Google Drive etc in Firefox.  After a little more diligent searching I came across the hint here:

http://www.techrepublic.com/blog/google-in-the-enterprise/the-strange-case-of-the-google-certificate-roadblock/1292

It turns out I was missing a Windows root certificate update pushed earlier this year.  See http://support.microsoft.com/kb/931125

I downloaded it after validating my system and that fixed my issue.  You would think that Google Support would have this as one of the first things to check for this issue

sqlplus / as sysdba vrs sqlplus sys/pwd@sid as sysdba

Working with Ora10gXE on a Windows 2003 server I could not connect  sqlplus / as sysdba but could as sqlplus sys/pword@sid as sysdba

Got ORA-12560:TNS:protocol adapter error".

After big searches on Google could not get a clear cut answer, everything trended towards not being able to sqlplus at all.  I found a couple posts where someone specifically asked why they can do sqlplus sys/pwd@sid as sysdba but not sqlplus / as sysdba
But most of the answers where as if the user could not sqlplus at all.

Finally out of curiosity I echo’d %ORACLE_SID% and got nothing back.
So I added the SID to the environmental variables rebooted and the problem was fixed.

Not sure about the exact mechanics of the fix but I assume that when just connecting sqlplus / it is looking for the environmental variable vrs using the listener to make the connection?
Maybe someone can explain?

AF 512e Hard Drive

I received a new Dell M6600 laptop with two drives a standard SATA and a SSD.  The box the laptop came in had an ominous orange note saying one or more of my drives may be one the new the new Advanced Format 512e drives.  The note pointed out that it is important to understand the implications of the new drive and how that relates to the OS to be installed.

The AF 512e drive is formatted using 4K sectors vrs the old school 512 bytes sector but emulates 512 for backwards compatibility with today’s OS’s.  From what I found online Windows 7 and the newest Linux versions (like RHEL 6)support AF 512e natively but older Windows/Linux distros have to have special considerations, specifically ensuring that the partitions are aligned correctly.

I really wanted to know what drive I had since I intended on installing RHEL5.5 which would involve extra work to insure the drive was partitioned correctly to use  AF512e.  I also needed to know which drive(s) were AF512e.

<RANT>Anyway according to the Dell propaganda that came with the laptop I could download software called “Dell advanced Format HDD Detection Tool”.  So I goto the link provided which leads to their Drivers and page where I put the system tag number and there is no such software available.  I searched everywhere on Dell’s site and found nothing but links back to the driver page.  </RANT>  

Another option was to disassemble the laptop and check the drive for an “AF” symbol on the label. Luckily this  info can be gained from the command line as well in Windows 7 using fsutil. The fsutil you use must be v3 which comes as part of KB9822018.
So I went ahead and ran the default Win7 setup that the new laptop had pre-installed and went to work.  It turned out the SSD was an AF512e drive.

At the command prompt enter

fsutil fsinfo ntfsinfo c:

Look for these lines:

A standard 512 byte drive will show
“Bytes Per Sector :           512”
“Bytes Per Physical Sector : 512”

While a AF512e drive will return
“Bytes Per Sector :           512”
“Bytes Per Physical Sector : 4096”


So knowing that I had AF512e drive I decided to go with RHEL 6 instead of RHEL 5 since it could supposedly handle the drive.

The RHEL 6 install went without a hitch.  And a quick fdisk -l /dev/sdb showed the the start sector for the partition was 2048 which is divisible by 512 so the partition seems to be aligned correctly as I have read online.


That part of the job was now done.