A little more information would be helpful. Which Linux are you running? What application or database are you running? What was being run when this error occurred.
If this is a Sybase database server, this link should help.
While this may have gotten the OP to their solution, I think this is the worst type of response that could have been given. This basically is telling the OP that there are no answers here and that they should go somewhere else. This type of response will end up killing this site.
This link to sybase.com is the first result of a Google search for the OP's error message. It is insulting to the OP to carelessly paste the first result of a Google search. What if other Google results would also be valuable to the OP?
If the OP had been given an actual response, with maybe a background explanation so they could learn what had happened, and maybe some tips on how to troubleshoot that kind of problem in the future, then people going to Google first with the same problem may end up on Tek-Tips. That's how this site will survive, not by sending people to other sites.
Quote (SamBones)
Tek-Tips has a Forum specifically for Sybase. They may be able to give you some very detailed and helpful recommendations for this problem.
This may be more careless misdirection. The Tek-Tips Sybase forum has very little traffic. You have to go back to 2017 to find the last time anybody replied to a Sybase question. The last reply before that was in 2014. The last time anybody asked an unanswered Sybase question was in 2019.
It would certainly be helpful if a more responsive member could have shared a more immediate resource, much earlier...and not have that useful resource deleted from this discussion. That type of petty reporting will slowly kill this site.
Red Flag Submitted
Thank you for helping keep Tek-Tips Forums free from inappropriate posts. The Tek-Tips staff will check this out and take appropriate action.
Reply To This Thread
Posting in the Tek-Tips forums is a member-only feature.
Talk To Other Members
RE: Error: 694, Severity: 24, State: 10 An attempt was made to read logical page '153', virtpage '616' f
A little more information would be helpful. Which Linux are you running? What application or database are you running? What was being run when this error occurred.
If this is a Sybase database server, this link should help.
https://infocenter.sybase.com/help/index.jsp?topic...
RE: Error: 694, Severity: 24, State: 10 An attempt was made to read logical page '153', virtpage '616' f
Tek-Tips has a Forum specifically for Sybase. They may be able to give you some very detailed and helpful recommendations for this problem.
https://www.tek-tips.com/threadminder.cfm?pid=187
RE: Error: 694, Severity: 24, State: 10 An attempt was made to read logical page '153', virtpage '616' f
While this may have gotten the OP to their solution, I think this is the worst type of response that could have been given. This basically is telling the OP that there are no answers here and that they should go somewhere else. This type of response will end up killing this site.
This link to sybase.com is the first result of a Google search for the OP's error message. It is insulting to the OP to carelessly paste the first result of a Google search. What if other Google results would also be valuable to the OP?
If the OP had been given an actual response, with maybe a background explanation so they could learn what had happened, and maybe some tips on how to troubleshoot that kind of problem in the future, then people going to Google first with the same problem may end up on Tek-Tips. That's how this site will survive, not by sending people to other sites.
This may be more careless misdirection. The Tek-Tips Sybase forum has very little traffic. You have to go back to 2017 to find the last time anybody replied to a Sybase question. The last reply before that was in 2014. The last time anybody asked an unanswered Sybase question was in 2019.
It would certainly be helpful if a more responsive member could have shared a more immediate resource, much earlier...and not have that useful resource deleted from this discussion. That type of petty reporting will slowly kill this site.