Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Moving Code to Production

RE: Moving Code to Production

From: Odland, Brad <>
Date: Thu, 22 May 2003 07:17:37 -0800
Message-ID: <>

Well.....that the code has been tested and it works would be a good place to start...  

Have a recorvery and backout contingency in place. Be able to restore the old code if needed.  

Make sure you ask the developer...."Does it work? Did you test it the test environment?" If they hem and haw and say "Oh it works fine" check to make sure the code is in the test and development environments. If its not...ask again and ask why it is not in the test and developement areas....  

Depending on the code there are ooddles of things....permissions on the objects or code....grants etc...dependencies on objects  

Downstream effects of code changes are hard to predict in production environments where there is a lot of adhoc work.  

You can take to tacks one is to send out notices via e-mail what is changeing and when it is and if anyone has issues with the objects in questions. Provide examples of how the data will be effected.  

Also predicting the effects of time. What will the result of this code be a week, a month and year from now....sometimes tables just grow and grow with no cap built into the code. No clean up or purge process.  

Brad O.    

-----Original Message-----
Sent: Thursday, May 22, 2003 9:27 AM
To: Multiple recipients of list ORACLE-L

Would like some feedback as to what to check, etc. when moving new code changes into the production environment.  

Thanks much,
Ken Janusz, CPIM


Please see the official ORACLE-L FAQ:

Author: Odland, Brad

Fat City Network Services    -- 858-538-5051
San Diego, California        -- Mailing list and web hosting services
To REMOVE yourself from this mailing list, send an E-Mail message to: (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Thu May 22 2003 - 10:17:37 CDT

Original text of this message