on 01-15-2013 6:05 AM
Dear All,
I am getting below error in sm21 on daily basis.
Database error: TemSe->XRTAB(4)->64 for table TST01 key \\SAPSID\sapmnt\SID\SYS\global\900JOBLG\0001X18254500X05216
Database error: TemSe->XRTAB(4)->64 for table TST01 key \\SAPSID\sapmnt\SID\SYS\global\900JOBLG\0001X09403700X32262
Database error: TemSe->XRTAB(4)->64 for table TST01 key \\SAPSID\sapmnt\SID\SYS\global\910JOBLG\0001X01513100X83226
I went to SP12 and performed consistency check and do not find any inconsistency also performed kernel upgrade still i am facing this error
Kindly help to solve this error.
System: ECC6 EHP4 ORACLE 10.2.0.4 OS WIN2008
Thanks
Tabrayz
Good Day
I suggest you to perform a Consistency Check of Spool Database.
Cheers
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tab,
Since this is not a space issue for TemSe, first of all perform cosistency check and delete all 'orphane' request.
User t-code SP12 --> TemSe Data Storage --> Consitency Check . This will run for a while based on your TemSe size. Delete all 'orphane' spool request.
Next use t-code SPAD --> Administration --> Check Consistency.
Check SM21 logs after these two consistency check.
Regards,
Dipam
Dear Dipam,
Thanks for your inputs, we have performed the steps as you mention
in the last step after running sp12 we went to spad and did a consistency check and out put is as below
25280 No object found in TST01
25299 No object found in TST01
25649 No object found in TST01
25696 No object found in TST01
26231 No object found in TST01
Can we go ahead and delete this from SPAD??
Thanks
Tabrayz
Hi Abdul,
Did you try to run the report RSTS0022 ?
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Ashutoash,
I did not try this report yet because in note 48400 its mention as
CAUTION:
You can use the report RSTS0022 to delete old TemSe objects. Execute this report with care. Only execute it if you know precisely what you are deleting. This report does not take into account dependencies between TemSe tables and other tables, so inconsistencies may occur.
Hence i am holding kindly let me know your inputs.
Thanks
Tabrez
Hi Abdul,
If you goto the directory \\SAPSID\sapmnt\SID\SYS\global\900JOBLG\
Can you go to the directory \\SAPSID\sapmnt\SID\SYS\global\900JOBLG\
and check the below file in 900JOBLG directory .check whether file exists or not.
and also the TST01 table , whether information about this file is there or not.
You can delete the files at os level which are 1 month or 2 month old.
Kindly check and revert.
With Regards
Ashutosh Chaturvedi
Hi Abdul,
Run the report RSTS0022 which will delete only the Tempse object and the header entry in TST01.
Note 48400 - Reorganization of TemSe and Spool
With Regards
Ashutosh Chaturvedi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi tabryz,
It seems that there are header entries in TST01 which seems to be inconsistent on file system.
Try by running report RSPO1043 to remove such inconsistencies.
Regards,
Divyanshu
R
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The Note 67055 - Explanation of syslog message xrtab(?)->? for ???? explains the reason for this behaviour.
Please check and confirm whether you are executing any report like RSPO1041 . If yes, please check the
Note 852141 - Large spool request cannot be deleted
I Hope it helps.
Thanks and Regards,
Vimal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
As well as I would suggest you to do the following:
Please do a consistency check of the BTC Processing System as follows:
1. Run Transaction SM65
2. Select Goto ... Additional tests
3. select these options: Perform TemSe check
Consistency check DB tables
List
Check profile parameters
Check host names
Determine no. of jobs in queue
All job servers
and then click execute.
4. Once you get the results check to see if you have any inconsistencies in any of your tables.
5. If there are any inconsistencies reported then run the "Background Procesing Analyses" (SM65 .. Goto ... Additional Tests) again.
This time check the "Consistency check DB tables" and the "Remove Inconsistencies" options.
6. Run this a couple of times until all inconsistencies are removed from the tables.
Make sure you run this SM65 check when the system is quiet and no other batch jobs are running as this would put a lock on the TBTCO table till it finishes. This table may be needed by any other batch job that is running or scheduled to run at the time SM65 checks are running.
As well as please check Note 48400 - Reorganization of TemSe and Spool
Please check and provide your feedback.
Thanks and Regards,
Vimal
Dear Vimal,
As per your suggestion i have performed all the steps please find below results.
Analysis Tool - Background Processing
********************************************************************************
Test: Determine all background-capable servers
********************************************************************************
Server name Host name
FNGPRD1_FNP_02 FNGPRD1
FNGPRD2_FNP_02 FNGPRD2
********************************************************************************
Test: Test TemSe functionality
********************************************************************************
==> TemSe test completed successfully
********************************************************************************
Test: Database table consistency test
********************************************************************************
==> released jobs with start time 'Date/Time' without TBTCS entries:
SAP_COLLECTOR_FOR_PERFMONITOR 07000100
SAP_COLLECTOR_FOR_PERFMONITOR 11002400
SAP_RSICFDLT 11002600
==> No entry found in TBTCO for the folllowing TBTCP entry:
EU_PUT 17452101
EU_REORG 17463701
==> all job contexts are consistent
==> All job spool IDs are consistent
********************************************************************************
Test: Check profile parameters
********************************************************************************
Server = FNGPRD1_FNP_02 , Date = 16.01.2013 , Time = 11:49:19
********************************************************************************
rdisp/btctime = 60
rdisp/wp_no_btc = 3
==> Server is configured correctly for background processing
********************************************************************************
Test: Check local host names against message server
********************************************************************************
Server = FNGPRD1_FNP_02 , Date = 16.01.2013 , Time = 11:49:19
********************************************************************************
Local host name = FNGPRD1
==> Local host name matches the name on the message server
********************************************************************************
Test: Determine no.of requests in background mode
********************************************************************************
Server = FNGPRD1_FNP_02 , Date = 16.01.2013 , Time = 11:49:19
********************************************************************************
==> No.of requests in background queue = 0
********************************************************************************
Test: Check profile parameters
********************************************************************************
Server = FNGPRD2_FNP_02 , Date = 16.01.2013 , Time = 11:49:18
********************************************************************************
rdisp/btctime = 60
rdisp/wp_no_btc = 3
==> Server is configured correctly for background processing
********************************************************************************
Test: Check local host names against message server
********************************************************************************
Server = FNGPRD2_FNP_02 , Date = 16.01.2013 , Time = 11:49:18
********************************************************************************
Local host name = FNGPRD2
==> Local host name matches the name on the message server
********************************************************************************
Test: Determine no.of requests in background mode
********************************************************************************
Server = FNGPRD2_FNP_02 , Date = 16.01.2013 , Time = 11:49:18
********************************************************************************
==> No.of requests in background queue = 0
Thanks
Tabrayz
Dear Vimal,
Most welcome!!
I followed your inputs
1. Run Transaction SM65
2. Select Goto ... Additional tests
3. select these options: Perform TemSe check
Consistency check DB tables
List
Check profile parameters
Check host names
Determine no. of jobs in queue
All job servers
and then click executed
But I did not find any inconsistency and in sm21 error still exists.
Thanks
Tabrez
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.