issues with upgrades CMOD 9.5 to 10.1.0.4

[bruce.mchendry]

Hi,
Wow where to start. Actually it started with a Java issue in Content Navigator and we moved up our planned 2019 upgrade into now. To set context due to Sun Life policy we have to use a remote database managed by the database team. What we did was :
- stopped LibLibSrvr service in windows
- ran the 10.1 install
- ran the 10.1.0.4 fix pack
- installed PDF indexer
While we were doing that the DBA copied the existing sql2012 database onto a new server and upgraded to SQL2016
- Uninstalled v9.5 which brought up the Configurator where we deleted the 9.5 instance / services
- Set up a new 64 bit ODBC Connection with new alias / server. Test connection worked.
- Ran new configurator and set up new instance
- Ran commands to drop and redo index's ( i.e. arsdb -I <instance> xxxxx)
- rebooted server because the developer wanted to, some other misc things
- Ran arsdate to see version and it came back with v10.1.0.4
- DBA confirmed the ID and password are good on the SQL server, ODBC connection tests ok on the Windows app server
- I perused the registry and it looks like the proper keys have updated to v10.1
- tried to restart the service in both the Configurator and LibSrvr in Windows Services and it won't start
Windows event log we get to consistent errors of event 13 and 151 :
- DB Error: [Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name 'keystore_type'. -- SQLSTATE=42S22, SQLCODE=207, File=arssys.c, Line=3895
- Unable to initialize server database system parameters.  Contact your system administrator.
Also if after running the index commands I try the arrsockd start command I get
- In StartServiceCtrDispatcher  Error number : 1063
We've opened a ticket with IBM but so far it's been more educational than successful.
BTW One thing I noticed it in our other environments as well as using the ODBC we have SQL server / feature pack installed (v2012). I can't find a doc for the requirements of setting up an SQL 2016 remote database and connection. I've asked IBM the same. And to think this all goes back to the Security team pushing a bloody Java update.
Cheers

[Justin Derrick]

Likely omitted the arsdb -I <instance-name> -uv.

-JD.

[bruce.mchendry]

Hello,
Thanks for the reply. We did run through the list of commands as per IBM :
Stop the IBM Content Manager OnDemand server
        arssockd [-I <OD_INSTANCE>] -T
      Install the base IBM Content Manager OnDemand V10.1.0.0
        See the section on your specific platform
      Apply the current fix pack
        See the section on your specific platform
      For SQL Server: Drop the current indexes
            arsdb [-I <OD_INSTANCE>] -efv
      Update the database
            arsdb [-I <OD_INSTANCE>] -uv
      For SQL Server: Create the current indexes
            arsdb [-I <OD_INSTANCE>]-rfv
      Then perform database maintenance
            arsdb [-I <OD_INSTANCE>] -mv
         
      Start the IBM Content Manager OnDemand Server
        arssockd [-I <OD_INSTANCE>] -S
With my PMR and IBM's request we ran the "-uv" command a couple times but no change. I had trouble finding an install / config doc for setting up a remote SQL 2016 database. There's a 2012 one on IBM's site but SQL 2016 has changed and I can't find anything as a guide. I've asked IBM as well but so far no reply. We're using the v11 native ODBC connection and it tests ok. Our DBA says the database looks fine on the server but it's like there's something missing or wrong to make the connection between our app server and SQL server. Any ideas ?
Cheers

[Justin Derrick]

Generally I look for the usual suspects...

Double check domain names, IPs, port numbers, UserID & Password combos, then it moves to network stuff...  gateways / firewalls / pings...  Then I start digging with UNIX network tools like TCPdump, and netstat and lsof.  No idea how to help with that stuff in the windows world, aside from making sure to use the 'OnDemand Command Line' shortcut so you get the correct environment.  Don't forget to try enabling tracing in arssockd.

-JD.