OnBase18 Unity client and EP5

[Inger_Granli]

Hi

We are upgrading from OnBase 18 to EP5, and were hoping to be able to run the v18 Unity Client towards the EP5 database for a short periode.   Ufortunately we are getting an error when starting up the client, presumably caused by changes to the datamodel. 

I have not found any information suggesting that this should not work for these two versions, so I wonder if anyone else has tried to do this and succeeded?  

If so, what do we need to do to make it work?  We are running on Oracle DB.

[George_Sialmas · Accepted solution]

Inger

I recently configured an IPUP environment for a customer in which the old version was still accessible whilst the customer performs UAT on EP5. What this involved was having a new Application Server being provisioned in order to install/configure Application Server x64 EP5 version. The existing Application Server remained as the old (current) version which was 16. 

Having two Application Servers for the old version and the new version allows for the Unity Client v16 to continue to connect to the Application Server v16 and Unity Client EP5 to connect to Application Server vEP5. So far, I have not come across any issue for this IPUP environment, in which Unity Client v16 not working. It works perfectly fine because it connects via the Application Server v16 build and not via the new Application Server EP5 build.

Without knowing your environment, I'm going to take a stab in the dark and assume that when you state that you upgraded OnBase 18 to EP5, did you keep the Application Server v18 or did you upgrade this to EP5? If you have upgraded it to EP5 and you do not have the old Application Server (v18) anymore then you will not be able to get Unity Client v18 to connect to a newer Application Server (EP5) build.

Regards,

George

[George_Sialmas · Accepted solution]

Inger

I recently configured an IPUP environment for a customer in which the old version was still accessible whilst the customer performs UAT on EP5. What this involved was having a new Application Server being provisioned in order to install/configure Application Server x64 EP5 version. The existing Application Server remained as the old (current) version which was 16. 

Having two Application Servers for the old version and the new version allows for the Unity Client v16 to continue to connect to the Application Server v16 and Unity Client EP5 to connect to Application Server vEP5. So far, I have not come across any issue for this IPUP environment, in which Unity Client v16 not working. It works perfectly fine because it connects via the Application Server v16 build and not via the new Application Server EP5 build.

Without knowing your environment, I'm going to take a stab in the dark and assume that when you state that you upgraded OnBase 18 to EP5, did you keep the Application Server v18 or did you upgrade this to EP5? If you have upgraded it to EP5 and you do not have the old Application Server (v18) anymore then you will not be able to get Unity Client v18 to connect to a newer Application Server (EP5) build.

Regards,

George

[Inger_Granli · Accepted solution]

Hi George,

thanks for your quick response. 

What we actually did was to install EP5 on a set of new application servers. We have also installed OnBase 18 appserver on these new servers.  We have  tried to set up a new database connection from the old appservers to the EP5 database, but the same error occurs.

What happens is that when we try to connect to the EP5 database from OnBase 18 we get an ORA-32795: cannot insert into a generated alwasy identity column

Examining the database I can see that several log-tables has a change in datatype from number to 'Identity column, ‘Generated Always as identity…'  for some of  their columns, amongst these is SECURITYLOG.SECURITYLOGNUM which I suspect is the problem during logon.

I am glad to hear that you did not experience this from version 16, then probably it should work for our environment also.   Any suggestions on what could be wrong? 

Regards,

Inger

[Cindy_Catalano]

We recently upgraded our test and prod DB from v18 to EP3 with no issues.  We left the v18 app server in place and set as the default app server.  We have not yet upgraded any of our clients to EP3, they are still using v18 clients.

We are in the process of upgrading one of our test DB from EP3 to EP5, and so far have not run in to any issues similar to yours.  We are presently testing the EP5 clients in the test system that we upgraded the DB to EP5.

[Inger_Granli]

Hi Cindy

Thanks for your response. Are you also running on Oracle database, and if so, which version?

Regards,

Inger