Date: Wed, 28 Jan 2004 11:05:55 -0500
Reply-To: "Richard A. DeVenezia" <radevenz@IX.NETCOM.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Richard A. DeVenezia" <radevenz@IX.NETCOM.COM>
Subject: Re: Anybody have a fix for PROC DBLOAD bug?
"Stephen Hirsch" <email@example.com> wrote in message
Is the SAS metadata migrated to the Oracle tables ? (I don't think Oracle
has anything quite like sas formats,
maybe some simpler indicators how a numeric should be displayed)
If a value is too large for the SAS format defined for a variable, is not
this a data issue with the CRO ?
>Therefore, it is very
>important that I maintain the metadata;
Maintain the metdata in SAS or Oracle, or both ? What happens in Oracle
when a value is too large to be rendered according to a columns display
There was a www.SAS.com article (don't recall the exact link) on how to
adjust a table that has values too large for a columns format. The article
deals with the all too familiar
At least one W.D format was too small for the number to be printed. The
decimal may be shifted by the "BEST" format."
From this info, you should be able to define a view to the CRO data which
will not have any ***, and dbload the view.
Richard A. DeVenezia