In the future this probably a question that should be posted to
opendatakit-developers list as digging into this could get quite
technical.

My guess is looking at your form it appears to be quite large so the
form may need to be split up into smaller tables to fit the database
requires. Aggregate has a built in algorithm for splitting forms into
separate tables if a single table will be too large for the database
engine.

There is a wiki on the code site that talks about the way Aggregate
structures the database tables:
http://code.google.com/p/opendatakit/wiki/AggregateDatabaseStructure

Here are some relevant parts of the text.

"The top-level table for a user-uploaded xform will end with _CORE or
_COREn, where 'n' is a number. The name of the top-level table is
roughly formID + "_" + groupName + "_CORE". But that is all shrunk
down to be less than 64 characters, so if you have a long form id, it
will be compressed into a shorter string. The same compression is done
for column names. If you have an xform with nested non-repeat groups,
the full path of the group is preserved, but similarly compressed.
...
The actual table name may vary from one instance to the next depending
upon the tables defined in the database at the time the form was
uploaded; the server ensures that the table names do not collide and
modifies table names until there are no collisions. Also, because of
column count and row size limitations, larger forms, such as eIMCI
will be split across multiple tables. eIMCI uses more than 6 tables,
for example. The software first attempts to split the xform data
following the groupings within the xform. Consider, for example, an
xform representing a medical record where you have a group describing
the provider, a group describing the patient, and a group describing
the reason for the visit and the treatments proscribed. If this
information cannot fit within one database table, the system will
first attempt to split it into 3 tables, one holding the
characteristics of the provider, one holding the characteristics of
the patient, and one holding the visit information because the xform
had that structure. "

Best,
Waylon