Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Weird Error Message - Transaction Terminated....

Former Member
0 Likes
1,784

Hi

I am running one job at the background and it has failed twice since morning giving this error message in system job log....I cant make out anything out of this any clues???

07:51:16 prd0ap02_P01_79 BTC 4 100 ZB_JB F6F TemSe object JOBLGX06594301X77660 was closed remotely

07:51:16 prd0ap02_P01_79 BTC 4 100 ZB_JB F61 TemSe input/output to unopened file

07:51:16 prd0ap02_P01_79 BTC 4 100 ZB_JB F61 TemSe input/output to unopened file

07:51:16 prd0ap02_P01_79 BTC 4 100 ZB_JB F71 Error in TemSe Management

07:51:16 prd0ap02_P01_79 BTC 4 100 ZB_JB R47 Delete session 001 after error 023

-


09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F62 Positioning error in a file for a TemSe object

09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F62 Positioning error in a file for a TemSe object

09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F62 Positioning error in a file for a TemSe object

09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F71 Error in TemSe Management

09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F3V Error 22 for write/read access to a file. File = /usr/sap/P01/SYS/global/100SP

OOL/00010000064625

09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F64 Unable to close TemSe object file

09:10:37 prd0ap02_P01_79 BTC 2 100 ZB_JB Q0E Signal 11 received by operating system

09:10:41 prd0ap02_P01_79 BTC 2 100 ZB_JB Q02 Stop Workproc 2, PID 1510907

09:11:35 prd0ap02_P01_79 BTC 2 Q01 Start Workproc 2, 2 times since system startup. PID 1528811

09:11:35 prd0ap02_P01_79 BTC 2 100 ZB_JB F6F TemSe object JOBLGX08170801X47537 was closed remotely

09:11:35 prd0ap02_P01_79 BTC 2 100 ZB_JB F61 TemSe input/output to unopened file

09:11:35 prd0ap02_P01_79 BTC 2 100 ZB_JB F61 TemSe input/output to unopened file

09:11:35 prd0ap02_P01_79 BTC 2 100 ZB_JB F71 Error in TemSe Management

09:11:35 prd0ap02_P01_79 BTC 2 100 ZB_JB R47 Delete session 001 after error 023

Thanks

Sameer

Hi

I am running one job at the background and it has failed twice since morning giving this error message in system job log....I cant make out anything out of this any clues???

07:51:16 prd0ap02_P01_79 BTC 4 100 ZB_JB F6F TemSe object JOBLGX06594301X77660 was closed remotely

07:51:16 prd0ap02_P01_79 BTC 4 100 ZB_JB F61 TemSe input/output to unopened file

07:51:16 prd0ap02_P01_79 BTC 4 100 ZB_JB F61 TemSe input/output to unopened file

07:51:16 prd0ap02_P01_79 BTC 4 100 ZB_JB F71 Error in TemSe Management

07:51:16 prd0ap02_P01_79 BTC 4 100 ZB_JB R47 Delete session 001 after error 023

-


09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F62 Positioning error in a file for a TemSe object

09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F62 Positioning error in a file for a TemSe object

09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F62 Positioning error in a file for a TemSe object

09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F71 Error in TemSe Management

09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F3V Error 22 for write/read access to a file. File = /usr/sap/P01/SYS/global/100SP

OOL/00010000064625

09:10:34 prd0ap02_P01_79 BTC 2 100 ZB_JB F64 Unable to close TemSe object file

09:10:37 prd0ap02_P01_79 BTC 2 100 ZB_JB Q0E Signal 11 received by operating system

09:10:41 prd0ap02_P01_79 BTC 2 100 ZB_JB Q02 Stop Workproc 2, PID 1510907

09:11:35 prd0ap02_P01_79 BTC 2 Q01 Start Workproc 2, 2 times since system startup. PID 1528811

09:11:35 prd0ap02_P01_79 BTC 2 100 ZB_JB F6F TemSe object JOBLGX08170801X47537 was closed remotely

09:11:35 prd0ap02_P01_79 BTC 2 100 ZB_JB F61 TemSe input/output to unopened file

09:11:35 prd0ap02_P01_79 BTC 2 100 ZB_JB F61 TemSe input/output to unopened file

09:11:35 prd0ap02_P01_79 BTC 2 100 ZB_JB F71 Error in TemSe Management

09:11:35 prd0ap02_P01_79 BTC 2 100 ZB_JB R47 Delete session 001 after error 023

Thanks

Sameer

5 REPLIES 5
Read only

Former Member
0 Likes
979

It seems to be a problem with the spool. Please check that the expired spools on the system are cleared.

Sudha

Read only

0 Likes
979

Sudha,

Our spool remains only for a week only.

Read only

former_member66264
Contributor
0 Likes
979

i have the same problem, did you find the rootcause?

Read only

0 Likes
979

I think the spool that was being created was more than 2GB, so there was no space on the server to accomodate. Talk to BASIS it might be the same case.

Read only

0 Likes
979

Appears to be a file system full.