Sent: Friday, September 19, 2003 6:24
PM
Subject: Fwd: Re: Tempfile
weirdness
funny how my previous email seems to have been truncated
where I put three dots [ie , "."] tosignifiy 3 lines.Resend
:For a critical database where I want to be SURE that the file system
has en
funny how my previous email seems to have been truncated where I put
three dots [ie , "."] to
signifiy 3 lines.
Resend :
For a critical database where I want to be SURE that the file system has
enough space for the
TempFile, I run a large
SELECT * FROM DBA_SOURCE
UNION
SELECT * FROM DBA_SOURCE
U
For a critical database where I want to be SURE that the file system has
enough space for the
TempFile, I run a large
SELECT * FROM DBA_SOURCE
UNION
SELECT * FROM DBA_SOURCE
UNION
has detected sensitive content.
>
> Place = Multiple recipients of list ORACLE-L; ; ; [EMAIL PROTECTED]
> Sender = Tanel Poder
> Subject = Re: Tempfile weirdness
> Delivery Time = September 18, 2003 (Thursday) 05:43:08
> Policy = Sexual Discrimination
> Action on this mail = Quaran
> >
> > ---
> > Trend SMEX Content Filter has detected sensitive content.
> >
> > Place = Multiple recipients of list ORACLE-L; ; ; [EMAIL PROTECTED]
> > Sender = Tanel Poder
> > Subject = Re: Tempfile weirdness
> > Delivery Time = September 1
as detected sensitive content.
>
> Place = Multiple recipients of list ORACLE-L; ; ; [EMAIL PROTECTED]
> Sender = Tanel Poder
> Subject = Re: Tempfile weirdness
> Delivery Time = September 18, 2003 (Thursday) 05:43:08
> Policy = Sexual Discrimination
> Action on this mail = Qu
Heh, look what happens if you try to help someone ;)
(an automatic reply to my message)
---
Trend SMEX Content Filter has detected sensitive content.
Place = Multiple recipients of list ORACLE-L; ; ; [EMAIL PROTECTED]
Sender = Tanel Poder
Subject = Re: Tempfile weirdness
Delivery Time
It also can be caused by bad sectors or other hardware errors, but I'd bet
on sparse file problem as you described.
When I create temp tablespaces, I either copy the tempfile into another
filename and then rename to original using cp, that way the file isn't
sparse anymore, thus no problems using i
We also ran into the IO error situation on a few of our 9i R2 databases using
TEMPfiles.
DBAs forgot that the file system contained those tempfiles and created other datafiles
on those.
We are now considering using dedicated file system naming convention that will hold
TEMPfiles. We
already have
Any comments on the following??
When creating index, got
ORA-00603: ORACLE server session terminated by fatal error
apparently caused by
ksedmp: internal or fatal error
ORA-01114: IO error writing block to file 121 (block # 149)
ORA-27063: skgfospo: number of bytes read/written is incorrect
Add
10 matches
Mail list logo