Links
Home
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
Standby databases and adding datafiles

Standby databases and adding datafiles

2005-04-08       - By daniel.hubler@(protected)
Reply:     1     2  

This is Oracle v8174  on OpenVMS v732.
We run a standby database in managed mode.

In the past, when we were forced to add datafiles to the primary,
we would get an ORA-01516 (See ORA-01516.ora-code.com) (nonexistent log file, datafile or tempfile
'xxxxxxx')
on the standby, when that transaction hit.   We would then do the
ALTER DATABASE CREATE DATAFILE 'xxxxxxxx'
AS
'yyyyyyyyyyyy'.
We would then restart manged recovery on the standby.

Recently we have started to get a different message on the standby when
adding datafiles.  It looks like this:
==============
8-APR-2005 14:45:14.27:
WARNING! Recovering data file 1514 from a fuzzy file. If not the current
file
it might be an online backup taken without entering the begin backup
command.
Successfully added datafile 1514 to media recovery
Datafile #1514: 'PRODD13:[V500.DB_PROD]D_PERSON_15.DBS'
===============
At this point, managed recovery continues on the standby;  archive log
files continue to be processed.

So we then end the managed recovery ("recover managed standby database
cancel")
and then alter the new datafile into the standby, just like before.

We then restart recovery.  Logs that have already been processed once, get
processed again.
I am assuming that the newly created datafile forces this.

This scenario seems to be working.  We invoked the standby just last
weekend and it came up fine.
We have rebuilt it since, copying from primary, and continue to get the
"WARNING - fuzzy file" message.

Can anyone explain why we would start getting a different message in this
situation?
Thanks.

Dan Hubler
Database Administrator
Aurora Healthcare
daniel.hubler@(protected)

--
http://www.freelists.org/webpage/oracle-l