gget79
21st September 2009, 20:48
Hi experts,

I am working with LN 6.1 FP3.

I have a big problem when we want to change a table index of old table, then 512 error showing us, the only way that we have found are restart the server, we asked for the solution to Infor, but They tell us that is a problem with shared memory.....

Anybody can explain me how can fix this?

mark_h
21st September 2009, 21:46
Is this during the convert to runtime or when logging back in? I thought you could just stop and start shared memor. Wait for an expert to visit this thread.

gget79
21st September 2009, 22:05
Hi Mark,

This is when logging back in... How to do stop / start shared memory when SO server is UNIX........... Would We have that logout all users?

Thank you a lot....

dave_23
21st September 2009, 22:43
Can you explain the problem a little more? Specifically, is it reproduceable?

Unix doesn't require a restart of shared memory when reconfiguring tables. Only windows does.

Dave

gget79
21st September 2009, 22:54
Hi Dave,

Yes the problem is reproduceable, for example
- I have a old table tdcpe400
- I have to change the first index of this table, may be to add a field to index. I do it.....
- I convert to RTD
- I logout to LN
- I loggin to LN
- I want to see tdcpe400 for ttaad4500
- I get the 512 error
- I have made all it is possible to fix the 512 error, but I don't get.
- Only solution is restart the server and it works for me..

Infor says us that is a problem with shared memory....

My question how to can fix this problem, without I have to restart each time the server?

dave_23
22nd September 2009, 00:18
What OS are you using? you're profile just says unix.

Dave

gget79
22nd September 2009, 00:39
Hi,

My OS version is SUSE LINUX ENTERPRISE SERVER 10

baan_learner
22nd September 2009, 06:59
Please try reorganizing the table.

Hitesh Shah
22nd September 2009, 18:31
When u reconfig probably there is in error and it does not reconfig . However dict file dppmmmnnn is replaced and current one becomes .old .

At the time u get error 512 , u get an error in or log.oracle / log.bshell like dd len and database len etc . In all probability the reconfig is not done successfully and replacing .old to new one (keeping backups ) u can access the old table with old definition.