| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Tablespace for BPCDB (process choreographer database). |
« View previous topic :: View next topic » |
| Author |
Message
|
| venky |
 Posted: Mon Nov 17, 2008 5:43 pm Post subject: Tablespace for BPCDB (process choreographer database). |
 |
|
Master
Joined: 08 Jul 2003
Posts: 205
|
hi All,
I am in the process of configuring WPS 612 and we have decided to create the database objects manually. While creating the tables and tablespace for BPCDB, I noticed that the scripts have predefined names for tablespaces - however, my Oracle admin team is recommending that we change the names for tablespaces ( to follow their naming convention) - and I am reluctant to do so.
has anyone changed the tablespace names ? does it impact the normal functioning for process server ?
Please share your experiences.
Thanks, V |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Nov 17, 2008 6:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You should not change any of the table names. Tell the oracle DBA team that unless they are willing to rewrite the app they will leave this alone.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| JLRowe |
| Posted: Tue Nov 18, 2008 7:00 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
| fjb_saper wrote: |
You should not change any of the table names. Tell the oracle DBA team that unless they are willing to rewrite the app they will leave this alone.
Have fun |
Don't change the table names!
But, yes you can change the tablespace names, we did this in a 6.0.2 implementation, the BPC container is none the wiser. |
|
| Back to top |
|
|
| dzifchock |
| Posted: Thu Dec 04, 2008 12:11 pm Post subject: |
|
|
Apprentice
Joined: 21 Feb 2007
Posts: 41
|
| We followed the 6.1.2 install and configure guide for oracle databases as far as the schema naming convention, but it gets into a management nightmare using a different tablespace for every schema user. I would suggest generating all of the sql scripts, then editing the sql scripts to have all of the users using a shared tablespace, that way when you need to pop out another environment you can just run all of the sql scripts before doing profile creation, assuming that the dba will allow you to do so. I've did this in 3 environments so far and its made for a pretty easy repeatable process. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
