we have fields in our oracle database identified as integer, but when they get imported into the physical layer they are changed to 'double'. Is there
a default setting in OBIEEĀ that's doing this ?
Actually I don't think there is a setting managing that but it's also what I saw. It generally isn't a problem as integer can be a double (the opposite would be a real issue).
Does this change from integer to double give you problems somewhere?
Check this OBIEE - Integer Datatype [Gerardnico]
this explains why it does!
I hope you do know that an OBIEE integer is a 32bit SIGNED INTEGER!
So you might want to NOT use integer if you're storing anything above 2'147'483'647 (or below -2'147'483'647) or you'll get Youtube-like Gangan-Style-itis.
Basically you're hitting slide 5 of my worst practices: 50 shades of #Fail - Oracle BI worst practices in real life ;-)
