Tuesday, February 21, 2012

Upgrade Issues BW 7.3 SP5

Quickly I would like to share some technical lessons learned from the upgrade at a customer that i work for:

- SID generation now checks if characteristic value is valid for conversion routine of infoobject.This could potentially show problems in your datamodel. Please perform a regular delta load in a test system to avoid surprises after upgrade.
- Masterdata activation has changed in 7.3, we encountered a few issues with deadlocks during activation/SID generation. (1637633 note)
- Data activation in DSO's is/was a bit instable after upgrade. Also, no real improvement on data activation can be measured so far.
- Many problems with JAVA Web frontend, please test thoroughly. Many notes are already available since SP5. (also IP issues)
- Start/End routines of transformations are changed, now fields should be selected induvidually. Note 1635588 imported to fix issue with conversion 7.0 > 7.3 transformation with start/endroutines.
- Semantic key of DTP towards Infoobject should now be selected, otherwise no parallel loading can take place.
- Upgrading JAVA stack was really troublesome for SAP Basis team.
- Vague error messages when loading towards a cube with SID generation..check notes 1639786, 1657854 and 1664648.

Some nice new features:
- Skip button in process chains
- Drag and drop DTP's and Infopackages to proces chains
- Proces chain hierarchy when using local chains
- Extra checks when releasing transports
- Documentation of objects improved
- Version management of BW objects
- Hierarchy view in proces chains

5 comments:

  1. Great! Could you please share more - like steps involved in upgrades, checklist - Prepare, Transport releases, SPDD and SPAU issues etc

    ReplyDelete
  2. Hi AGK, Sorry for the late reply. I don't have the runbooks anymore.

    Hope you upgraded your system already :)

    ReplyDelete
    Replies
    1. Hi Frake,

      Really thank you for the blog. I was searching for the post upgrade BW issues and I guess you have only shared this. Can you please share any other lesson learnt. An pre upgrade and post upgrade activity will be very helpful.

      Regards,
      Dibakar

      Delete
    2. Hi Dibakar,

      Pre upgrade steps...are general ones:

      Try to get your system landscape as synchronized as possible (no transports imported to QA in between) Take a copy of you production system for QA to test the upgrade. Perform regular process chain loads.

      Try to identify hotnotes that are relevant for your SP upgrade. Scan them and see if they can apply in your case.

      Post steps are sanity checks to see if everything still works properly (sourcesystem check, reports check, webreport check etc.

      Good luck!

      Delete

  3. very useful information thanks for sharing thank you

    ReplyDelete