Re: rman test restore

On May 29, 11:18 am, cptkirkh <k..._at_scic.com> wrote:
> On May 29, 12:45 pm, Frank van Bortel <frank.van.bor..._at_gmail.com>
> wrote:
>
> > cptkirkh wrote:
> > > Ok with that in mind I have one more question. If theserverI am
> > > using to do a testrestorehas adatabasewith the samenameand if
> > > there is an application on thatserverthat connects to the production
> > > DB will the application be able to connect to the production DB after
> > > I create a DB by the samename?
>
> > Naming has little to do with it (or everything...).
> > As the application connects to the production db, which is
> > on another machine (names....), the application will still
> > connect to the originaldatabaseinstance, not the clone.
>
> > Depends somewhat on how the application connects:
> > - - using jdbc, the connection would be of the form
> > machine_name:listener_port:service_name.
> > - - using Oracle Net, the connection would either be using
> > the same form, or a TNS alias.
>
> > In the first case, the machinenamediffers, so the application
> > will connect to the originaldatabaseinstance.
> > In the seconds case, you either have the first case, or your
> > TNS alias would point to the original machine, causing the
> > application to connect to the originaldatabaseinstance.
>
> > In short: it will connect to the original one, unless you
> > change the way the application connects. You may consider
> > defining duplicate connections - SQL*Net does try all defined
> > connections sequentially, until the connection succeeds (or
> > fails completely, of course)
> > - --
> > Regards,
> > Frank van Bortel
>
>
> Thnaks Frank... after talkign to one of the developers I think I am
> going to move the app and then do the restore.- Hide quoted text -
>

If you have metalink access, a search on: dbid RMAN
may be quite informative. Note: 360962.1 is pretty interesting.

jg

--
@home.com is bogus.
Pocket pacman:  http://www.signonsandiego.com/uniontrib/20070529/news_1b29key.html