It just won't work that way since all the data is within the DATA folder. You would have to break up 1000 folders separately. As far as the package being 100MB why does it run out of memory the machine has 4GB and it's no where near full usage when the error occurs. My guess is this is some .NET array crash due to the amount of sub-folders. No one else has run into this would be my best guess.
The Rock On Fri, May 16, 2008 at 5:16 PM, Steve Dang <[EMAIL PROTECTED]> wrote: > MapGuide does not restrict the amount of objects or sub folders within a > repository. The Server performs/protects a Load Package operation within a > single transaction. The bigger the package is, the more memories/time are > required. Try to break the package into smaller ones, then run them > sequentially. > > > > Steve. > > > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *Rock Beans > *Sent:* Friday, May 16, 2008 3:00 PM > *To:* MapGuide Users Mail List > *Subject:* [mapguide-users] An exception occurred in DB XML component. > Error: DbSequence::get: Not enough space > > > > What does this error mean when loading a 103MB package? I am using the > 2.0.1 version of MapGuide OS. The log was about 27,000 lines long before > this error came up. Is there a limit to the amount of objects or sub folders > within a repository? Any info would be great as we are gearing up a BIG > corporate customer for you guys (Autodesk). > > Error from MapAdmin: An exception occurred in DB XML component. Error: > DbSequence::get: Not enough space > > The Rock > > _______________________________________________ > mapguide-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapguide-users > >
_______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
