Problems moving from Database 9.2 to 10.2

Hi Greg,

to start isqlplus use "isqlplusctl start".
Port should be 5560.
By the way, i never installed the companion stuff to get
this running.


hth

Torsten

> I just managed to migrate from 9.2 to 10.2 and am
having a few problems.
> The most significant of these is not having access to
ISQLPLUS.  Under
> 9.2,
> you automatically got an apachectl script to start and
stop the Oracle
> HTTP
> server when you installed the database.  Under 10.2, it
is apparently now
> separate under the "companion" component.  I
installed that component and
> tried running "opmnctl startall", which I
understand is the new way of
> starting Oracle HTTP.  When I issue that command, I get
back --
>
> opmnctl:  Starting opmn and all managed processes...
> opmnctl:  opmn start failed
>
> I went to the log files under the same directory path
as the bin where
> opmnctl is located and found the following
>
> ipm.log ->
>
> 06/12/09 11:50:03 [4] Create pm state directory:
>
/u01/app/oracle/product/10.2.0.Commpanion/opmn/logs/states
> 06/12/09 11:50:03 [4] PM state file does not exist:
>
/u01/app/oracle/product/10.2.0.Commpanion/opmn/logs/states/.
opmndat
> 06/12/09 11:50:03 [4] OPMN server ready.  Request
handling enabled.
> 06/12/09 11:50:03 [4] Request 2 Started.  Command:
start
> 06/12/09 11:50:03 [4] Starting Process:
> HTTP_Server~HTTP_Server~HTTP_Server~1 (2001403905:0)
> 06/12/09 11:50:05 [4] Process Alive:
HTTP_Server~HTTP_Server~HTTP_Server~1
> (2001403905:25328)
> 06/12/09 11:50:05 [4] Request 2 Completed. Command:
start
> 06/12/09 13:46:58 [4] PM state directory exists:
>
/u01/app/oracle/product/10.2.0.Commpanion/opmn/logs/states
> 06/12/09 13:46:58 [4] OPMN server ready.  Request
handling enabled.
> 06/12/09 14:13:30 [4] PM state directory exists:
>
/u01/app/oracle/product/10.2.0.Commpanion/opmn/logs/states
> 06/12/09 14:13:30 [4] OPMN server ready.  Request
handling enabled.
>
> ons.log ->
>
> 06/12/09 11:50:03 [4] ONS server initiated
> 06/12/09 13:46:58 [4] ONS server initiated
> 06/12/09 13:46:58 [2] BIND (Address already in use)
> 06/12/09 13:46:58 [2] 127.0.0.1:6113 - listener BIND
failed
> 06/12/09 13:46:58 [4] Listener thread -1268642912:
127.0.0.1:6113 (0x442)
> terminating
> 06/12/09 13:46:58 [1] Local listener terminated
> 06/12/09 14:13:30 [4] ONS server initiated
> 06/12/09 14:13:30 [2] BIND (Address already in use)
> 06/12/09 14:13:30 [2] 127.0.0.1:6113 - listener BIND
failed
> 06/12/09 14:13:30 [4] Listener thread -1268003936:
127.0.0.1:6113 (0x442)
> terminating
> 06/12/09 14:13:30 [1] Local listener terminated
>
> states/p2001403905 ->
>
> standalone
> HTTP_Server
> HTTP_Server
> HTTP_Server
> 2001403905
> 25328
> 1:1
> 2
> 0
> 0
> -
>
/u01/app/oracle/product/10.2.0.Commpanion/opmn/logs/HTTP_Ser
ver~1
>
/u01/app/oracle/product/10.2.0.Commpanion/opmn/logs/HTTP_Ser
ver~1
> portStart
> 7202  http
> 
> 127.0.0.1
> portend
>
> Out of all of that, the only thing that seems to
possibly be indicative of
> an error is the following under the ons.log --
>
> 06/12/09 14:13:30 [2] BIND (Address already in use)
> 06/12/09 14:13:30 [2] 127.0.0.1:6113 - listener BIND
failed
>
> Maybe that is telling me that it's trying to listen on
port 6113 and that
> port is already in use.  What's really confusing is the
following --
>
> During installation of the database, I got a message
that ISQLPLUS would
> be
> using port 5561.  But ISQLPLUS wouldn't have been
installed until I
> installed "companion", right?  After I found
out that ISQLPLUS was
> separate,
> I figured that maybe the port was simply pre-assigned
by database, even
> though the HTTP server wasn't there yet.  But then
ons.log seems to be
> referring to port 6113.  Also, from states/p2001403905,
--
>
> portStart
> 7202  http
>
> 127.0.0.1
> portend
>
> so isn't it saying that it's trying to use port 7202,
or am I misreading
> that?  Things were so much simpler under 9.2.  Is there
anything in this
> information that anyone can see that points directly to
my problem?  If it
> is a port problem, I don't know where I would go to
make that change.
> Under
> 9.2, the ports were embedded right in the apachectl
script itself.  So
> far,
> in my browsing, I haven't been able to find out where
that assignment is
> made under 10.2.  Any help with this greatly
appreciated.
>
> Thanks,
> Greg Wallace
>
>
> --
> To unsubscribe, email: suse-oracle-unsubscribesuse.com
> For additional commands, email: suse-oracle-helpsuse.com
> Please see http://www.suse.com/oracl
e/ before posting
>
>


-- 
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting

On Saturday, December 09, 2006  9:10 PM, suseloof.cc
wrote:

>Hi Greg,

>to start isqlplus use "isqlplusctl start".
>Port should be 5560.
>By the way, i never installed the companion stuff to get
this running.


>hth

<snip>

Yes, isqlplusctl start does the trick and it does use port
5560, just as I
was told when I installed database.  And I believe you are
correct about not
needing companion just to run isqlplus.  There was something
in the
description on one of the companion components that made it
sound like it
might be needed, but apparently it isn't.  Oh well, maybe
I'll use it some
day anyway.

Thanks,
Greg Wallace


-- 
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting