When I create a repository, BO runs a sql script to create the tables and indexes. Is there a way I can specify the Tablespace for the tables and indexes. There is a sql file under DataAccess<DBType>\ directory, which will be executed while creation of repository. We can modify the sql script, but that will be a lot of work. Is there any simple way, we simply specify the tablespace for tables and indexes.
Vasan,
If you plan is to put BO tables & indexes in one specific default tablespace , then probably you can achieve that by associating default tablespace for the database user. In that case all tables and indexes for that user will go to that tablespace unless specifically mentioned in the script.
Abhijit
You wrote - "
When I create a repository, BO runs a sql script to create the tables and indexes. Is there a way I can specify the Tablespace for the tables and indexes. There is a sql file under DataAccess<DBType>\ directory, which will be executed while creation of repository. We can modify the sql script, but that will be a lot of work. Is there any simple way, we simply specify the tablespace for tables and indexes."
Vasan,
If you plan is to put BO tables & indexes in one specific default tablespace , then probably you can achieve that by associating default tablespace for the database user. In that case all tables and indexes for that user will go to that tablespace unless specifically mentioned in the script.
Abhijit
You wrote - "
When I create a repository, BO runs a sql script to create the tables and indexes. Is there a way I can specify the Tablespace for the tables and indexes. There is a sql file under DataAccess<DBType>\ directory, which will be executed while creation of repository. We can modify the sql script, but that will be a lot of work. Is there any simple way, we simply specify the tablespace for tables and indexes."
******************************************************************************* Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Ernst & Young LLP
You will have to make modifications into the SQL script file if you want the indexes to go into another tablespace ( and not get clubbed into the data tablespace ).
Specifying a default tablespace at user creation time will put both table data and its indexes into the default. OR
have another script file for indexes.
After the tables are created into its default space, alter the user to default to the index tablespace and then run the index script ( if you do not want to modify the index script to include the index tablespace name ). Then switch it back to the default tablespace.
My client currently has BusinessObjects 4.1.5 installed on 6 sites. = There are only 2 or 3 users on each site.
Each site has a identical copy of an Oracle 8 database, and has an = identical universe. None of the databases are linked in anyway.
At the moment there is no repository in place and all universe/document = distribution is done within the file system and are held locally.
I have been tasked with creating a standard environment using a = repository.
Question 1
Do I need a single repository that resides within just one of the = databases ? If so which one ? or does it matter ?
Question 2
Can a different connection (i.e. different database) be attached in some = way to a username ? Otherwise when a user connection wont the link refer = to the database the repository resides on ?
Question 3
Finally a DAS question: Is it possible to run the DAS on a users desktop = ? In this situation there would be few other conflicting resources, the = DAS would primarily be used to automate report processing.