What caused the following error:
Error 509 (Bad memory cursor; bad table pointer)

Thank you.

Can you give more details, I mean from log.bshell? It might be related to shared memory, but can be confirmed only after looking at log.bshell

-- Avinash

This usually occurs when you abnormally terminate a session (like "output to console"->exit)

Or if something happens on the box that causes the driver to lose connection to the database.

Dave

In my opinion 509 is a symptom, not a cause. If nothing went wrong in terms of crashing users etc., then it may help to reorganize the tables.

From my experience within Baan and this 509, IF you are getting a lot of these errors, then it comes from a mismatch between portingset, standard objects and BW. Check that your versions are within a decent range.

Dear Victor,

Yes, same error I facing lot of time, please help me to find decent range.

OS : WIN NT 4.0
BackEnd : Oracle 8.0.5
BaaN : IV C4
Poring Set : 6.1c.06.02
Service Pack : 10
BW : B40c.67

Waiting for immediate reply.

-Suhas

Ok, hang on...
Portingset: 6.1c.06.07, solution 15219
BW client software: 068, solution 13743
Standard Program: solution 10923
bic_include6.1: solution 114812

... this is Victor's advice though... what tables are involved?

You need to check the dates of compilation/release of those objects (use bic_info6.1 command, bshell6.1 -v, etc.) and then select the most recent date and update the remaining ones to the version nearer that date (more or less).

You can check what solutions to install then by looking in the Baan website, searching for the solutions released per component code.

If you're not sure of what to do exactly or don't have enough experience, log a case with Baan: they will provide you the combination or, at least, they will tell you to upgrade all to the most recent versions and provide the solutions nr. to you. They may also know a different reason for those errors 509 besides that one I highlighted (it can happen!).

Actually the solution numbers I mentioned refer to the latest solutions of a component... these are generic solutions.

Other updates will depend on where you find your error most of the time. Still I think reorganizing could be a good option to get rid of the error.