I've been trying to get help from my FLOS and Hyland on this AFKS issue! Now I am finally finding it after over two weeks in the making !!! I am running Oracle 19cR10 on Linux VM Ware. I also installed Oracle 19c Client, 32 Bit and 64 Bit, on my OnBase EP3 Web/App Server. Using OnBase 20.3.23.1000, recently installed. I see the problem with the AFKS displaying the incorrect SQL. When I stood up my database (Export from 12cR2 OnBase Prod DB to Import 19cR10 OnBase Dev DB), I went into Config to change my database ODBC 32 Bit in my AFKS so that it would point to my Dev DB as I always would do. Then I did a SAVE without knowing the SQL from the keywordset table is displayed wrong (even though it is on the database table correct). So, because I did a SAVE to save the changes I made so it points to the correct db (Dev DB instead of Prod DB), the SQL that is displayed incorrectly overwrote my good SQL on the keywordset table. Therefore when my LifeCycles/WorkFlows run, scanned documents would not pick up the keywords. So, I reopened the AFKS in Config and Now I see the SQL screwed up, picking up SQL from other AFKS. I can paste the correct keywordset in and save it. It will update the keywordset table with what I need but if I reopen the AFKS in Config module, it will look to be the wrong SQL. I have an Oracle 12c Client installed on my workstation, so I can see the SQL displays correctly. I really wonder how long it will take Oracle to correct this issue!!! Next, I am having difficulty with the Unity Scheduler Installer. On the screen where you input the Data Source, User ID, and Password, I have used the same values that I used in the past Data Source=dbname.world; User Id=HSINET; Password=<pwd for hsinet> I continue on with the install and the install fails. What I discovered is that it will only install when I use this string for the Data Source Data Source=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=servername.domainname.com)(PORT=####))(CONNECT_DATA=(SERVICE_NAME=dbname.world))); User Id=HSINET; Password=<pwd for hsinet I am still looking for an answer to why I'd need to specify essentially a string that would display from a tnsping dbname.world. There are bigger problems/challenges to how you set up Authentication in iiS and Web Application Management Console. There is a white paper out there for this. But with some help from Hyland Tech, I also had to manually modify the web.config files under appserver and appnet for getting my front end application to open documents out of OnBase. I've been working for over 7 weeks on this whole process, converting my 12c DB to 19c and then upgrading from OnBase 18 to OnBase 19. I have used OnBase 12, OnBase 16, Onbase 18, and now OnBase EP3. I will tell you that this upgrade has been the BIGGEST challenge of them all!!! You better look at EP5 and see if it is even certified with 19c. Regards, Mike
Hi Mike,
They Hyland applications include the Oracle.ManagedDataAccess.dll in their distributions. Accessing the Oracle.ManagedDataAccess.dll in the Hyland folders means that the .dll can't find the TNSNAMES.ORA file in that directory, and it doesn't know about any client drivers that are installed.
To get around this issue, I set a global environment variable on the server(s) to point to the location of the TNSNAMES.ORA file, SQLNET.ORA file and LDAP.ORA file.
eg:
TNS_ADMIN=C:\Oracle\19c_32bit\network\admin
Please note, this global environment variable will impact all applications that use Oracle.ManagedDataAccess.
My servers are OnBase only so that works fine.
I hope this helps.
Cheers,
Steve Williams
