Quantcast
Channel: SCN : Discussion List - SAP NetWeaver Application Server
Viewing all articles
Browse latest Browse all 3078

Output from "R3trans -d" shows "“Caught signal 11 SIGSEGV (SEGV_MAPERR) Address not mapped to object” "

$
0
0

Hi,

 

 

We have just installed SAP Solution Manager 7.1 using SWPM 1.0 SP08. The installation
scenario is Distributed, HA. ASCS, SCS, ERS ( Abap ), ERS ( Java ) and DB
instance are installed at server: sapprddb ( sapprddb1, -2 ), AIX 6.1. Central
Instance ( PI ) is installed at server:smprdapp1, SUSE Linux Enterprise Server
11.

 

 

The installation completes successfully for all instances.

 

 

http://smprdapp1:50000 and Gui Logon works fine.

 

 

All instances except for Central Instance ( PI ) stops and start successfully.

 

Central Instance ( PI ) cannot be restarted. When starting the instance ( startsap ) startsap.trc shows: “DB_LOCAL=0  DB_RUNNING=0  hasABAP=1  hasJava=0  hasSpecial=0  TASK=ALL  Database db must be started first  Log on to remote server and start database Exit
code 6”.

 

 

“R3trans –d” at database server sapprddb1 completes successfully: “ This is R3trans version
6.24 (release 721 - 01.04.15 - 20:15:04).unicode enabled version R3trans
finished (0000). sapprddb1:psmadm 2>

 

 

“R3trans –d” at Central Instance/Application server seems as from trans.log and output to
complete successfully “R3trans finished (0000)” BUT in output output “R3trans
finished (0000)”  follows by “Caught
signal 11 SIGSEGV (SEGV_MAPERR) Address not mapped to object” ref paste in
below,

 

 

“R3trans -d

 

 

This is R3trans version 6.24 (release 721 - 14.10.14 - 20:14:08).

 

 

unicode
enabled version

 

 

R3trans
finished (0000).

 

 

1AETW000
Caught signal 11 SIGSEGV (SEGV_MAPERR) Address not mapped to object (at
0xfab00000fffa5b58)

 

 

(LinStack+0x7c)[0x101247e8]

 

 

(CTrcStack2+0x64)[0x10124e8c]

 

 

(tw_sighandler+0x33c)[0x101d06bc]

 

 

[0xfffaac40418]

 

 

[0x0]

 

 

/usr/lib64/libstdc++.so.6(_ZdlPv-0x5e3b0)[0xfffaab75808]

 

 

/usr/sap/PSM/SYS/global/db6/LINUXPPC64_64/db6_clidriver/lib/libdb2.so(_ZN9rccConfig14clearInstancesEv-0x21039d0)[0xfffa7144b70]

 

 

/usr/sap/PSM/SYS/global/db6/LINUXPPC64_64/db6_clidriver/lib/libdb2.so(_Z24sqle_myexitlist_functionv-0x2053e4c)[0xfffa71f824c]

 

 

/usr/sap/PSM/SYS/global/db6/LINUXPPC64_64/db6_clidriver/lib/libdb2.so(_Z30sqleExitApplicationEnvironmentj-0x20546b4)[0xfffa71f799c]

 

 

/usr/sap/PSM/SYS/global/db6/LINUXPPC64_64/db6_clidriver/lib/libdb2.so[0xfffa74c0c6c]

 

 

/usr/sap/PSM/SYS/global/db6/LINUXPPC64_64/db6_clidriver/lib/libdb2.so(sqlo_execute_list-0x1d96f84)[0xfffa74c0bd4]

 

 

/lib64/power7/libc.so.6[0xfffaa79bbbc]

 

 

/lib64/power7/libc.so.6(exit-0x154190)[0xfffaa79bc38]

 

 

(my_exit+0x58)[0x101cfc58]

 

 

(nlsui_main+0x1fa8)[0x10208398]

 

 

/lib64/power7/libc.so.6[0xfffaa77f13c]

 

 

Segmentation
fault

 

 

“.

 

 

 

 

 

Medias used for the installation

 

 

AIX

 

 

70SWPM10SP08_20009697

 

 

721_EXT_UC_Kernel_for_SWPM_SP08_AIX_64_51049435_3

 

 

51042609_SAP_SOLMAN_71_SR1_Java_Comp_1_To_5

 

 

51042607_SAP_SOLMAN_71_SR1_Inst_Export_12_of_12

 

 

DB2/LUW:V9COMP_V10.1
FP1:RDBMS:DB2/LUW:D51044949

 

 

DB2/LUW:V9COMP_V10.1
FP1:CLI/JDBC-DRIVER:DB2/LUW:CD51044952

 

 

 

 

 

Linux

 

 

70SWPM10SP08_20009610

 

 

Krnl_7.21_EXT_LINUX_Power_SP08_51049438_3

 

 

51042609_SAP_SOLMAN_71_SR1_Java_COMP_1To5

 

 

DB2/LUW:V9COMP_V10.1
FP1:CLI/JDBC-DRIVER:DB2/LUW:CD51044952

 

 

 

 

Trans.log from sapprddb1 and smprdapp1 attached.

 

 

ALL FEEDBACK will be appreciated !

 

 

 

 

 

Best regards

 

 

Hanne
Münther


Viewing all articles
Browse latest Browse all 3078

Trending Articles