Standalone E900 and Cross Reference


Well Known Member
Hello guys,

So I have this E900 standalone with MSSQL database.
I'm trying to generate the cross reference on them.
First problem that arose is that the cross reference builder batch looked for the specs in the DEMO pathcode which is empty for specs (central objects are only stored "locally" and are not in DEMO pathcode, probably to save some space for the already huge installation program)
So what I did is I copied all the tables from spec_master ("local" specs) to JDEVL (central objects for DEMO pathcode), since I couldn't find a way to make the cross reference batch read in spec_master (the tables have an added "MASTER" after their name so I dont think it is possible to make OCM redirections to them, but maybe you guys have a better idea ?).

here are the SQL commands I used :

insert into jdevl.dbo.F98710 select * from SPEC_MASTER.DBO.F98710MASTER;
insert into jdevl.dbo.F98711 select * from SPEC_MASTER.DBO.F98711MASTER;
insert into jdevl.dbo.F98712 select * from SPEC_MASTER.DBO.F98712MASTER;
insert into jdevl.dbo.F98713 select * from SPEC_MASTER.DBO.F98713MASTER;
insert into jdevl.dbo.F98720 select * from SPEC_MASTER.DBO.F98720MASTER;
insert into jdevl.dbo.F98740 select * from SPEC_MASTER.DBO.F98740MASTER;
insert into jdevl.dbo.F98741 select * from SPEC_MASTER.DBO.F98741MASTER;
insert into jdevl.dbo.F98743 select * from SPEC_MASTER.DBO.F98743MASTER;
insert into jdevl.dbo.F98745 select * from SPEC_MASTER.DBO.F98745MASTER;
insert into jdevl.dbo.F98750 select * from SPEC_MASTER.DBO.F98750MASTER;
insert into jdevl.dbo.F98751 select * from SPEC_MASTER.DBO.F98751MASTER;
insert into jdevl.dbo.F98752 select * from SPEC_MASTER.DBO.F98752MASTER;
insert into jdevl.dbo.F98753 select * from SPEC_MASTER.DBO.F98753MASTER;
insert into jdevl.dbo.F98760 select * from SPEC_MASTER.DBO.F98760MASTER;
insert into jdevl.dbo.F98761 select * from SPEC_MASTER.DBO.F98761MASTER;
insert into jdevl.dbo.F98762 select * from SPEC_MASTER.DBO.F98762MASTER;
insert into jdevl.dbo.F98770 select * from SPEC_MASTER.DBO.F98770MASTER;

After that, I successfully ran the cross reference batch on Business View Object. it did create the cross reference entries.

But when i tried to run the cross reference batch on applications, I had some errors in log after a while :

6236/2484 WRK:Starting jdeCallObject Mon Sep 12 22:52:23.859002 Jdbodbc.c6904
ODB0000164 - STMT:00 [42000][1105][2] [Microsoft][SQL Native Client][SQL Server]Could not allocate space for object 'DBO.F980021'.'F980021_2' in database 'JDEVL' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding ad

Do you guys have any idea on how to solve this ?
Using SQL Manager I looked at the maximum size of the database files and it's way above the current size so I don't really understand the problem.


Well Known Member
so i found out why i had this problem it is because SQL Server Express 2005 which comes with jde E900 standalone, MSSQL database, is limited to 4GB file size.
I am looking for other ways to generate the XREF


Well Known Member
after truncating the tables in JDEVL ,because it was preventing the Local Web from working(web needs to insert records to F989999 which is in jdevl and JDEVL was full at 4 Gb), i found another way of generating the Xref, without having to copy the specs tables.
I created a fake pathcode(in fact I think it only needs ocm record to F9861 because it's the only one I activated in OCM) .I had to duplicate the F9861 records to my pathcode also.
Then I created SQL views that redirected the "select"s from F98XXXX to F98XXXXMASTER.
Finally it worked ! But I suspect the Xref tables alone (F980011 and F980021) take more than 4 gb if you build them all.
I even created separated databases for F980011 and F980021 and then created the data sources in JDE and OCM redirections but I suspect 4 GB is not even enough for just F980021.
The last solution is to create 3 separate database for APPL, UBE, and then, the rest, and then create 3 JDE users and redirect their OCM to each table.