Hi,
I tried to view the TAR posted by you, But it said that I don't have sufficient
privileges to view the TAR.
Can u pl send me a copy of the TAR 1766421.999.
TIA
venkat
--
On Thu, 16 Aug 2001 05:10:58
Farnsworth, Dave wrote:
I did this from svrmgrl. The database was shutdawn at the
Hi Dave,
do you use Alter tablespace .. begin backup ??
if yes then ..FWIW ..try mounting the DB and doing a
alter tablespace .. end backup for tablespace that
might still be in that mode(maybe the one containing
file10)
hth
Deepak
--- Farnsworth, Dave
[EMAIL PROTECTED] wrote:
I have a very
Hi Dave,
do you use Alter tablespace .. begin backup ??
if yes then ..FWIW ..try mounting the DB and doing a
alter tablespace .. end backup for tablespace that
might still be in that mode(maybe the one containing
file10)
hth
Deepak
--- Farnsworth, Dave
[EMAIL PROTECTED] wrote:
I have a very
Dave,
First thing I always look at on this is directory/file ownership and
permissions. Make sure that Oracle can write there. This is obviously
NT. Check your disk administrator tool. I have (in the past) seen
where NT on a reboot reassigns drive letters to the various drives (D
becomes E, F
Hi Dave,
Are you in archive log mode?
-Rocky
--- Farnsworth, Dave [EMAIL PROTECTED] wrote:
I have a very bad situation. When I got in this morning I saw that the
nightly backup was hung up. I do a cold backup to another server and
then
the network admins backup my backup to tape. I did a
Dave,
I hope all is okay with your father.
It sounds like you still have some datafiles that are still under the control of the
os backup script. If you did a cold backup and it was still hung, who started the
database up where you had to shutdown abort? Did the alert log show any problems with
Never mind. I found the recover database command. It worked like a
charm!! The network admin was happy too!!
Dave
-Original Message-
Sent: Monday, August 13, 2001 1:10 PM
To: Multiple recipients of list ORACLE-L
I have a very bad situation. When I got in this morning I saw that
The unable to write to might simply be because another process has it
... i.e. the backup process.
You need to find out if the file is open by another process. If its
possible, kill that hold.
-Original Message-
Sent: Monday, August 13, 2001 1:10 PM
To: Multiple recipients of
