Monday, October 6, 2008

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


ORA-00372

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

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

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

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_SOFT_SESSIONSPACE_LIMIT

Property

Description

Parameter type

Integer

Default value

0

Modifiable

No

Range of values

0 to 2 GB - 1

Basic

No

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.

Note:

1. Related parameter: _JAVA_MAX_SESSIONSPACE_SIZE

2. Query for the current value of the parameter

select name, value, isdefault, isses_modifiable, issys_modifiable,

isinstance_modifiable, isdeprecated, description

from v$parameter

where upper(name) = ‘JAVA_SOFT_SESSIONSPACE_LIMIT’;

NAME

VALUE

IS

DEFAULT

ISSES_

MODIFIABLE

ISSYS_

MODIFIABLE

ISINSTANCE_

MODIFIABLE

IS

DEPRECATED

DESCRIPTION

java_soft_sessionspace_limit

0

TRUE

FALSE

FALSE

FALSE

FALSE

warning limit on size in

bytes of a Java sessionspace

Oracle initializatoin parameters

JAVA_POOL_SIZE

Thank you for visiting Spatial DBA - Oracle and ArcSDE.

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

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



Property
Description
Parameter type
Big integer
Syntax
JAVA_POOL_SIZE = integer [K | M | G]
Default value
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:
1. This parameter was introduced in Oracle8i.
Information on current usage of the Java Pool can be found using the query:
 
Select pool, name, bytes
FROM v$sgastat
WHERE pool = 'java pool';
 
This query will return under the name column the values of 'free memory' and 'memory in use'.
 

POOL
NAME
BYTES
java pool
joxs heap
141120
java pool
free memory
312166720
java pool
joxlod exec hp
6459264
 
2. Query for the current value of the parameter
select name, value, isdefault, isses_modifiable, issys_modifiable,
isinstance_modifiable, isdeprecated, description
from v$parameter
where upper(name) = ‘JAVA_POOL_SIZE’;
NAME
VALUE
IS
DEFAULT
ISSES_
MODIFIABLE
ISSYS_
MODIFIABLE
ISINSTANCE_
MODIFIABLE
IS
DEPRECATED
DESCRIPTION
java_pool_size
318767104
FALSE
FALSE
IMMEDIATE
TRUE
FALSE
size in bytes
of java pool

Oracle initializatoin parameters