Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in August and this forum will be retired.

We recently updated the database system from an older 12.0.1 to the current EBF, during this process we identified, that a dbupgrade was needed otherwise the db file would not start anymore.

Now we would like to automate this process and are looking for a good way how to check, if the dbupgrade is really necessary (or recommended).

asked 29 May '13, 10:11

Martin's gravatar image

accept rate: 14%

Don't know of an automatic process - however, usually the EBF readme will tell whether a particular fix needs a DBUPGRAD - cf. this one for 12.0.1:

================(Build #3782  - Engineering Case #717689)================

If an 11.x or 12.x database was upgraded using either the Upgrade utility, or ALTER DATABASE UPGRADE, then external environments would no longer have started. This problem has now been fixed.
Note that in order to apply this fix, the database will need to be upgraded again once this fix has been properly deployed.

So careful reading might be a first step:)

(29 May '13, 17:32) Volker Barth
Replies hidden

Good point, anyway: If you have heterogeneous customer sites your update procedure might have to apply the upgrade for one customer but not for another because the later one already have the upgraded db file. And to spare the effort of always upgrading I would like to be able to identify if it is necessary...

(31 May '13, 03:17) Martin

The upgrade process doesn't take a long time, does it? (says the person who hasn't run an upgrade in years :)

(31 May '13, 09:44) Breck Carter

In my limited experience (a few upgrades in years), it doesn't take long. But it some cases it made the DB inaccessable - cf. that FAQ, so the timespan needed was not the problem. AFAIK, that problem was solved for newer versions, and that note should not be seen as argument against a DBUPGRAD...

(31 May '13, 10:44) Volker Barth

If you just want to know whether a particular database has been upgraded or not (or to what EBF) - in contrast to know whether a new feature requires a DBUPGRAD run or not - , then you can query SYSHISTORY. That system view will contain an entry named "DBUPGRADE" for each DBUPGRAD-operation with the according version number, and thereby it should be easy to find out if another DBUPGRAD is required or not.

If no upgrade has ever been made, the "INIT" value will tell the version of the system catalog and the like...

permanent link

answered 31 May '13, 07:42

Volker%20Barth's gravatar image

Volker Barth
accept rate: 34%

Thanks I wasn't aware of the operation value UPGRADE in syshistory.

(31 May '13, 09:36) Martin
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 29 May '13, 10:11

question was seen: 1,845 times

last updated: 31 May '13, 10:44