Lyle, you have to restart the listener in order for changes in the ora files to 
take effect.
 
Regards,

Nicky Madjarov
phone: 973-202-4278
Find out how to bust your AR System performance @
http://www.SpeedUpARS.com
  ----- Original Message ----- 
  From: Lyle Taylor 
  Newsgroups: public.remedy.arsystem.general
  To: [email protected] 
  Sent: Monday, March 30, 2009 5:27 PM
  Subject: Re: 75 Install and Database Administrator username/password


  ** 
  That doesn't appear to have made any difference.  It still can't connect to 
the database.  I get the same error as before.

   

  Thanks,
  Lyle

   

  From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Grooms, Frederick W
  Sent: Monday, March 30, 2009 1:41 PM
  To: [email protected]
  Subject: Re: 75 Install and Database Administrator username/password

   

  ** 

  Since you say you are trying to use TNSNAMES switch the order of them around 
in the sqlnet.ora file.

    NAMES.DIRECTORY_PATH= (TNSNAMES,LDAP)

   

  This will at least get you past that point in the install.

   

  Fred

   

  From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Lyle Taylor
  Sent: Monday, March 30, 2009 10:56 AM
  To: [email protected]
  Subject: Re: 75 Install and Database Administrator username/password

   

  Sqlnet.ora contatins

   

  NAMES.DIRECTORY_PATH= (LDAP,TNSNAMES)

   

  Thanks,
  Lyle

   

  From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Grooms, Frederick W
  Sent: Monday, March 30, 2009 8:01 AM
  To: [email protected]
  Subject: Re: 75 Install and Database Administrator username/password

   

  Check your SQLNET.ORA file for the names.diretory.path to make sure it 
includes TNSNAMES.  

   

  I normally use the following:

  NAMES.DIRECTORY_PATH= (TNSNAMES, LDAP, HOSTNAME)

   

  Fred

   

  From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Lyle Taylor
  Sent: Friday, March 27, 2009 6:31 PM
  To: [email protected]
  Subject: Re: 75 Install and Database Administrator username/password

   

  I took a look at the installation log files, and it looks like it's actually 
not able to connect to the database to start with, so it probably thinks it 
needs to create a new schema, and that's why it's asking for the db 
administrator username/password.  This is what I'm seeing in the log file:

   

  ORA-12505, TNS:listener does not currently know of SID given in connect 
descriptor

  The Connection descriptor used by the client was

  A036:1601:A036

   

  I can tnsping A036 fine.  I've also created a tnsnames.ora file for it, just 
in case it doesn't like ldap, but based on what I see here, it kind of looks 
like it's not even trying to actually look up the service in ldap or tnsnames.  
It looks like it's just going straight to the server and port and passing it 
this connect string, or something like that.  The connect string appears to be 
in this format:

   

  <server>:<port>:<db instance>

   

  Any ideas?

   

  Thanks,
  Lyle

   

    ----- Original Message ----- 

    From: Lyle Taylor 

    Newsgroups: public.remedy.arsystem.general

    To: [email protected] 

    Sent: Friday, March 27, 2009 1:21 PM

    Subject: 75 Install and Database Administrator username/password

     

    Hi again all,

     

    My experience with past installers was that if you were creating a new 
schema (for Oracle at least) from within the installer, it would prompt your 
for the database administrator username and password, but if you already had a 
schema, it would instead ask you if you want to overwrite, upgrade or share the 
database.  For 7.5, our DBA has created a new schema for us to install into, 
and in the 7.5 installer, I have entered the server, port and schema login 
information and then moved forward.  A couple screens later, it then asks me 
for the database administrator username and password.  Does the 7.5 installer 
_always_ ask for this, or does this mean that it may not be able to connect to 
the database using the information previously provided, causing it to think 
that we're creating a fresh new schema?

     

    Note that one thing we did not do was create a tnsnames entry for the 
database, as we are using LDAP.  We did, however, create a DNS alias in 
/etc/hosts that cause our database name to resolve to the first host in our 
RAC.  Is a TNSNAMES entry absolutely essential?

     

    Let me know if you need any further information.

     

    Thanks,

    Lyle

   

   

  __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ 



  NOTICE: This email message is for the sole use of the intended recipient(s) 
and may contain confidential and privileged information. Any unauthorized 
review, use, disclosure or distribution is prohibited. If you are not the 
intended recipient, please contact the sender by reply email and destroy all 
copies of the original message.

  __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"

Reply via email to