Monday, 3 September 2012

Manual checks before starting Technical Downtime


Database and IS specific preparation
--------------------------------------------
  • Deactivaion of cluster failover during the technical downtime
  • Free memory space avalable for the database
  • rrequired memory space avalable in F.S
  • Automatic restart of SAP system is deactivated
  • Dattabase statistics is updated

SAP system side preparation.
------------------------------------
  • All functional that is bussiness-critiacal, background jobs are complete and planned.
  • Outstanding updates are processed.
  • Setting up a system messsage (SM02) with the inforamtion that system is unavaliable
  • No SAP object locked by repairs
  • consistence check (missing table and indexes ) successful (DB02)
  • Background jobs of class C configurred for CI
  • RDDIMPDP background job configurred for CI
  • Batch process configured for CI
  • Locking of SAP users
  • No active users logged into the system
  • No open or aborted updates in system(SM13)
  • BW delta queues processed (SMQ1)
  • General : interface gueues cleaned (LBWG)
  • Monitoring tools ( application server and CI) stoipped during downtime.
  • Isolation of CI (stopping the application servers)
  • Take a complete offline database backup( better if you take F.S backup of /oracle directoty)
  • Consisttent backup of installation directory,of the kernel directory and SAP profiles avaliable as they will be overwritten during downtime. 

No comments:

Post a Comment