Blog Archives

MS Access 2016 — a bug finally fixed after 16 years – NOT! (Part 2)

Only recently, I realized that I was dead wrong (two years ago), claiming that Microsoft finally fixed a bug in Microsoft Access 2016 that caused wrong results whenever we use a combination of:

  • linked tables via Oracle ODBC driver,
  • Oracle table contains attribute(s) with data type NUMBER(n,m),
  • and Windows client OS is properly using whatever (Eastern Europe) regional settings is valid for the country. In Slovenia we’re using comma as a decimal separator.

If above requirements are met, then MS Access (any version!) interprets the decimal number as integer (2342,45 becomes 234245). This can be a potential hefty salary raise for someone.

When I reported that Microsoft finally fixed a bug, I didn’t realize that I was working on Windows 10 VirtualBox VM, where I freshly installed Oracle Client 12c, but didn’t bother to check NLS_LANG in the registry. As it is usually the case, Oracle installer puts (incorrect) NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252 in the registry, instead of correct one, NLS_LANG=SLOVENIAN_SLOVENIA.EE8MSWIN1250.

While preparing some new standard PC configuration for our current customer, I was surprised when I found out that an old bug is back. It was “back” because on this “matrix” machine Oracle client was properly setup with NLS_LANG=SLOVENIAN_SLOVENIA.EE8MSWIN1250. Since going back to 32-bit MS Office 16 and Microsoft ODBC driver for Oracle (only 32-bit version is available!) was not an option, we were left to figure out some workaround. And we did. We found out that MS Access interprets decimal data type in Oracle table correctly, if we change territory from Slovenia to America (without changing *any* other regional settings at OS level!).

Something like this:

-- open cmd, setup NLS_LANG, then run MS Access
cmd> "C:\Program Files\Microsoft Office\Office16\msaccess.exe"

Changing NLS_LANG variable at registry (machine) level to SLOVENIAN_AMERICA.EE8MSWIN1250 doesn’t sound as a smart move, just for the sake of fixing a bug in one faulty product, so we decided to write some simple launcher for MS Access that can fix NLS_LANG variable behind a scene, leaving NLS_LANG in registry intact.

Below is a simple Go code that’ll run MS Access after properly setting up territory part of NLS_LANG variable. Note that we deliberately used absolute paths to MS Access binary that works for our Windows 10 standard configuration, something that you might want to change if you decide to use it. You can change language and character set part of NLS_LANG variable as well.

To build executable from the code follow these steps:

  • download and install Go
  • save code in some file, such as G:\SRC\runAccess.go
  • compile code, open cmd and execute: cd G:\SRC & go build
  • ** or, you can compile the code with: go build -ldflags -H=windowsgui

** The alternative build with the -ldflags -H=windowsgui is optional but recommended. It will cause console window to close after it launches MS Access.

// runAccess.go -- MS Access launcher
package main
 import (
func main() {

	var version *bool
	var help *bool
	version = flag.Bool("version",false,"18.02")
	help = flag.Bool("help",false,"MS Access 2016 Launcher") 
	if *version {
		fmt.Printf("February 2018 by AlesK\nVersion %s\n", (flag.Lookup("version")).Usage)
	if *help {
		fmt.Println("I'm here to silently run this code for a user:")
		fmt.Println("cmd /c SET NLS_LANG=SLOVENIAN_AMERICA.EE8MSWIN1250 & start C:\\Program Files\\Microsoft Office\\Office16\\msaccess.exe")
    if (os.Args != nil && len(os.Args) > 1) {
		cmd := exec.Command("cmd", "/C", "set NLS_LANG=SLOVENIAN_AMERICA.EE8MSWIN1250 & start C:/\"Program Files\"/\"Microsoft Office\"/Office16/msaccess.exe", os.Args[1])
		if err := cmd.Run(); err != nil {
			fmt.Println("Error: ", err)
	} else {
		cmd := exec.Command("cmd", "/C", "set NLS_LANG=SLOVENIAN_AMERICA.EE8MSWIN1250 & start C:/\"Program Files\"/\"Microsoft Office\"/Office16/msaccess.exe")
		if err := cmd.Run(); err != nil {
			fmt.Println("Error: ", err)

You can do two things with runAccess.exe. You can run it as a standalone program. It’ll open MS Access with territory part of NLS_LANG set to AMERICA. Or, you can associate *.accdb or *.mdb file extension with this launcher and it’ll correctly start MS Access if user double clicks on MS Access database file.

If you’re wondering what is perhaps a negative consequence of tweaking territory part of NLS_LANG variable, then you can refer to Oracle official NLS lang FAQ, a quote:

What does the TERRITORY component of the NLS_LANG parameter control?

The territory component of the NLS_LANG parameter controls the operation of a subset of globalization support features. It specifies conventions such as the default date, monetary, and numeric formats. Each supported territory has a unique name; for example, AMERICA , FRANCE , or CANADA . If the territory is not specified, then the value is derived from the language value.

We can certainly leave with “wrong” monetary value and having american “default date” is easy to fix with a proper NLS_DATE_FORMAT.

Please, can someone deliver some cloud “stuff” to Oracle Support?

Can you tell me what is wrong with this screen capture that I took on MOS and is part of my Service Request?

Right now, I’m waiting SR analyst to download and install Oracle software, so that he can run query provided by us. I hope that they have at least a decent bandwidth, if they’re not able to use provisioned virtual machines in the first place. And that is the same company touting their cloud offerings. LOL.

20th anniversary

When I started to work for a current employer in 1995 the company run a tiny Oracle 6 production database on IBM mainframe (OS/390). Nothing serious or big. The majority of data processing at that time was still done in Cobol and TPL. Development with Oracle*Case of the new state Business registry however started on LAN, with Oracle 7 on Netware 4. Yes. Life. Was. Exciting. Recovery from a server crash was almost a daily routine. But for a starter like me, it was definitely fun and exciting working environment.
In the mid 90’s company was using a myriad of OS’s (OS/390, Netware 3 and 4, OS/2, DOS, Windows 3.1, Windows 3.11, Windows NT 3.5, SCO Unix, IRIX….but not Windows 95!). We used two network protocols, primary one was IPX/SPX and secondary was TCP/IP (Oracle Listener was listening on IPX/SPX adapter). It was a ZOO.
After Microsoft released Windows NT 4 at the end of 1996, the decision was made to consolidate OS environment on NT 4 at every level, from laptops, desktops to the servers. With one exception. Two main file servers were left to run on Netware.
Why not Unix? Due to the lack of skilled workforce with strong Unix skills on the market it was somehow logical choice to pick a mainstream OS player.
So, on March 1997 we put our first non-mainframe production Oracle database in use. It was IBM PC Server 320 with two Pentium 133Mhz processors, a whooping 128MB of RAM and four 2GB Fast Wide SCSI disks. We run NT 4 and Oracle 7.3. Backups were done with ArcServe and HP Surestore DAT tape library. This first PC based host was (predictably) named ORANT.

At that time we were considered as weirdos (perhaps we still are?), because no one run Oracle production on Windows. Local Oracle representatives used us as a reference whenever someone asked them if anyone is using Oracle on NT or how stable Oracle is on NT. Honestly, from 1997-1999, it was not as stable as we wished to be (regular monthly reboots were needed), but it was certainly a giant leap forward compared to Oracle on Netware. The real stability came with Windows 2000/2003. Twenty years later our production still runs on Windows Servers, but this is gonna to change soon. Not because of the lack of stability (modern Windows Servers are rock solid, and we can prove it;) but because of clear Tux technology dominance and advantages in the Cloud/OSS era.

Anyway, I took a couple of screenshots from my VirtualBox guest, running Windows NT 4 (SP1) and Oracle 7.3.4:

For the record: installation of the Windows NT 4 took ~10 minutes. Installation of Oracle 7.3.4 with Replication option took another ~10 minutes (including building a database). It took 1.3GB of disk space for both OS, RDBMS and sample database. For comparison, Oracle 12c R2 ISO file with all the components is 9.7 GB.

Unicode and Oracle SQLcl…on Windows — solved

I was struggling with sqlcl on Windows 7 to properly display our umlauts (we’re using Windows 7 desktops with NLS_LANG=SLOVENIAN_SLOVENIA.EE8MSWIN1250 setup in the registry — note: sqlcl is not reading this variable).
When I read Jeff Smith blog post “Unicode and Oracle SQLcl…on Windows” I though that my problem was solved. Someone reading an article without reading the comments would assume that sqlcl works out of the box on Windows with proper UTF-8 support, which does not. Partly due to the omission of proper parameter in supplied sql.bat file, but mostly because of the state of cmd.exe (powershell.exe) in versions of Windows 7 and below, Windows 10 is much better.

In this demo we’re using Windows 7 EE (Windows 10 EE), Oracle 12c R1 and

First, we created test table called UMLAUT in SQL*Developer and inserted our umlauts:


Then we run a query from this table with sqlcl. Note an extra line between the rows returned from the query….


ok, how about writing some umlauts on the command line….


Well, we can write umlauts but console won’t show us what we wrote (note a presence of squares)…nevertheless the result of the query is correct.

What we can do? Well, for a start we need to patch the officially supplied sql.bat script.

Open sql.bat and replace line

SET STD_ARGS=-Djava.awt.headless=true -Xss10M


SET STD_ARGS=-Djava.awt.headless=true -Xss10M -Dfile.encoding=UTF-8

But don’t celebrate yet…what we achieved is this….


We still have an extra line between the rows, which is annoying, but at least we can see what we wrote in the WHERE condition. Plus an extra square :-)…if you’re “lucky” Windows 7 user.
However, above patch is enough on Windows 10, where, both writing of umlauts and properly displaying the records (without extra blank line) works as expected….


The only “workaround” that we found for Windows 7 clients is to simply forget about official console applications (cmd.exe and powershell.exe) as a “host” for sqlcl and use some alternative. We found out that ConEMU works great…(patch in the sql.bat is of course still mandatory until sqlcl guys do this for you).


And what about the suggestion that we can tweak the registry and permanently change the console application (cmd.exe) code page to UTF? Don’t do this, because you’ll disable some non-java applications, including SQL*Plus…look what happens with sqlplus.exe….


Installing Standalone Oracle Http Server 12c R2 ( on Windows 2012 R2


According to MOS note Oracle Web Tier – Statement of Direction (Doc ID 1576588.1) Oracle mod_plsql in Oracle HttpServer is deprecated as of version OHS 12.1.3.
If you’re reading this to learn how to install OHS because your application depends on mod_plsql functionality, then we have a bad news for you. Oracle removed mod_plsql from OHS 12.2. So, the best help that we can give you is our reference installation note for OHS 12.1.3 installation on Windows 2012 R2.
Oracle recommends to move to Oracle REST Data Services (ORDS) (formerly known as Apex Listener) on top of Oracle WebLogic, Oracle Glassfish or Apache Tomcat.
Of course, if you’re still interested in installation procedure for OHS 12.2 on top of Windows 2012 R2 keep reading….

Once again, we got a brand new server with Windows 2012 R2, on which we wanted to install standalone Oracle HttpServer 12c R2 ( If you read our post from the last year covering Oracle HttpServer 12.1 installation on Windows 2012 R2, you already know that we’re a big fans of Oracle end user friendliness and admiration of Oracle engineering capabilities to transform a mouse to an elephant. Let’s see if this crap excellent piece of software installs as smooth in Release 2 as it did in Release 1.

Find and download from OTN, at the time of this writing you should see something like this:


Unpack and run setup_fmw_12.

Setup will check the system prerequisites, you should be fine if you’re installing on Windows 2012 R2. Now, we’ll show you some screenshots from our installation with comments whenever we think they’re necessary. Basically, we left most options at default (apart from changing the Oracle home).







According to Oracle documentation:
On the Windows platform, Oracle HTTP Server requires Microsoft Visual C++ run-time libraries to be installed on the system.
To meet this system requirement for Oracle HTTP Server, download the Visual C++ Redistributable for Visual Studio 2012
software from the following URL:

After we downloaded and installed Visual C++ (VS 2012) redistributable we hit the Rerun button and the check completed successfully…










As you can notice, there is no screenshot of step #9. After we clicked Next on Step #8 the new dialog window opened for a second and immediately closed. Perhaps it was just us….fortunately, we could made an educated guess that the last screen should likely be an informative one, like the one that we saw during OHS 12c R1 installation:


…suggesting that fun is not over yet and that you need to create domain with the Configuration Wizard. Start configuration Wizard from:


and configure Oracle Http Server in standalone mode…










If you check Windows services at this time you’ll see, well, nothing. We need to create service for Node Manager before we can start Http server.
Note that we installed Oracle HttpServer 12c R2 in ORACLE_HOME: D:\ORACLE\OFM.

First open command prompt (cmd) wit “Run as Administrator” and set the path before you run installNodeMgrSvc.cmd:

set DOMAIN_HOME_BIN=D:\ORACLE\OFM\OFM12\user_projects\domains\base_domain\bin

And if everything has gone well you should see the message at command prompt, with the line:

Oracle Weblogic base_domain NodeManager (D_ORACLE_OFM_OFM12_wlserver) installed.

Script installeNodeMgrSvc.cmd created a new service, that reads, don’t hold your breath….:

"Oracle Weblogic base_domain NodeManager (D_ORACLE_OFM_OFM12_wlserver)"

with path to the executable like this:


Yes, they probably set a World record for the length of a Windows service. What a schmucks.
The service is installed using the default Node Manager listen port (5556). By default Node Manager Listens only on localhost.

Now, we can finally start Oracle HttpServer 12c R2. First, make sure that Node manager service is running and if it’s not then start “Oracle Weblogic base_domain NodeManager (D_ORACLE_OFM_OFM12_wlserver)”.

You can START Oracle HttpServer 12c R2 on command line with:

set DOMAIN_HOME_BIN=D:\ORACLE\OFM\OFM12\user_projects\domains\base_domain\bin
startComponent ohs1

You’ll be asked to enter password for Node Manager which you entered on screen 6 of Oracle Fusion Middleware Configuration Wizard.

You can STOP Oracle HttpServer 12c R2 on command line with:

set DOMAIN_HOME_BIN=D:\ORACLE\OFM\OFM12\user_projects\domains\base_domain\bin
stopComponent ohs1

There is also a WLST tool (wlst.cmd) that allow us to manipulate with running OHS.

Using WLST to control OHS:

Open WLST D:\ORACLE\OFM\OFM12\oracle_common\common\bin\wlst.cmd:
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> nmConnect('administrator','mysecretpassword','localhost','5556','base_domain','D:/ORACLE/OFM/OFM12/user_projects/domains/base_domain','ssl')
// status
wls:/nm/base_domain> nmServerStatus(serverName='ohs1', serverType='OHS')
// soft restart
wls:/nm/base_domain> nmSoftRestart(serverName='ohs1', serverType='OHS')
// stop OHS
wls:/nm/base_domain> nmKill(serverName='ohs1', serverType='OHS')
Killing server ohs1 ...
Successfully killed server ohs1
// status
wls:/nm/base_domain> nmServerStatus(serverName='ohs1', serverType='OHS')
// start
wls:/nm/base_domain> nmStart(serverName='ohs1', serverType='OHS')

And finally, let’s see where is the config file for httpd. According to the Oracle Http 12c documentation there are runtime and staging config files and we should always edit staging config file(s). In our example the config file location is:

Domain home bin        : D:\ORACLE\OFM\OFM12\user_projects\domains\base_domain\bin
httpd.conf             : D:\ORACLE\OFM\OFM12\user_projects\domains\base_domain\config\fmwconfig\components\OHS\ohs1 

Final Test….open IE and go to http://localhost:7777: