SQL Anywhere Personal Server Version 11.0.1.2276 dbunload generates the following ALTER TABLE for a proxy table that was originally created on a Version 9 catalog table.

FWIW this is probably a pretty obscure bug feature, but it does cause Application Profiling to choke stop when it tries to create a profiling database.

CREATE EXISTING TABLE "p001"."proxy_V9_SYSCONSTRAINT" (
    "constraint_id"                  unsigned int NOT NULL
   ,"table_id"                       unsigned int NOT NULL
   ,"column_id"                      unsigned int NULL
   ,"index_id"                       unsigned int NULL
   ,"fkey_id"                        smallint NULL
   ,"constraint_type"                char(1) NOT NULL
   ,"constraint_name"                char(128) NOT NULL
) AT 'p001..SYS.SYSCONSTRAINT' LOCAL ONLY
go

ALTER TABLE "p001"."proxy_V9_SYSCONSTRAINT"
    ADD UNIQUE ( "table_id","constraint_name" )
go

***** SQL error: Feature 'Alter remote table' not implemented

Note: I did not create the UNIQUE constraint (how could I?) but it exists in the V11 system tables. I think under certain circumstances the CREATE EXISTING TABLE command creates local thingies like this for some reason, perhaps performance. Since a proxy table has no rows, ever, a local constraint makes no sense except as a hint for cross-database queries... AFAIK.

This may open a can of worms for dbunload... just how is it SUPPOSED to add these hints to the reload sql file?