RDBPROD: Reports Builder 188.8.131.52 running on Linux crashes when connecting to Oracle Rdb
Last updated on AUGUST 04, 2017
Applies to:Oracle SQL/Services for Rdb on OpenVMS - Version 7.3 and later
Information in this document applies to any platform.
You have been successfully using Reports Builder 184.108.40.206 on Red Hat Linux with Oracle Rdb 220.127.116.11.1 and SQL/Services 18.104.22.168.1 on OpenVMS. You want to upgrade your OpenVMS environment to Oracle Rdb 22.214.171.124 and SQL/Services 126.96.36.199. When you test Reports Builder it crashes on "connect".
Unexpected Signal : 11 occurred at PC=0x425BBD4F
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
08048000-0808d000 r-xp 00000000 09:02 25084009 /home/oracle/products/ids10g/bin/rwbuilder
0808d000-080a3000 rw-p 00044000 09:02 25084009 /home/oracle/products/ids10g/bin/rwbuilder
40000000-40015000 r-xp 00000000 09:02 18137201 /lib/ld-2.3.2.so
40015000-40016000 rw-p 00015000 09:02 18137201 /lib/ld-2.3.2.so
40018000-40019000 r-xp 00000000 09:02 786499 /etc/libcwait.so
40019000-4001a000 rw-p 00000000 09:02 786499 /etc/libcwait.so
Heap at VM Abort:
def new generation total 576K, used 536K [0x46bd0000, 0x46c70000, 0x48840000)
eden space 512K, 99% used [0x46bd0000, 0x46c4f980, 0x46c50000)
from space 64K, 40% used [0x46c60000, 0x46c666e8, 0x46c70000)
to space 64K, 0% used [0x46c50000, 0x46c50000, 0x46c60000)
tenured generation total 2856K, used 2308K [0x48840000, 0x48b0a000, 0x56bd0000)
the space 2856K, 80% used [0x48840000, 0x48a812d0, 0x48a81400, 0x48b0a000)
compacting perm gen total 16384K, used 14337K [0x56bd0000, 0x57bd0000, 0x5abd0000)
the space 16384K, 87% used [0x56bd0000, 0x579d0748, 0x579d0800, 0x57bd0000)
Local Time = Mon Apr 6 18:31:22 2009
Elapsed Time = 20
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Server VM (1.4.2_02-b03 mixed mode)
# An error report file has been saved as hs_err_pid890.log.
# Please refer to the file for further information.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms