ORA-32006

ORA-32006: %s initialization parameter has been deprecated

Cause: A deprecated parameter was specified at startup

Action: Consult Oracle documentation to find new parameters to use instead.

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

ORA-27040: file create error, unable to create file

Cause: create system call returned an error, unable to create file

Action: verify filename, and permissions

imp.log:

IMP-00017: following statement failed with ORACLE error 1119:
"CREATE TABLESPACE "RBS" DATAFILE '/oracle_data/mydb/rbs01.dbf' "
"SIZE 1073741824 , '/oracle_data/mydb/rbs02.dbf' SIZE 536870"
"912 DEFAULT STORAGE(INITIAL 516096 NEXT 516096 MINEXTENTS 2 MAXEXTEN"
"TS 2147483645 PCTINCREASE 1) ONLINE PERMANENT "
IMP-00003: ORACLE error 1119 encountered
ORA-01119: error in creating database file '/oracle_data/mydb/rbs01.dbf'
ORA-27040: file create error, unable to create file
--------
ORA-28000: the account is locked
Cause: The user has entered wrong password consequently for maximum number of times specified by the user's profile parameter FAILED_LOGIN_ATTEMPTS, or the DBA has locked the account
Action: Wait for PASSWORD_LOCK_TIME or contact DBA
[sde log] [05/07/2007 15:29:47;SdeId=0;Client=GIOMGR] Error (-51):Couldn't Start Server Task.
DB_open_instance()::db_connect (OCI8) error: 28000
CAN'T OPEN INSTANCE: idw10g.
Reason: the account is locked. Use Oracle Enterprise Manager to unlock the account.

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

ORA-19905: log_archive_format must contain %%s, %%t and %%r

Cause: log_archive_format is missing a mandatory format element. Starting with Oracle 10i, archived log file names must contain each of the elements %s(sequence), %t(thread), and %r(resetlogs id) to ensure that all archived log file names are unique.

Action: Add the missing format elements to log_archive_format.

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

ORA-19504: failed to create file "string"

Cause: call to create file returned an error

Action: check additional messages, check access permissions

alert.log:
< Errors in file /oracle/admin/mydb/bdump/mydb_arc0_1604.trc:
< ORA-19504: failed to create file "/mydb/archivelogs/mydb_2085_1_633269081.dbf"

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

ORA-12913: Cannot create dictionary managed tablespace

Cause: Attemp to create dictionary managed tablespace in database which has system tablespace as locally managed

Action: Create a locally managed tablespace.

imp.log:
IMP-00017: following statement failed with ORACLE error 12913:
"CREATE TABLESPACE "TEMP" DATAFILE '/oracle_data/mydb/temp02.dbf"
"' SIZE 1048576000 , '/oracle_data/mydb/temp01.dbf' SIZE 419"
"430400 , '/fs/u02/oracle_data/mydb/temp03.dbf' SIZE 419430400 "
" DEFAULT STORAGE(INITIAL 1048576 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 214"
"7483645 PCTINCREASE 1) ONLINE TEMPORARY "
IMP-00003: ORACLE error 12913 encountered
ORA-12913: Cannot create dictionary managed tablespace
--------
ORA-13226: interface not supported without a spatial index
Cause: The geometry table does not have a spatial index.
Action: Verify that the geometry table referenced in the spatial operator has a spatial index on it.

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-12018: following error encountered during code generation for "string"."string"

ORA-12018: following error encountered during code generation for "string"."string"

Cause: The refresh operations for the indicated materialized view could not be regenerated due to errors.

Action: Correct the problem indicated in the following error messages and repeat the operation.

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

ORA-10630: Illegal syntax specified with SHRINK clause

Cause: An illegal option was specified with the SHRINK clause

Action: Verify the SQL Reference Manual and reissue the command

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

ORA-10615: Invalid tablespace type for temporary tablespace

Cause: Tablespace with AUTO SEGMENT SPACE MANAGENEMT specified cannot be used as a temporary tablespace

Action: Recheck the tablespace name and re-issue the statement

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

ORA-04030: out of process memory when trying to allocate string bytes (string,string)

Cause: Operating system process private memory has been exhausted

Action: none

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

ORA-01918: user "string" does not exist

Cause: User does not exist in the system.

Action: Verify the user name is correct.

Note:
The error occurred when performing Oracle import process:

IMP-00003: ORACLE error 1918 encountered
ORA-01918: user 'USER2' does not exist
IMP-00017: following statement failed with ORACLE error 1918:
"ALTER USER "USERA" QUOTA UNLIMITED ON "TBS_BUS" QUOTA UNLIMITED ON "IN"
"TBS_BUS" QUOTA UNLIMITED ON "TEMP""

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

ORA-01691: unable to extend lob segment string.string by string in tablespace string

Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated.

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

alert.log
Wed Sep 24 13:01:06 2008
ORA-1691: unable to extend lobsegment APP_DAW.SYS_LOB0000488635C00008$$ by 64 in tablespace APP_DAW_TABLES

If the datafiles of the tablespace are set to auto extend, the reason is that the datafiles have reached its maximum size. The following scripts can be used to check and increase the size:


1- For Non TEMP tablespaces :

SELECT file_name,bytes,autoextensible,maxbytes 
FROM dba_data_files 
WHERE tablespace_name='XX';

2- For TEMP Tablespaces :

SELECT file_name,bytes,autoextensible,maxbytes 
FROM dba_temp_files 
WHERE tablespace_name=' XX'; 

1- For datafiles :

 Change the datafiles attributes to be autoextensible without the maxbytes file size limitation by setting the MAXBYTES column to unlimited as follows :


SQL> alter database datafile '' autoextend on maxsize unlimited;



2- For Temp files :

SQL> alter database tempfile '' autoextend on maxsize unlimited;

--------------------------------------------------

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

ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

Cause: Either incomplete or backup control file recovery has been performed. After these types of recovery you must specify either the RESETLOGS option or the NORESETLOGS option to open your database.

Action: Specify the appropriate option.

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

ORA-01537: cannot add datafile - file already part of database

Cause: During a CREATE or ALTER TABLESPACE, a file being added is already part of the database.

Action: Correct spelling of the datafile name or use a different file.

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

 Thank you for visiting Spatial DBA - Oracle and ArcSDE.

Please visit Oracle DBA Tips (http://www.oracledbatips.com) for more Oracle DBA Tips.

====================================================================


ORA-01507: database not mounted

Cause: A command was attempted that requires the database to be mounted.

Action: If you are using the ALTER DATABASE statement via the SQLDBA startup command, specify the MOUNT option to startup; else if you are directly doing an ALTER DATABASE DISMOUNT, do nothing; else specify the MOUNT option to ALTER DATABASE. If you are doing a backup or copy, you must first mount the desired database. If you are doing a FLASHBACK DATABASE, you must first mount the desired database.

Note:

When an Oracle database is on NOMOUNT mode, the following query results in the error.

SQL> select * from v$database;
select * from v$database
*
ERROR at line 1:
ORA-01507: database not mounted

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-01446: cannot select ROWID from, or sample, a view with DISTINCT, GROUP BY, etc.

 Thank you for visiting Spatial DBA - Oracle and ArcSDE.

Please visit Oracle DBA Tips (http://www.oracledbatips.com) for more Oracle DBA Tips.

====================================================================

Oracle10g Release 1 Message ORA-01446: cannot select ROWID from, or sample, a view with DISTINCT, GROUP BY, etc. Cause: Action:

Oracle 9.2 or Earlier Error Message ORA-01446: cannot select ROWID from view with DISTINCT, GROUP BY, etc. Cause: A SELECT statement attempted to select ROWIDs from a view containing columns derived from functions or expressions. Because the rows selected in the view do not correspond to underlying physical records, no ROWIDs can be returned. Action: Remove ROWID from the view selection clause, then re-execute the statement.

Last updated: August 24, 2009

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

ORA-01219: database not open: queries allowed on fixed tables/views only

Cause: A query was issued against an object not recognized as a fixed table or fixed view before the database has been opened.

Action: Re-phrase the query to include only fixed objects, or open the database.

Note:
When an Oracle database is in NOMOUNT mode, query on data dictionary views results the error:

SQL> select * from dba_users;
select * from dba_users
*
ERROR at line 1:
ORA-01219: database not open: queries allowed on fixed tables/views only

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

ORA-01109: database not open

Cause: A command was attempted that requires the database to be open.

Action: Open the database and try the command again

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

ORA-01012: not logged on

Cause: A host language program issued an Oracle call, other than OLON or OLOGON, without being logged on to Oracle. This can occur when a user process attempts to access the database after the instance it is connected to terminates, forcing the process to disconnect.

Action: Log on to Oracle, by calling OLON or OLOGON, before issuing any Oracle calls. When the instance has been restarted, retry the action.

sde.log:
[02/18/2008 16:23:41;SdeId=6365799;Client=Mojave] db_array_fetch_spix_recs OCI Fetch Error (1012)
[02/18/2008 16:23:41;SdeId=6365799;Client=Mojave] 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-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=POPCORN] 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-00439

ORA-00439: feature not enabled: string

Cause: The specified feature is not enabled.

Action: Do not attempt to use this feature.

Note:
CREATE TABLE wb_rt_dp_columninfo (

*

ERROR at line 1:

ORA-00439: feature not enabled: Partitioning

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