Hi friends,

I have little problem. I added few field in an existing table, using new domains. The runtime DD of table is created without any error. I also created runtime DD for domans before creating the runtime DD of table. Now, if I try to access the table through the session "Display general table information (ttaad4500)" and "General table maintenance (ttaad4100)", I got error for runtime DD. If I drop the new fields from the table and then create again runtime DD, table can access through session ttaad4500 & ttaad4100. The same problem for new table, if new table use the new domains. If I use existing domains, there is no problem but if use new domains, got error for runtime DD. Yes, runtime DD for new domains are already created.

I also restarted the shared memory service just to try if new domains are not loaded, but problem not resolved. The problem is only in the Live Company, but no problem with the test company in the same installation. Any idea???

Thanks in advance.

Still could be shared memory as this doesn't seem to reliably "refresh" on NT/Windows. I have found that removing the individual domain & table definition through the shared memory manager sometimes helps.

Ed

HI,

I have removed the table defintion from shared memory and loaded it again, but still problem not resolved. Yes how whould I removed the domain from the shared memory, the domain name is "cisli.doct".

Thanks in advance

hi,

First run creat runtime for domain for live package VRC then for table with select " Reconfigure " option . It may solved the problem. But mind it no users should use that table.

Regards

__________________
Deb
Arise Awake & Stop not till the Goal is Reached...........Swami Vivekananda.

Deb's option may work for you but just in case:

to remove the domain from shared memory, you actually remove all of the domains for the package.

So in shared memory manager, go to show loaded, wait until it refreshes the list then find the package - which I think is "ci" then click remove object.

Ed

From my experience, you need to have all bshells closed before restarting the shared memory server. When all bshells are closed, i.e. no active users in Baan, and also make sure no old "hanging" bshells, then you restart the shared memory server. This should work.