OWB (10.2.0.1) repository assistant - repository owner creating problem

Question

Oracle9i Release 2 (9.2.0.1)
Oracle Warehouse Builder 10g Release 2 (10.2.0.1)
Microsoft Windows XP
Hi,
during creating the repository owner in repository assistant in about 96% I had an ORA-22905 exception. I read somewhere that I need to patch 9i. I used
Oracle PatchSet 9.2.0.6
Now "Creating repository owner" step has stopped after i had set owner user and password. CPU is working on 100% and memory used by process is growing. There is no exceptions and Repository Assistant hangs.
.BorderLayout,title=Repository Assistant - Etap 5 z 8: Repository Owner Information,resizable,normal,defaultCloseOperation=DO_NOTHING_ON_CLOSE,rootPane=javax.swing.JRootPane[,4,30,690x543,invalid,layout=javax.swing.JRootPane$RootLayout,alignmentX=null,alignmentY=null,border=,flags=385,maximumSize=,minimumSize=,preferredSize=],rootPaneCheckingEnabled=true]
main.AWT-EventQueue-0[6]20060712@11:14:04.004: 00> oracle.wh.service.impl.assistant.ValidationEngine.display(ValidationEngine.java:2003): [ValidationEngine] ... I am in checkOnSysDbmsLock ...
main.AWT-EventQueue-0[6]20060712@11:14:04.004: 00> oracle.wh.service.impl.assistant.ValidationEngine.display(ValidationEngine.java:2003): query = select distinct s.username, s.sid,s.serial# from dba_kgllock l, v$session s, x$kgllk x where l.kgllktype = 'Pin' and s.saddr = l.kgllkuse and s.saddr = x.kgllkuse and x.kglnaobj like '%DBMS_LOCK%' and s.STATUS <>'INACTIVE'
main.AWT-EventQueue-0[6]20060712@11:14:04.004: 00> oracle.wh.service.impl.assistant.DatabaseEngine.display(DatabaseEngine.java:391): getSysConnection() is ok.
(End of log file)

Answer 1

I've had the same problem:
On windows XP pro, 32 bit
- Installed 9.2.0.1 Server
- Installed 9.2.0.6 Patch
- Installed Oracle Worflow + and created workflow user
- Installed OWB_10.2.0.1.win.zip
All seemed to be fine until attempting to create the OWB repository owner.
The first problem is the same as mentioned above. The issue relates to the view dba_kgllock which was forced created against objects that do not exist. To solve this I used TOAD to find the script used to create the view, deleted the view and created an empty table with the same columns.
This is a complete HACK but allowed OWB Repository Assistant. All then continued and was looking good until about 60% complete and then the system fails with a socket read fail within java.
Thats it, I've stopped dead now, going to continue installation attempts in the morning