on 10-06-2009 12:39 AM
While trying to print something from SAP we get a dump with the following error:
Error analysis
An I/O error occurred when calling the SAP spool system. This may be
due to an overflow in the spool database.
More detailed description of error: "dbrtab error in SpTSP02Insert "
Further information:
See below under "Spool error information".
How to correct the error
If the spool database has overflowed, you must perform a
reorganization.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"SPOOL_I/O_ERROR"
"SAPMSPAD " or "MSPADF30 "
"_ADMIN_LIST"
We have cleared most of our spool queue and job queue. We have run SP12 and cleared everything in there. After we run SP12 we can print one thing and then we get a dump. I clear SP12 again and can print one thing. If I try to print a 2nd thing I either get a dump or a GUI error stating:
PRD: SAP System Message:
Work process re-started, session terminated
We now can't MIGO.
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
SAP provided the answer using OSS notes 18674 and 48400.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill,
OK, I give up. What is MIGO? I cannot find any appropriate references. In the future, please use complete words instead of acronyms or lingo.
For your issue, I would also suggest taking a look at Notes 18674 and 48400.
Best Regards,
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Make sure you do check the consistency in SP12 and delete all the inconsistencies.
Did you also check if there are really old spool/Ouput requests in SP01.Among the the ones which are there is there a really big one. Have seen requests for 10,000 pages before.
Check for the dates. Your rerog job should have deleted them but double check.
Another thing to also check would be your global direcotry at OS level.
Make sur eyour Reorg Job for Jobs is also running.
Run RSBTCDEL and choose the time period and make sure to check the Force button and get rid of the logs.
This will make space in Global directory
Pravin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
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.