ORA-01861

ORA-01861: literal does not match format string

Cause: Literals in the input must be the same length as literals in the format string (with the exception of leading whitespace). If the "FX" modifier has been toggled on, the literal must match exactly, with no extra whitespace.

Action: Correct the format string to match the literal.

sde.log:
db_sda_execute_stmt::OCIStmtExecute (1861)
.
[01/28/2008 09:52:34;SdeId=6036064;Client=mypc] db_array_fetch_attrs OCI Fetch Error (1861)
[01/28/2008 09:52:34;SdeId=6036064;Client=mypc] 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-01858

Error: ORA-01858: a non-numeric character found where a digit was expected
Cause: You tried to enter a date value using a specified date format, but you entered a non-numeric character where a numeric character was expected.
Action: The options to resolve this Oracle error are:
Check the date formats recognized by the to_date function. Correct the date value and retry.

sde.log:
db_sda_execute_stmt::OCIStmtExecute (1858)
.
[01/23/2008 13:42:08;SdeId=6021520;Client=STRINGER] db_array_fetch_attrs OCI Fetch Error (1858)
[01/23/2008 13:42:08;SdeId=6021520;Client=STRINGER] 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-01847

ORA-01847: day of month must be between 1 and last day of month

Cause: The day of the month listed in a date is invalid for the specified month. The day of the month (DD) must be between 1 and the number of days in that month.

Action: Enter a valid day value for the specified month.

sde.log:

db_sda_execute_stmt::OCIStmtExecute (1847)
.
[01/23/2008 13:40:22;SdeId=6021520;Client=STRINGER] db_array_fetch_spix_recs OCI Fetch Error (1847)
[01/23/2008 13:40:22;SdeId=6021520;Client=STRINGER] load_buffer error -51

ORA-01659

ORA-01659: unable to allocate MINEXTENTS beyond string in tablespace string

Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created.

Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with smaller value for MINEXTENTS, NEXT or PCTINCREASE.


All Oracle errors in the blog can be found at: Oracle errors
All ESRI ArcSDE errors in the blog can found at: ArcSDE Errors

More Oracle DBA tips, please visit Oracle DBA Tips 

ORA-01650

ORA-01650: unable to extend rollback segment name by num in tablespace name

Cause: Failed to allocate extent for the rollback segment in tablespace.

Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the specified tablespace.

Solution:


--Querying DBA_SEGMENTS for the rollback segments will determine if the rollback segments are at their maximum extent:

SELECT segment_name, extents, max_extents FROM dba_segments WHERE segment_type='ROLLBACK';

--If your rollback segments are at max extents, you can increase the max number of extents as follows:

ALTER ROLLBACK SEGMENT rollback_segment_name STORAGE (MAXEXTENTS xx);

--It may also be likely that your rollback segment tablespace is full. Increase the size of the tablespace by adding another datafile to the tablespace:

ALTER TABLESPACE ts_name ADD DATAFILE '/directory/file_name' SIZE xxxM AUTOEXTEND ON NEXT xxxM MAXSIZE xxxM;


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-01441

ORA-01441: cannot decrease column length because some value is too big

Cause: An ALTER TABLE MODIFY statement attempted to decrease the size of a character field containing data. A column whose maximum size is to be decreased must contain only NULL values.
Action: Set all values in column to NULL before decreasing the maximum size.



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-01089

ORA-01089: immediate shutdown in progress - no operations are permitted
Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running ORACLE instance, so your operations have been terminated.
Action: Wait for the instance to be restarted, or contact your DBA.

sde.log:
[07/15/2008 13:02:02;SdeId=243827;Client=lawn] db_array_fetch_attrs OCI Fetch Error (1089)
[07/15/2008 13:02:02;SdeId=243827;Client=lawn] load_buffer error -51
db_sda_execute_stmt::OCIStmtExecute (3135)
.
[07/15/2008 13:08:00;SdeId=0;Client=GIOMGR] DBMS error code: 3114
ORA-03114: not connected to ORACLE


[07/15/2008 13:08:00;SdeId=0;Client=GIOMGR] Error in DB_instance_get_status(), SQL: SELECT num_prop_value FROM SDE.server_config WHERE prop_name = :prop_name