problem setting up evaluation of visual 10.0 on oracle 19c

All, and specifically @charles-hooper who has been immensely helpful in the past with everything oracle. I am currently running 6.3.8 on oracle 9i. we are going to be doing a re implementation to 10.0 in the coming months. at this point I would like to setup a completely separate sandbox for users to get a feel for the new version. because I am completely unfamiliar with SQLserver I am going with the oracle 19c install. following the instructions from infor I have a database running with the visual application server installed. just straight following the PDF included with the downloads. I have installed the oracle client as well, created tnsnames.ora in both the home and client and they both test out. I can connect to the blank DB via sqlplus and developer. I am to the point I am supposed to Run visual's vmcvtutl.exe and create the schema. I open the file, select Oracle, change the database name from "visual" to match mine (both alias and database named vmfg) leave the SYSADM pw alone, then click begin. it prompts me for a login of "SYS AS SYSDBA" which I enter the pw. it goes away back to the original VMCVTUTL.exe screen the prompts me for a login again after a few seconds. I get no errors and no schema is created. I checked the VMCVTUTL.exe log in the Visual directory and it just says the exe started and stopped. I'm assuming this is some sort of issue with my sql.ini or a path?? I tried to verify the paths were correct. no extra sql.ini files. I modified the sql.ini per the instructions, and compared it to the one I use in 6.3.8 and made a few changes.

current system setup is just a basic spare workstation with a local admin account, not domain joined that I intend to be a client and server (I did this with Version 9 back a few years ago with no issues):

win10 pro with 8gb ram

static IP

computer name is "visual10"

application install directory is c:visual

team developer is c:TD73

oracle home is c:oracle

oracle client is c:appclient%username%

sql.ini is in the c:TD73 dir.

any ideas on why the visual application will not talk to the database?? I have contacted support and they literally have no clue what I am trying to do... I can almost hear them say "ew oracle?" during the two support calls we have had, which I had to tell them why the sysadm account didn't mean anything at this point, repeatedly.

Find more posts tagged with

VISUAL - Enterprise General Discussions

Accepted answers

All comments

charles-hooper

Hi Kevin,

I am sorry to hear that Infor support appears to be having an allergic reaction to Oracle Database.

If you are a member of the VMIUG-TEC Google Group (I know that you were in the older Yahoo VMIUG-TEC group), I suggest that you take a look at the "How To: Using Oracle Database 19c with Visual Manufacturing 9.0.8" ( https://groups.google.com/g/vmiug-tec/c/vxHKdBpN5nY/m/oY-CEgaKBQAJ ) article that I wrote in February 2022. Problem #2 mentioned in that article should not apply to Visual 10.0.0, but will apply to Visual 9.0.8.

We had to stick to using the 12.1.0.2 32 bit Oracle Client software on Windows 10 and Windows 11 - the 19.x version of the 32 bit Oracle Client was either not compatible with Visual or several of my custom programs (sorry, I do not remember which was the case). You will need to reboot the computer after the Oracle Client installation (if the Oracle Client is to be installed on the Oracle Server, it should be installed after the Oracle Database software is installed). Don't forget to add the database name to the SQL.INI file so that Visual is able to find the database.

I uploaded a file named "Oracle 19 VMFG Database Creation Scripts.zip" to the VMIUG-TEC group's Oracle folder ( https://drive.google.com/drive/folders/1hRPbWQ2cJFN-jgJDzDh0VXyxiW_nLuVa ) for you - that file contains scripts that are similar to the scripts that I used to build the 20 or so production and test databases on my Oracle server. NOTE: that the CreateDB.sql script specifies that the WE8MSWIN1252 character set should be used, which does NOT match Infor's Oracle Database guidelines document. I intentionally used that WE8MSWIN1252 character set with my Visual databases to eliminate certain problems (the character set that Infor recommends will use between one and four bytes to store each character in the database tables, while the WE8MSWIN1252 character set uses a single byte per character - this is important for any database tables that still contain VARCHAR2 or CHAR columns, as most of those columns were likely created using the default byte-length specification rather than character-length specification) .

Charles Hooper
Senior Software Engineer
Meadville Forging Company

csepulveda

Thanks Charles, I did forget to mention I installed the 64bit version of oracle 19C. the install docs do not specify 32 vs 64 bit. should I give it a shot with a 32 bit version?? infor support left off with "they will verify their instructions by creating a new server instance on their end" I do feel that they will be in the same boat as I am given their seeming lack of knowledge of oracle.

charles-hooper

The Oracle Database software will likely be 64 bit, which is fine. Visual requires the 32 bit Oracle client, as it is a 32 bit application. By installing the 32 bit client after the 64 bit Oracle software, the 32 bit client's BIN folder will end up in the system PATH before the 64 bit BIN folder, which will help avoid problems when running Visual on the computer.

Charles Hooper
Senior Software Engineer
Meadville Forging Company

csepulveda

see, this is why I ask you for help lol. installed the 32 bit client and it works. I knew it would be something **** I did. I just figured the infor tech would point out my stupidity pretty easily.

thanks Charles as always you're a life saver.

Copyright © 2025 Infor. All rights reserved.