cancel
Showing results for 
Search instead for 
Did you mean: 

Maintainence Optimizer failing when tried to select ECC6 system

Former Member
0 Kudos

Dear All,

I have configured my Maintainance Opt according to guide. All bcsets were activated with warnings, but no errors.

I also maintained my ECC6 server in SMSY and generated RFC destinations + defined "Solution". But when I start MOP, select system ID, i.e. RTX in my case and click on continue, it gives me following error:

SMS:SAP System Message

SQL error 3127 occurred when accessing program SAP

I tried searching over net but to no avail. Any ideas please as this is urgent for support packs.

I am surely aware of reward points rule.

regards, Sean.

Accepted Solutions (1)

Accepted Solutions (1)

former_member185954
Active Contributor
0 Kudos

Hello Shantanu,

I think this error has more to do with the warnings you got while activating MOPZ.

Probably some function module/function group is not activated properly and you may have to activate it manually.

Have a look at the note:

SAP Note 1095700 - Error "GETWA_NOT_ASSIGNED" during activation of the BC Set

Although the above note is not related to your problem directly, it would give you some clues to your problem.

Regards,

Siddhesh

Former Member
0 Kudos

Dear All,

The problem was resolved by activating base components data capture. Actually I had made more configurations after my first mop transaction. Just created another one which works fine now.

regards, Sean.

Former Member
0 Kudos

Hello Sean,

How exactly were you able to activate base components data capture. I'm currently facing a similar problem, and I'd really appreciate if you could help me out.

Warm regards,

Glenn

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Shantanu,

Kindly provide more details of the error,

Till then check out the note 567866, this may solve the problem.

Regards,

Kaustubh.

Former Member
0 Kudos

Hi Guys,

Thanks for your response. In regard to error, that's all I got.

But yes, I have two dumps:

1. GETWA_NOT_ASSIGNED

Field symbol has not yet been assigned.

Error in the ABAP Application Program

The current ABAP program "SAPLDSWP_SSA_UTILITIES" had to be terminated because it has come across a statement that unfortunately cannot be executed.

You attempted to access an unassigned field symbol

(data segment 32773).

This error may occur if

- You address a typed field symbol before it has been set with

ASSIGN

- You address a field symbol that pointed to the line of an

internal table that was deleted

- You address a field symbol that was previously reset using

UNASSIGN or that pointed to a local field that no longer exists

- You address a global function interface, although the respective function module is not active - that is, is not in the list of active calls. The list of active calls can be taken from this short dump.

keywords:

"GETWA_NOT_ASSIGNED" " "

"SAPLDSWP_SSA_UTILITIES" or "LDSWP_SSA_UTILITIESU09"

"DSWP_SSA_GET_EWA_OVERVIEW"

User and Transaction

Client.............. 100

User................ "SHANTANU"

Language key........ "E"

Transaction......... " "

Transactions ID..... "826F1CDD2CA1F180A2450011258E14AB"

Program............. "SAPLDSWP_SSA_UTILITIES"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

Information on where terminated

Termination occurred in the ABAP program "SAPLDSWP_SSA_UTILITIES" - in

"DSWP_SSA_GET_EWA_OVERVIEW".

The main program was "RDSWP_SELF_DIAGNOSIS ".

In the source code you have the termination point in line 56

of the (Include) program "LDSWP_SSA_UTILITIESU09".

The program "SAPLDSWP_SSA_UTILITIES" was started as a background job.

Job Name....... "SM:SELFDIAGNOSIS"

Job Initiator.. "SHANTANU"

Job Number..... "0016160G"

-


2. A lot of DBIF_REPO_SQL_ERROR dumps at same timestamp as per SM21:

SQL error 3127 occurred when accessing program "SAPMS380 " part "LOAD".

How to correct the error

Database error text........: "ORA-03127: no new operations allowed until the

active operation ends"

Triggering SQL statement...: "SAPMS380 "

Internal call code.........: "[REPO/*/43/LOAD/SAPMS380 ]"

Client.............. 100

User................ "SAP*"

Language key........ "E"

Transaction......... "SOLUTION_MANAGER "

Transactions ID..... "61CE1CDD7DC5F15BA2450011258E14AB"

Program............. "????????????????????????????????????????"

Internal notes

The termination was triggered in function "db_info"

of the SAP kernel, in line 251 of the module

"//bas/700_REL/src/krn/runt/abload5.c#3".

The internal operation just processed is " ".

Internal mode was started at 20080508124554.

Internal call code.........: "[REPO/*/43/LOAD/SAPMS380 ]"

-


Now I'm trying to search, but in case anyone can corelate the issue to MOP, please help me out here. I performed RFC dest checks in SMSY and all are successfull.

I just have a little doubt although. We are using client 100 in our ECC6 systems. I have generated RFCs for client 100, 000 and001 only. Do I need it for 066 as well becuase right now i'm not config early watch reports.

PLease check.

regards, Sean.

Former Member
0 Kudos

Do you see any dump in ST22...

? If so please try to put some data from error analysis.