Dump Error When Launching UJS_ACTIVATE_CONTENT

former_member117942 · ‎2015 Jul 10

Hi all,

we're facing an issue when try to activate ENVIRONMENTSHELL through SE38 and program UJS_ACTIVATE_CONTENT.

NW and BPC are installed on a single windows server. Hana on a separate server operating SUSE

We installed HANABPC component on top of CPMBPC, as well as POASBC and followed all the step of the last installation guides to install a standard version of BPC 10.1

During activation from SE38 we got this error:

Any suggestion would be appreciated.

Thanks.

damovand · ‎2015 Jul 13

Hello,

Are you using HANA in a distributed system? Then please make sure that you have enabled the parameter ENABLE_HANA_DISTRIBUTION. Please see note 2010964 for more details.

Best Regards,

Leila Lappin

former_member117942 · ‎2015 Jul 13

Here is the full dump log.

Yes, the user performing Environment Shell activation is a SAP_ALL user...

@Andy Xu:

BPC and NW ARE running on top of HANA but, as previously said, hana is not installed on the same server...

former_member117942 · ‎2015 Jul 13

Category

ABAP Programming Error

Runtime Errors

MESSAGE_TYPE_X

ABAP Program

SAPLRSDG_IOBJ_DB_READ

Application Component

BW-WHM-MTD

Date and Time

10.07.2015

15:17:47

	Short Text
		The current application has triggered a termination with a short dump.

	What happened?
		The current application program has detected a situation that should
		not occur. A termination with short dump has therefore been triggered
		by the key word MESSAGE (type X).

	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
		Short text of the error message:
		System error in program LRSDG_IOBJ_DB_READF40 and form REGULAR_IOBJ_GET_
		FOR_META
		Long text of the error message:
		Diagnosis
		This internal error is a targeted termination since the program has
		an
		incorrect status.
		Procedure
		Analyse the situation and inform SAP.
		Technical information about the message:
		Message class....... BRAIN
		Number.............. 299
		Variable 1.......... LRSDG_IOBJ_DB_READF40
		Variable 2.......... REGULAR_IOBJ_GET_FOR_META
		Variable 3..........
		Variable 4.......... " "

	How to correct the error
		Probably the only way to eliminate the error is to correct the program.
		-
		If the error occurs in a non-modfied SAP program, you might be able to
		find a solution in the SAP Notes system. If you have access to the SAP
		Notes system, check there first using the following keywords:

		"MESSAGE_TYPE_X"
		"SAPLRSDG_IOBJ_DB_READ" bzw. LRSDG_IOBJ_DB_READF40
		"REGULAR_IOBJ_GET_FOR_META"
		If you cannot solve the problem yourself, please send the following
		information to SAP:

		1. This description of the problem (short dump)
		To do this, choose System -> List -> Save -> Local File (unconverted)
		on the screen you are in now.

		2. A suitable system log
		To do this, call the system log in transaction SM21. Restrict the time
		interval to ten minutes before the short dump and five minutes after
		it. In the display, choose System -> List -> Save -> Local File
		(unconverted).

		3. If these are programs of your own, or modified SAP programs: Source
		code of these programs
		To do this, choose More Utilities -> Upload/Download -> Download in
		the Editor.

		4. Details regarding the conditions under which the error occurred or
		which actions and input caused the error.

	System environment
		SAP Release..... 740
		SAP Basis level 0011

		Application server... SAPBPDDBCI
		Network address...... 172.17.10.148
		Operating system... Windows NT
		Release.............. 6.3
		Hardware type....... 4x AMD64 Level
		Character length..... 16 Bits
		Pointer length........ 64 Bits
		Work process number... 7
		Shortdump setting. full

		Database server... saphbddb
		Database type..... HDB
		Database name..... BPD
		Database user ID SAPBPD

Terminal.......... Canca

Character set C

		SAP kernel....... 742
		Created on....... Mar 24 2015 16:58:40
		Created at....... NT 6.1 7601 x86 MS VC++ 16.00
		Database version SQLDBC 1.00.097.00.1434028111
		Patch level....... 101
		Patch text.......

		Database............. HDB 1.0
		SAP database version. 742
		Operating system... Windows NT 6.0, Windows NT 6.1, Windows NT 6.2, Windows NT
		6.3

		Memory consumption
		Roll.... 0
		EM...... 30403504
		Heap.... 0
		Page.... 65536
		MM used. 16330304
		MM free. 2842944

	User and Transaction
		Client................. 100
		User.................. SM_ICMS
		Language key.......... E
		Transaction......... SE38
		Transaction ID...... 080627E54CBFF1A180C90050569F26F4

		EPP whole context ID...... 0050569F26F41ED589E05D6D5BC900C9
		EPP connection ID........ 00000000000000000000000000000000
		EPP call counter......... 0

		Program.............. SAPLRSDG_IOBJ_DB_READ
		Screen.............. SAPMSSY0 1000
		Screen line.......... 6
		Active debugger..... "none"

	Information on where terminated
		The termination occurred in ABAP program "SAPLRSDG_IOBJ_DB_READ", in
		"REGULAR_IOBJ_GET_FOR_META". The main program
		was "UJS_ACTIVATE_CONTENT".

		In the source code, the termination point is in line 31 of (Include)
		program "LRSDG_IOBJ_DB_READF40".

Source Code Extract (Source code has changed)

Line

SourceCde

	1		----------------------------------------------------------------------
	2		* INCLUDE LRSDG_IOBJ_DB_READF40 *
	3		----------------------------------------------------------------------
	4
	5
	6		---------------------------------------------------------------------
	7		* Form REGULAR_IOBJ_GET_FOR_META
	8		---------------------------------------------------------------------
	9		* read a regular InfoObject as Meta InfoObject
	10		---------------------------------------------------------------------
	11		* --> I_INFOCUBE InfoCube
	12		* --> I_IOBJNM InfoObject
	13		* <-> C_T_COB_PRO InfoCube specific InfoObject properties
	14		---------------------------------------------------------------------
	15		FORM regular_iobj_get_for_meta USING i_infocube TYPE rsinfocube
	16		i_iobjnm TYPE rsiobjnm
	17		CHANGING c_t_cob_pro TYPE rsd_t_cob_pro.
	18
	19		DATA: l_s_cob_pro TYPE rsdcobpro.
	20
	21		CALL FUNCTION 'RSD_IOBJ_INCL_ATR_NAV_GET'
	22		EXPORTING
	23		i_iobjnm = i_iobjnm
	24		i_objvers = rs_c_objvers-active
	25		IMPORTING
	26		e_s_cob_pro = l_s_cob_pro
	27		EXCEPTIONS
	28		iobj_not_found = 1
	29		illegal_input = 2.
	30		IF sy-subrc <> 0.
	>>>>>		MESSAGE x299(brain) WITH 'LRSDG_IOBJ_DB_READF40'
	32		'REGULAR_IOBJ_GET_FOR_META'.
	33		ENDIF.
	34
	35		* time charact --> time dimension / In BEX not visible
	36		IF i_iobjnm = rsd_c_chanm-date OR
	37		i_iobjnm = rsd_c_timnm-calday.
	38		l_s_cob_pro-chasel = rsd_c_chasl-not_allowed.
	39		l_s_cob_pro-chanav = rsd_c_chanv-not_allowed.
	40
	41		** from 3.0 these InfoObjects are marked as META objects
	42		* l_s_cob_pro-iobjtp = rsd_c_objtp-meta.
	43		* the olap processor uses 0DATE / 0CALDAY as default for exceptional aggregation -
	44		* therefore it has to be in the cobpro
	45		* but it must not be of type META, since then day of validity logic
	46		* does not work
	47		* solution for 3.0: OLAP processor uses the flags CHASEL and CHANAV to determine
	48		* if 0DATE / 0CALDAY is part of the infocube
	49
	50		* leave dimension empty

Contents of system fields

Name

Val.

	SY-SUBRC				1
	SY-INDEX				0
	SY-TABIX				1
	SY-DBCNT				0
	SY-FDPOS				1
	SY-LSIND				0
	SY-PAGNO				0
	SY-LINNO				1
	SY-COLNO				1
	SY-PFKEY
	SY-UCOMM
	SY-TITLE				BPC: Content Activation
	SY-MSGTY				X
	SY-MSGID				BRAIN
	SY-MSGNO				299
	SY-MSGV1				LRSDG_IOBJ_DB_READF40
	SY-MSGV2				REGULAR_IOBJ_GET_FOR_META
	SY-MSGV3
	SY-MSGV4
	SY-MODNO				2
	SY-DATUM				20150710
	SY-UZEIT				151746
	SY-XPROG				SAPCNVE
	SY-XFORM				CONVERSION_EXIT

Active Calls/Events

No.

Ty.

Program

Include

Line

Name

35

FORM

SAPLRSDG_IOBJ_DB_READ

LRSDG_IOBJ_DB_READF40

31

REGULAR_IOBJ_GET_FOR_META

34

FUNCTION

SAPLRSDG_IOBJ_DB_READ

LRSDG_IOBJ_DB_READU32

106

RSD_ALL_META_IOBJ_GET

33

METHOD