Re: Export error in 10.2.0.4 database stating temp tablespace is offline but it's not
- From: Jozsef Horvath <horvathjozsef@xxxxxxxxx>
- To: jrkhym@xxxxxxxxx
- Date: Fri, 5 Nov 2010 12:30:50 +0000
Hi Jason,
Since it is "just" a temporary tablespace probably the easiest and quickest
"solution" is to drop and re-create it.
I guess the tempfile got corrupted when your server panicked that could be
an explanation why the exp utility thinks it is offline.
Just an idea: It might be worth to run dbv -if it is not done yet- against
the datafiles to see if any of them got corrupted when the server panicked.
-- Jozsef
On 5 November 2010 09:26, Jason Khym <jrkhym@xxxxxxxxx> wrote:
> My apologies for not including the tablespace information. Tablespace is a
> true temporary tablespace . It is a Locally Managed Tablespace.
>
> I also forgot to mention that this problem started after our database
> server paniced due to a null pointer condition in the driver for our
> encrypted volumes(we use a Voremtric solution for encrypting data at rest).
> Since we were in a VCS cluster the service grop failover to the secondary
> node. Oracle did crash recovery on the secondary node and opened without
> errors. Well except this error in the exp started afterwards.
>
> 1* select * from dba_tablespaces where tablespace_name='TEMP'
> SQL> /
> TABLESPACE_NAME BLOCK_SIZE INITIAL_EXTENT NEXT_EXTENT
> MIN_EXTENTS MAX_EXTENTS
> ------------------------------ ---------- -------------- -----------
> ----------- -----------
> PCT_INCREASE MIN_EXTLEN STATUS CONTENTS LOGGING FOR EXTENT_MAN
> ALLOCATIO PLU SEGMEN DEF_TAB_
> ------------ ---------- --------- --------- --------- --- ----------
> --------- --- ------ --------
> RETENTION BIG
> ----------- ---
> TEMP 32768 1048576
> 1048576 1
> 0 1048576 *ONLINE* TEMPORARY NOLOGGING NO *LOCAL *
> UNIFORM NO MANUAL DISABLED
> NOT APPLY NO
Other related posts:
