Assertion Error Sybase Adaptive Server Anywhere


Does anyone know what causes a Sybase Adaptive Server Anywhwere Database version 8.02 to stop servicing all
odbc requests and produce a select error s1000 Internal database error assertion failed 200601 (8.0.2.4322) Page for requested record not a table page or record not present on page. The dbase continues to run and if a run a validation on the databse it returns ok.

I have 10 + ODBC connections to this database. I use task scheduler to run the dbbackup application every 10 minutes on the database. The crash occurs both during the dbbackup and inbetween so I feel it is not related.

Jim



JffishbonesAsked:
Who is Participating?
 
grant300Commented:
I think you are just hosed.  You can't meet contractually-specified Service Level Agreements just by wishing (or in this case, badgering the poor system admin).  Clearly they are trying to wring every last penny out of whatever this business deal is and don't care to "do it right".

Realistically, your only choice is to:
1) document the problems with the existing setup
2) make recommendations on one or more solutions
3) get/make some estimates on the cost of those solutions
4) quantify the cost of downtime and or needless disaster recovery
5) hope that an obvious cost-benefit analysis will open their eyes.
6) if it doesn't, look for a job that does not involve working for in-duh-viduals.

Even if you are sure they won't be swayed by your arguments, you have built an airtight cover for your ass when they finally have a major outage.

TANSTAFL  (There Ain't No Such Thing As a Free Lunch)
0
 
grant300Commented:
Why are you running the dbbackup app every ten minutes?  If you are maintaining the transaction logs correctly, you can use the last full backup and the log to get up-to-the-second recovery and you aren't beating the snot out of the system every 10..

Bill
0
 
JffishbonesAuthor Commented:
Bill

My environment requires a recovery process with a database that is out of date almost immediately which is why I backup everything
every 10 minutes. Are you saying that I can just backup the transaction log and not the entire dbase every 10 minutes. Just backup the dbase say once a day on off hours. If so what is the best way to do this? I thought the transaction log writes back to the database at configurable times? If so the database would be out of date every time this write back occurs? Thanks for any help.

Jim
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
grant300Commented:
Tell me about your recovery requirements.
- Are you protecting the system against disk/system failure?
- Are you worried about complete system loss (disaster recovery)?
- Is the application so unstable that it sometimes corrupts things to the point you just want to recover the last valid state?

If you are worried about disk failure, you can do a nightly full backup, create transaction log(s) large enough to handle a complete days worth of work, and mirror the logs on two physical devices.  You get up-to-the second recovery and only have to backup the system once a day.  This is how banks and every other organizations who can't afford to loose any data setup their systems.

Disaster recovery is generally not expected to operate up-to-the-minute unless you are a very large organization with at least two physical sites and can afford the network bandwidth to either replicate the database or use high-end storage arrays that replicate writes remotely.  Doesn't sound like your situation.

Application corruption is a whole different kettle of fish.  The obvious solution here is to fix the application.  If you do not have control of the application or cannot convince the powers that be to fix the sucker, then your technology solution is to use a storage array or filer that alllows you to take regular snapshots.  If/when things get screwed up, you can simply recover the storage array or filer to the last snapshot that was O.K. and pick up from there.

Hope that helps,
Bill
0
 
JffishbonesAuthor Commented:
Bill

Recently we had our transaction log file get corrupt, we lost the database.
I am trying to prevent this from happening again. I know asa does not have real time replication so I came up with backing
up the datbase regularly as a solution using the dbbackup application.

My goal it to be able to recover from the last stable state. The database is mission critical, if it is down more than 2 hours it could cost big bucks in fines from our customer. I am looking for the best solution to be able to recover the database from it's most current stable state.

Thanks again.

Jim
0
 
grant300Commented:
Well, we have a couple of issues here.

1)  How and why did the transaction log file get corrupted?  Was it a bad sector on the disk, or did something happen programatically with the database?

2)  You have to come up with a system that is architected adequately for your mission critical service level requirements.

I don't have enough information to address item 1 but it does need to be addressed.

I have some thoughts on item 2.

In order to meet enterprise grade service level agreements you have to have the proper hardware and software environment.  There is no way to cheap out here and be succesful.  How big is the database and how many simultaneous users are there?  It may be you have simply outgrown ASA and should consider moving to ASE.

Even if you stay with ASA, there are two areas you can shore up.  The first is to do periodic backups of the LOG, rather than the whole database.  Less load on the system and less likely to cause probelms by itself.  The other is to look at some enterprise grade disk technology.  Look at something like a NETAPP filer.  It (and some similar products) has all kinds neat software inside that can do things like take regular snapshots of the filesystem.  You could set it up to take a snapshot every 10 to 30 minutes.  It really just keeps track of the changed sectors since the last snapshot.  The other slick thing about it is that you can rollback to a snapshot very quickly.  It sounds as if that would address your issues in a bullet-proof way.

Another step I would take soon is to upgrade to a newer release of ASA.  9.0.1 is current and the 10 User Server Upgrade cost is only $499.

Bill.
0
 
JffishbonesAuthor Commented:

Not sure how the transaction log got corrupt. Database would just not open.

Item 2 - we have redundant database servers but the powers to be will not spend the money for MS sql for real time replication so I am
trying to find the best way to recover from either a database or server failure.

Jim
0
 
JffishbonesAuthor Commented:
I agree Thansk, I am opening anther question on live dbbackup / recovery.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.