Re: connect with internal user in oracle 8.0.5

On Dec 30, 2:49 pm, chijar <chi..._at_gmail.com> wrote:
> On 21 dic, 18:20, joel garry <joel-ga..._at_home.com> wrote:
>
>
>
>
>
> > On Dec 21, 12:00 pm, Frank van Bortel <frank.van.bor..._at_gmail.com>
> > wrote:
>
> > >chijarwrote:
> > > > On 20 dic, 18:37, joel garry <joel-ga..._at_home.com> wrote:
> > > >> On Dec 20, 2:15 pm,chijar<chi..._at_gmail.com> wrote:
>
> > > >>> dear all,
> > > >>> iconnectthrough svrmgr30 but it shows me an error:
> > > >>> ORA-12203: TNS:no se ha podido conectar con el destino
> > > >>> SVRMGR>
> > > >>> SVRMGR>connectinternal
> > > >>> Clave:
> > > >>> ORA-12203: TNS:no se ha podido conectar con el destino
> > > >>> SVRMGR>connectinternal
> > > >>> Clave:
> > > >>> ORA-12203: TNS:no se ha podido conectar con el destino
> > > >>> SVRMGR>
> > > >>> i put "oracle" and "manager" in clave field but it seems the same
> > > >>> error.
> > > >>> i had set ORACLE_SID=SERVICE but didn't function. shows the same
> > > >>> error, or i must to restart the service ?
> > > >>> oracle std 8.0.5
> > > >>> windows 2000 server
> > > >>> thanks again
> > > >>> cesar.
> > > >> $ oerr ora 12203
> > > >> 12203, 00000, "TNS:unable toconnectto destination"
> > > >> // *Cause: Invalid TNS address supplied or destination is not
> > > >> listening.
> > > >> // This error can also occur because of underlying network transport
> > > >> // problems.
> > > >> // *Action: Verify that the service name you entered on the command
> > > >> line
> > > >> // was correct. Ensure that the listener is running at the remote node
> > > >> and
> > > >> // that the ADDRESS parameters specified in TNSNAMES.ORA are correct.
> > > >> // Finally, check that all Interchanges needed to make the connection
> > > >> are
> > > >> // up and running.
>
> > > >> OK, you perhaps want to be doing this locally?  Please display your
> > > >> entire environment, it is likely that you have something set wrong,
> > > >> either pointing to the wrong home or TWO_TASK is overriding something,
> > > >> or the home is not in the path.  Let's see your tnsnames.ora while you
> > > >> are at it.
>
> > > >> ORACLE_SID=SERVICE?  Your instance is named SERVICE?  Sure it's not
> > > >> something like ORCL?
>
> > > >> You may simply need to use oradim to delete and recreate the service.
> > > >> It's been too long, but I seem to recall situations where this would
> > > >> fix things.
>
> > > >> Obadvice: 8.0.5!?@#$@!!!
>
> > > >> jg
> > > >> --
> > > >> @home.com is bogus.http://www.wired.com/gadgets/gadgetreviews/multimedia/2007/12/YE_Vapo...de la cita -
>
> > > >> - Mostrar texto de la cita -
>
> > > > well..
> > > > After that situation i could connect locally but with SYS.
> > > > The error was that i connect through terminal server client to my
> > > > oracle db server. when i connect in front of oracle db server i can
> > > > connect but in this way:
>
> > > > **********************************************************************
> > > > C:\Documents and Settings\Administrador>svrmgr30
>
> > > > Oracle Server Manager Release 3.0.5.0.0 - Production
>
> > > > (c) Copyright 1997, Oracle Corporation. Todos los derechos reservados.
>
> > > > Oracle8 Release 8.0.5.0.0 - Production
> > > > PL/SQL Release 8.0.5.0.0 - Production
>
> > > > SVRMGR> CONNECT
> > > > Nombre de Usuario: SYS AS SYSDBA
> > > > Clave:
> > > > Conectado.
> > > > ***********************************************************************
>
> > > > but when i try to connect with internal, i can't, do you know what is
> > > > default password of that? i put "oracle" and "manager" but it shows
> > > > "invalid passsword, logon denied"
>
> > > > thanks again.
>
> > > Because internal was invented with 8i - you're even before that.
> > > Any reason you're not on the terminal version of Oracle 8.0?
> > > --
> > > Regards,
> > > Frank van Bortel
>
> > > Top-posting is one way to shut me up...
>
> > ???
>
> > "The following methods for authenticating database administrators
> > replace the CONNECT INTERNAL syntax provided with earlier
> > versions of the Oracle7 Server (CONNECT INTERNAL continues to be
> > supported for backwards compatibility only):
> > * operating system authentication
> > * password files" -http://download.oracle.com/docs/pdf/A32535_1.pdf
> > Oracle7 Server Administrator's
> > Guide
>
> > Anyways,  I think Ed got it with the terminal services thing that
> > seems to be in a black hole in my brain.
>
> > jg
> > --
> > @home.com is bogus.http://www.sciencemag.org/sciext/btoy2007/-Ocultar texto de la cita -
>
> > - Mostrar texto de la cita -
>
> Thanks for your asnwers my friends, yes, through Terminal server i
> can't connect by neither way.
> But when i connect in server console, it was good. but there is a
> problem... because i can connect in this way:
> - SVRMGR30
> - CONNECT INTERNAL
> (and it shows me that iws wrong password/user)
>
> i put:
> - oracle
> - manager
>
> do you know what is the default password in order to connect in this
> way?
>
> thabks- Hide quoted text -
>
> - Show quoted text -

Oracle has never provided, by default, an 'oracle' database user. That account is usually used in Unix installations at the O/S level. And, if you're using CONNECT INTERNAL that is all you should need as INTERNAL is the equivalent of SYS as SYSDBA; entering any other username/password is unnecessary if this is truly considered a local connection. Besides, any installation of Oracle still using default passwords for the SYS and SYSTEM users either needs to change those passwords immediately or close up shop (in my opinion) as they are simply begging for a hacker/cracker to attack their database.

You've been provided options with this Terminal Services setup you're using. I suggest you read them again and try using what you've been told.

David Fitzjarrell Received on Mon Dec 31 2007 - 08:44:19 CST