Re: Keeping a DB from Phoning Home...
- From: David Mann <dmann99@xxxxxxxxx>
- To: "Mark W. Farnham" <mwf@xxxxxxxx>
- Date: Sat, 14 Sep 2013 09:37:01 -0400
You got it Mark, I want to prevent any activity where the DB instance tries
to initiate connections to the outside world. This was a key system that
was a hub of activity before it was initially retired. We are resurrecting
it to give it a proper documented archival so it can be brought up at any
time in the future without causing any problems with other systems.
Outgoing DB links are the first concern, custom Java with network
permissions was 2nd concern, then was looking for group feedback for any
other concerns.
Sent from my iPhone
On Sep 13, 2013, at 12:22 PM, "Mark W. Farnham" <mwf@xxxxxxxx> wrote:
> While those are indeed useful parameters, they function with regard to
> clients reaching in; I'm pretty sure David want to prevent any attempts of
> the database server to reach out, so that if there are pending jobs or
> schedules hilarity cannot ensure by it kicking something off or changing
> something in duplicate with some production server that now is
responsible,
> or at all if the job or transaction is still possible but obsolete.
>
> Have I got that right, David?
>
> mwf
>
--
Dave Mann
General Geekery | www.brainio.us
Database Geekery | www.ba6.us | @ba6dotus | http://www.ba6.us/rss.xml
--
//www.freelists.org/webpage/oracle-l
Other related posts:
