(
java: xcb_xlib.c:52: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
)
can be avoided by
1. sed -i 's/XINERAMA/FAKEEXTN/g' /usr/lib/jvm/java-1.5.0-sun-1.5.0_update12/jre/lib/i386/xawt/libmawt.so
(saving the original libmawt.so before doing this is maybe a good idea)
2. /orainst/runInstaller -jreLoc /usr/lib/jvm/java-1.5.0-sun-1.5.0_update12/jre
3. sed -i 's/XINERAMA/FAKEEXTN/g' $ORACLE_HOME/jdk/jre/lib/i386/xawt/libmawt.so
(this suppresses the error when using dbca)
4. when using dbca:
Try to type several time "return" in the terminal window if dbca is not responding
Enterprise manager configuration should be disabled when creating a database
5.emca -config dbcontrol db
This configures enterprise manager for the database (as we see this was not working in the previous step) If errors about missing free ports are shown than temprary change to /etc/hosts can help
(
127.0.0.1 localhost
#xxx.xxx.xxx.xxx hostname.domain hostname
127.0.0.1 hostname.domain hostname
)
Change this back after emca has succeeded.
More:
[Xcb] Workarounds for locking assertions in Sun Java 1.5 and 1.6
Josh Triplett josh at freedesktop.orgFri Jun 1 18:23:34 PDT 2007
- Previous message: [Xcb] Processed: Re: Bug#426715: 100_sloppy_lock.diff missing from libxcb 1.0-3
- Next message: [Xcb] Bug#402165: Workarounds for locking assertions in Sun Java 1.5 and 1.6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
tags 402165 + patch
tags 414535 + patch
thanks
I worked with jcristau and christoph4 via IRC on #debian-x, and we managed to
track down the problem with broken locking in Sun Java 1.5 and 1.6. It only
occurs if Java finds the Xinerama extension, at which point it does something
broken with locking and triggers the assertion. If Java never finds the
Xinerama extension, it doesn't trigger the assertion for broken locking.
The following workarounds address this problem:
For sun-java5-bin:
sed -i 's/XINERAMA/FAKEEXTN/g' /usr/lib/jvm/java-1.5.0-sun-1.5.0.11/jre/lib/i386/xawt/libmawt.so
For sun-java6-bin:
sed -i 's/XINERAMA/FAKEEXTN/g' /usr/lib/jvm/java-6-sun-1.6.0.00/jre/lib/i386/xawt/libmawt.so
The same fix (applied to the appropriate file) might work for other
proprietary JDKs.
Would the Debian maintainers of sun-java5-bin and sun-java6-bin please
consider applying these workarounds to the packages, to avoid locking
assertion failures when libx11-6 with Xlib/XCB enters unstable?
- Josh Triplett
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.freedesktop.org/archives/xcb/attachments/20070601/09b55dd3/attachment.pgp
- Previous message: [Xcb] Processed: Re: Bug#426715: 100_sloppy_lock.diff missing from libxcb 1.0-3
- Next message: [Xcb] Bug#402165: Workarounds for locking assertions in Sun Java 1.5 and 1.6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Xcb mailing list
Maybe this resolves the problem as well!
One point of the movie perhaps warrants specific mention: I deliberately show you that simply launching Oracle's installer causes a new and rather odd java locking error. The cure for that is to set the delightfully-named LIBXCB_ALLOW_SLOPPY_LOCK environment variable to 1... after which the Java stuff all works as advertised.
Check also this site:
http://www.dizwell.com/prod/node/1033
0 comments:
Post a Comment