How do I resolve history problems in Sybase?

An example of a history problem is:

Having problems retrieving more than 24 hours of data on some datasets but others can go back one month or more, even though they have been logging to the sysbase for same periods and have the same data type.

To resolve this, one can first check if there are no conflicts within the data given (i.e. checking if certain columns have proper values for not null property). Another reason for this is when a deadlock error occurs; this usually indicates that there are instances wherein multiple transactions are executed at the time. Verify if there are other concurrent gateways that are logging onto this database; it may be the reason for the deadlock message in the logs.

Then there are alterations made to the database scheme.

You will find the details in the resources/databses/sysbase/alter-1.2-row-level-locking.sql

For more information on this:

Sybase is used only to do page-level locking, to maximize performance in the absence of contention. If application designers did not understand how to work with this, one would see lots of deadlocks, especially with redundant conflicting locks on index pages. It can now do row-level locking and DBAs have no qualms about enabling that (or the ?datapages? halfway house) where necessary. For Sybase?s official story, see these two links: 

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc20021_1251/html/locking/X25549.htm 

http://manuals.sybase.com/onlinebooks/group-as/asg1250e/ptallbk/@Generic__BookTextView/18982;pt=19235