Thank you for visiting Spatial DBA - Oracle and ArcSDE.
Please visit Oracle DBA Tips (http://www.oracledbatips.com) for more Oracle DBA Tips.
===================================================================
ORA-06550: line string, column string:string
Cause: A PL/SQL compilation error has occurred. The numbers given for line and column are the location in the PL/SQL block where the error occurred.
Action: Refer to the following PL/SQL messages for more information about the error.
sde.log:
db_sda_execute_stmt::OCIStmtExecute (6550)
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
Wednesday, January 16, 2008
ORA-06550
ORA-04044
ORA-04044: procedure, function, package, or type is not allowed here
Cause: A procedure, function, or package was specified in an inappropriate place in a statement.
Action: Make sure the name is correct or remove it.
sde.log:
[01/15/2008 13:52:40;SdeId=5924336;Client=gispc] db_describe_select describe error (4044), column 1.
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-02201
ORA-02201: sequence not allowed here
Cause: An attempt was made to reference a sequence in a from-list.
Action: A sequence can only be referenced in a select-list.
sde.log:
[01/15/2008 13:52:26;SdeId=5924336;Client=gispc] db_describe_select describe error (2201), column 1.
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-02019
ORA-02019: connection description for remote database not found
Cause: An attempt was made to connect or log in to a remote database using a connection description that could not be found.
Action: Specify an existing database link. Query the data dictionary to see all existing database links. See your operating system-specific Net8 documentation for valid connection descriptors.
sde.log:
[01/15/2008 13:52:49;SdeId=5924336;Client=gispc] db_describe_select describe error (2019), column 1.
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-01543
ORA-01543: tablespace 'string' already exists
Cause: Tried to create a tablespace which already exists
Action: Use a different name for the new tablespace
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-01502
ORA-01502: index 'string.string' or partition of such index is in unusable state
Cause: An attempt has been made to access an index or index partition that has been marked unusable by a direct load or by a DDL operation
Action: DROP the specified index, or REBUILD the specified index, or REBUILD the unusable index partition
Metalink:
Note:281500.1
-- initialization parameter SKIP_UNUSABLE_INDEXES in Oracle Database
-- Setting this parameter to TRUE disables error reporting of indexes and index partitions marked UNUSABLE.
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-01119
Thank you for visiting Spatial DBA - Oracle and ArcSDE.
Please visit Oracle DBA Tips (http://www.oracledbatips.com) for more Oracle DBA Tips.
===============================================================
ORA-01119: error in creating database file 'string'
Cause: Usually due to not having enough space on the device.
Action: none
imp.log:
. importing SYSTEM's objects into SYSTEM
IMP-00017: following statement failed with ORACLE error 1119:
"CREATE TABLESPACE "RBSBIG" DATAFILE '/fs/u02/oracle_data/mydb/rbsbig01"
".dbf' SIZE 629145600 , '/fs/u02/oracle_data/mydb/rbsbig02.dbf' SIZ"
"E 629145600 , '/fs/u02/oracle_data/mydb/rbsbig03.dbf' SIZE 8388608"
"00 DEFAULT STORAGE(INITIAL 2097152 NEXT 2097152 MINEXTENTS 2 MAXEXTE"
"NTS 2147483645 PCTINCREASE 1) ONLINE PERMANENT "
IMP-00003: ORACLE error 1119 encountered
ORA-01119: error in creating database file '/fs/u02/oracle_data/mydb/rbsbig01.dbf'
ORA-27040: file create error, unable to create file
SVR4 Error: 2: No such file or directory
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-00980
ORA-00980: synonym translation is no longer valid
Cause: The synonym used is based on a table, view, or synonym that no longer exists.
Action: Replace the synonym with the name of the object it references or re-create the synonym so that it refers to a valid table, view, or synonym.
sde.log:
[01/15/2008 13:52:40;SdeId=5924336;Client=GISPC] db_describe_select describe error (980), column 1.
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-00907
ORA-00907: missing right parenthesis ")"
Cause: A left parenthesis has been entered without a closing right parenthesis, or extra information was contained in the parentheses. All parentheses must be entered in pairs.
Action: Correct the syntax and retry the statement.
sde.log
db_sda_execute_stmt::OCIStmtExecute (907)
.
[01/08/2008 06:57:27;SdeId=5794874;Client=GISPC] db_array_fetch_attrs OCI Fetch Error (907)
[01/08/2008 06:57:27;SdeId=5794874;Client=GISPC] load_buffer error -51
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-00439
ORA-00439: feature not enabled: string
Cause: The specified feature is not enabled.
Action: Do not attempt to use this feature.
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
Saturday, January 12, 2008
ORA-04063
ORA-04063: %s has errors
Cause: Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view’s defining query to a non-existent table. Can also be a table which has references to non-existent or inaccessible types.
Action: Fix the errors and/or create referenced objects as necessary.
sde.log
[12/02/2007 06:09:17;SdeId=5502900;Client=GISServer] db_describe_select describe error (4063), column 1.
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
Sunday, December 30, 2007
ORA-13032
ORA-13032: Invalid NULL SDO_GEOMETRY object
Cause: There are invalid SDO_POINT_TYPE or SDO_ELEM_INFO_ARRAY or SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid fields. To specify a NULL geometry, specify the whole SDO_GEOMETRY as NULL instead of setting each field to NULL.
Note: Oracle Database Error Messages 10g Release 2 (10.2)
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-13031
ORA-13031: Invalid Gtype in the SDO_GEOMETRY object for point object
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the VARRAYs are NULL but the SDO_GTYPE is not of type POINT.
Action: Verify that the geometries have valid gtypes.
Note: Oracle Database Error Messages 10g Release 2 (10.2)
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-13030
ORA-13030: Invalid dimension for the SDO_GEOMETRY object
Cause: There is a mismatch between the dimension in the SDO_GTYPE and dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object.
Action: Verify that the geometries have valid dimensionality.
Note: Oracle Database Error Messages 10g Release 2 (10.2)
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-13029
ORA-13029: Invalid SRID in the SDO_GEOMETRY object
Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified SRID may be outside the valid SRID range.
Action: Verify that the geometries have valid SRIDs.
Note: Oracle Database Error Messages 10g Release 2 (10.2)
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-13028
ORA-13028: Invalid Gtype in the SDO_GEOMETRY object
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid gtypes.
Note: Oracle Database Error Messages 10g Release 2 (10.2)
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-13027
ORA-13027: unable to read dimension definition from string
Cause: There was a problem reading the dimension definition from the
Action: Verify that the
Note: Oracle Database Error Messages 10g Release 2 (10.2)
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-13026
ORA-13026: unknown element type for element string.string.string
Cause: The SDO_ETYPE column in the
Action: Redefine the geometric element type in the
Note: Oracle Database Error Messages 10g Release 2 (10.2)
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-13025
ORA-13025: polygon does not close
Cause: The coordinates defining a polygonal geometric element represent an open polygon.
Action: Redefine the coordinates of the polygon.
Note: Oracle Database Error Messages 10g Release 2 (10.2)
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
ORA-13024
ORA-13024: polygon has less than three segments
Cause: The coordinates defining a polygonal geometric element represent less than three segments.
Action: Redefine the coordinates for the polygon.
Note: Oracle Database Error Messages 10g Release 2 (10.2)
All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors
Subscribe to:
Posts (Atom)
