libjox10.sl error While applying the 10.2.0.2 patch

Issue 2: While applying the 10.2.0.2 patch, you receive the following error message:


The following actions are not applicable:

Copy Action: Desctination File

"/bugmnt4/ap/rmtdchp6/BOD/10.2.0.2/A/64bit/app/oracle/product/10.2.0.2/lib/libjox10.sl" is not writeable.

'oracle.javavm.server, 10.2.0.2.0': Cannot copy file from 'libjox10.sl' to

'/bugmnt4/ap/rmtdchp6/BOD/10.2.0.2/A/64bit/app/oracle/product/10.2.0.2/lib/libjox10.sl'



Do you want to proceed? [y|n]


This error is likely to occur for any third party library that comes with out write permission, like libons.sl, libjox10.sl etc.

Workaround (perform all of the following steps):

Stop the patch installation by typing n as the response.

Make note of the file permissions on the libraries that are not writeable.

Provide write permission (preferably 755) to the libraries.

Reapply the patch.

Revert back to the original file permissions for the libraries. Failure to do so may result in the following error:


usr/lib/pa20_64/dld.sl: Mmap failed for the

library<....10.2.0.2/@ lib/libjox10.sl> : Permission denied.

ERROR:

ORA-12547: TNS:lost contact

xchm installation

after installation, you might have problem after type "xchm &" with below error message.
[root@localhost Desktop]# xchm
xchm: error while loading shared libraries: libchm.so.0: cannot open shared object file: No such file or directory

Solution:
　　#ln -s /usr/local/lib/libchm.so.0 /usr/lib/libchm.so.0

　　#ln -s /usr/lib/libwx_gtk-2.4.so.0 /usr/lib/libwx_gtk-2.4.so

ORA-00600: internal error code, arguments: [opixrb-4], [1036]

ORA-00600: internal error code, arguments: [opixrb-4], [1036], [ORA-01036: illegal variable name/number
], [], [], [], [], []

According to metalink , this is a known bug.

Bug 4964703 OERI[opixrb-4] [1036] from SELECT over DBLINK with trailing :N or :Q bind names
Fixed-Releases: 9208 A203

PROPOSED SOLUTION(S)
======================
1.Applying patch 4964703
2.Replacing Bind Variable 'n' with another character. (if you use TOAD,this workaround can't
be accepted becuase this variable is defined in TOAD code.)


For my case, it is caused by TOAD 8.6.0.38