on 02-11-2015 11:22 AM
Hi,
I am in the process of upgrading from BW3.5 to BI 7.0. I get the an error in XPRAS_UPG phase. It does not allow me to proceed. It asks me to check the job RDDEXECL that got cancelled. The job logs ask to check st22. The short dump says :
-
Runtime Errors CREATE_DATA_UNKNOWN_TYPE
Exception CX_SY_CREATE_DATA_ERROR
Date and Time 04.11.2009 17:24:41
Short text
CREATE DATA: The specified type "/BI0/APERS_BOD00" is no valid data type.
What happened?
Error in the ABAP Application Program
The current ABAP program "RS_PERS_XPRA_1" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
-
Please help.
Regards,
Sufaid
Hi,
Could you share memory configurations for the system.
malloc failed
Please follow SAP Note 217351 - No free memory of class PERM available/Malloc failed
& tune parameters mentioned in it.
Regards,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok .
Can you post your New support pack levels . ( Somehow getting a strong feeling that the Note suggested by Sunil may be valid - In that case you may apply the corrections manually )
Please also raise an message with SAP
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manu
Please find the patch level given below,
SAP_ABA | 700 | 0014 | SAPKA70014 | Cross-Application Component |
SAP_BASIS | 700 | 0014 | SAPKB70014 | SAP Basis Component |
PI_BASIS | 2005_1_700 | 0014 | SAPKIPYJ7E | PI_BASIS 2005_1_700 |
SAP_BW | 700 | 0016 | SAPKW70016 | SAP NetWeaver BI 7.0 |
BI_CONT | 310 | 0000 | - | Business Intelligence Content |
______________________________ | __________ | ____ | ____________________ | ________________________________________________________________________________ |
Thanks
Sufaid
Hi Sufaid ,
If i were you i will do the following
1 Stop Sum tool . Take a backup of your SUM directory and if Possible the DB .
2 . Apply manually the corrections mentioned in SAP Note 1160105 in the main instance .
3. Start SUM tool and Try once again
Thanks ,
Manu
Current Date | 12.02.2015 |
Time | 15:33:37 |
Application Server | ASBWSBOX_B12_00 |
User Name | DDIC |
Client ID | 000 |
Keep | C |
Name of runtime error | CREATE_DATA_UNKNOWN_TYPE |
Exception | CX_SY_CREATE_DATA_ERROR |
Index of Work Process | 10 |
Transaktions-ID | F7AAB2E40D90F1A89AD7002219537AE5 |
Runtime Errors CREATE_DATA_UNKNOWN_TYPE
Exception CX_SY_CREATE_DATA_ERROR
Date and Time 12.02.2015 15:33:37
Short text
CREATE DATA: The specified type "/BI0/APERS_BOD00" is no valid data type.
What happened?
Error in the ABAP Application Program
The current ABAP program "RS_PERS_XPRA_1" had to be terminated because it
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CREATE_DATA_ERROR', was not
caught and
therefore caused a runtime error.
The reason for the exception is:
The dynamically specified type "/BI0/APERS_BOD00" at CREATE DATA is no valid
data type.
The type is either unknown or an object type.
How to correct the error
If the specified type "/BI0/APERS_BOD00" is an object type, then new objects of
this
type (instances) are not created with CREATE DATA, but with
CREATE OBJECT.
If the type is unknown, then it must be created in the program or in the
ABAP dictionary.
Probably the only way to eliminate the error is to correct the program.
-
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"CREATE_DATA_UNKNOWN_TYPE" "CX_SY_CREATE_DATA_ERROR"
"RS_PERS_XPRA_1" or " "
"START-OF-SELECTION"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Hi Sufaid
You can follow the SAP note 2075289 solutions. same error message in Solution manager 7.1 BW area.
BR
SS
Hi Sufaid ,
You may start the shadow system . Check the object and shut it down .
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sunil
Please find the requested logs given below,
SAP-R/3-Startup Program
Starting at 2015/02/11 17:02:51
Startup Profile: "g:\usr\sap\put\B12\SYS\profile\START_DVEBMGS02_ASBWSBOX"
Starting Programs
(9572) CreateProcess: g:\usr\sap\put\exe\msg_server.exe pf=g:\usr\sap\put\B12\SYS\profile\B12_DVEBMGS02_ASBWSBOX
(9540) CreateProcess: g:\usr\sap\put\exe\disp+work.exe pf=g:\usr\sap\put\B12\SYS\profile\B12_DVEBMGS02_ASBWSBOX
-------------------------------------------------------------------------
---------------------------------------------------
trc file: "dev_w0", trc level: 1, release: "700"
---------------------------------------------------
*
* ACTIVE TRACE LEVEL 1
* ACTIVE TRACE COMPONENTS all, MJ
*
M sysno 02
M sid B12
M systemid 562 (PC with Windows NT)
M relno 7000
M patchlevel 0
M patchno 353
M intno 20050900
M make: multithreaded, ASCII, 64 bit, optimized
M pid 8620
M
M kernel runs with dp version 247(ext=110) (@(#) DPLIB-INT-VERSION-247)
M length of sys_adm_ext is 364 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 8620) [dpxxdisp.c 1407]
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M DpShMCreate: sizeof(wp_adm) 26928 (1224)
M DpShMCreate: sizeof(tm_adm) 5283968 (26288)
M DpShMCreate: sizeof(wp_ca_adm) 18048 (60)
M DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552048/552064
M DpShMCreate: sizeof(comm_adm) 552064 (1088)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm) 0 (104)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm) 0 (72)
M DpShMCreate: sizeof(vmc_adm) 0 (1616)
M DpShMCreate: sizeof(wall_adm) (25648/36736/64/104)
M DpShMCreate: sizeof(gw_adm) 48
M DpShMCreate: SHM_DP_ADM_KEY (addr: 0000000010280050, size: 5957216)
M DpShMCreate: allocated sys_adm at 0000000010280050
M DpShMCreate: allocated wp_adm at 0000000010281D30
M DpShMCreate: allocated tm_adm_list at 0000000010288660
M DpShMCreate: allocated tm_adm at 00000000102886C0
M DpShMCreate: allocated wp_ca_adm at 0000000010792740
M DpShMCreate: allocated appc_ca_adm at 0000000010796DC0
M DpShMCreate: allocated comm_adm at 0000000010798530
M DpShMCreate: system runs without slock table
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 000000001081F1B0
M DpShMCreate: allocated gw_adm at 000000001081F230
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 000000001081F260
M DpShMCreate: allocated wall_adm at 000000001081F2C0
M DpRqQInit: Parameter rdisp/queue_lock_level = 2
M rdisp/queue_size_check_value : -> on,50,30,40,500,50,500,80
M ***LOG ST0=> PERM SHORT 1600056 [saprstg.c 4724]
Y *** ERROR => malloc failed [saprstg.c 4728]
Y *** ERROR => size 1600056 [saprstg.c 4729]
Y *** ERROR => sapinit: no memory or improper size for SHORT (-3) [sapinit.c 1048]
M *** ERROR => DpMemInit: sapinit (-3) [dpxxdisp.c 10536]
M *** DP_FATAL_ERROR => DpSapEnvInit: DpMemInit
-----------------------------------------------------------------------------------------
---------------------------------------------------
trc file: "dev_ms", trc level: 1, release: "700"
---------------------------------------------------
[Thr 3700] Wed Feb 11 17:02:53 2015
[Thr 3700] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid 562 (PC with Windows NT)
relno 7000
patchlevel 0
patchno 302
intno 20050900
make: multithreaded, ASCII, 64 bit, optimized
pid 9572
[Thr 3700] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 9572) [msxxserv.c 1837]
[Thr 3700] MsInitAclInfo: acl file g:\usr\sap\put\B12\SYS\global\ms_acl_info.DAT not found, unrestricted access
[Thr 3700] MsGetOwnIpAddr: my host addresses are :
[Thr 3700] 1 : [172.16.10.126] ASBWSBOX.alseersap.net (HOSTNAME)
[Thr 3700] 2 : [127.0.0.1] ASBWSBOX.alseersap.net (LOCALHOST)
[Thr 3700] MsHttpInit: full qualified hostname = ASBWSBOX.alseersap.net
[Thr 3700] HTTP logging is switch off
[Thr 3700] MsHttpOwnDomain: own domain[1] = alseersap.net
[Thr 3700] ms/icf_info_server : deleted
[Thr 3700] *** I listen to port sapmsSHDB12 (3602) ***
[Thr 3700] CUSTOMER KEY: >O1084318028<
[Thr 3700] Wed Feb 11 17:15:55 2015
[Thr 3700] *** ERROR => MsSCheckConnections: no response from client C0 (172.16.10.126) after 300 secs received [msxxserv.c 3187]
[Thr 3700] *** ERROR => MsSCheckConnections: disconnect now [172.16.10.126] [msxxserv.c 3191]
Thanks
Sufaid
Hi Sufaid ,
Can you check in SE11 whether the Data type exists and if it exists whether it is active
If it exists and if it is not active you can troubleshoot
Thanks ,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manu
I am almost in the last session of the upgrade.
We are in the process of BW 3.1 to BI 7.0 upgrade.
The system status showing all components are now in 7.0.
Shadow system was created and it is stopped during the upgrade.
Should I start the shadow system and check the data type?
Thanks
Sufaid
have you checked the note 1160105 - Termination in XPRA RS_PERS_XPRA_1
I am not sure upto what level you have included the support pack in your upgrade but this note says about to import SAPKW70018 or advance correction.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.