 | |
Deregister a Metadata repository from a (non existent) OID
comp.databases.oracle.misc comp.databases.oracle.misc
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Deregister a Metadata repository from a (non existent) OID -
11-21-2007
, 02:32 AM
#2
| |||
| |||
|
|
Does anyone know how to solve this: We have a metadata repository on a database server (10g rel 2), and a separate OID server (AS10g rel 2 on SLES 9.3 64 bit) Unfortunately, the OID server 'died'. No backup available (don't blame me.... some people just don't backup development environments it seems) So with the old repository intact, we want to install a new OID server. But Repca only wants to deregister the old OID if and when it can connect to it (which is technically correct, for you actually deregister the Metadata Repository from OID). But it's not there anymore.... BTW: I built a testcase on two different servers to deregister an EXISTING oid server. Repca refuses to deregister, because: the repository is used by OID. So what's the use of repca deregister anyway? It won't deregister non-existent nor existent OID's..... Shakespeare |
Shakespeare
#3
| |||
| |||
|
|
"shakespeare" <what... (AT) xs4all (DOT) nl> schreef in berichtnews:4743ed28$0$244$e4fe514c (AT) news (DOT) xs4all.nl... Does anyone know how to solve this: We have a metadata repository on a database server (10g rel 2), and a separate OID server (AS10g rel 2 on SLES 9.3 64 bit) Unfortunately, the OID server 'died'. No backup available (don't blame me.... some people just don't backup development environments it seems) So with the old repository intact, we want to install a new OID server. But Repca only wants to deregister the old OID if and when it can connect to it (which is technically correct, for you actually deregister the Metadata Repository from OID). But it's not there anymore.... BTW: I built a testcase on two different servers to deregister an EXISTING oid server. Repca refuses to deregister, because: the repository is used by OID. So what's the use of repca deregister anyway? It won't deregister non-existent nor existent OID's..... Shakespeare Solved.... deconfig.pl did the job.... Shakespeare |
delete cn=<your_sid>, cn=OracleContext,dc=<your base dn>
from the OID.
Use a program that actually supports cascaded deletes, such as
LdapAdmin (http://ldapadmin.sourceforge.net/), or OIDManager
if you're slightly masochistic
#4
| |||
| |||
|
|
On 21 nov, 12:01, "shakespeare" <what... (AT) xs4all (DOT) nl> wrote: "shakespeare" <what... (AT) xs4all (DOT) nl> schreef in berichtnews:4743ed28$0$244$e4fe514c (AT) news (DOT) xs4all.nl... Does anyone know how to solve this: We have a metadata repository on a database server (10g rel 2), and a separate OID server (AS10g rel 2 on SLES 9.3 64 bit) Unfortunately, the OID server 'died'. No backup available (don't blame me.... some people just don't backup development environments it seems) So with the old repository intact, we want to install a new OID server. But Repca only wants to deregister the old OID if and when it can connect to it (which is technically correct, for you actually deregister the Metadata Repository from OID). But it's not there anymore.... BTW: I built a testcase on two different servers to deregister an EXISTING oid server. Repca refuses to deregister, because: the repository is used by OID. So what's the use of repca deregister anyway? It won't deregister non-existent nor existent OID's..... Shakespeare Solved.... deconfig.pl did the job.... Shakespeare Another option: delete cn=<your_sid>, cn=OracleContext,dc=<your base dn from the OID. Use a program that actually supports cascaded deletes, such as LdapAdmin (http://ldapadmin.sourceforge.net/), or OIDManager if you're slightly masochistic |
thank you for your suggestion. This will only work when OID is still alive,
so only in my test case. When the OID server is dead and gone, it's not
possible to connect through LDAP anymore. I have made a Metalink SR on this,
will follow up.
Shakespeare
#5
| |||
| |||
|
|
"Frank van Bortel" <frank.van.bortel (AT) gmail (DOT) com> schreef in bericht Another option: delete cn=<your_sid>, cn=OracleContext,dc=<your base dn from the OID. Use a program that actually supports cascaded deletes, such as LdapAdmin (http://ldapadmin.sourceforge.net/), or OIDManager if you're slightly masochistic Frank, thank you for your suggestion. This will only work when OID is still alive, so only in my test case. When the OID server is dead and gone, it's not possible to connect through LDAP anymore. I have made a Metalink SR on this, will follow up. Shakespeare |
Trying to figure out how else to approach this... As far as I can
figure it out, registering does the following:
- adjusts rdbms_server_dn (and never restarts the instance...)
- adds some entries in OID
- creates a wallet (which is not used?)
The situation you're in is that your OID is gone, so
no worries about any entries. Just reset rdbms_server_dn
to an empty string, delete, or move, the wallet, and
you should be done...
For purists, you might want to delete ldap.ora, and revert
sqlnet.ora, but these only influence networking.
Somewhere along the line there must be another entry.
--
Regards,
Frank van Bortel
Top-posting is one way to shut me up...
#6
| |||
| |||
|
|
shakespeare wrote: "Frank van Bortel" <frank.van.bortel (AT) gmail (DOT) com> schreef in bericht Another option: delete cn=<your_sid>, cn=OracleContext,dc=<your base dn from the OID. Use a program that actually supports cascaded deletes, such as LdapAdmin (http://ldapadmin.sourceforge.net/), or OIDManager if you're slightly masochistic Frank, thank you for your suggestion. This will only work when OID is still alive, so only in my test case. When the OID server is dead and gone, it's not possible to connect through LDAP anymore. I have made a Metalink SR on this, will follow up. Shakespeare Yup, realized that the day after I posted... Sorry 'bout that. Trying to figure out how else to approach this... As far as I can figure it out, registering does the following: - adjusts rdbms_server_dn (and never restarts the instance...) - adds some entries in OID - creates a wallet (which is not used?) The situation you're in is that your OID is gone, so no worries about any entries. Just reset rdbms_server_dn to an empty string, delete, or move, the wallet, and you should be done... For purists, you might want to delete ldap.ora, and revert sqlnet.ora, but these only influence networking. Somewhere along the line there must be another entry. -- Regards, Frank van Bortel Top-posting is one way to shut me up... |
re-installing Metadata Repository. That's about the same the doc's say as
well. Which seems to be ackward when someome wants to move the OID server to
new hardware without recreating the whole repository... But I won't give in
yet, will try some other options.
Shakespeare
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.