A 'select/into' is actually a DDL command (create table) combined with a DML command (insert). ("Duh, Mark!" ?)
And since a 'select/into' cannot be run from within a transaction, I'd also expect the DSI to issue the 'select/into' outside of a transaction (ie, there's nothing to rollback).
---------------------
As for the error message ... it seems to think that the database name is:
"Invalid pointer param number 2, pointer value 0x0x100000018"
Obviously that's not a valid database name, but it does look like part of an ASE error message. So there are 2 issues we can see from this invalid database name ...
1 - the 'select/into' is generating an error message, most likely during the DML part of the operation (ie, the DDL - create table - portion *is* creating the table)
2 - and there's a syntax/structure error in how the ASE error message is being processed by the DSI
I'd follow-up with the following:
1 - try to manually run the 'select/into' in the RDB (preferably using the same login used by the DSI) and see what, if any, error messages are generated; objective being to troubleshoot any resulting error messages [Hopefully an error will be generated thus highlighting an issue with your RDB ... and thus the error message being received by the DSI; this would also be nice to see (an error) since you seem to have indicated in your original post that the (same?) 'select/into' is being successfully replicated elsewhere]
2 - open a case with tech support to see if there are any known issues with the way the DSI and RDS are communicating (related to 'select/into' errors) for your particular RS/ASE version combination;