Home
All Oracle Error Codes
Oracle DBA Forum

Frequent Oracle Errors

TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated

MVIEW on-demand refresh - rollback space issue

Mindaugas Navickas

2006-02-21

Replies:
Hi,

Platform Oracle 9.2.0.5 on HP-UX
Error(s):
ORA-12008: error in materialized view refresh path
ORA-01562: failed to extend rollback segment number 2
ORA-01650: unable to extend rollback segment RBS_1 by 125 in tablespace
ROLLBACK

A big table is updated during a day on primary location. This table has MV log
created - using PK.
Once a day changes to this table has to be propagated to a remote site
(on-demand replication based on PK).

Most of times replication process works fine, however, there are times when
larger number of rows are updated. Then replication fails with errors above.
I know that most straightforward way would be to increase rollback tablespace
size on remote site, however, we are short of disk space on that site and
growing rollback tablespace (already 1.2G) just to accommodate this case it
doesn't makes much sense (most of transactions on that database are small).

<b>Is there a way of splitting replication transaction into number of
transactions?</b>

May be I am looking for something what does not exists, however, I hope, that
others might faced similar problem and can share how they solved that.

Thank you
Mindaugas Navickas
DBA, OCP 10g, 9i, 8i



 

 
   
__________________________________________________________
Find your next car at http://autos.yahoo.ca
--
http://www.freelists.org/webpage/oracle-l