I guess by 'separate index' you mean index in a different dbspace from data, right?
So e.g. your tables in a dbspace called datadbs, and associated indices in dbspace indexdbs.
Since we seem to be talking 'import', so unload from old and load into new database server, you'd have to newly define the database, its tables and indices in the new server anyway ... and could just augment the CREATE INDEX statements with an 'IN indexdbs' clause. Also be sure to not have any constraints defined inline in the CREATE TABLE statements as those would create implicit indices without direction to the indexdbs, so they'd reside with the tables.
In case you're planning to use dbexport/dbimport utilities instead, simply edit the <database>.sql in the <database>.exp directory adding the 'IN indexdbs' clause.
As for the chunk question: you'd either use one extendable chunk per dbspace, or multiple non-extendable ones. If you had multiple extendable ones, I'm not sure they'd be used evenly, and your evidence seems to confirm only (the first) one would grow. Technically, multiple chunks per dbspace would allow flushing new data to all of them in parallel, during checkpoint, but in reality this depends on a number of other factors, and if this isn't going to be a high throughput system, you won't sense any difference.
HTH,
Andreas
------------------------------
Andreas Legner
------------------------------