You are viewing limited content. For full access, please sign in.

Question

Question

Repository creation error. SQL error: ORA-00955: name is already used by an existing object

asked on June 12, 2015

While creating a new repository with Oracle database we are facing the following error:

 

 

When we checked the event viewer it showed the following details:

"Repository creation error. SQL error: ORA-00955: name is already used by an existing object"

 

How to erase all the traces of the previous repository in the Oracle database?

We are just trying to create a new repository by reusing the old Oracle database. Please note that we have dropped the previous repository schema and all the public synonms owned by the schema.

 

Thanks!

0 0

Answer

SELECTED ANSWER
replied on June 12, 2015

You cannot use a schema where you only have some of the repository tables, it will result in a misconfigured repository. It's probably best that you go through Tech Support so they can double-check your settings.

0 0

Replies

replied on June 12, 2015

If you're trying to use an existing schema that already has Laserfiche tables in it, you want to attach the repository instead. Creating the repository assumes the tables do no exist, hence the error you're seeing.

0 0
replied on June 12, 2015 Show version history

Hi Miruna,

 

We have dropped almost all the tables from the schema. Further, if we try to register an existing repository by pointing to the folder where the repository files are located, we are getting the following error:

 

 

When we checked the event viewer it gave the following information:

 

"Mounting repository 'default' failed.  Please ensure that the Laserfiche Server has the ability to log in to the database used by the repository, and that the repository directory is accessible. Error reading repository GUID"

 

Is there something we are not doing correctly in registering the repository?

 

*Edit: We have dropped the schema entirely and created a new one. But it still gives the same error.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.