the real DBAs aren't around for a few days, so rather than
shoot myself in a tender spot, i thought i'd ask first.

what docs i can find say that the syntax is:

DROP TABLESPACE FOO

seems simple enough, except that the other side is

CREATE TABLESPACE FOO IN BARx

in this shop, BAR is referred to as a database (not sure
that's what DB2 thinks it is). there are multiple
FOO tablespaces spread over many BAR1, BAR2, etc. so,
how does DB2 know which FOO to drop??

thanks,
robert

"robert" <gnuoytr@rcn.com> wrote in message
news:da3c2186.0402131256.25b614c2@posting.google.c om...
> the real DBAs aren't around for a few days, so rather than
> shoot myself in a tender spot, i thought i'd ask first.
>
> what docs i can find say that the syntax is:
>
> DROP TABLESPACE FOO
>
> seems simple enough, except that the other side is
>
> CREATE TABLESPACE FOO IN BARx
>
> in this shop, BAR is referred to as a database (not sure
> that's what DB2 thinks it is). there are multiple
> FOO tablespaces spread over many BAR1, BAR2, etc. so,
> how does DB2 know which FOO to drop??
>
> thanks,
> robert

You need the SQL Reference manual. You can download the PDF version from the
IBM website.

DROP TABLESPACE BARX.FOO

Here is the stuff from the manual:

DROP TABLESPACE database-name.table-space-name

Identifies the table space to be dropped. The name must identify a table
space
that exists at the current server. The database name must not be DSNDB06.
Omission of the database name is an implicit specification of DSNDB04.
Whenever a table space is directly or indirectly dropped, all the tables in
the
table space are also dropped. The name of a dropped table space cannot be
reused until a commit operation is performed.

A table space in a TEMP database can be dropped only if it does not contain
an active declared temporary table. A LOB table space can be dropped only if
it
does not contain an auxiliary table.

Whenever a base table space that contains tables with LOB columns is
dropped, all the auxiliary tables and indexes on those auxiliary tables that
are
associated with the base table space are also dropped.

"Mark A" <ma@switchboard.net> wrote in message news:<kcbXb.166$M93.33585@news.uswest.net>...

i had looked up the syntax in our local copy of
the 390/V6 manual.

i'll get a new copy of the pdf.

thanks,
robert

> "robert" <gnuoytr@rcn.com> wrote in message
> news:da3c2186.0402131256.25b614c2@posting.google.c om...
> > the real DBAs aren't around for a few days, so rather than
> > shoot myself in a tender spot, i thought i'd ask first.
> >
> > what docs i can find say that the syntax is:
> >
> > DROP TABLESPACE FOO
> >
> > seems simple enough, except that the other side is
> >
> > CREATE TABLESPACE FOO IN BARx
> >
> > in this shop, BAR is referred to as a database (not sure
> > that's what DB2 thinks it is). there are multiple
> > FOO tablespaces spread over many BAR1, BAR2, etc. so,
> > how does DB2 know which FOO to drop??
> >
> > thanks,
> > robert
>
> You need the SQL Reference manual. You can download the PDF version from the
> IBM website.
>
> DROP TABLESPACE BARX.FOO
>
> Here is the stuff from the manual:
>
> DROP TABLESPACE database-name.table-space-name
>
> Identifies the table space to be dropped. The name must identify a table
> space
> that exists at the current server. The database name must not be DSNDB06.
> Omission of the database name is an implicit specification of DSNDB04.
> Whenever a table space is directly or indirectly dropped, all the tables in
> the
> table space are also dropped. The name of a dropped table space cannot be
> reused until a commit operation is performed.
>
> A table space in a TEMP database can be dropped only if it does not contain
> an active declared temporary table. A LOB table space can be dropped only if
> it
> does not contain an auxiliary table.
>
> Whenever a base table space that contains tables with LOB columns is
> dropped, all the auxiliary tables and indexes on those auxiliary tables that
> are
> associated with the base table space are also dropped.