Oracle generated column aliases different on two DB's
It turns out there's a parameter called cursor_sharing that was set to FORCE instead of EXACT

select nvl(1,0.0) from DUAL;


The query above returns the following depending on the value of the parameter:

FORCE=NVL(1,0)
EXACT=NVL(1,0.0)