Sponsored Content
Top Forums UNIX for Advanced & Expert Users Upgrading legacy packages with patch Post 303043799 by Neo on Friday 7th of February 2020 04:23:05 AM
Old 02-07-2020
Normally if we are making upgrades to mission critical applications in 100s of servers in a large organization with a risk management team we should notify them if if we plan any upgrades which may cause an outage.

You should test in a test bed, make a plan, identify the risks and notify your risk management team.

Upgrading the core "mission critical" application on 200-300 web servers requires planning and team work.

What happens if you make a mistake and bring down the application(s)? Do you want your organization to be caught off guard when customers are calling in, angry their service is down?

You have described a major infrastructure upgrade. You certainly do not want to upgrade with YUM over a manually installed configuration until you have completed tested this idea in a test bed, insure you have backups of each application and database before hand, etc. In other words, you need a plan in coordination with your IT risk management team, customer service, etc.

This is how we work as IT professionals.
 

9 More Discussions You Might Find Interesting

1. Programming

CMI Legacy

Is there anyone who still uses CMI to connect to the legacy system , my c applications do uses the binaries and libraries for using the CMI functionality but i do not have access to the original source code , and since this is a very old stuff , i just could not get any source to get to knwo the... (0 Replies)
Discussion started by: dino_leix
0 Replies

2. IP Networking

Patch-o-matic (patch for iptable) for linux2.4.08 & iptable1.2.7a

Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down. I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies

3. Red Hat

upgrading packages

Hello, I am using Redhat Linux Enterprise 4 AS. To upgrade NFS, I had to browse the internet and finally I got the latest rpm https://rhn.redhat.com/errata/RHBA-2005-727.html That was a time-consuming procedure. On Solaris, I am used to go to sunfreeware.sun.com and download the latest... (3 Replies)
Discussion started by: melanie_pfefer
3 Replies

4. Programming

VERSYS Legacy System

I need help locating the tables that hold the demograhic data in this system on an AIX box. Does anyone know the path? (0 Replies)
Discussion started by: Chelcye
0 Replies

5. Slackware

Find Slackware Packages - packages.acl.org.ua

Hi! Let me introduce a project for find and download Slackware packages and browse Slackware repositories. The site provides following features: * Large, daily updated database with RPM, DEB, TGZ, TXZ packages for well-known repositories of the Slackware, Fedora, CentOS, RHEL, Debian,... (2 Replies)
Discussion started by: lystor
2 Replies

6. Solaris

Facing problem after upgrading the kernal patch level to 142900-12

I have a Solaris 10 OS having kernal patch level 138888-03 on several servers but recenlty I upgraded it into 142900-12 on some T-Series servers & v890 server after install them my syslog is increasing at a rate of 1GB on average on all servers . I believe its a bug, can somebody help me in... (1 Reply)
Discussion started by: sb200
1 Replies

7. What is on Your Mind?

Tron Legacy

Watched it. Major disappointment. (10 Replies)
Discussion started by: ni2
10 Replies

8. Ubuntu

Encountering problem on upgrading the packages

Hi folks, Ubuntu 9.04 I have an old box not running for years. I just dig it out from the store room. On running; $ sudo aptitude update ...... ...... Err http://hk.archive.ubuntu.com jaunty/main Packages 404 Not Found Err http://hk.archive.ubuntu.com jaunty/restricted Packages ... (1 Reply)
Discussion started by: satimis
1 Replies

9. Solaris

Determine if you are in a Legacy Zone?

Hi Folks, Just a quick question here, about Legacy Zones. Well more about how to determine if you are actually in one, on logging into a legacy zone - is there a quick way of checking that? Regards Gull04 (7 Replies)
Discussion started by: gull04
7 Replies
RDF::Query::Plan::Service(3pm)				User Contributed Perl Documentation			    RDF::Query::Plan::Service(3pm)

NAME
RDF::Query::Plan::Service - Executable query plan for remote SPARQL queries. VERSION
This document describes RDF::Query::Plan::Service version 2.908. METHODS
Beyond the methods documented below, this class inherits methods from the RDF::Query::Plan class. "new ( $endpoint, $plan, $silent, $sparql, [ \%logging_keys ] )" Returns a new SERVICE (remote endpoint call) query plan object. "<$endpoint"> is the URL of the endpoint (as a node object). "<$plan"> is the query plan representing the query to be sent to the remote endpoint (needed for cost estimates). "<$sparql"> is the serialized SPARQL query to be sent to the remote endpoint. Finally, if present, "<%logging_keys"> is a HASH containing the keys to use in logging the execution of this plan. Valid HASH keys are: * bf - The bound/free string representing C<<$plan>> "new_from_plan ( $endpoint, $plan, $context )" Returns a new SERVICE query plan object. "<$endpoint"> is the URL of the endpoint (as a string). "<$plan"> is the query plan representing the query to be sent to the remote endpoint. The exact SPARQL serialization that will be used is obtained by getting the originating RDF::Query::Algebra object from "<$plan">, and serializing it (with the aid of the RDF::Query::ExecutionContext object "<$context">). "execute ( $execution_context )" "next" "close" "endpoint" "sparql" Returns the SPARQL query (as a string) that will be sent to the remote endpoint. "lhs" "silent" Returns a boolean value indicating whether the service plan will ignore errors. "pattern" Returns the query plan that will be used in the remote service call. "distinct" Returns true if the pattern is guaranteed to return distinct results. "ordered" Returns true if the pattern is guaranteed to return ordered results. "plan_node_name" Returns the string name of this plan node, suitable for use in serialization. "plan_prototype" Returns a list of scalar identifiers for the type of the content (children) nodes of this plan node. See RDF::Query::Plan for a list of the allowable identifiers. "plan_node_data" Returns the data for this plan node that corresponds to the values described by the signature returned by "plan_prototype". "graph ( $g )" "explain" Returns a string serialization of the query plan appropriate for display on the command line. AUTHOR
Gregory Todd Williams <gwilliams@cpan.org> perl v5.14.2 2012-01-31 RDF::Query::Plan::Service(3pm)
All times are GMT -4. The time now is 03:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy