Message in system log 88 record - Ran out of load-id naming conventions.

[jeffs42885]

 I was just performing system integrity checks, and noticed this.

arsload: 06/04/12 13:17:55 Indexing completed
arsload: 06/04/12 13:17:55 -- Loading started, 20130901477 bytes to process
OnDemand Load Id = >19931-3-0-3091FAA-15493-15494<
OnDemand Load Id = >19931-3-0-3091FAA-15493-15496<
Ran out of load-id naming conventions.  Increase the size of the Application Group Object Size.
The last row successfully loaded was 13150
Loaded 13150 rows into the database
arsload: 06/04/12 13:44:05 Loading failed
arsload: Processing failed for file >/OnDemand/load/AFPFILE.ARD<
arsload: 06/04/12 13:44:05 -- Unloading started
OnDemand UnLoad Successful - LoadId(19931-3-0-3091FAA-15493-15496) Rows Deleted(13150)

This is an AFP file that is indexed using Xenos 5.6. Any thoughts? I have never seen this message before

[pankaj.puranik]

I am not 100% sure of what I am writing below.

Looking at the input file size, it's around 20 GIGS.
When CMOD process a report, it stores the data in storage objects.
You can configure the storage object size in the Application Group.

As per the message, it looks like CMOD is having problem in allocating the next storage object name when one storage object is full.
In the message below, '3091FAA' is the storage object name.

As per the suggestion in the message, increase the storage object size from the default of 10 MB may help.

Cheers
Pankaj.

[Justin Derrick]

Yeah, I'd recommend dramatically increasing the size of an individual object -- I wouldn't go any larger than 100MB.  This WILL cause performance problems for users with slow network connections, as the size of a single (ie, the first) object is now much larger.

If you have large object support enabled as well, I'd increase that number to 1000 pages.

Good luck, and please let us know what the solution to your issue is!