[4375] in sapr3-soft
Re: Splitting Large Tablespaces (PSAPBTABD) into smaller more manageable parts
daemon@ATHENA.MIT.EDU (Jon Eichelberger)
Sat Nov 13 22:45:08 1999
To: sapr3-soft@MIT.EDU
Date: Sun, 14 Nov 1999 03:44:14 GMT
From: "Jon Eichelberger" <eichelbe@bellatlantic.net>
Message-Id: <01bf2e52$09349460$9078c597@eichelbe>
Hi. R/3 does not care about the names of the tablespaces you use. You can
split up PSAPBTABD into multiple tablespaces by creating one or more new
tablespaces and moving some of the big tables into the new tablespace(s).
I do this all the time. All R/3 cares about is that the tables exist
somewhere, not what the name of the tablespace is. There is something in
R/3 called an application class, and that sometimes has to do with which
tablespace a table goes in (the tablespace names do actually mean
something), but there is no requirement as to where a table goes. You
could create something like tablespace PSAPBTABD_A for some tables and
PSAPBTABD_B for all the others. You might even create a tablespace for
just one large table. You could use Oracle table partitioning, too. If
I'm getting over your head, you should speak with your nearest Oracle DBA.
The bottom line is this: if you took down R/3 and got the DBA to create
some new tablespaces and he/she moved some of your tables into the new
tablespaces, R/3 would not care when you brought it back up and R/3 would
work just fine.
Regards,
Jon
Simon Clayton <simon.clayton@uk.bosch.com> wrote in article
<7ui0f0$853$1@proxy2.fe.internet.bosch.de>...
> Does anyone know how to split large Oracle tablespaces (SAP specific)
into
> smaller more manageable parts?
>
> Cheers
>
> Simon
> BASIS
>
>
>
>
>
