Re: tablespace problem with standby database

You may wish to create another separate temporary tablespace in the primary db for use by your read-only reporting user on the standby. Assign the reporting user the new temporary tablespace as its temporary tablespace on the primary. When all the archive logs are applied to the standby, your reporting user should have all the temporary tablespace it needs.

I hope these ideas help.

Mike

"clueless" <ro_cright_at_hotmail.com> wrote in message news:TW679.8211$V21.159030_at_news...
> oracle 8.1.7.4 on w2k, dell box 4 processors
>
> I have a standby database that I use for reporting purposes. The standby
is
> in NON-managed mode and remotely hosted.
>
> Several reports are run against the standby database that is open in read
> only mode and some of the queries cause a lot of sorting, etc. Oracle
> attempts to increase the size of the TEMP tablespace to accommodate the
> sorting and fails because the database is in read only mode.
>
> I want to increase the size of the TEMP tablespace in the production
> database then migrate that change to the standby via the ARLogs. The
> problem I have is that I cannot drop the TEMP tablespace and re-create it
> and set the initial size higher than it is. I see a lot of information on
> the web concerning reducing the size of an existing tablespace but nothing
> on increasing the size of an existing tablepsace forcing it to increase
the
> size immediately.
>
> The existing temp tablespace uses 2 datafiles tmp1(2 gig, .008% used,
> autoextend) and tmp2(11gig 9%used, autoextend).
> The tablespace itself, temp, is 12gig and at 9% used and the extents are
> unlimited.
>
> I will continue looking into this issue today and will post the solution
> if/when I find it.
>
> Cheers
>
>
Received on Fri Aug 16 2002 - 12:03:20 CDT