Set up a friendly environment to share my understanding and ideas about Oracle / Oracle Spatial database administration, ESRI ArcSDE Geodatabase administration and UNIX (Solaris) operating system.
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: 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;
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
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.
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
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.
ORA-00372: file string cannot be modified at this time
Cause: attempting to modify the contents of a file that cannot be modified. The file is most likely part of a read only tablespace but may be in the process of going offline, or the database may be in the process of closing.
Action: check the status of the file and its 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-00257: archiver error. Connect internal only, until freed.
Cause: The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file.
Action: Check archiver trace file for a detailed description of the problem. Also verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving.
sde.log:
DB_open_instance()::db_connect (OCI8) error: 257
CAN'T OPEN INSTANCE: mydb.
Spatial Engine Connection Failed (-51).
Cannot Get Access to Instance mydb
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-00060: deadlock detected while waiting for resource
Cause: Your session and another session are waiting for a resource locked by the other. This condition is known as a deadlock. To resolve the deadlock, one or more statements were rolled back for the other session to continue work.
Action: Either:
Enter a ROLLBACK statement and re-execute all statements since the last commit or
Wait until the lock is released, possibly a few minutes, and then re-execute the rolled back statements.
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-00028: your session has been killed Cause: A privileged user has killed your session and you are no longer logged on to the database. Action: Login again if you wish to continue working.
Java session space is the memory that holds Java state from one database call to another. JAVA_SOFT_SESSIONSPACE_LIMIT specifies (in bytes) a soft limit on Java memory usage in a session, as a means to warn you if a user's session-duration Java state is using too much memory. When a user's session-duration Java state exceeds this size, Oracle generates a warning that goes into the trace files.
If SGA_TARGET is set: If the parameter is not specified, then the default is 0 (internally determined by the Oracle Database). If the parameter is specified, then the user-specified value indicates a minimum value for the memory pool.
If SGA_TARGET is not set: 24 MB, rounded up to the nearest granule size
Modifiable
ALTER SYSTEM
Range of values
Minimum: 0 (values greater than zero are rounded up to the nearest granule size)
Maximum: operating system-dependent
Basic
No
JAVA_POOL_SIZE specifies (in bytes) the size of the Java pool, from which the Java memory manager allocates most Java state during runtime execution. This memory includes the shared in-memory representation of Java method and class definitions, as well as the Java objects that are migrated to the Java session space at end-of-call. Note:
I reserve the right to delete comments that are not contributing to the overall theme of the BLOG or are insulting or demeaning to anyone. The posts on this BLOG are provided "as is" with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer.
