Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.tools -> Re: Portal 3.0 EA refuses to connect to oracle Server 8.1.6.0.0
Hi, I just installed Portal 3.0 last night. I'm having fun- this could be kewl : ) Anyway I don't see any mention of your starting the database listener!?
My database is on Linux, but I'm sure NT must be similar. I think you can just run this from command. I don't think it would be a Service...
[oracle_at_frodo oracle]$ lsnrctl start
The 'lsnrctl status' is a bit misleading if the listener is not running. But after you start it you should see:
[oracle_at_frodo oracle]$ lsnrctl status
LSNRCTL for Linux: Version 8.1.6.0.0 - Production on 17-OCT-2000 22:36:46
(c) Copyright 1998, 1999, Oracle Corporation. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC))) STATUS of
the LISTENER ------------------------ Alias LISTENER Version TNSLSNR for Linux: Version 8.1.6.0.0 - Production Start Date 17-OCT-2000 21:18:58 Uptime 0 days 1 hr. 17 min. 47 sec Trace Level off Security OFF SNMP OFFListener Parameter File
Hope this helps,
Allison
In article <8sh8t0$vuv$03$1_at_news.t-online.com>,
"Wolf Hermann" <w.hermann_at_nit-consultants.de> wrote:
> Problem: Portal 3.0 EA refuses to connect to the database regardless of DAD
> settings.
> Setup:
> NT 4.0 SP6a
> 8i R2 (8.1.6.0.0)
> Portal 3.0 EA
>
> Steps to reproduce:
> 1) Install 8i R2 under NT 4.0 SP 6a in a new home (OraHome81) on
> <Drive1>\Oracle\Ora81.
> 2) Configure TNSNames, test local and tns connections using SQL*Plus.
> 3) Install Portal 3.0 in a seperate home (OraHomeWeb) on
> <Drive1>\Oracle\OraWeb.
> 4) Configure TNSNames, test local and tns connections using SQL*Plus.
> 5) Make sure the Oracle Home is set to OraHomeWeb.
> 6) Make sure the web listener is running and check the DAD's in the gateway.
> 7) In IE.5.5 enter the following URL:
> http://<myserver>/pls/portal30
>
> Results:
> Client Logon Failed with errorcode:604
>
> Error-Code:604
> Error TimeStamp:Tue, 19 Sep 2000 16:55:53 GMT
> Database Log In Failed
> TNS is unable to connect to destination. Invalid TNS address supplied or
> destination is not listening. This error can also occur because of
> underlying network transport problems.
>
> Verify that the TNS name in the connectstring entry of the DAD for this URL
> is valid and the database listener is running.
>
> Notes: No matter how I change the connection DAD it makes no difference
> although SQL*Plus can connect without a alias or with one. I've tried no
> alias, a simple alias (webdb), a fully qualified alias (webdb.mydomain.com),
> and the direct string(<myserver>:<port>:<sid>). All fail.
>
> Any help is appreciated.
>
>
Sent via Deja.com http://www.deja.com/
Before you buy.
Received on Tue Oct 17 2000 - 21:39:46 CDT
![]() |
![]() |