I am testing version 12 (184.108.40.20606) and planning an upgrade very soon from v10.01.3960.
As part of test, I take the latest v10 backup, read in last log file to recover (dbeng10 -a) and then attempt to start as a v12 database (as I understand upgrade or unload/reload is not a requirement).
v12 database will not load successfully, instead creates Error Report (which I sent to Sybase under reporting option).
I can still load engine with v10. What should I try next? I really want to get to v12 but my hands are tied until I can get this engine to load sucessfully.
Other details: Windows 7 200 GB database 8GB RAM
asked 16 Aug '11, 13:30
Have you considered doing a full unload and reload? That way you get the full benefit of v12. A v10 database running under 12 is still a v10 database and many of the new features will not be available.
Have a look at this:
Rebuilding is often a good thing anyway as it reorganizes all the tables / indexes etc.
answered 17 Aug '11, 06:00
I realize this is possibly something I will have to open a case with tech support on, but here are some more details from error log that is generated.
VERSION=220.127.116.1106 FILENAME=C:\ProgramData\SQL Anywhere 12\diagnostics\SA12_20110816_160740_6804.crash_log OS=Windows 7 Build 7601 Service Pack 1 PROCESSOR=X86_64 EXEC_ARCH=X86_64 EXEC_PATH=C:\Program Files\SQL Anywhere 12\Bin64\dbeng12.exe MODULE_PATH=C:\Program Files\SQL Anywhere 12\Bin64\dbserv12.dll EXCEPTION_PTR=000000000CAADEF0 EXCEPTION_CODE=3221225477 EXCEPTION_FLAGS=0 EXCEPTION_RECORD=0000000000000000 EXCEPTION_ADDRESS=000000002072A970 EXCEPTION_NumParameters=2 EXCEPTION_Param0=0000000000000000 EXCEPTION_Param1=000000031FD5A000 TRYING_TO_SAVE_MINI_DUMP C:\ProgramData\SQL Anywhere 12\diagnostics\SA12_20110816_160740_6804.dmp DUMPLEVEL 0 SAVING_MINI_DUMP_COMPLETED CRASH_LOG_COMPLETE
Our game plan was to:
1. Thoroughly test as much as possible.
2. Upgrade software to v12.
3. Start up v10 database under v12.
4. If any issues arose, we could then abandon v12 and re-start engine as v10 until v12 issues could be resolved.
I was able to take another v10 backup and load up on server as v12. I ran some tests and am now getting the database to crash with error:
Assertion failed: 101212 (18.104.22.16809)[Backup]Page number on page does not match page requested--transaction rolled back.
I was able to re-start engine again as v12, but error re-occurs when I run statements again (large DELETE statement).
What does this assertion error indicate? Could one of the database spaces be corrupted somehow? How can you tell? I run a full validation with v10 weekly and that does not report any errors.
Next steps? Wait for newer ebf and start testing process again? Revert back to maintenance release or older ebf? Unload/Reload (takes 24 hours due to size of database and then lose ability to rollback to v10).
answered 17 Aug '11, 12:25