Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 9063

Error EXPORT_TOO_MUCH_DATA

$
0
0

I have en error in ST22 EXPORT_TOO_MUCH_DATA.

 

The current ABAP program "CL_SWNC_COLLECTOR_DB==========CP" had to be terminated because one

of the statements could not be executed at runtime.

 

I heard that SAP_COLLECTOR_FOR_PERFMONITOR job must be scheduled by the DDIC user.

My job runs under ADMIN user, but it DEV and QAS system it works good for a long time.

 

System info:

ParameterValue
OSRHEL 6.5
SAP BASIS 7.31 SP6 (SAPKB73106)
Oracle11.2.0.3
Kernel720 SP 401
SystemEWM

 

 

So it is SP6 and note 1283931 can't be implemented. Also I found that saposcol doesn't work. I think that this error and saposcol are related.

I tried to start it manually from ST06, from OS - nothing hapaned. Saposcol starts for 10 seconds and shuts down again. I tried to clean, kill and start saposcol. I think there are a lot of data accumulated while saposcall have not been working.

 

Collector PID       : 17101 (42cd)

Collector           : running

Start time coll.    : Wed Dec 25 11:48:03 2013

 

 

Collector PID       : 17101 (42cd)

Collector           : not running (process ID not found).

Start time coll.    : Wed Dec 25 11:48:03 2013

 

If found this message in dev_coll log:

*** buffer overflow detected ***: /usr/sap/hostctrl/exe/saposcol terminated


I tried to remove file and start saposcol again:

 

Could you please check whether "saposcol" is running, check the version  "saposcol -v"

$ saposcol -v

Update if available

To update saposcol, first stop saposcol and remove the coll.put file:

1) saposcol -kc

2) rm /usr/sap/tmp/coll.put

Then restart the new saposcol:

3) saposcol -l


It doesn't help.


What can I do ?

Thanks a lot for answers.


 










Viewing all articles
Browse latest Browse all 9063

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>