BusinessObjects Board

Unable to schedule Information space

other Explorer
#1

Hi,

We are using Polestar XI 3.1 .
When I am trying to schedule an information space in test environment I am getting the error given below.

" FAILED TO UPDATE THE INFORMATION SPACE
Internal error.
com.businessobjects.datadiscovery.persistence.exceptions.PersistenceException: com.businessobjects.datadiscovery.persistence.exceptions.PersistenceException: com.businessobjects.repository.RepositoryException: Trying to update more than one object: where SI_PROGID = ‘CrystalEnterprise.DataDiscovery’ where SI_CONTENT_TYPE = ‘com.businessobjects.datadiscovery.core.model.IExplorationSpace’ where SI_CONTENT_ID = ‘9e5dfe20-82a3-4470-b1f4-1f349650adb7’ "

In DEV environment, I am able to schedule the same one.

In both DEV & TEST environments I am having the Admin rights.

Any help on this would be appriciated…

Thanks,
Vijayakrishna

vijayakrishna.bos (BOB member since 2007-08-29)

#2

Hi,

Goto Universe Parameters-> Control tab

Uncheck Limit size of result set to:

Click the Indexing button.

Now you will get green button.

:smiley: :smiley:

pardhu (BOB member since 2011-08-29)

#3

[quote:442ed504bb=“vijayakrishna.bos”]Hi,

We are using Polestar XI 3.1 .
When I am trying to schedule an information space in test environment I am getting the error given below.

" FAILED TO UPDATE THE INFORMATION SPACE
Internal error.
com.businessobjects.datadiscovery.persistence.exceptions.PersistenceException: com.businessobjects.datadiscovery.persistence.exceptions.PersistenceException: com.businessobjects.repository.RepositoryException: Trying to update more than one object: where SI_PROGID = ‘CrystalEnterprise.DataDiscovery’ where SI_CONTENT_TYPE = ‘com.businessobjects.datadiscovery.core.model.IExplorationSpace’ where SI_CONTENT_ID = ‘9e5dfe20-82a3-4470-b1f4-1f349650adb7’ "

In DEV environment, I am able to schedule the same one.

In both DEV & TEST environments I am having the Admin rights.

Any help on this would be appriciated…

Thanks,
Vijayakrishna
[/quote]

Getting similar type of error message when attempting to index.

Were you able to recover or find out what the issue you were having in BOE?

toscajo (BOB member since 2002-09-04)

#4

Okay, got the answer… not sure I like it but for anyone out there who suffers this same issue here is what you have to do.

Make a copy of the Information Space that has the problem.
Delete the original Information Space.

The copy will index without a problem.

Done.

toscajo (BOB member since 2002-09-04)