EMCA Fails With Error "ORA-00955: name is already used by an existing object" For SYNONYM MGMT_AVAILABILITY (Doc ID 470246.1)
Information in this document applies to any platform.
***Checked for relevance on 27-Oct-2011***
Drop the Repository using RepManager
If above RepManager fails with conflicts for any other SYNONYM then manually drop the DBConsole repository and objects referring to Note 278100.1 How To Drop, Create And Recreate DB Control In A 10g Database
Fileload fails with ORA-00955: name is already used by an existing object (Doc ID 801963.1)
Information in this document applies to any platform.
Fact:
Auto Purge Enabled is set to "Yes"
File Version Keep is set to "0"
Steps To Reproduce:
1. Login to JavaClient as admin
2. Goto Admin tab > System Settings > Viewers & Files
3. Make configuration as below and Save changes:
- Auto Purge Enabled = Yes
- File Version Keep = 0
4. Create index file to load files. (File can be URL. Create about 10 lines)
5. Login to JavaClient with user that have Fileload privilege
6. Goto Tools > Fileload
7. Set Index File
8. Change "Number Of Dedicated Threads" to a number greater than 1. (i.e. 10)
9. Set Log File Directory and OK
To workaround the issue, please follow below instructions:
1. Login to JavaClient as admin
2. Goto Admin tab > System Settings > Viewers & Files
3. Change File Version Keep to "1" and Save
4. Run Fileload.
5. After Fileload is completed, change back File Version Keep to "0".
Applies to:
Enterprise Manager for Oracle Database - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]Information in this document applies to any platform.
***Checked for relevance on 27-Oct-2011***
Symptoms
While recreating the database control in 11g database, it fails as below errors in emca_repos_create_timestamp.log fileDec 9, 2007 10:41:26 AM oracle.sysman.emcp.EMReposConfig createRepository
CONFIG: ORA-00955: name is already used by an existing object
oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-00955: name is already used by an existing object
at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeImpl(SQLEngine.java:1500)
at oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeScript(SQLEngine.java:874)
at oracle.sysman.assistants.util.sqlEngine.SQLPlusEngine.executeScript(SQLPlusEngine.java:270)
at oracle.sysman.assistants.util.sqlEngine.SQLPlusEngine.executeScript(SQLPlusEngine.java:311)
at oracle.sysman.emcp.EMReposConfig.createRepository(EMReposConfig.java:492)
at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:218)
at oracle.sysman.emcp.EMReposConfig.invoke(EMReposConfig.java:147)
at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:221)
at oracle.sysman.emcp.EMConfigAssistant.invokeEMCA(EMConfigAssistant.java:534)
at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:1214)
at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:518)
at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:467)
Dec 9, 2007 10:41:26 AM oracle.sysman.emcp.EMReposConfig invoke
SEVERE: Error creating the repositoryCREATE PUBLIC SYNONYM MGMT_AVAILABILITY FOR MGMT_AVAILABILITY
*
ERROR at line 1:
ORA-00955: name is already used by an existing objectCause
Related Bug 6111734 EMCA THROWS CONFIG: ORA-00955 CREATE PUBLIC SYNONYM MGMT_AVAILABILITY FOR MGMT_ASolution
As a workaround,Drop the Repository using RepManager
<ORACLE_HOME>/sysman/admin/emdrep/bin/RepManager <hostname> <listener_port> <sid> -action drop
Note : This will not remove the configuration
files, but only the repository related objects from the database.Also,
the database will be put in Quiescing mode when RepManager is ran.
Refer Note 375946.1 Running EMCA Results in Database quiesce And No New Connections or Operations Can Be Performed During the DB Control Repository Creation
Refer Note 375946.1 Running EMCA Results in Database quiesce And No New Connections or Operations Can Be Performed During the DB Control Repository Creation
If above RepManager fails with conflicts for any other SYNONYM then manually drop the DBConsole repository and objects referring to Note 278100.1 How To Drop, Create And Recreate DB Control In A 10g Database
Fileload fails with ORA-00955: name is already used by an existing object (Doc ID 801963.1)
Applies to:
Oracle Agile PLM Framework - Version 9.2.2.4 to 9.3.0.0 [Release 9.2.0.0 to 9.3.0.0]Information in this document applies to any platform.
Symptoms
Fileload fails with ORA-00955: name is already used by an existing object when running by multithreaded mode.Fact:
Auto Purge Enabled is set to "Yes"
File Version Keep is set to "0"
Steps To Reproduce:
1. Login to JavaClient as admin
2. Goto Admin tab > System Settings > Viewers & Files
3. Make configuration as below and Save changes:
- Auto Purge Enabled = Yes
- File Version Keep = 0
4. Create index file to load files. (File can be URL. Create about 10 lines)
5. Login to JavaClient with user that have Fileload privilege
6. Goto Tools > Fileload
7. Set Index File
8. Change "Number Of Dedicated Threads" to a number greater than 1. (i.e. 10)
9. Set Log File Directory and OK
Cause
Code bug Bug 8413389; Root cause:purging involved creation of temporary table.the name for temporary table was not threadsafeSolution
Upgrade to Agile PLM 9.3.0.1 or above.To workaround the issue, please follow below instructions:
1. Login to JavaClient as admin
2. Goto Admin tab > System Settings > Viewers & Files
3. Change File Version Keep to "1" and Save
4. Run Fileload.
5. After Fileload is completed, change back File Version Keep to "0".
No comments:
Post a Comment