Switching spool destination to file system

[Former Member]

Hi,

We are getting the spool errors below in the system log SM21. To avoid

writing to spool logs to database we changed the parameter

rspo/store_location = G. Spool is being written, but we still have the

problem. We are running the spool and TemSe consistency checks daily.

Please advise how we can completely avoid using databse for spool

logs. Thanks, Abdul

System Logs:

OPERATION MODES: Switch to operation mode normal_day triggered

SQL error 12571. Work processes in reconnect status

Database error: TemSe->XRTAB(0)->1 for table TST01 key

retry creation JOBLGX btctlgow216

Database error: TemSe->XRTAB(0)->1 for table TST01 key [100]

JOBLGX23572401X87963,1

retry creation JOBLGX btctlgow216

Database error: TemSe->XRTAB(0)->1 for table TST01 key [100]

JOBLGX23572401X87963,1

retry creation JOBLGX btctlgow216

Database error: TemSe->XRTAB(0)->1 for table TST01 key [100]

JOBLGX23572401X87963,1

Failed to create log for job SWFSLSDLEX #00024771000########ﵝŚ##03###ᒥ

Job SWFSLSDLEX

Failed to read status entry for job SWFSLSDLEX

Job SWFSLSDLEX

SQL error 12571. Work processes in reconnect status

Database error: TemSe->XRTAB(0)->1 for table TST01 key

retry creation JOBLGX btctlgow216

Database error: TemSe->XRTAB(0)->1 for table TST01 key [100]

JOBLGX02552402X01262,1

retry creation JOBLGX btctlgow216

Database error: TemSe->XRTAB(0)->1 for table TST01 key [100]

JOBLGX02552402X01262,1

retry creation JOBLGX btctlgow216

Database error: TemSe->XRTAB(0)->1 for table TST01 key [100]

JOBLGX02552402X01262,1

Failed to create log for job ZMR_RSWUWFMLEC

#30024737000########ﵝŚ##03###ᒥ

Job ZMR_RSWUWFMLEC

Failed to read status entry for job ZMR_RSWUWFMLEC

Job ZMR_RSWUWFMLEC

SQL error 12571. Work processes in reconnect status

Database error: TemSe->XRTAB(0)->1 for table TST01 key

retry creation JOBLGX btctlgow216

Database error: TemSe->XRTAB(0)->1 for table TST01 key [100]

JOBLGX11572500X07676,1

retry creation JOBLGX btctlgow216

Database error: TemSe->XRTAB(0)->1 for table TST01 key [100]

JOBLGX11572500X07676,1

retry creation JOBLGX btctlgow216

Edited by: Abdul Rahim Shaik on Jun 26, 2008 5:14 PM

[Former Member · Accepted solution]

hi

Please try this:

Check the tcode SP12-->consistence check

Run tcode SP12 and do a TST01 consistency check and delete all records with errors.

[Former Member · Accepted solution]

Hi,

We are running SP12 consistency checks as part of the daily health checks.

My idea is to stop writing any logs to TST01 and write all the relevant logs to the filesystem. For this reason, I have applied the parameter rspo/store_location = G. The batch job logs, spool etc are being written now to the file system. However, the TST01 errors are again reported in SM21.

Any guesses?

Thanks,

Abdul

[former_member185954 · Accepted solution]

Hello,

Since you have switched to a new storage location, these inconsistencies would occur initially.

Check the following link to run the consistency check properly

http://help.sap.com/saphelp_47x200/helpdata/en/fc/04ca3bb6f8c21de10000000a114084/frameset.htm

Regards,

Siddhesh

[former_member59574]

Hello,

What your error means>

TemSe->XRTAB(0)->1 for table TST01

0 - Function: 0 RT_READ_ONLY

1 - Return code: 1 Sql error

See SAP Note 48400 Reorganization of TemSe and Spool

Snip from NOTE>>

IMPORTANT:

There are two fundamentally different consistency checks: the TemSe and consistency checks specific for the respective object type (spool, background, input and so on).

Neither of the two checks contains the other check, which means you must use BOTH checks!

The TemSe consistency check checks the header entry in table TST01 and the corresponding object for ALL TemSe objects. The spool consistency check, for example, also checks the entries in tables TSP01 and TSP02, but only the spool objects are checked. For background input logs, see Note 175596.

A. TemSe consistency check

1. Online:

Transaction SP12 (menu path see above)

-> TemSe database -> Consistency check

B. Spool consistency check

1. Online

Transaction SPAD (menu path, see above)

-> Consistency check (as of Release 4.X: Administration ->

-> Consistency check of spool database

<<

I am doing this check this way>

run both check, save output at file, nothing delete.

After e.g. 30/minute or 1 hour run check again, compare result and delete only those which match, those should be inconsistencies.

Peter

[Former Member]

Thanks everyone for your response so far.

I am not looking for suggestions on how to run spool & temse consistency checks.

I am looking for suggestions how to avoid these errors " even after I have changed the spool storage location to file system."

Any pointers?

Regards,

Abdul

[former_member59574]

Hi,

How to avoid this problem?

You need to solve inconsistencies in or between the tables of the Spool and/or TemSe

So re-run consistencies check and do it when workload is low with at least 30 minutes delay, then delete those which are same.

Peter

[nelis]

Hi Abdul,

Does you system consist of more than one instance ? ..if so have you made sure to mount your global directory centrally on all instances ? As the parameter documentation says "error free spool operation is not possible without this".

Regards,

Nelis

[Former Member]

Hi,

We have a single instance only.

Regards,

Abdul

[former_member185954]

Hello,

I think you cannot totally avoid these errors. If you configure the standard job to do Job reorgs, you can limit these errors.

Regards,

Siddhesh

[Former Member]

Hi,

Thanks for your responses so far.

My main question is: WHY AM I GETTING THESE ERRORS EVEN WHEN I HAVE CHANGED THE SPOOL DESTINATION TO FILE SYSTEM? SPOOL DESTINATION IS NOT THE DATABASE, SO I SHOULDNT BE GETTING TST01 TABLE ERRORS.

Regards,

Abdul

[former_member185954]

Hello Abdul,

There is no need for 'Flaming Text'.

Every TemSe object consists of a header entry in table TST01 and the actual object. This can be stored in the file system (for example, job logs) or in table TST03 (for example, HR data).

So, TST01 continues to hold header level data, so it stays in the database.

Only TST03 data is stored in the filesystem.

Field DLOCAT in TST01 table dictates where the object resides.

Try and check both tables TST01 and TST03.

Regards,

Siddhesh

[nelis]

Abdul,

The answer is simple, these tables TSP01 and TST01 are still required for administration irrespective of whether you are spooling data in database or the file system.

Nelis

[former_member59574]

Hello,

It is really complicated to understand the whole concept, but keep in mind that>

setting up storage location on file system you will only store data on the file system, but TemSe objects are still on db.

So at the end, solution is run consistencies check as was mentioned above at least 2 time between 30 minutes, but when your system is "quite" without big load.

Delete only inconcistencies with match; because if you delete all probably you will get more inconcestencies then before; e.g. imagine if "job peter" is running and doing some TemSe object; but during this time you run concistencies check and delete my "object" ; job peter will have TemSe info inconcistencie

Peter