DB-Server 16.0.0.2127 can't open database created with 16.0.0.1324

[reimer_pods]

I've recently installed a Support Package updating my SA16 version to 16.0.2127. Today I tried starting a database that had been created some time ago using an engine with build 16.0.1324. That resulted in the following message:




Here's a dump from the database header indicating the dbinit version:

---

Update: installing the last availabe EBF (16.0.2158) didn't change anything

Any ideas how this could happen?

[Breck_Carter]

Please start the database with 16.0.0.1324 and show us the result from SELECT @@VERSION, * FROM SYSHISTORY;

The following attempt to create a reproducible used 16.0.0.2127 to start the 16.0.0.1324 demo.db... since the database started OK, it was a failure as a reproducible:

"%SQLANY16%\\bin64\\dbspawn.exe"^
  -f "%SQLANY16%\\bin64\\dbsrv16.exe"^
  -o dbsrv16_log_demo.txt^
  -oe dbsrv16_log_fatal_demo.txt^
  demo.db

"%SQLANY16%\\bin64\\dbisql.com"^
  -c "ENG=demo;DBN=demo;UID=dba;PWD=sql;CON=demo-1"

PAUSE

I. 08/11 11:33:26. SQL Anywhere Network Server Version 16.0.0.2127 
...
I. 08/11 11:33:26. Starting database "demo" (C:\\download\\SQL Anywhere 16.0.0.1324 GA\\demo.db) at Tue Aug 11 2015 11:33
I. 08/11 11:33:26. Performance warning: Database file "C:\\download\\SQL Anywhere 16.0.0.1324 GA\\demo.db" consists of 3 disk fragments
I. 08/11 11:33:26. Transaction log: demo.log
I. 08/11 11:33:26. Starting checkpoint of "demo" (demo.db) at Tue Aug 11 2015 11:33
I. 08/11 11:33:26. Finished checkpoint of "demo" (demo.db) at Tue Aug 11 2015 11:33
I. 08/11 11:33:26. Database "demo" (demo.db) started at Tue Aug 11 2015 11:33
I. 08/11 11:33:26. Database server started at Tue Aug 11 2015 11:33
I. 08/11 11:33:26. Trying to start SharedMemory link ...
I. 08/11 11:33:26.     SharedMemory link started successfully
I. 08/11 11:33:26. Trying to start TCPIP link ...
I. 08/11 11:33:26. Unable to start on default port; starting on port 49158 instead
I. 08/11 11:33:31.     TCPIP link started successfully
I. 08/11 11:33:31. Now accepting requests
I. 08/11 11:34:18. Cache size adjusted to 19192K

SELECT @@VERSION, * FROM SYSHISTORY;

@@VERSION,operation,object_id,sub_operation,version,platform,first_time,last_time,details,first_time_utc,last_time_utc
'16.0.0.2127','INIT',0,'','16.0.0.1324','W2008R2 #7601 SP 1 X86','2013-01-24 21:11:53.000','2013-01-24 21:11:53.000',,'2013-01-25 01:11:53.000+00:00','2013-01-25 01:11:53.000+00:00'
'16.0.0.2127','LAST_START',0,'','16.0.0.2127','W7 #7601 SP 1 X86_64','2015-08-11 11:33:26.000','2015-08-11 11:33:26.000',AT=0x20;DB=SATA;DM=ATA_____WDC_WD10EZEX-75M1A01;,'2015-08-11 15:33:26.000+00:00','2015-08-11 15:33:26.000+00:00'
'16.0.0.2127','START',0,'','16.0.0.1324','W2008R2 #7601 SP 1 X86','2013-01-24 21:11:53.000','2015-08-11 11:33:26.000',AT=0x20;DB=RAID SATA;DM=ATA_____WDC_WD10EZEX-75M1A01 DELLPERC_H7002.10;,'2013-01-25 01:11:53.000+00:00','2015-08-11 15:33:26.000+00:00'
'16.0.0.2127','START',0,'','16.0.0.2127','W7 #7601 SP 1 X86_64','2015-08-11 11:33:26.000','2015-08-11 11:33:26.000',AT=0x20;DB=SATA;DM=ATA_____WDC_WD10EZEX-75M1A01;,'2015-08-11 15:33:26.000+00:00','2015-08-11 15:33:26.000+00:00'

[reimer_pods · Accepted solution]

Older versions of the engine have the same symptom and can't start the database. But with SA17 I could finally start the database and check SYSHISTORY

operation;object_id;sub_operation;version;platform;first_time;last_time;details;first_time_utc;last_time_utc
'START';0;'';'16.0.0.2076';'W7 #7601 SP 1 X86_64';2015-04-16 14:12:37.0;2015-07-20 18:25:07.0;AT=0x20;DB=SATA Unknown;DM=((( ST31000524AS____________JC4A;;'2015-04-16 12:12:37.000+00:00';'2015-07-20 16:25:07.000+00:00'
'START';0;'';'17.0.0.1062';'W7 #7601 SP 1 X86_64';2015-07-20 18:25:07.0;2015-07-20 18:25:07.0;AT=0x20;DB=SATA;DM=ST31000524AS____________JC4A;;'2015-07-20 16:25:07.000+00:00';'2015-07-20 16:25:07.000+00:00'
'LAST_START';0;'';'17.0.0.1062';'W7 #7601 SP 1 X86_64';2015-07-20 18:25:07.0;2015-07-20 18:25:07.0;AT=0x20;DB=SATA;DM=ST31000524AS____________JC4A;;'2015-07-20 16:25:07.000+00:00';'2015-07-20 16:25:07.000+00:00'
'LAST_BACKUP';0;'';'17.0.0.1062';'W7 #7601 SP 1 X86_64';2015-07-20 18:30:31.0;2015-08-11 17:42:18.0;BU=Type:Full 'Imag';;'2015-07-20 16:30:31.000+00:00';'2015-08-11 15:42:18.000+00:00'
'UPGRADE';0;'';'17.0.0.1062';'W7 #7601 SP 1 X86_64';2015-07-20 18:30:34.0;2015-07-20 18:30:34.0;CA=E00C3000D000FEDFF7FDD;;'2015-07-20 16:30:34.000+00:00';'2015-07-20 16:30:34.000+00:00'

So it looks like the database has been upgraded, but not rebuilt to SA17. The changes of the structure or system tables made by the upgrade seem to prevent SA16 from starting the database.
Thanks, Breck, for reminding me of SYSHISTORY.

[Breck_Carter · Accepted solution]

I stupidly read the original message as saying "database must be upgraded" when in fact it spoke the truth: "server must be upgraded"... Foxhound issues similar messages, and I misread those too... with great age comes great confusion ( Spider-Man is 53 years old so it's time to warn him 🙂