Many of you probably know this already, but it took me by surprise (and
caused no end of grief) so I thought I'd warn people.
I cloned our 8.0.4 production database onto another machine for some testing
we were doing (copy of entire Oracle filesystem, copied hot backup over) and
started it up
Jay,
Did that several months ago with our HP-MPE box. The problem was that we
changed the IP address of the box and brought a new one online, with the old
ones original IP. Now MPE has NO idea of what a DNS server is so one has to
bury the actual IP address into things like listener.ora
Yeah, you discovered one of the gaping holes in SQL Net.
Putting a password on the listener is of little help either.
As I recall, you can prevent someone from starting the
listener, but not from remotely stopping it.
Someone please correct me if I have this wrong, but we
tested it a few
Another thing to watch are the dbms_job entries, especially ones which interact with
other databases. For example a job which pulls data from another database and writes
back to that database the success of its efforts. If this job were to run in the
clone, it might perform this task before
Been there, done that;-)
-Original Message-
Sent: Wednesday, July 11, 2001 7:57 AM
To: Multiple recipients of list ORACLE-L
Many of you probably know this already, but it took me by surprise (and
caused no end of grief) so I thought I'd warn people.
I cloned our 8.0.4 production
And watch out for any database links that points to other production servers.
[EMAIL PROTECTED] 07/11/01 12:27PM
Another thing to watch are the dbms_job entries, especially ones which interact with
other databases. For example a job which pulls data from another database and writes
back to
unique passwords in listener.ora files prevents this.
Kimberly Smith wrote:
Been there, done that;-)
-Original Message-
Sent: Wednesday, July 11, 2001 7:57 AM
To: Multiple recipients of list ORACLE-L
Many of you probably know this already, but it took me by surprise (and
caused
Use localhost as hostname in listener.ora and you will never have this
problem.
Alex Hillman
-Original Message-
Sent: Wednesday, July 11, 2001 11:18 AM
To: Multiple recipients of list ORACLE-L
Jay,
Did that several months ago with our HP-MPE box. The problem was that
we
changed
Immediately after this happened I thought of that and removed all other
entries from tnsnames.ora so database links wouldn't work (and of course
changed the reference for the local entry).
-Original Message-
Sent: Wednesday, July 11, 2001 1:03 PM
To: Multiple recipients of list ORACLE-L
When you run HP ServiceGuard that is not an option.
-Original Message-
Sent: Wednesday, July 11, 2001 10:16 AM
To: Multiple recipients of list ORACLE-L
Use localhost as hostname in listener.ora and you will never have this
problem.
Alex Hillman
-Original Message-
Sent:
Nor is it an option on MPE where the network layer is primitive to say the
least. One HAS to use the actual IP address of the server.
Reply Separator
Author: Kimberly Smith [EMAIL PROTECTED]
Date: 7/11/2001 10:26 AM
When you run HP ServiceGuard
And I think in a cluster, if you configure the listener process to
be a service, then it has to use the IP as well.
[EMAIL PROTECTED] 07/11/01 03:51PM
Nor is it an option on MPE where the network layer is primitive to say the
least. One HAS to use the actual IP address of the server.
12 matches
Mail list logo
