Precision and Scale in NUMBER datatype

In oracle, if you want to store a number like 892.34, you need to declare the NUMBER type like
number(5,2)Here 5 stands for the total number of digits including the numbers after the decimal point.
2 stands the number of digits to the right of the decimal.
Isn't this confusing? Can't they just make the syntax like
number(3,2)where 3 is the number of digits from left till the decimal and 2 is the number of digits after the decimal.

create table t ( n number( 6, 5 ) ) ;
alter table t add constraint c check ( n between 0.00001 and 0.1 ) ;
invalid value will throw
SQL Error: ORA-02290: check constraint (SYS.C) violated
*Cause: The values being inserted do not satisfy the named check
*Action: do not insert values that violate the constraint.

Similar Messages

How to specify precision and scale for a datatype in create procedure statement

Specifying precision and scale in the datatype when creating a procedure does not work:
create or replace function SqlTxFunctionTesting(inparam in number(9,2)
Error(1,48): PLS-00103: Encountered the symbol "(" when expecting one of the following: := . ) , @ % default character The symbol ":=" was substituted for "(" to continue.

user4928701 wrote:
Specifying precision and scale in the datatype when creating a procedure does not work:
create or replace function SqlTxFunctionTesting(inparam in number(9,2)
Error(1,48): PLS-00103: Encountered the symbol "(" when expecting one of the following: := . ) , @ % default character The symbol ":=" was substituted for "(" to continue.
And one of the cons in the PL/SQL language in my view.
The language does not allow parameters to be declared in the fashion you are attempting to. Even declaring a subtype and using that, does not enforce either the precision or scale, on the parameter value passed.
Even worse - the parameter value can be a different data type all together from the defined parameter type - and a silent and implicit data type conversion will be done at run-time.
So you can expect run-time errors in your code unit caused by the caller passing invalid values, despite the compiler okaying the call from the caller to your code.
There are pros and cons to this approach. But if you are from a very strong type language environment like C or Pascal, you tend to see more cons than pros in this specific case.

What is the point of Precision and Scale in Number Type?

Version :11.2
What is the point in having PRECISION and SCALE in number type? If you create the column with just NUMBER ie.without
specifying precision or scale , you can enter numbers with any precision and scale.
SQL> select * From v$version where rownum < 2;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
SQL> create table t1 (col1 number);
Table created.
SQL> insert into t1 values (223.9939394);
1 row created.
SQL> insert into t1 values (88.228384);
1 row created.
SQL> insert into t1 values (9.34);
1 row created.
SQL> insert into t1 values (000.00);
1 row created.
SQL> commit;
Commit complete.
SQL> select * from t1;
      COL1
223.993939
88.228384
      9.34
         0Did you ever have a business scenario where a Numerical column should store values only with a fixed precision and scale ?

Omega3 wrote:
Version :11.2
What is the point in having PRECISION and SCALE in number type? If you create the column with just NUMBER ie.without
specifying precision or scale , you can enter numbers with any precision and scale.
SQL> select * From v$version where rownum < 2;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
SQL> create table t1 (col1 number);
Table created.
SQL> insert into t1 values (223.9939394);
1 row created.
SQL> insert into t1 values (88.228384);
1 row created.
SQL> insert into t1 values (9.34);
1 row created.
SQL> insert into t1 values (000.00);
1 row created.
SQL> commit;
Commit complete.
SQL> select * from t1;
COL1
223.993939
88.228384
9.34
0Did you ever have a business scenario where a Numerical column should store values only with a fixed precision and scale ?Lots of business requirements for specific precisions and scales.
A persons Age may required to be stored as whole numbers of no more than 3 digits.
A sum of money may required to be stored with no more than 2 decimal places of accuracy e.g. GB Pounds and Pence or US Dollars and Cents
A unit of length may required to be stored in metres with 2 decimal places for centimetres
A shoe size may be required to be stored with one decimal place for half sizes
etc.
etc.
Yes, you may just create all of them as generic NUMBER datatype, but creating them with precision and scale can provide additional information about the limitations expected for the values stored, especially for things like reporting tools that may use the specified precision and scale to determine how to display the values automatically (by default).
If you start questioning "what's the point?" then you may as well say what's the point in having a NUMBER datatype when we can store numbers in a VARCHAR2 datatype? or what's the point in having a DATE datatype when we can stored dates as VARCHAR2 datatype? etc.
No point in asking such a question because there's almost always a point to these things (and if there isn't they get deprecated in later versions).

Precision and scale for numeric datatypes

Could be in XSU, could be in Oracle thin driver, but I'd expect the SAL column of the EMP table to include its precision and scale, e.g. 800.00 and not 800.
oracle: decribe EMP
NAME TYPE
SAL NUMBER(7,2)
sql server: sp_help EMP
Column_name Type Length Prec Scale
SAL numeric 5 7 2
sql server:
java myOracleXML getXML -conn "jdbc:inetdae7:aetius:1433?database=Northwind" -user "sa/sa" "select SAL from EMP where EMPNO > 7999"
<?xml version = '1.0'?>
<ROWSET>
<ROW num="1">
<SAL>800.00</SAL>
</ROW>
</ROWSET>
oracle:
java OracleXML getXML -user "scott/tiger" "select sal from
emp where empno > 7999"
<?xml version = '1.0'?>
<ROWSET>
<ROW num="1">
<SAL>800</SAL>
</ROW>
</ROWSET>
So who loses the scale in the Oracle case, the driver or XSU.
Steve.

user4928701 wrote:
Specifying precision and scale in the datatype when creating a procedure does not work:
create or replace function SqlTxFunctionTesting(inparam in number(9,2)
Error(1,48): PLS-00103: Encountered the symbol "(" when expecting one of the following: := . ) , @ % default character The symbol ":=" was substituted for "(" to continue.
And one of the cons in the PL/SQL language in my view.
The language does not allow parameters to be declared in the fashion you are attempting to. Even declaring a subtype and using that, does not enforce either the precision or scale, on the parameter value passed.
Even worse - the parameter value can be a different data type all together from the defined parameter type - and a silent and implicit data type conversion will be done at run-time.
So you can expect run-time errors in your code unit caused by the caller passing invalid values, despite the compiler okaying the call from the caller to your code.
There are pros and cons to this approach. But if you are from a very strong type language environment like C or Pascal, you tend to see more cons than pros in this specific case.

Precision and Scale

I am creating some application tables with APEX. When i define a column on my table for primary or foreign keys I select the NUMERIC datatype. The form then prompts me for Precision and Scale. What are the recommended values for precisions and scale for key columns? I understand that precision is the total number of digits before and after the radix but what is meant by scale - the number of digits after the radix? I'm a little rusty on these issues as it has been a long time since I used them.
Thanks, Ned

Hi
Just to add to this (definitions spot on though as Paul pointed out)...
'NUMERIC' is not an Oracle datatype. The datatype is NUMBER. Oracle supports NUMERIC in a create statement but it is stored as NUMBER under the hood.
Using precision and scale definitions is not necessary, you can define number just on it's own and it will handle what you throw into it. The design consideration comes into exactly what you are going to use the field for.
I came across a situation where a company were creating their administration system (and this was a reasonably large company with some very important data) and had decided to use NUMBER(9) for the PK ID column on all their major tables. Sure enough, 10 years later this started to cause a problem cause the were running out of numbers! (okay, this is no big deal to fix but it's just an example). The reasoning had originally been because Oracle Forms defaulted the display field length to that in the data dictionary it would save them the effort of changing it manually every time they created a new form!
I generally define NUMBER as NUMBER unless there is a valid rule to say that it is and always be something that can be defined. For example monetary amounts - Japanese Yen can't have decimals so it should be held in a NUMBER (10,2) field (although lots of people do this for their 'amount' columns anyway). The data rules.
Cheers
Ben
http://www.munkyben.wordpress.com
Don't forget to mark replies helpful or correct ;)
Edited by: Munky on Aug 19, 2009 8:01 AM

When -ve scale in number datatype is used??????????

dear friends,
in the number datatype we specify precision and scale
limit of precision is 1-38 & scale is -64 to 127 if i m right
so i wll like 2 know when & how -ve scale value is used for data design
also plz tell me how 2 declare col if expected values 2 b entered in it r like 0.0000078 etc.
waiting for reply
thanking you
ganesh

Perhaps the following will help
SQL> create table test1 (
2 a number(5,0),
3 b number(5,1),
4 c number(5,2),
5 d number(5,-1),
6 e number(5,-2)
7 );
Table created.
SQL> insert into test1 values (1.234, 1.234, 1.234, 1.234, 1.234);
1 row created.
SQL> insert into test1 values (12.34, 12.34, 12.34, 12.34, 12.34);
1 row created.
SQL> insert into test1 values (123.4, 123.4, 123.4, 123.4, 123.4);
1 row created.
SQL> insert into test1 values (.1234, .1234, .1234, .1234, .1234);
1 row created.
SQL> insert into test1 values (.01234, .01234, .01234, .01234, .01234);
1 row created.
SQL> select * from test1
2 ;
         A          B          C          D          E
         1        1.2       1.23          0          0
        12       12.3      12.34         10          0
       123      123.4      123.4        120        100
         0         .1        .12          0          0
         0          0        .01          0          0
SQL>

Can I know the precision and scale of a decimal field using ACEDAO?

Using ACEDAO in VC++, I am trying to retrieve the field details of an Access database (.accdb file) table of which one field is of decimal type. I am able to get the details using the functions of
DAO::_FieldPtr field;
as follows:
fieldName = field->GetName().GetBSTR();
nType = field->GetType() // returns DAO::dbDecimal
lSize = field->GetSize(); // returns 16
lAttr = field->GetAttributes(); // returns 0x000002H
nOrdinal = field->GetOrdinalPosition(); // returns 11
bAutoIncrement = ((lAttr & DAO::dbAutoIncrField) > 0);
DAO::PropertiesPtr props;
DAO::PropertyPtr prop;
int k, nProp;
std::wstring propName, propNames;
props = field->GetProperties();
if(props)
nProp = props->GetCount(); // returns 33
for(k = 0; k < nProp; k++)
prop = field->GetProperties()->GetItem((short) k);
if(prop)
propName = prop->GetName().GetBSTR();
propNames += propName;
propNames += L"\n";
// After exiting the loop, propNames contain 33 properties as:
// Value
// Attributes
// CollatingOrder
// Type
// Name
// OrdinalPosition
// Size
// SourceField
// SourceTable
// ValidateOnSet
// DataUpdatable
// ForeignName
// DefaultValue
// ValidationRule
// ValidationText
// Required
// AllowZeroLength
// AppendOnly
// Expression
// FieldSize
// OriginalValue
// VisibleValue
// GUID
// ColumnWidth
// ColumnOrder
// ColumnHidden
// Description
// DecimalPlaces
// DisplayControl
// TextAlign
// AggregateType
// ResultType
// CurrencyLCID
//But does not have any property named "Scale" or "Precision"
I could not find any function for retrieving the value for precision and scale for the decimal field.
Though I am able to retrieve the field value as a decimal number and get the required information from the structure, I think it is not the right way. Because, what will happen if the data for field is not available in the table?
Is there any other method to retrieve the precision and scale of a decimal type field using ACEDAO?
Thanks.

I cannot find a method or property in ACEDAO to retrieve the precision and scale of a field. Maybe you could try get the number of a decimal type and use some mathematical methods to get the precision.
I find there are some way to get the precision by ADO or OLEDB.
For ADO way, you could check this thread:
https://social.msdn.microsoft.com/Forums/office/en-US/883087ba-2c25-4571-bd3c-706061466a11/how-can-i-programmatically-access-scale-property-of-a-decimal-data-type-field?forum=accessdev
For OLE DB , you could use IColumnsInfo::GetColumnInfo to get DBCOLUMNINFO::bPrecision.
https://msdn.microsoft.com/en-us/library/windows/desktop/ms722704(v=vs.85).aspx
Also people in C++ may not familiar with access development, the
Access for Developers forum is good place for access develop issue. You could try there.
Hope this helps some.
Shu
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Validation of numeric value precision and scale

Hi all,
Iam using ADF with EJBs.
I have one inputText field that will accept numeric values (of java.lang.Double type). Due to database constraints I want to validate the input value on its precision and scale.
I put an f:convertNumber tag under the inputText and set the MaxIntegerDigits and MaxFractionDigits properties with the desired values.
I also set the ApplyValidation property of the corresponding attribute in the pagedef file. However no validation worked.
I made the same test with af:ConvertNumber with no result too.
I know that with BC4J it is easy to set such constraints at the entity level.
Is there any neat way to set validation or I need to write code in the backing bean?

<af:convertNumber> works fine for me. see the following code
<af:inputText id="it1">
<af:convertNumber type="number" minFractionDigits="2" maxIntegerDigits="4" maxFractionDigits="2"/>
</af:inputText>
Another possible solution with regular expression
<af:inputText id="it3" value="9999.99">
<af:validateRegExp pattern="\[0-9\]\[0-9\]\[0-9\]\[0-9\].\[0-9\]\[0-9\]"/>
</af:inputText>
regards
srini
Edited by: sangara on Jan 17, 2010 9:53 PM

Number precision and scale

I have a xml document that I want to test against the shredded schemas. The XSD type creates a number(6,1).
When I insert the xml document if the number is 2.22 it will insert the record even if the XSD has a xs:fractionDigits value="1"
I realize Oracle uses floating point and truncates or rounds the number. Is there a way to have an error on the xml document load if the decimal point is larger then one digit as defined in the XSD?

Mark,
The schema has 10 xsd files with includes. I pasted a portion of the one that had the fractional digit 6,1. Did you want all 10, or this what you are looking for?
<?xml version="1.0" encoding="UTF-8"?>

<xs:schema targetNamespace="http://science.doe.gov/ePME" xmlns:epme="http://science.doe.gov/ePME" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
     <xs:include schemaLocation="countries.xsd"/>
     <xs:include schemaLocation="purpose.xsd"/>
     <xs:include schemaLocation="reason.xsd"/>
     <xs:include schemaLocation="research_areas.xsd"/>
     <xs:include schemaLocation="research_cat_ids.xsd"/>
     <xs:include schemaLocation="work_cat_ids.xsd"/>
     <xs:complexType name="fiscal_year_budget_info">
          <xs:sequence>
               <xs:element name="staffing_scientific" nillable="false" minOccurs="0">
                    <xs:annotation>
                         <xs:documentation>Scientific staffing in full-time equivalent person years</xs:documentation>
                    </xs:annotation>
                    <xs:simpleType>
                         <xs:restriction base="xs:decimal">
                              <xs:fractionDigits value="1"/>
                              <xs:totalDigits value="6"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="staffing_other_direct" minOccurs="0">
                    <xs:annotation>
                         <xs:documentation>Other direct staffing in full-time equivalent person years</xs:documentation>
                    </xs:annotation>
                    <xs:simpleType>
                         <xs:restriction base="xs:decimal">
                              <xs:fractionDigits value="1"/>
                              <xs:totalDigits value="6"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element name="staffing_total_direct" minOccurs="0">
                    <xs:annotation>
                         <xs:documentation>Total direct staffing in full-time equivalent person years</xs:documentation>
                    </xs:annotation>
                    <xs:simpleType>
                         <xs:restriction base="xs:decimal">
                              <xs:fractionDigits value="1"/>
                              <xs:totalDigits value="6"/>
                         </xs:restriction>
                    </xs:simpleType>

Specifying precision and scale

Hello,
I have a table that was created with a column pfixed NUMBER(38). The data contains up to 16 numbers after the decimal point (e.g. <pfixed>4.8283510208129883</pfixed>). XSU loads it with scale of 0, which results in everything after the decimal being truncated. The precision is correctly set to 38, to match the NUMBER column.
Is this a problem with the create table statement, or is there a way to tell XSU what scale to use?
Thanks,
Leila

i'm not sure if i understand your problem..
you say you (or someone else) declared a
table with NUMBER(38) and you want 0.??? written to it (or from ??)...
then why not declare your own precision
( format NUMBER(a,b)
where a is size and b is precision)
assume the number xxx.yyyy
format NUMBER(2,4) stores xx.yyyy
format NUMBER(1,2) stores x.yy
format NUMBER(3,1) stores xxx.y
38 is NOT your precision, it's SIZE !!
i hope this helps...
null

Shp2sdo precision and scale

The SDO_ORDINATES in the CTL file generated by shp2sdo contain only 6 decimal places even though the source shapefile contains ordinates with a larger scale (as evidenced via ESRI products and reviewing the geometries generated when the spatial layer is created via ArcSDE). The -t tolerance parameter seems to have no effect on the actual SDO_ORDINATES scale (just effects the metadata). Is this a limitation in shp2sdo or is something else going on here?
Thank you for your help, James

Can anyone please tell were I can get a copy of shp2sdo. I have done a search on it's name and have found no software by this name.
Thanks,
John look at:
http://otn.oracle.com/software/products/spatial/content.html
for the shapefile converter and other Spatial tools
Mark

How to update precision value in number datatype

hello all
i hava a database containing data in that there is a table which contan a number datatype
that is number(10)
the table contain large amount of data
now i need the precision value 2
that is number(10,2)
how i can update is
i try alter command the do this bu the error is there the table contain data
so please suggest the solution
thanks in advance

The number of columsn has nothing to do with it. The number of rows has nothing to do with it.
Here is a step-by-step example to address your problem. I will change DATA_OBJECT_ID from NUMBER to NUMBER(10,2) even though there are thousands of rows in the table, the column is "in the middle " of the table, and there are many rows with non-null values in that column.
07:02:43 > create table t3 as select * from all_objects;
Table created.
Elapsed: 00:00:06.22
07:04:08 > desc t3
Name                                      Null?    Type
OWNER                                     NOT NULL VARCHAR2(30)
OBJECT_NAME                               NOT NULL VARCHAR2(30)
SUBOBJECT_NAME                                     VARCHAR2(30)
OBJECT_ID                                 NOT NULL NUMBER
DATA_OBJECT_ID                                     NUMBER
OBJECT_TYPE                                        VARCHAR2(19)
CREATED                                   NOT NULL DATE
LAST_DDL_TIME                             NOT NULL DATE
TIMESTAMP                                          VARCHAR2(19)
STATUS                                             VARCHAR2(7)
TEMPORARY                                          VARCHAR2(1)
GENERATED                                          VARCHAR2(1)
SECONDARY                                          VARCHAR2(1)
NAMESPACE                                 NOT NULL NUMBER
EDITION_NAME                                       VARCHAR2(30)
07:04:12 > alter table t3 modify (data_object_id number(10));
alter table t3 modify (data_object_id number(10))
ERROR at line 1:
ORA-01440: column to be modified must be empty to decrease precision or scale
Elapsed: 00:00:00.98
07:08:05 > select count(*), min(data_object_id), max(data_object_id), count(distinct data_object_id), count(data_object_id)
07:09:06   2 from t3;
COUNT(*) MIN(DATA_OBJECT_ID) MAX(DATA_OBJECT_ID) COUNT(DISTINCTDATA_OBJECT_ID) COUNT(DATA_OBJECT_ID)
    184456                   0             1526320                         12225                 70092
1 row selected.
Elapsed: 00:00:00.11
07:09:41 > alter table t3 add (temp_data_object_id number(10,2));
Table altered.
Elapsed: 00:00:00.07
07:10:27 > update t3 set temp_data_object_id = data_object_id, data_object_id = null;
184456 rows updated.
Elapsed: 00:00:04.49Notice that our column of interest is now entirely null, so the restriction against reducing its scale or precision will not longer impact us.
07:11:00 >
07:11:17 > select count(*), min(data_object_id), max(data_object_id), count(distinct data_object_id), count(data_object_id) from t3;
COUNT(*) MIN(DATA_OBJECT_ID) MAX(DATA_OBJECT_ID) COUNT(DISTINCTDATA_OBJECT_ID) COUNT(DATA_OBJECT_ID)
    184456                                                                     0                     0
1 row selected.
Elapsed: 00:00:00.04
07:11:51 > alter table t3 modify (data_object_id number(10,2))
07:12:33 > /
Table altered.
Elapsed: 00:00:00.07
07:12:35 > update t3 set data_object_id=temp_data_object_id;
184456 rows updated.
Elapsed: 00:00:04.01
07:14:40 > select count(*), min(data_object_id), max(data_object_id), count(distinct data_object_id), count(data_object_id) from t3;
COUNT(*) MIN(DATA_OBJECT_ID) MAX(DATA_OBJECT_ID) COUNT(DISTINCTDATA_OBJECT_ID) COUNT(DATA_OBJECT_ID)
    184456                   0             1526320                         12225                 70092
1 row selected.
Elapsed: 00:00:00.09
07:14:49 > alter table t3 drop column temp_data_object_id;
Table altered.
Elapsed: 00:00:02.40
07:15:11 > desc t3
Name                                                              Null?    Type
OWNER                                                             NOT NULL VARCHAR2(30)
OBJECT_NAME                                                       NOT NULL VARCHAR2(30)
SUBOBJECT_NAME                                                             VARCHAR2(30)
OBJECT_ID                                                         NOT NULL NUMBER
DATA_OBJECT_ID                                                             NUMBER(10,2)
OBJECT_TYPE                                                                VARCHAR2(19)
CREATED                                                           NOT NULL DATE
LAST_DDL_TIME                                                     NOT NULL DATE
TIMESTAMP                                                                  VARCHAR2(19)
STATUS                                                                     VARCHAR2(7)
TEMPORARY                                                                  VARCHAR2(1)
GENERATED                                                                  VARCHAR2(1)
SECONDARY                                                                  VARCHAR2(1)
NAMESPACE                                                         NOT NULL NUMBER
EDITION_NAME                                                               VARCHAR2(30)
07:15:15 >

How do i check number datatype with precision is 6

Hello,
If a variable is declared as number datatype with precision 6.
Foe testing purpose ,i want to check which value is having precision >6
because iam getting ORA-06502 error PL/SQL numeric or value error
what can be the reason

Hi Kamal,
In my case everyday a nightly job is executed to execute the stored procs
and stores the errors in error table,
The complete eror description is
error in updating grant_vest_estm_amrtzn redistributing the overlapping expense ORA-06502:PL/SQL numeric or value error
Here is the query-- which is placed ina stored proc
o_Error_Text := 'Error in updating GRANT_VEST_ESTM_AMRTZN redistributing the overlapping expense ' ;
EXECUTE IMMEDIATE 'UPDATE GRANT_VEST_ESTM_AMRTZN
SET GRN_ESTM_TRNCHE_EXPS_Y = :1,
GRN_AMRTN_ORIGL_TRNCHE_EXPS_Y = :2,
GRN_VEST_ADJST_OPT_Q = :3
WHERE ORG_GRP_I = :4
AND GRN_N = :5
AND GRN_VEST_D = :6'
USING V_GRN_ESTM_TRNCHE_EXPS_Y(I), V_GRN_AMRTN_ORIG_TRNC_EXP_Y(I), V_GRN_VEST_NEW_ADJST_OPT_Q(I),
I_ORG_GRP_I, NEW_GRN(I), V_GRN_VEST_D(I);
V_GRN_ESTM_TRNCHE_EXPS_Y(I) are calculated based on some conditions
for example
V_GRN_ESTM_TRNCHE_EXPS_Y (I) := V_GRN_ESTM_TRNCHE_EXPS_Y(I) +
( (V_REM_GRN_VEST_ORIGL_OPT_Q(I) / V_GRN_VEST_OLD_ORIGL_OPT_Q(J)) * V_GRN_ESTM_EXPS_Y(J));
V_GRN_AMRTN_ORIG_TRNC_EXP_Y(I) := V_GRN_AMRTN_ORIG_TRNC_EXP_Y(I) +
( (V_REM_GRN_VEST_ORIGL_OPT_Q(I) / V_GRN_VEST_OLD_ORIGL_OPT_Q(J)) * V_GRN_ESTM_ORIGL_A(J));
V_GRN_VEST_NEW_ADJST_OPT_Q(I) := V_GRN_VEST_NEW_ADJST_OPT_Q(I) +
( (V_REM_GRN_VEST_ORIGL_OPT_Q(I) / V_GRN_VEST_OLD_ORIGL_OPT_Q(J)) * V_GRN_VEST_OLD_ADJST_OPT_Q(J));
V_REM_GRN_VEST_OLD_ORIGL_OPT_Q(J) := V_GRN_VEST_OLD_ORIGL_OPT_Q(J) - V_REM_GRN_VEST_ORIGL_OPT_Q(I);
V_REM_GRN_VEST_ORIGL_OPT_Q(I) := 0;
Looking forward for the response

Having trouble after osi7 on my iPad, I have one contact that won't recognize a number? Also can't move and scale a photo for wallpaper.

Having trouble after osi7 on my iPad, I have one contact that won't recognize a number? Also can't move and scale a photo for wallpaper.

Downloads available:
Suites and Programs: CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4 | CS3
Acrobat: XI, X | 9,8 | 9 standard
Premiere Elements: 13 | 12 | 11, 10 | 9, 8, 7
Photoshop Elements: 13 |12 | 11, 10 | 9,8,7
Lightroom: 5.7.1| 5 | 4 | 3
Captivate: 8 | 7 | 6 | 5
Contribute: CS5 | CS4, CS3
Download and installation help for Adobe links
Download and installation help for Prodesigntools links are listed on most linked pages. They are critical; especially steps 1, 2 and 3. If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

Problem while modifying number datatype.

Hi All,
I have modified a column, which is of number datatype.
Initially it was number(8,2), now I have changed this to Number(10,2).
But, due to some change in requirement, I have to revese the changes. Now, I am trying to make it Number(8,2), but it is giving me the following error.
Error report:
SQL Error: ORA-01440: column to be modified must be empty to decrease precision or scale
01440. 00000 - "column to be modified must be empty to decrease precision or scale"
Is there a way to make it?
Please suggest..
I am using Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production.
Thnx in advance..
Bits..

You'd have to jump through some hoops to decrease the allowable number of digits in a column. You'd either have to re-create the table, i.e.
-- Save off the data in FOO
ALTER TABLE foo
RENAME TO foo_bkup;
CREATE TABLE foo (
-- New column definitions
INSERT /*+ APPEND */ INTO foo( list_of_columns )
SELECT list_of_columns
    FROM foo_bkupOr you could create a new column, copy the data, and rename the old column
ALTER TABLE foo
   ADD( temp_col_name number(8,2) );
UPDATE foo
   SET temp_col_name = old_col_name;
ALTER TABLE foo
DROP COLUMN old_col_name;
ALTER TABLE foo
RENAME COLUMN temp_col_name TO old_col_name;Justin

Precision and Scale in NUMBER datatype

Similar Messages

Maybe you are looking for