<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tt/onlinemanual/100150" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">To reconfigure tables on a Microsoft x86 Windows platform</Title>
		<Keyword ContextSensitive="No"><Level1>Reconfigure tables</Level1>
			<Level2>MS Windows</Level2>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph class="Default">At runtime, table definitions are stored in files in the operating system. To improve the performance of your ERP LN system, these runtime table definitions can be loaded into the shared memory.</Paragraph>
		<Paragraph class="Default">When table definitions are changed, you must reconfigure the corresponding tables.</Paragraph>
		<Paragraph class="Default">On Microsoft x86 Windows machines the shared memory is static: changed table definitions are not automatically loaded into the shared memory.</Paragraph>
		<Paragraph class="Default">So, when table definitions are changed, (for example, because you installed a PMC solution or you converted table definitions, that you have changed through the Application Development sessions, to runtime), there is a mismatch between the new table definitions in the runtime data dictionary and the old definitions in the shared memory. A reconfiguration of the tables will therefore result in error messages.</Paragraph>
		<Paragraph class="Default">To avoid this problem, you must remove the table definitions from the shared memory, before the reconfiguration process starts.</Paragraph>
		<ProcedureList><ListIntro>To successfully change table definitions, and reconfigure the corresponding tables, take the following steps:</ListIntro>
			<ListItem>Move the $BSE\lib\srdd_tab6.2 file to a different folder.</ListItem>
			<ListItem>Clear the shared memory: <List><ListItem>Start the <GUIRef href="" role="manual">Infor Enterprise Server Service Manager</GUIRef> snap-in and stop the shared memory for your BSE environment.</ListItem>
					<ListItem>Close the <GUIRef href="" role="manual">Enterprise Server Service Manager</GUIRef> snap-in.</ListItem>
					<ListItem>Start the <GUIRef href="" role="manual">Enterprise Server Service Manager</GUIRef> snap-in again and start the shared memory.</ListItem>
					<ListItem>Open the <GUIRef href="" role="manual">Loaded Shared Memory</GUIRef> tab in the <GUIRef href="" role="manual">Shared Memory Properties</GUIRef> dialog box. Verify whether all table definitions (and program objects and report objects) are removed from the shared memory. The shared memory should now only contain a number of tss files and Unicode files.</ListItem>
				</List>
			</ListItem>
			<ListItem>Change the runtime table definition(s), for example: <List><ListItem>install a PMC solution, or</ListItem>
					<ListItem>convert table definitions, which you changed through the Application Development sessions, to runtime.</ListItem>
				</List>
			</ListItem>
			<ListItem>Reconfigure the tables.</ListItem>
			<ListItem>Log off from the ERP LN application and log on again.</ListItem>
			<ListItem>Run the <GUIRef href="/baanerp/tt/aad/ttaad4232m000" role="session">Check Tables (ttaad4232m000)</GUIRef> session.</ListItem>
			<ListItem>Move the srdd_tab6.2 file back to the $BSE\lib folder.</ListItem>
			<ListItem>Fill the shared memory: <List><ListItem>Start the <GUIRef href="" role="manual">Enterprise Server Service Manager</GUIRef> snap-in and stop the shared memory for your BSE environment.</ListItem>
					<ListItem>Close the <GUIRef href="" role="manual">Enterprise Server Service Manager</GUIRef> snap-in.</ListItem>
					<ListItem>Start the <GUIRef href="" role="manual">Enterprise Server Service Manager</GUIRef> snap-in again and start the shared memory. The changed table definitions are now loaded into the shared memory</ListItem>
				</List>
			</ListItem>
		</ProcedureList>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">This procedure does not apply to UNIX platforms. On UNIX machines the shared memory is dynamic. Changed table definitions are read directly from disk, so that you can reconfigure tables immediately after the table definitions were changed.</Paragraph>
		</Note>
	</GeneralSection>
</ManualTopic>
