RE:[sap-basis] We can not run batch jobs (sm37)
Posted by
Admin at
|
Share this post:
|
|
0 Comments
 | Posted by Al Fournier (SAP Basis Administrative Staff) on Mar 10 at 9:59 AM |  Mark as helpful |
Glad to have helped. Please go back to the System copy guide and make sure
you have performed the post copy steps to prevent any other copy related
issues from occurring.
From: acicuno via sap-basis [mailto:sap-basis@Groups.ITtoolbox.com]
Sent: Wednesday, March 10, 2010 8:46 AM
To: Fournier, Albert - 1140 - MITLL
Subject: RE:[sap-basis] We can not run batch jobs (sm37)
Posted by acicuno
on Mar 10 at 8:48 AM
<http://it.toolbox.com/api/ContentVote/3362021/1/1 /> Mark this reply as
helpfulMark as helpful
Dear Al Fournier, my friend ... you are right... It works!
Thanks you very much for you gurus... again... this forum is great !
---------------Original Message---------------
From: acicuno
Sent: Tuesday, March 09, 2010 1:14 PM
Subject: We can not run batch jobs (sm37)
> SAP 4.6c
> Windows 2003 SP2 64 bits
> MS SQL 2005 Sp2 64 bits
>
> Hello gurus
> We have a problem, after system copy (attach-detach) Productive to Test,
we can not run batch jobs (sm37)
> because the following message is showed:
>
> Error reading job log
> Message no. BT 167
>
> Diagnosis
> The background processing system was unable to read the job log named in
the message.
>
> This message suggests that there is a problem with the TEMSE storage
system of the SAP System. The TEMSE storage system is a repository for
temporary R/3 objects, such as job logs and spool requests. Job logs are
always stored in the TEMSE as operating system files.
>
> This error occurs if the TEMSE system is not able to find or access the
file that contains the text of the job log that you requested. Possible
causes for the loss or unavailability of the job log include the following:
>
>
>
> So we want to fix and run tx sp12 but another error appear:
>
>
>
> ABAP runtime errors DBIF_RSQL_SQL_ERROR
> SQL error 9105 occurred when accessing table "TST01 ".
>
>
>
> At file dev_w0 we have:
>
> C Tue Mar 09 13:20:02 2010
> C HandleOledbError [RpcExec,line 22204]: Error/Message: (err 9105, sev 0),
The provided statistics stream is corrupt.
> C RpcExec failed. HR 80040e14 DBSL retcode 99. proc:
[Y8R40000001K3993149TST01ut01]
> C DbSlRead - Error 99 (dbcode 9105) on open
> C DbSlRead - <Y8R40000001K3993149TST01ut01>
> C DbSlRead - Error 99 (dbcode 9105) on fetch
> C DbSlRead - <Y8R40000001K3993149TST01ut01>
> B ***LOG BY4=> sql error 9105 performing SEL on table TST01 [dbtrtab 6295
]
> B ***LOG BY0=> The provided statistics stream is corrupt. [dbtrtab 6295 ]
> C HandleOledbError [RpcExec,line 22204]: Error/Message: (err 9105, sev 0),
The provided statistics stream is corrupt.
>
>
> Thank you for your time
__.____._ you have performed the post copy steps to prevent any other copy related
issues from occurring.
From: acicuno via sap-basis [mailto:sap-basis@Groups.ITtoolbox.com]
Sent: Wednesday, March 10, 2010 8:46 AM
To: Fournier, Albert - 1140 - MITLL
Subject: RE:[sap-basis] We can not run batch jobs (sm37)
Posted by acicuno
on Mar 10 at 8:48 AM
<http://it.toolbox.com/api/ContentVote/3362021/1/1 /> Mark this reply as
helpfulMark as helpful
Dear Al Fournier, my friend ... you are right... It works!
Thanks you very much for you gurus... again... this forum is great !
---------------Original Message---------------
From: acicuno
Sent: Tuesday, March 09, 2010 1:14 PM
Subject: We can not run batch jobs (sm37)
> SAP 4.6c
> Windows 2003 SP2 64 bits
> MS SQL 2005 Sp2 64 bits
>
> Hello gurus
> We have a problem, after system copy (attach-detach) Productive to Test,
we can not run batch jobs (sm37)
> because the following message is showed:
>
> Error reading job log
> Message no. BT 167
>
> Diagnosis
> The background processing system was unable to read the job log named in
the message.
>
> This message suggests that there is a problem with the TEMSE storage
system of the SAP System. The TEMSE storage system is a repository for
temporary R/3 objects, such as job logs and spool requests. Job logs are
always stored in the TEMSE as operating system files.
>
> This error occurs if the TEMSE system is not able to find or access the
file that contains the text of the job log that you requested. Possible
causes for the loss or unavailability of the job log include the following:
>
>
>
> So we want to fix and run tx sp12 but another error appear:
>
>
>
> ABAP runtime errors DBIF_RSQL_SQL_ERROR
> SQL error 9105 occurred when accessing table "TST01 ".
>
>
>
> At file dev_w0 we have:
>
> C Tue Mar 09 13:20:02 2010
> C HandleOledbError [RpcExec,line 22204]: Error/Message: (err 9105, sev 0),
The provided statistics stream is corrupt.
> C RpcExec failed. HR 80040e14 DBSL retcode 99. proc:
[Y8R40000001K3993149TST01ut01]
> C DbSlRead - Error 99 (dbcode 9105) on open
> C DbSlRead - <Y8R40000001K3993149TST01ut01>
> C DbSlRead - Error 99 (dbcode 9105) on fetch
> C DbSlRead - <Y8R40000001K3993149TST01ut01>
> B ***LOG BY4=> sql error 9105 performing SEL on table TST01 [dbtrtab 6295
]
> B ***LOG BY0=> The provided statistics stream is corrupt. [dbtrtab 6295 ]
> C HandleOledbError [RpcExec,line 22204]: Error/Message: (err 9105, sev 0),
The provided statistics stream is corrupt.
>
>
> Thank you for your time
Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Al FournierSAP Basis Enthusiast
Contributed 100 posts in a group to earn a Bronze Achievement
In the Spotlight
55% of IT Pros Use Social Media to Advance Their Careers. See the Survey Results
View this thread online
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
_.____.__ 
