SQL Anywhere 17 removed during BOBJ 4.2 SP6 upgrade

[keithfisherdsc]

Hi,

I was running the service pack to upgrade BOBJ 4.2 SP5 to SP6 on a Windows Server 2012 R2 machine. All was working fine before the upgrade. The system uses the bundled SQL Anywhere 17 database for CMS and Audit.

However the upgrade failed and the SIA\CMS failed to restart afterwards because the whole install of SQL Anywhere on the machine had disappeared, taking the DSNs and install files with it!! The install dir\sqlanywhere directory has 'BIN64', 'database', and 'Jajva' folders in it, but nothing else and no content to those folders (except for the original CMS and Audit database and log files, thankfully).

How do I get out of this predicament? I have run a repair install but this has not replaced the SQL Anywhere installation. Can I manually install SQL Anywhere? How do I do that without specific licence keys for it, as I assume they are bundled somewhere in the BOBJ install.

Any other suggestions or am I facing a complete reinstall and rebuild using the database and filestore?

thanks

Keith

[keithfisherdsc · Accepted solution]

I eventually solved the problem - the version of SQL Anywhere 17 that was available in the 'installation' section of the support portal was build 17.0.0.1062. The version that was installed with SP5/6 was 17.0.7.3382. It was only through cross checking against another system that this became obvious.

The later build was available from the maintenance section of the downloads area on the portal.

Once this update was installed it was possible to start and connect to the two BI4_Audit and BI4_CMS databases

However the CMS would not start (although I could now rebuild teh SQLAnywhereForBI service)

tried to update the DSN in the SIA properties and got an error: FWB (00090)

this error was resolved with SAP note 2054800

the system has now restarted. No idea if the SP6 update was 'good' or not, I am going to apply service packs to Lumira ad Explorer now to see if they work ok.

[chris_keating · Accepted solution]

If you create a SQL Anywhere database in a new major version, you will not be able to run that newer database file on an older engine. You can run an older database file on a new engine in most cases. If you are using a patch that includes file format changes, you will not be able to run the database created with that patch level or newer on database servers that are older than the patch level where the file format change was introduced. That is what has happened here. The database appears to have been created using later patch of v17 and attempting to start it on the initial release of v17.

SQL Anywhere 17 has had 3 updates that have also had database file format changes (and documented in SAP Help).

• SP0 PL8 Build 2066
• SP0 PL22 Build 4003
• SP0 PL29 Build 4793

In this case, the details of the version used to create the database may not be obvious to the end user and there should be clear information on the minimum version required for this environment.

[keithfisherdsc]

I thought that maybe the upgrade message was being thrown because I had installed SQL Anywhere without a licence key (as the developer version) so I reinstalled it with the temp key that is available from the download page in SAP portal. However the databases BI_Audit and BI_CMS would still not start. I spotted that I was trying to start them with the demo personal server that starts when you connect to the sample demo.db file. So I have tried to start the Network Server but I still get this message:

is capability 98 a specific thing or a red-herring?

I see in the other window that my server is still only licenced as a restricted use developer edition. Is that my problem?

[amitrathi239]

I would suggest to raise a SAP support ticket.Support team will better in this scenrio to provide you the update.

[chris_keating]

That error means you are trying to run a newer database file version on an older engine version. I cannot recall the specific file version for Capability 98. In any event, check the service definition in SQL Central (v17 renamed Sybase Central) and make sure that you are using the version 17 engine instance. It would be helpful to look at BI4_log.txt as that may include helpful information.

I will also note that the engine console that you included shows you are using the developer edition. This version cannot be used in productive environments so will need to be licensed appropriately.

[keithfisherdsc]

I have installed SQL Anywhere 17 in a new location and am trying to follow this blog (https://blogs.sap.com/2017/02/14/sap-bi4.x-installationupdatepatching/) to recreate the service but I get this error:

the sample sql anywhere database is connectable to with no problems.

when I try to start and connect to the old BI4_Audit.db file via an ODBC connection I get this error:

I have downloaded the latest version of the SQL Anywhere database client and engine from SAP and have that installed already

[amitrathi239]

check mentioned SAP notes.

2509148 - How to recreate SQL Anywhere service for BI 4.2 Enterprise

2523373 - Where to download Installation package - SQL Anywhere