Yes you can create it in your own tablespace. You need to include the
“create tablespace” stmt. before creating the table and prefix the table
name(s) with the tablespace name. You are probably aware that the DB name
also need to be substituted.
-Sai
Nandhini Sundararajan wrote:
Is there a way to set the tablespace under which the BO should have its
repository tables??? By default it creates them under system
tablespace
which we wanted to have in a different tablespace…
In a message dated 99-03-15 17:00:47 EST, you write:
Is there a way to set the tablespace under which the BO should have its
repository tables??? By default it creates them under system
tablespace
which we wanted to have in a different tablespace…
It depends on the database. For Oracle, the DBA must set up the “owner” of the
tables. That user can be adjusted so that the default tablespace is any
available tablespace. If memory serves, the syntax is something like:
alter user repo_owner default tablespace tablespace name
or something along those lines. For other RDBMS’s the syntax may be different.
In a message dated 99-03-15 17:54:31 EST, you write:
Is there a way to have the BO security files (obj,ds_ls,unv files) under a
different tablespace other than the SYSTEM tablespace??? I could not find
anyway changing this setting in BO.
Regards
Nandhini
It depends on the database. For Oracle, the DBA must set up the “owner” of
the
tables. That user can be adjusted so that the default tablespace is any
available tablespace. If memory serves, the syntax is something like:
alter user repo_owner default tablespace tablespace name
or something along those lines. For other RDBMS’s the syntax may be
different.
You cannot configure this under BO. Your DBA has to set this up when creating
the user that will be used to create the repository tables. If you create a
user, say “BOREP” to own the repository tables, then here are some sample sql
scripts that would work for Oracle. It assumes that there is a tablespace
called “tools” that is available for production systems, and one called
temp_data for temporary storage. (It’s an excellent idea to separate the two.)
create user borep identified by borep
grant connect, resource to borep
alter user borep default tablespace tools
alter user borep temporary tablespace temp_data
If these scripts are run to create the user BOREP, then when you use the
Supervisor application to create the repository tables, they will be
automatically placed in the default tablespace for BOREP, which will be TOOLS.
Nandhini wrote:
Is there a way to set the tablespace under which the BO should have its
repository tables??? By default it creates them under system
tablespace
which we wanted to have in a different tablespace…