cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

STORAGE_PARAMETERS_WRONG_SET

Go to solution
Former Member

on ‎01-11-2008 3:27 PM

0 Kudos

In the solution manager 4.0 several runtime errors STORAGE_PARAMETERS_WRONG_SET are occuring:

-

Date

Time

App.Server

User

Client

Keep

Name of runtime error

Exception

Appl. component

Report

WP

Transaktions-ID

-

11.01.2008

14:03:21

gauri_SLM_27

DDIC

001

C

STORAGE_PARAMETERS_WRONG_SET

3

0E35C0DC82C7F1FDBD26000BCDFF367D

11.01.2008

12:01:16

gauri_SLM_27

DDIC

001

C

STORAGE_PARAMETERS_WRONG_SET

0

4B24C0DCE22EF195BD26000BCDFF367D

11.01.2008

09:05:22

gauri_SLM_27

DDIC

001

C

STORAGE_PARAMETERS_WRONG_SET

2

250BC0DCF7CFF184BD26000BCDFF367D

11.01.2008

06:56:31

gauri_SLM_27

DDIC

001

C

STORAGE_PARAMETERS_WRONG_SET

2

62FABFDC813BF1DEBD26000BCDFF367D

11.01.2008

04:58:06

gauri_SLM_27

DDIC

001

C

STORAGE_PARAMETERS_WRONG_SET

3

9EE9BFDC589FF1C3BD26000BCDFF367D

11.01.2008

02:54:13

gauri_SLM_27

DDIC

001

C

STORAGE_PARAMETERS_WRONG_SET

0

DAD8BFDC13F5F135BD26000BCDFF367D

-

Here's more details:

Runtime Errors STORAGE_PARAMETERS_WRONG_SET

Date and Time 11.01.2008 14:03:21

-

Short text

The system is configured incorrectly.

-

-

What happened?

The current program had to be terminated because of an

error when installing the R/3 System.

The program had already requested 1614147616 bytes from the operating

system with 'malloc' when the operating system reported after a

further memory request that there was no more memory space

available.

-

-

Error analysis

When the program was running, it was established that more

memory was needed than the operating system is able safely

to provide. To avoid a system crash, you must prevent this

situation from occurring.

-

-

System environment

SAP-Release 700

Application server... "gauri"

Network address...... "172.16.112.17"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "8x Intel 801586"

Character length.... 16 Bits

Pointer length....... 32 Bits

Work process number.. 3

Shortdump setting.... "full"

Database server... "GAURI"

Database type..... "ORACLE"

Database name..... "SLM"

Database user ID.. "SAPSR3"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Jun 11 2007 00:13:41"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "OCI_10201_SHARE (10.2.0.1.0) "

Patch level. 114

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

Memory consumption

Roll.... 1709536

EM...... 380461536

Heap.... 1614147616

Page.... 0

MM Used. 1981744448

MM Free. 11941488

-

-

User and Transaction

Client.............. 001

User................ "DDIC"

Language Key........ "E"

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

Transactions ID..... "0E35C0DC82C7F1FDBD26000BCDFF367D"

Program............. "SAPLSCCMSBI_STAT_EXTRACTORS"

Screen.............. "SAPMSSY7 3001"

Screen Line......... 3

Information on caller of Remote Function Call (RFC):

System.............. "SLM"

Database Release.... 700

Kernel Release...... 700

Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

Call Type........... "synchron and non-transactional (emode 0, imode 0)"

Inbound TID.........." "

Inbound Queue Name..." "

Outbound TID........." "

Outbound Queue Name.." "

Client.............. 001

User................ "DDIC"

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

Call Program........."SAPLE2E_FUNC"

Function Module..... "SMD_SSR_DATA"

Call Destination.... "NONE"

Source Server....... "gauri_SLM_27"

Source IP Address... "172.16.112.17"

Additional information on RFC logon:

Trusted Relationship " "

Logon Return Code... 0

Trusted Return Code. 0

Note: For releases < 4.0, information on the RFC caller are often

only partially available.

-

Noticed that the runtime error occurs by the user DDIC and the batch job E2E_EC_XID_0020217764 and program E2E_EXTRACTOR_CONTROLLER.

-

Job

Ln

Job CreatedBy

Status

Start date

Start time

Duration(sec.)

Delay (sec.)

-

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

15:05:04

33

4

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

14:05:04

608

4

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

13:05:04

0

4

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

12:05:03

7.110

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

11:05:03

0

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

10:05:03

6.991

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

09:05:03

1

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

08:05:03

0

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

07:05:03

7.236

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

06:05:03

0

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

05:05:03

6.693

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

04:05:03

0

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

03:05:03

6.789

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

02:05:03

0

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

01:05:03

6.569

3

E2E_EC_XID_0020217764

DDIC

Finished

11.01.2008

00:05:03

33

3

-

The batch job E2E_EC_XID_0020217764 is running with a 60 minutes frequency and when the 1st job is running longer then 60 minutes the 2nd job starts and encounters runtime error STORAGE_PARAMETERS_WRONG_SET and the following message appears in the spool output of the job:

11.01.2008 E2E: Extractor Controller 1

EC: 11.01.2008 07:05:03 UTC Extractor Controller started for SID XID

EC: 11.01.2008 08:05:03 CET Installation Number 0020217764

EC: Locked for System, not starting. Previous EC still running?

Job log overview for job: E2E_EC_XID_0020217764 / 06050300

The 1st job has the following job log entries:

Date Time Message text

11.01.2008 07:05:03 Job started

11.01.2008 07:05:03 Step 001 started (program E2E_EXTRACTOR_CONTROLLER, variant XID_0020217764, user ID DDIC)

11.01.2008 09:05:31 SQL: 11.01.2008 09:05:31 DDIC

11.01.2008 09:05:31 ALTER TABLE "/BI0/F0SMD_PI2H" ADD PARTITION

11.01.2008 09:05:31 "/BI0/F0SMD_PI2H0000000017" VALUES LESS THAN

11.01.2008 09:05:31 (0000000017 ) TABLESPACE "PSAPSR3"

11.01.2008 09:05:32 SQL-END: 11.01.2008 09:05:32 00:00:01

11.01.2008 09:05:32 SQL: 11.01.2008 09:05:32 DDIC

11.01.2008 09:05:32 ALTER TABLE "/BI0/F0SMD_PI2H" MODIFY PARTITION

11.01.2008 09:05:32 "/BI0/F0SMD_PI2H0000000017" REBUILD UNUSABLE

11.01.2008 09:05:32 LOCAL INDEXES

11.01.2008 09:05:32 SQL-END: 11.01.2008 09:05:32 00:00:00

11.01.2008 09:05:32 SQL: 11.01.2008 09:05:32 DDIC

11.01.2008 09:05:32 ANALYZE TABLE "/BI0/F0SMD_PI2H" PARTITION (

11.01.2008 09:05:32 "/BI0/F0SMD_PI2H0000000017" ) ESTIMATE STATISTICS

11.01.2008 09:05:32 SAMPLE 10 PERCENT

11.01.2008 09:05:32 SQL-END: 11.01.2008 09:05:32 00:00:00

11.01.2008 09:05:39 Job finished

Any idea how to avoid the runtime error STORAGE_PARAMETERS_WRONG_SET ?

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎01-14-2008 3:59 PM
0 Kudos

Here's the boot.ini:

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect /3GB

Show replies
Show replies
markus_doehr2
Active Contributor
‎01-14-2008 4:39 PM
0 Kudos

Well.. in that case you may be lost with a 32bit operating system. The activation needs more memory than a 32bit process can handle.

I see that you are using a 8way machine - if that is a dual core process you can install a 64bit operating system on that box and use the 64bit binaries - and all those (and subsequent problems) concerning that 32bit limitation will go away.

I´m sure that one can "make it work" somehow with tuning the memory settings just for this specific task and setting them back but you may get later other errors where you need to act again.

Check 996600 - 32 Bit platforms not recommended for productive NW2004s apps

Markus

Answers (6)

Answers (6)

Former Member
‎02-11-2008 8:38 AM
0 Kudos

Hi Vinayak P,

Problem is not solved, still got an customer message open at SAP.

When solved i will write this in the thread.

Gidion

Show replies
Show replies
Former Member
‎02-11-2008 7:46 AM
0 Kudos

Hi G. Stamp,

Pls let me know how did your problem has been solved.

Pls tell me. pls write in the same thread.

Thanks

Show replies
Show replies
Former Member
‎01-15-2008 10:15 AM
0 Kudos

Markus,

Thanks for your advice.

This dump is solved and for future an upgrade to 64bit OS will be planned.

Gidion

Show replies
Show replies
markus_doehr2
Active Contributor
‎01-14-2008 3:24 PM
0 Kudos

Your error is pretty "classical" on 32bit windows.

As you can see in the dump you are exhausting the maximum extended memory. Do you have the /3GB /USEVA:2600 parameter set in your operating systems boot.ini?

Markus

Show replies
Show replies
Former Member
‎01-14-2008 9:36 AM
0 Kudos

Hi Sri,

The thread 1229124 is about adjusting the ABAP code to improve the selection.

I am using the SAP ABAP program E2E_EXTRACTOR_CONTROLLER, only adjust that one on advice of SAP

Found note 44528 also before, but is applicable from release 30 to 45A and my system is on release 700.

Regards,

Gidion

Show replies
Show replies
Former Member
‎01-11-2008 3:57 PM
0 Kudos

Hi Stamp,

Plz check this thread.

In one of the sites, also the following info was given by Anupam...as well...

SAP Administration Questions Answers

What is the use of profile paramater ztta/roll_area?

The value specifies the size of the roll area in bytes. The roll area is one of several memory areas, which satisfies the user requests of user programs. For technical reasons, however, the first 250 KB or so of a user context are always stored in the roll area, further data

- up to the roll area limit ztta/roll_first,

- in the extended memory, up to the limit ztta/roll_extension or if extended memory is exhausted, then

- again in the roll area, until the roll area is full, then

- in the local process area, up to the limit abap/heap_area_dia or abap/heap_area_total or until the address space or the

swap space is exhausted.

Followed by termination with errors like STORAGE_PARAMETERS_WRONG_SET an error code, that points to memory bottleneck Minimum data transfer with context change; however, the increase helps to avoid problems (address space, swap space, operating system paging). *-- Anupam Sharma

Also there are many OSS Notes on this topic.

A good one -- Note 44528 - STORAGE_PARAMETERS_WRONG_SET

PLease check and let me know if they are helpful.

Award points for helpful answers.

Rgds,

Sri

Show replies
Show replies
Ask a Question