SA12 freezes when running a database created with SA11

[former_SQLA_member1694875]

Hello, Has anyone had a problem with SA12 (12.0.1.3356) freezes when running a database that was created with SA11? The database has not been rebuilt, and as far as I understand, it doesn't need to be rebuilt according to http://infocenter.sybase.com/help/topic/com.sybase.help.sqlanywhere.12.0.0/pdf/sachanges12.pdf (see Upgrading to SQL Anywhere 12). The database works well and sometimes mystical freezes occur (once or twice an hour) - it seems like the database server is doing something internally, and nothing (or very slow) can be done (from several seconds to several minutes). Is there any other option than rebuild?

[Breck_Carter]

Please show us exactly where you read that "it must not be rebuilt"... you can find specific pages online here http://dcx.sybase.com/index.html#1201/en/sachanges/sachanges12.html instead of referring to a PDF.

[Breck_Carter]

Foxhound might help you find the cause, or perhaps a clue to the cause. http://www.risingroad.com/

[former_SQLA_member1694875]

http://dcx.sybase.com/index.html#1201/en/sachanges/v10upgrade-up-sql-any-123456.html says:

"If you are upgrading from version 10 or later, you can either upgrade or rebuild your database. Upgrading or rebuilding is an optional step because the version 12 software can be used with a version 10 or later database. However, if you want to take advantage of all the new features in version 12, you must rebuild your database."

So if we do not want to take advantage of all the new features it should be enough to just start an old database on SA12 server without migration or rebuild. We want to firstly make sure that SA12 has no problems with our software and then (and only then) rebuild.

[MarkCulp]

Thanks for the clarification. I think we are confused by your use of "must not be" - what you mean is that it "doesn't need to be" which is correct; a 12.0.x server can run/use a database that has been built by v10.0.x or v11.0.x

[former_SQLA_member1694875]

Sorry, my English is not good enough. I have corrected the description of this topic.

[MarkCulp]

Platform? Windows? Version of OS? When the server "freezes" how much CPU is the server using? How much IO?

Check the server console log to see if there is a checkpoint running at the time that the server "freezes" - it could be that the server is in the process of flushing all dirty pages from the cache in preparation for a checkpoint?

[former_SQLA_member1694875]

Windows 2008 R2 64bit, 2 CPU. It is the same server on which the same database was running with SA11 before without problems. IO on freeze: average 15, max 150 IOPS. CPU use: 30 to 50 percent. There are no suspicious changes (gaps in time) in the console log when checkpoints are being done. I mean that checkpoint has no influence to the speed of other operations.

[MCMartin]

From Volker and Breck came this advice for a different question:

"I fully agree that dbsrvX -o (possibly with its variants -oX) should be using on every production server to help diagnosis.

(Jan 22 at 18:56)Volker Barth

Further to what Tyson and Volker said: -o filespec1.txt -oe filespec2.txt -os 1M is a good combination for production. The -os 1M keeps the file size manageable for browsing with Wordpad etcetera. For a service the filespecs probably have to have the full path. "

[former_SQLA_member1694875]

-o is always being used but I do not see anything suspicious in the .slg file.