Recently upgraded to XI R2 SP2 from SP1 and now I cannot get the CMS
to start. I had the same problem with SP1 but after many Webx hours wth BO we got it started. I never really found out what change was made to get the CMS to start so I am again in the same situation. If anyone fimilar with Sybase can shed some light on getting CMS to start with Sybase I would be greatful.
I tried to use the existing Sybase CMS from SP1 and get the following
error in the event log:
The root server reported an error Initialization Failure. (Reason: The relationship named ‘UserGroup-User’ with id 126 cannot be created because the table requested (‘RELATIONS’) already exists and does not have the correct schema.).
After creating a new Sybase CMS db I get the following event error when attempting to start:
The root server reported an error Initialization Failure. (Reason: Error creating an index for Index InfoObject 0: property SI_GUID of type asciistring (on table CMS_InfoObjects5 column SI_GUID): Sybase error:Column names in each table must be unique. Column name ‘SI_GUID’ in table ‘CMS_InfoObjects5’ is specified more than once.
When I look at the trace log for this start attempt I see error messages
for tring to alter database to add column SI_GUID. the column is already in the db so I am not supprised to get an error. I am supprised to see
that IX is trying to add the column.
I believe I have set all of the appropriate permissions and options. I am actually login as sa so I should be able to do anything.
I would appreciate any ideas or advice. I really do not want to get in volved with BO support again if I can help it. there does not seem they have much XI/Sybase expertise.
Hi,
We are also facing same issue and now we are SP3 (BO XI R2) . Can you suggest how did ou resolved that issue , would be thankful for your advise.Thanks
Before doing anything look into the supported platforms document if the version you are using is mentioned in it.
We always had issues creating CMS with Sybase.
Also try giving full rights to the user building those CMS repository tables
"The database needs to be configured with at least an 8K page size. This is a system-wide parameter that you cannot change this for an existing database server. Consult your Database Administrator as you need to install another server or migrate the existing one.
Once you have done this, create a database for your CMS, and an account to use for the CMS. DO NOT set this account as the owner of the database as that will not work. Leave the owner of the database as an administrator type account. Open the list of users for that database and add the CMS account that you have just created. Once the user account is added, click Properties > Commands tab > Create Table option."
There are several articles The database needs to be configured with at least an 8K page size. This is a system-wide parameter that you cannot change this for an existing database server. Consult your Database Administrator as you need to install another server or migrate the existing one.
Once you have done this, create a database for your CMS, and an account to use for the CMS. DO NOT set this account as the owner of the database as that will not work. Leave the owner of the database as an administrator type account. Open the list of users for that database and add the CMS account that you have just created. Once the user account is added, click Properties > Commands tab > Create Table option."
There are several articles emphasizing the Sybase user can not be the DBO. If you created the CMS database as SA and using SA to create the tables, then you certainly violated that requirement.
(BOB member since 2005-07-18)
(BOB member since 2007-08-01)