Due to the way system column metadata was handled in the code system columns of these types are always created with precision 0.
User defined columns of these types will have precision 10 (INT) and 19 (BIGINT)
DERBY-1734 will fix this for 10.3 and hopefully 10.2 by a merge before the release.
This bug is here to investigate upgrade issues and fix them if required.
Not known of any incorrect issues due to this, except for incorrect JDBC metadata for such columns.