
|
[oracle-l]
||
[Date Prev]
[02-2008 Date Index]
[Date Next]
||
[Thread Prev]
[02-2008 Thread Index]
[Thread Next]
RE: Wierd resistance to upgrade
- From: "Taylor, Chris David" <Chris.Taylor@xxxxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 31 Jan 2008 15:03:14 -0600
Apparently this is classified as a 'project' not a maintenance task. So
it needs a project code etc etc etc etc etc ad infinitum.
Funny that our 9i OEM to 10.2 Grid Control wasn't a 'project', but
10.2.0.2, to 10.2.0.4 is....
Yep, I'm definitely in a bad mood.
Chris Taylor
Sr. Oracle DBA
Ingram Barge Company
Nashville, TN 37205
Office: 615-517-3355
Cell: 615-354-4799
Email: chris.taylor@xxxxxxxxxxxxxxx
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Taylor, Chris David
Sent: Thursday, January 31, 2008 11:29 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Wierd resistance to upgrade
Any of you guys/gals ever run into something like this?
I'm trying to upgrade our Grid Control Release 2 to Release 4. We've
recently migrated many of our databases to 64bit and have freed up
several 32bit boxes.
Our existing GC Rel 2 server box is underpowered for having all the
components installed on it. I've installed the new version on a
previous development box that is much more powerful and am ready to
start moving the jobs from Rel 2 to Rel. 4. Now I'm being told to hold
off and not spend time on this "project". But I'm not being given a
clear reason why.
I've never been held back before when trying to upgrade our environment
when there is a server available and not spending any additional $$$. I
would expect resistance if I was asking the company to shell out money,
but this is ridiculous. (or seems that way anyway). I have asked mgmt
for reasons why they are resistant and hopefully will be given something
to maybe explain this.
Or maybe I'm just in a bad mood.
GRRRRR
Chris Taylor
Sr. Oracle DBA
Ingram Barge Company
Nashville, TN 37205
Office: 615-517-3355
Cell: 615-354-4799
Email: chris.taylor@xxxxxxxxxxxxxxx
|

|