Now,upgrading from 92028 to 9203,OWB

Question

Folks,
I am in the process of applying the
OWB 9.2.0.3 patch to my 9.2.0.2.8 OWB env.
Just a brief history,
1)I had OWB 9.0.3, then applied the 9.2.0.2.8 on it.
As part of that,
Created a design repository,runtime schema,runtime access user and also created target schema.
2)Now I am applying the 9.2.0.3 (3152515)
The readme of the patch 3152515, has a section called
H) Bug specific Post-Patching Notes
Bug 3073545:
You must create a new Runtime Repository and a new Runtime Schema
using OWB Runtime Assistant 9.2.0.3
Bug 3043523 (duplicates 3038909,3044835):
You must create a new Runtime Repository using OWB Runtime Assistant 9.2.0.3
Bug 3028355:
You must create a new Runtime Repository using OWB Runtime Assistant 9.2.0.3
Bug 2827970:
You must create a new OWB Repository using OWB Repository Assistant 9.2.0.3
So my question is
Should I created another Runtime Repository schema for 9203
I thought under step
G)Mandatory Post-patching notes
We already upgraded our current Runtime repository schema (from 9208 to 9203)
I am confused here.
Thanks.
Ashish

Answer 1

Ashish,
I know, the combination of sections "G) Mandatory Post-Patching Notes" and "H) Bug specific Post-Patching Notes" might be confusing.
The steps in section G just upgrade the property of the runtime repository to 9.2.0.3.0, there is literally just one update statement in the script run. This is enough to insure compatibility between the runtime repository version value and the new jar files that the patchset installs. Otherwise your run-time service will simply not start.
The steps in section H tell you to re-create runtime repository because those particular four bug fixes in this patchset need updated PL/SQL objects in the runtime repository that can only be introduced by repository re-creation. As you have guessed already, re-creating the repository defeats the purpose of previously running any scripts on the old one, so yes, you can just do steps in section H without doing the steps in G.
In the future patchsets, we've streamlined the repository upgrade process, so this confusion should not occur again.
Nikolai