Spatial index creation error -ORA-13011: value is out of range
I am trying to create a spatial index and this is what I get.
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13200: internal error [ROWID:AAAFXYAADAAABxyAAD] in spatial indexing.
ORA-13206: internal error [] while creating the spatial index
ORA-13011: value is out of range
ORA-00600: internal error code, arguments: [kope2upic014], [], [], [], [],
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 7
ORA-06512: at line 1
I can't find any documentation as to how to fix this. How do you determine which row of data is out of range? Any help would be greatly appreciated!
Hi Jeff,
The data at rowid AAAFXYAADAAABxyAAD has a problem.
Can see what the issue is by doing:
select sdo_geom.validate_geometry(geom_col_name,diminfo)
from your_table_name a, user_sdo_geom_metadata b
where b.table_name='YOUR_TABLE_NAME'
and a.rowid='AAAFXYAADAAABxyAAD';
If you are using Oracle9iR2 then this would be even better:
select sdo_geom.validate_geometry_with_context(geom_col_name,diminfo)
from your_table_name a, user_sdo_geom_metadata b
where b.table_name='YOUR_TABLE_NAME'
and a.rowid='AAAFXYAADAAABxyAAD';
Similar Messages
-
操作系统:XP
MAX版本:14.0
IMAQdx版本:4.3.5
摄像头:北京嘉恒中自图像OK_AC1360
生产商的应用软件中使用正常。在AMCAP软件(视频测试软件)中使用也正常。
连接Gige摄像机时出错:Error:0xBFF69012 Attribute value is out of range Attribute Name CameraAttributes::AutoFunction::AutoTargetGrayValue
试着修改 ‘AutoTargetGrayValue’ 属性值,但是MAX会无相应并死掉。
Solved!
Go to Solution.Sometimes, camera firmware is the problem. Sometimes, the camera XML file is the problem. Sometimes, the way that IMAQdx tries to force settings onto the camera is the problem.
Things to try:
1. Check with the manufacturer, and ask if new firmware is available for the camera. If the firmware cannot be updated by the end user, you will need to get a Returm Merchandise Authorization number, and send the camera in for the upgrade.
2. Edit the XML file that was downloaded from the camera, and remove all references to CameraAttributes::AutoFunction::AutoTargetGrayValue. Do not alter, or remove the zip file that resides in the same location as the XML. If you do, IMAQdx will request a fresh copy from the camera, and overwritew your changes. You can find the XML file in C:\Users\Public\Documents\National Instruments\NI-IMAQdx\Data\XML
3. Edit the camera .icd file in C:\Users\Public\Documents\National Instruments\NI-IMAQdx\Data, and remove the reference to CameraAttributes::AutoFunction::AutoTargetGrayValue.
Machine Vision, Robotics, Embedded Systems, Surveillance
www.movimed.com - Custom Imaging Solutions -
BEx Error - The specified value is out of range
Hi
We areBI 7.0 (SP14) & recently installed SAPGUI 7.10 (patch 7).
When I select a query (Path: Info Areas --> WMH Warehouse Management --
> Shipping KPIu2019s --> Order Turnaround in Detail) and give date range
greater than 2 weeks, then I can a critical error message and the BEx session closes.
Following is the trace file details:
ListSeparator: ,
ExcelVersion: 12.0
AddinVersion: 7100.1.400.1062
10/13/2008 10:16:12 PM----
System.Exception: CriticalProgramError ---> System.Exception: CriticalProgramError ---> System.Exception: CriticalProgramError ---> System.Exception: CriticlaProgramError ---> System.Exception: CriticlaProgramError ---> System.ArgumentException: The specified value is out of range.
at Microsoft.VisualBasic.CompilerServices.LateBinding.InternalLateSet(Object o, Type& objType, String name, Object[] args, String[] paramnames, Boolean OptimisticSet, CallType UseCallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase, CallType CallType)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateSetComplex(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean OptimisticSet, Boolean RValueBase)
at com.sap.bi.et.analyzer.addin.BExExcelItem.set_RangeAddress(String value)
at com.sap.bi.et.analyzer.addin.BExItemGrid.AdjustItemRange()
at com.sap.bi.et.analyzer.addin.BExItemGrid.OnRender(Boolean iForceRendering)
at com.sap.bi.et.analyzer.api.BExItem.Render()
--- End of inner exception stack trace ---
at com.sap.bi.et.analyzer.api.BExItem.Render()
at com.sap.bi.et.analyzer.api.BExApplication.Render()
--- End of inner exception stack trace ---
at com.sap.bi.et.analyzer.api.BExApplication.Render()
at com.sap.bi.et.analyzer.api.BExApplication.set_Synchronize(Boolean iValue)
at com.sap.bi.et.analyzer.addin.BExExcelApplication.OpenQueryThreaded(BExParameter iParameter)
--- End of inner exception stack trace ---
at com.sap.bi.et.analyzer.addin.BExExcelApplication.OpenQueryThreaded(BExParameter iParameter)
at com.sap.bi.et.analyzer.addin.BExThreads.ProcessParameterSubExecuter.Execute()
at com.sap.bi.et.analyzer.addin.BExExcelApplication.OpenQuery(OSObjectInformation iObjectDescription, String iRRIVariableName, String iRRIVariableValue)
at com.sap.bi.et.analyzer.addin.BExThreads.ProcessOpenQueryExecuter.Execute()
--- End of inner exception stack trace ---
at com.sap.bi.et.analyzer.addin.BExThreads.ProcessOpenQueryExecuter.Execute()
at com.sap.bi.et.analyzer.addin.BExMenu.ProcessOpenQuery()
at com.sap.bi.et.analyzer.addin.BExUserInteraction.Process(String iStepName)
--- End of inner exception stack trace ---
at com.sap.bi.et.analyzer.addin.BExUserInteraction.Process(String iStepName)
at com.sap.bi.et.analyzer.addin.BExUserInteraction.ProcessUserInteraction(Sub iSubDelegate, BExStepType iStepType)
at com.sap.bi.et.analyzer.addin.BExMenu.Process(CMD iCMD)
at com.sap.bi.et.analyzer.addin.BExMenu.ProcessCMD(CMD iCMD)
at com.sap.bi.et.analyzer.addin.BExConnect.ExcelCommunication.ProcessBExMenuCommand(String iCMD)
CriticalProgramError
at com.sap.bi.et.analyzer.addin.BExUserInteraction.Process(String iStepName)
at com.sap.bi.et.analyzer.addin.BExUserInteraction.ProcessUserInteraction(Sub iSubDelegate, BExStepType iStepType)
at com.sap.bi.et.analyzer.addin.BExMenu.Process(CMD iCMD)
at com.sap.bi.et.analyzer.addin.BExMenu.ProcessCMD(CMD iCMD)
at com.sap.bi.et.analyzer.addin.BExConnect.ExcelCommunication.ProcessBExMenuCommand(String iCMD)
Thanks & Regards
Madhucheck if oyu can execute this query in RSRT, is so then you need to either go for SP > 16 or BEx Gui = 4 or 5 .,
Hope this helps -
Spatial Index Creation Error on 9.2.0.1
Hi,
I can´t create a spatial index on an Oracle 9.2.0.1, Windows 2000 Server. I create the table, register metadata and when I try to create the index the folowing error is returned (some messages in Portuguese):
ORA-29855: ocorreu um erro na execução da rotina ODCIINDEXCREATE
ORA-13249: Error executing stmt: begin mdsys.prvt_idx.execute_insert(NULL, NULL, ' VALUES (''TESTUSER'',''MDIDX_INIT'', 0, 0, 64, -1, NLS_UPPER(''MDRT_7844$''), ''I_SDOTEST'', 1, ''TESTUSER'', ''"GEOM"'', 0, 0, 2, 0, ''DEFAULT'', ''DEFAULT'', NULL,NULL, NULL, NULL, NULL, NULL, NULL, 2, ''DEFAULT'', 10, NULL, NULL, NULL, NULL, ''FALSE'', ''VALID'', NULL)', NULL); end;
ORA-13249: Error in Spatial index: insert to metadata failed
ORA-29400: erro no cartucho de dados
ORA-00913: valores demais
ORA-06512: em "MDSYS.PRVT_IDX", line 5
ORA-06512: em line 1
ORA-06512: em "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: em line 1
The same error occurs with other database users.
On my notebook (Windows XP) with the same Oracle version installed the index is created succesfully.
What can be wrong on the server ?
Thanks.When I connect through sqlplus it shows:
SQL*Plus: Release 9.2.0.1.0 - Production on Mon Jun 14 17:14:33 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL>
The select on dba_registry returns:
COMP_ID COMP_NAME VERSION STATUS MODIFIED CONTROL SCHEMA PROCEDURE STARTUP PARENT_ID
CATALOG Oracle9i Catalog Views 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS SYS DBMS_REGISTRY_SYS.VALIDATE_CATALOG
CATPROC Oracle9i Packages and Types 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS SYS DBMS_REGISTRY_SYS.VALIDATE_CATPROC
OWM Oracle Workspace Manager 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS WMSYS OWM_VALIDATE
JAVAVM JServer JAVA Virtual Machine 9.2.0.1.0 VALID 12-MAI-2002 16:55:28 SYS SYS
XML Oracle XDK for Java 9.2.0.2.0 VALID 14-JUN-2004 15:59:45 SYS SYS XMLVALIDATE
CATJAVA Oracle9i Java Packages 9.2.0.1.0 VALID 14-JUN-2004 15:59:45 SYS SYS DBMS_REGISTRY_SYS.VALIDATE_CATJAVA
ORDIM Oracle interMedia 9.2.0.1.0 LOADED 12-MAI-2002 17:27:10 SYS ORDSYS
SDO Spatial 9.2.0.1.0 LOADED 12-MAI-2002 17:40:16 SYS MDSYS
CONTEXT Oracle Text 9.2.0.1.0 VALID 12-MAI-2002 17:32:11 CTXSYS CTXSYS
XDB Oracle XML Database 9.2.0.1.0 VALID 14-JUN-2004 15:59:55 SYS XDB DBMS_REGXDB.VALIDATEXDB
WK Oracle Ultra Search 9.2.0.1.0 VALID 12-MAI-2002 17:44:01 WKSYS WKSYS WK_UTIL.VALID
ODM Oracle Data Mining 9.2.0.1.0 LOADED 12-MAI-2002 17:49:36 SYS ODM
APS OLAP Analytic Workspace 9.2.0.1.0 LOADED 12-MAI-2002 17:58:32 SYS SYS
XOQ Oracle OLAP API 9.2.0.1.0 LOADED 12-MAI-2002 17:59:07 SYS SYS
AMD OLAP Catalog 9.2.0.1.0 INVALID 14-JUN-2004 15:59:57 SYS OLAPSYS CWM2_OLAP_INSTALLER.VALIDATE_CWM2_INSTALL
Any ideas ? -
friends,
i m unable to create an index on table named counties having SDO_GEOMETRY column named geom.
when i execute the create index command it gives me this error
SQL> create index county_ind on counties(geom)
2 INDEXTYPE IS MDSYS.SPATIAL_INDEX
3 PARAMETERS('SDO_LEVEL = 16, SDO_NUMTILES=32');
create index county_ind on counties(geom)
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13200: internal error [ROWID:AAAG13AABAAAkfXAAD] in spatial indexing.
ORA-13197: element MDSYS.COUNTIES.. is out of range
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 7
ORA-06512: at line 1
please help me to solve this problem
Harpreet
nulltry this
create index idx_cities on cities(location)
indextype is mdsys.spatial_index
parameters('sdo_level=9');
the same procedure for counties,interstates
and states.first drop the index and then
recreate it.still if it doesnt work check
somepackageboby,package ie like triggers are
anyone of these invalid make this to be valid
and try again
srikanth.v
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Shalu:
I tried it all I still keep getting this error
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCI
ORA-13203: failed to read SDO_GEOM_METADATA table
ORA-29400: data cartridge error
ORA-00904: invalid column name
ORA-06512: at "MDSYS.SDO_INDEX_METHOD", line 7
ORA-06512: at line 1
Shalu<HR></BLOCKQUOTE>
null -
SQL Error: ORA-12899: value too large for column
Hi,
I'm trying to understand the above error. It occurs when we are migrating data from one oracle database to another:
Error report:
SQL Error: ORA-12899: value too large for column "USER_XYZ"."TAB_XYZ"."COL_XYZ" (actual: 10, maximum: 8)
12899. 00000 - "value too large for column %s (actual: %s, maximum: %s)"
*Cause: An attempt was made to insert or update a column with a value
which is too wide for the width of the destination column.
The name of the column is given, along with the actual width
of the value, and the maximum allowed width of the column.
Note that widths are reported in characters if character length
semantics are in effect for the column, otherwise widths are
reported in bytes.
*Action: Examine the SQL statement for correctness. Check source
and destination column data types.
Either make the destination column wider, or use a subset
of the source column (i.e. use substring).
The source database runs - Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
The target database runs - Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
The source and target table are identical and the column definitions are exactly the same. The column we get the error on is of CHAR(8). To migrate the data we use either a dblink or oracle datapump, both result in the same error. The data in the column is a fixed length string of 8 characters.
To resolve the error the column "COL_XYZ" gets widened by:
alter table TAB_XYZ modify (COL_XYZ varchar2(10));
-alter table TAB_XYZ succeeded.
We now move the data from the source into the target table without problem and then run:
select max(length(COL_XYZ)) from TAB_XYZ;
-8
So the maximal string length for this column is 8 characters. To reduce the column width back to its original 8, we then run:
alter table TAB_XYZ modify (COL_XYZ varchar2(8));
-Error report:
SQL Error: ORA-01441: cannot decrease column length because some value is too big
01441. 00000 - "cannot decrease column length because some value is too big"
*Cause:
*Action:
So we leave the column width at 10, but the curious thing is - once we have the data in the target table, we can then truncate the same table at source (ie. get rid of all the data) and move the data back in the original table (with COL_XYZ set at CHAR(8)) - without any issue.
My guess the error has something to do with the storage on the target database, but I would like to understand why. If anybody has an idea or suggestion what to look for - much appreciated.
Cheers.843217 wrote:
Note that widths are reported in characters if character length
semantics are in effect for the column, otherwise widths are
reported in bytes.You are looking at character lengths vs byte lengths.
The data in the column is a fixed length string of 8 characters.
select max(length(COL_XYZ)) from TAB_XYZ;
-8
So the maximal string length for this column is 8 characters. To reduce the column width back to its original 8, we then run:
alter table TAB_XYZ modify (COL_XYZ varchar2(8));varchar2(8 byte) or varchar2(8 char)?
Use SQL Reference for datatype specification, length function, etc.
For more info, reference {forum:id=50} forum on the topic. And of course, the Globalization support guide. -
I am getting error "ORA-12899: value too large for column".
I am getting error "ORA-12899: value too large for column" after upgrading to 10.2.0.4.0
Field is updating only through trigger with hard coded value.
This happens randomly not everytime.
select * from v$version
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
Table Structure
desc customer
Name Null? Type
CTRY_CODE NOT NULL CHAR(3 Byte)
CO_CODE NOT NULL CHAR(3 Byte)
CUST_NBR NOT NULL NUMBER(10)
CUST_NAME CHAR(40 Byte)
RECORD_STATUS CHAR(1 Byte)
Trigger on the table
CREATE OR REPLACE TRIGGER CUST_INSUPD
BEFORE INSERT OR UPDATE
ON CUSTOMER FOR EACH ROW
BEGIN
IF INSERTING THEN
:NEW.RECORD_STATUS := 'I';
ELSIF UPDATING THEN
:NEW.RECORD_STATUS := 'U';
END IF;
END;
ERROR at line 1:
ORA-01001: invalid cursor
ORA-06512: at "UPDATE_CUSTOMER", line 1320
ORA-12899: value too large for column "CUSTOMER"."RECORD_STATUS" (actual: 3,
maximum: 1)
ORA-06512: at line 1
Edited by: user4211491 on Nov 25, 2009 9:30 PM
Edited by: user4211491 on Nov 25, 2009 9:32 PMSQL> create table customer(
2 CTRY_CODE CHAR(3 Byte) not null,
3 CO_CODE CHAR(3 Byte) not null,
4 CUST_NBR NUMBER(10) not null,
5 CUST_NAME CHAR(40 Byte) ,
6 RECORD_STATUS CHAR(1 Byte)
7 );
Table created.
SQL> CREATE OR REPLACE TRIGGER CUST_INSUPD
2 BEFORE INSERT OR UPDATE
3 ON CUSTOMER FOR EACH ROW
4 BEGIN
5 IF INSERTING THEN
6 :NEW.RECORD_STATUS := 'I';
7 ELSIF UPDATING THEN
8 :NEW.RECORD_STATUS := 'U';
9 END IF;
10 END;
11 /
Trigger created.
SQL> insert into customer(CTRY_CODE,CO_CODE,CUST_NBR,CUST_NAME,RECORD_STATUS)
2 values('12','13','1','Mahesh Kaila','UPD');
values('12','13','1','Mahesh Kaila','UPD')
ERROR at line 2:
ORA-12899: value too large for column "HPVPPM"."CUSTOMER"."RECORD_STATUS"
(actual: 3, maximum: 1)
SQL> insert into customer(CTRY_CODE,CO_CODE,CUST_NBR,CUST_NAME)
2 values('12','13','1','Mahesh Kaila');
1 row created.
SQL> set linesize 200
SQL> select * from customer;
CTR CO_ CUST_NBR CUST_NAME R
12 13 1 Mahesh Kaila I
SQL> update customer set cust_name='tst';
1 row updated.
SQL> select * from customer;
CTR CO_ CUST_NBR CUST_NAME R
12 13 1 tst Urecheck your code once again..somewhere you are using record_status column for insertion or updation.
Ravi Kumar -
Replicat error: ORA-12899: value too large for column ...
Hi,
In our system Source and Target are on the same physical server and in the same Oracle instance. Just different schemes.
Tables on the target were created as 'create table ... as select * from ... source_table', so they have a similar structure. Table names are also similar.
I started replicat, it worked fine for several hours, but when I inserted Chinese symbols into the source table I got an error:
WARNING OGG-00869 Oracle GoldenGate Delivery for Oracle, OGGEX1.prm: OCI Error ORA-12899: value too large for column "MY_TARGET_SCHEMA"."TABLE1"."*FIRSTNAME*" (actual: 93, maximum: 40) (status = 12899), SQL <INSERT INTO "MY_TARGET_SCHEMA"."TABLE1" ("USERID","USERNAME","FIRSTNAME","LASTNAME",....>.
FIRSTNAME is Varchar2(40 char) field.
I suppose the problem probably is our database is running with NLS_LENGTH_SEMANTICS='CHAR'
I've double checked tables structure on the target - it's identical with the source.
I also tried to manually insert this record into the target table using 'insert into ... select * from ... ' statement - it works. The problem seems to be in the replicat.
How to fix this error?
Thanks in advance!
Oracle GoldenGate version: 11.1.1.1
Oracle Database version: 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
NLS_LANG: AMERICAN_AMERICA.AL32UTF8
NLS_LENGTH_SEMANTICS='CHAR'
Edited by: DeniK on Jun 20, 2012 11:49 PM
Edited by: DeniK on Jun 23, 2012 12:05 PM
Edited by: DeniK on Jun 25, 2012 1:55 PMI've created the definition files and compared them. They are absolutely identical, apart from source and target schema names:
Source definition file:
Definition for table MY_SOURCE_SCHEMA.TABLE1
Record length: 1632
Syskey: 0
Columns: 30
USERID 134 11 0 0 0 1 0 8 8 8 0 0 0 0 1 0 1 3
USERNAME 64 80 12 0 0 1 0 80 80 0 0 0 0 0 1 0 0 0
FIRSTNAME 64 160 98 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
LASTNAME 64 160 264 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
PASSWORD 64 160 430 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
TITLE 64 160 596 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
Target definition file:
Definition for table MY_TAEGET_SCHEMA.TABLE1
Record length: 1632
Syskey: 0
Columns: 30
USERID 134 11 0 0 0 1 0 8 8 8 0 0 0 0 1 0 1 3
USERNAME 64 80 12 0 0 1 0 80 80 0 0 0 0 0 1 0 0 0
FIRSTNAME 64 160 98 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
LASTNAME 64 160 264 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
PASSWORD 64 160 430 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
TITLE 64 160 596 0 0 1 0 160 160 0 0 0 0 0 1 0 0 0
Edited by: DeniK on Jun 25, 2012 1:56 PM
Edited by: DeniK on Jun 25, 2012 1:57 PM -
File_To_RT data truncation ODI error ORA-12899: value too large for colum
Hi,
Could you please provide me some idea so that I can truncate the source data grater than max length before inserting into target table.
Prtoblem details:-
For my scenario read data from source .txt file and insert the data into target table.suppose source file data length exceeds max col length of the target table.Then How will I truncate the data so that data migration will be successful and also can avoid the ODI error " ORA-12899: value too large for column".
Thanks
AnindyaBhabani wrote:
In which step you are getting this error ? If its loading step then try increasing the length for that column from datastore and use substr in the mapping expression.Hi Bhabani,
You are right.It is for Loading SrcSet0 Load data.I have increased the column length for target table data store
and then apply the substring function but it results the same.
If you wanted to say to increase the length for source file data store then please tell me which length ?Physical length or
logical length?
Thanks
Anindya -
INI: XOQ-01600: OLAP DML Error "ORA-01438: value larger than specified prec
I have created a Time dimension in AWM 11.1.0.7.0B.
I have added two Hierarchies to it. One Hierarchy has All Years, Year, Week, day. The second hierarchy has All Years, Year, Quarter.
When I maintain the dimension, the following error occurs:
An error has occurred on the server
Error class: Express Failure
Server error descriptions:
INI: Error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>
INI: XOQ-01600: OLAP DML Error "ORA-01438: value larger than specified precision allowed for this column
" while executing DML "SYS.AWXML!R11_LOAD_DIM('TIME.ALL_GREGORIAN_YEARS.LEVEL' SYS.AWXML!___R11_LONG_ARG_VALUE(SYS.AWXML!___R11_LONG_ARG_DIM 1) 'TIME.END_DATE.ATTRIBUTE' 'TIME.TIME_SPAN.ATTRIBUTE' 'TIME.LONG_DESCRIPTION.ATTRIBUTE' 'TIME.SHORT_DESCRIPTION.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_END_DATE.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_TIME_SPA.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_LONG_DES.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_SHORT_DE.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_TIME_SPA1.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_TIME_SPA2.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_TIME_SPA3.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_LONG_DES1.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_SHORT_DE1.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_TIME_SPA4.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_LONG_DES2.ATTRIBUTE' 'TIME.ALL_GREGORIAN_YEARS_SHORT_DE2.ATTRIBUTE' 'TIME.GREGORIAN_QUARTER_END_DATE.ATTRIBUTE' 'TIME.GREGORIAN_QUARTER_TIME_SPAN.ATTRIBUTE' 'TIME.GREGORIAN_QUAOLAP DML Error "%(1)s" while executing DML "%(2)s", Generic at TxsOqStdFormCommand::execute
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.executeBuild(Unknown Source)
at oracle.olap.awm.wizard.awbuild.UBuildWizardHelper$1.construct(Unknown Source)
at oracle.olap.awm.ui.SwingWorker$2.run(Unknown Source)
at java.lang.Thread.run(Thread.java:595)The most likely explanation is that you have a numeric attribute whose data type precision is less than that of the column it is mapped to. For example if you had an attribute with data type NUMBER(2) and you mapped it to a column with data type NUMBER(5), then you could get this error on load. Note that some of the attributes may not be visible in AWM. The offending SQL statement should be in the OUTPUT column of the CUBE_BUILD_LOG, but you may be able to fix this by just describing the view associated with the dimension. For example, here is the description of a TIME view created in 11.2..
Name Null? Type
DIM_KEY VARCHAR2(60)
LEVEL_NAME VARCHAR2(30)
MEMBER_TYPE VARCHAR2(1)
DIM_ORDER NUMBER
END_DATE DATE
TIME_SPAN NUMBER
LONG_DESCRIPTION VARCHAR2(60 CHAR)
SHORT_DESCRIPTION VARCHAR2(60 CHAR)
MONTH_END_DATE DATE
MONTH_TIME_SPAN NUMBER(5)
MONTH_LONG_DESCRIPTION VARCHAR2(60 CHAR)
MONTH_SHORT_DESCRIPTION VARCHAR2(60 CHAR)
FISCAL_QUARTER_END_DATE DATE
FISCAL_QUARTER_TIME_SPAN NUMBER(5)
FISCAL_QUARTER_LONG_DESC VARCHAR2(60 CHAR)
FISCAL_QUARTER_SHORT_DES VARCHAR2(60 CHAR)
FISCAL_YEAR_END_DATE DATE
FISCAL_YEAR_TIME_SPAN NUMBER(5)
FISCAL_YEAR_LONG_DESCRIP VARCHAR2(60 CHAR)
FISCAL_YEAR_SHORT_DESCRI VARCHAR2(60 CHAR)
CALENDAR_QUARTER_END_DAT DATE
CALENDAR_QUARTER_TIME_SP NUMBER(5)
CALENDAR_QUARTER_LONG_DE VARCHAR2(60 CHAR)
CALENDAR_QUARTER_SHORT_D VARCHAR2(60 CHAR)
CALENDAR_YEAR_END_DATE DATE
CALENDAR_YEAR_TIME_SPAN NUMBER(5)
CALENDAR_YEAR_LONG_DESCR VARCHAR2(60 CHAR)
CALENDAR_YEAR_SHORT_DESC VARCHAR2(60 CHAR)You can get the same information from user_cube_attributes
SQL> select attribute_name, data_precision from user_cube_attributes where dimension_name = 'TIME' and data_type = 'NUMBER';
ATTRIBUTE_NAME DATA_PRECISION
TIME_SPAN
MONTH_TIME_SPAN 5
FISCAL_QUARTER_TIME_SPAN 5
FISCAL_YEAR_TIME_SPAN 5
CALENDAR_QUARTER_TIME_SPAN 5
CALENDAR_YEAR_TIME_SPAN 5 -
CDC Failed with Error ORA-01438: value larger than specified precision
Hi,
I have created Asynchronous Distributed Change Data Capture Set-up as per the Guildines from Oracle.
Now My Change Set has become Invalid with error: ORA-01438: value larger than specified precision allowed for this column.
I Compared Change Table Structures with Source Table on Source Database and the structure is matching.
Now I am trying to Run below script:
Begin
dbms_cdc_publish.alter_change_set (Change_Set_name =><<Change Set Name>>,
recover_after_error => 'Y'
End;
I am getting the below error:
ORA-01438: value larger than specified precision allowed for this column
ORA-06512: at "SYS.DBMS_APPLY_ERROR", line 147
ORA-06512: at "SYS.DBMS_APPLY_ERROR", line 301
ORA-06512: at "SYS.DBMS_APPLY_ADM", line 490
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_CDC_PUBLISH", line 580
ORA-06512: at line 2
Still the error is existing, I couldn't find any issues with Change Table structure as it is in Line with Source Table Structure.
Can anyone please help me on this.
Staging Database details:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
TNS for Linux: Version 10.2.0.4.0 - Production
Source Database details:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
TNS for HPUX: Version 10.2.0.4.0 - Production
Also Can anyone let me know if it is possible to run CDC Set-up without DBA Privileges. i,e once the CDC Set-up is done, if we revoke the DBA Privilege will the Capture work properly. I know that for creating Change Table, Set and Source we require DBA Access. But once the set-up is done, do we really require DBA Privileges?
Thanks,
Shashi
Edited by: user8254952 on 09-Mar-2010 05:57
Edited by: user8254952 on 09-Mar-2010 06:00Hi Shashi,
As CDC is built on top of Oracle streams framework, for better responses you can post this ques under {forum:id=70} category.
"ORA-01438: value larger than specified precision allowed for this column" is usually encountered for NUMBER datatype columns. At what level did you check the datatypes? Please confirm if the precision(for NUMBER datatype) are also similar.
Please attach output for the following queries:
select error_message from dba_capture;
select error_number, error_message from dba_apply_error;Please re-validate the data types and then run the same API with remove_ddl = 'Y' option, like this:
exec DBMS_CDC_PUBLISH.ALTER_CHANGE_SET(change_set_name=>'CHANGE_SET_NAME' , recover_after_error=>'Y' , remove_ddl=>'Y');
Hope it helps!
Cheers,
AA -
Oracle ORA-01428: argument is out of range error
Oracle ORA-01428: argument is out of range error
I take it you don't feel like spending the extra money for the EE add-on that was designed to CREATE an INDEX on polygons of logitude,latitude values in such away that a simple
SELECT * FROM ZIP_CODES WHERE SDO_WITHIN_DISTANCE( Z.ZIPCODE_AREA, /* point for zipcode */, 'distance=' || in_distance ) = 'TRUE';
will be very efficient and fast.
primary thing:
you need to drop out the WHEN OTHERS THEN NULL;
also, take advantage of the NO_ROWS_FOUND exception for finding out if a row exists in the database. (instead of doing an IF statement on the results of COUNT(*))
back to your problem
You'll need to investigate which row is causing the problem.
Most likely, it is the zipcode that was the input for the search. I've seen this occur many times on similar trigonometric calculations.
You may have to surround a lot of those trigonometric functions with ROUND( ____, 25) to get it to work.
However, I highly advise you to take a look at what can be done with Oracle Spacial
MK -
Hello. This is the error I get on my iMac Lion using an i1Pro spectrometer and the latest Argyll ICC software. Chartread is the sub program for reading printed color targets.
chartread: Error - icoms - usb_is_usb_portno: port number out of range!
Q. 1 I can't figure out how to fix this and I have no X-Rite software remaining on my computer.
Q. 2 How do I get a list of usb devices (in terminal?) and if I can do that can I assign a new number to that device?
Regards
Mark MacKenzieWithout the KVM the results are the same, except that using the fallback grub entry shows the console but X fails to start
(EE) intel(0): No kernel modesetting driver detected.
(II) UnloadModule: "intel"
(EE) Screen(s) found, but none have a usable configuration.
The same happens if I load the i915 module
MODULES=(i915 !vesafb !uvesafb !vboxdrv)
If I load the i915 and use
kernel /boot/vmlinuz26 root=/dev/sda2 ro vga=795 i915.modeset=1
the console still is unusable, but X boots
And I still see the
fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
Last edited by noalwin (2009-12-28 12:38:51) -
ORA-1652: Index creation error
At the time of table re-organisation, Index creation got aborted for the secondary index creation. then we have continued our activity leaving the index creation due to short of System downtime.
Again we have run the sql statment when the sap system is up, then it has thrown an error:
ORA-1652 unable to extend temp segment by 128 in tablespace PSAPTEMP.
In the current system, we are not ready to increase the size of datafile or resizing.where it leads to the increase the size of database.
Here we have option to create a new temp tablespace, will delete after index creation, but while doing this how do we point the new tablespace which is created for this activity.
SAP 4.6c oracle 9 sun solaris.
Kindly advise what can be done. reply ASAPMartin,
We have discussed with the team like,
1. Create new temporary tablespace with desired Size which should be minimum 25GB
CREATE temporary tablespace PSAPTEMP1......
2. If the original tablespace is a default temporary tablespace, set the new tablespace as default temporary tablespace in the database.
SQL> alter database default temporary tablespace PSAPTEMP1;
3. Perform the index creation
4. Make the old tablespace PSAPTEMP as the default temporary tablespace.
SQL> alter database default temporary tablespace PSAPTEMP
5. Drop the new tablespace.
SQL> drop tablespace temp including contents.
Here I have a question, while switching the default temporary tablespace from PSAPTEMP to the much bigger new PSAPTEMP1Tablespace whether this will affect the running transaction.
Any impact on switching the tablespace online..?
We are performing this activity in the online system(running sap system)
Thanks, -
Spatial index creation fails in oracle9i but works in 8i
Hi--
i'm using oracle9.0.1.2.0 and arcSDE on solaris 8
when i create a spatial feature table and index oracle gives me the foloowing error:
Extended error code(29855): ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13236: internal error in R-tree processing: [failed to cluster in memory]
ORA-13249: Internal error in Spatial index: [mdrcrclmem]
ORA-13232: failed to allocate memory during R-tree creation
ORA-13249: Error in Rtree: [mdrcrrdtbl, select /*+ PARALLEL 4 */ rid , min_d1, max_d1 , min_d2, max_d2 from (select rownum rnum, rid , m(MDSYS.SPATIAL_INDEX)
this occurs whether i use cov2sde at the command line or Create Index in sqlplus:
SQL> create index COUNTY_IDX on COUNTY_SDO(shape)
2 indextype is mdsys.spatial_index
3 parameters ('SDO_INDX_DIMS=2 tablespace=sde2_idx');
create index COUNTY_IDX on COUNTY_SDO(shape)
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13249: Stmt-Execute Failure: SELECT count(*) from SDE.COUNTY_SDO
ORA-29400: data cartridge error
ORA-01116: error in opening database file 14
ORA-01110: data file 14: '/u04/oradata/GIS2/sde3_idx01.dbf'
ORA-27041: unable to open file
SVR4 Error: 24: Too many open files
Additional information: 3
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: at line 1
the bizarre thing is that everything works tickety-boo in oracle 8i *8.1.7.3)
has anyone run across this?
cheers
--kassimthanks for the suggestion, but that didnt work either
i increased the file descriptor limit from 256 to 2048 (my sysadmin sez that could break lots of things in solaris and had another go:
elvis{1}% ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 2048
vmemory(kbytes) unlimited
lvis{2}% cov2sde -o create -l plstrfill_sdo,shape -f $GISDATA/survey.ws/plstr_fill,poly -e a -R 1 -k spatial -a file=$GISDATA/survey.ws/plstr_fields.txt -g SPIDX_RTREE
ArcSDE 8.2 Build 115 Wed Mar 6 09:48:27 PST 2002
Coverage to Layer Loading Administration Utility
Reading column selection file "/data/jack02/in_put/survey.ws/plstr_fields.txt"
Library /data/jack02/in_put/survey not found.
Unable to open library "/data/jack02/in_put/survey"
Loading feature class/subclass "poly"
from Coverage "/data/jack02/in_put/survey.ws/plstr_fill"
sde_layer_plstrfill_sdo: plstrfill_sdo is in LOADONLY mode
Imported 158399 features into SDE plstrfill_sdo,shape from coverage /data/jack02/in_put/survey.ws/plstr_fill,poly
SDE Error(-51) Underlying DBMS error
Extended error code(29855): ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13230: failed to create temporary table [M2_8496$$] during R-tree creation
ORA-13249: Error in stmt: CREATE TABLE M2_8496$$ NOLOGGING tablespace SDE_IDX STORAGE (initial 4096K next 4096K pctincrease 0 maxextents unlimited) as (select rid , min_d1, max_d1 , min_d2, max_d2 from M0_8496$$ a, (select (min_d2+max_d2) value fro(MDSYS.SPATIAL_INDEX)
Not able to set layer into Normal-IO mode.
Cov2SDE completed.
No libraries currently set.
SQL> create index plstrfill_idx on plstrfill_sdo(shape)
2 indextype is mdsys.spatial_index
3 parameters ('SDO_INDX_DIMS=2 tablespace=sde4_idx');
create index plstrfill_idx on plstrfill_sdo(shape)
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13230: failed to create temporary table [M2_84A5$$] during R-tree creation
ORA-13249: Error in stmt: CREATE TABLE M2_84A5$$ NOLOGGING tablespace SDE4_IDX
STORAGE (initial 4096K next 4096K pctincrease 0 maxextents unlimited) as
(select rid , min_d1, max_d1 , min_d2, max_d2 from M0_84A5$$ a, (select
(min_d2+max_d2) value from M0_84A5$$ where rowid='AAAISqAAPAAACCYABK') b where
(((a.min_d2+a.max_d2) < b.value) or (((a.min_d2+a.max_d2) = b.value) and (a.rid
<= 'AAAISeAAJAAAnvnAASZ'))))
ORA-13230: failed to create temporary table [M2_84A5$$] during R-tree creation
ORA-29400: data cartridge error
ORA-00210: cannot open the specified controlfile
ORA-00202: controlfile: '/u01/oradata/GIS2/control01.ctl'
ORA-27041: unable to open file
SVR4 Error: 24: Too many open files
Additional information: 3
ORA-06512: at "MDSYS.SDO_INDEX_METH
this is really killing me
my oracle is setup following the esri and oracle guidelines:
all our tablespaces are with UNLIMITED extent and maxsize on
any files. All the tablespaces follow Oracle9i best practices
such as OFA, SAFE, and SAME including Temporary Tablespace.
any suggestions would be realy helpful
--kassim
Maybe you are looking for
-
Account error - Can't sign up for Xbox Music Pass
Hi there, when I try to sign up for the 30 day trial of Xbox Music Pass, I receive the following error, regardless of browser/PC used. It's been going on for several days. I have been in contact with a live support technician, and was directed here
-
Package with 2 procedures not working; Please help
When I try to run the procedures that are in this package manually, each one seperately works. But when I put together these procedures in a package, the second procedure does not work or not updating the table. Any idea why this is creating a proble
-
Safari 6.0 go directly to website
Prior to Safari 6.0, I was able to type in a name of a business and it would go straight to that business and not to a Google search. For example, in the prior version, if I typed in "Tingo", it would go directly to Tingo.com. But with 6.0, it goes t
-
Not able to open the workflow Template.
Hi All, Recenlty we have moved the workflow templates from 4.6c to ECC 5.0. We are able to open all the workflow templates except one workflow . While trying to open the workflow template Via PFTC_DIS or SWDD, We are getting following error. "Type de
-
QuickLook: How to make QuickLook preview fonts bigger?
Hi I have to preview an EPS header frequently the way as I need (drag an EPS on TextEdit icon and it will show an EPS header in text format), so I've asked one guy to write me a QuickLook plugin for to speedup my work. The plugin works perfect except