Skip to Content
0
Former Member
Jan 29, 2009 at 04:46 AM

RSUVSAVE Error

89 Views

Hi all,

While running our prepare in our production system, we are facing the below issue.

[prdb02:root] cat PSUVSAVE.ELG

-


See file JOBLOG.LOG in directory /usr/sap/put/log for the

job log, SYSLOG, and short dump of the

aborted job RSUVSAVE,

or use transactions SM37, SM21, and ST22.

[prdb02:root] cat PSUVSAVE.LOG

1 ETQ201XEntering upgrade-phase "JOB_RSUVSAVE" ("20090128224015")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '02', GwService = 'sapgw02'

4 ETQ399 Environment variables:

4 ETQ399 dbs_ora_schema=SAPR3

4 ETQ399 auth_shadow_upgrade=0

4 ETQ260 Starting batchjob "RSUVSAVE"

4 ETQ010 Date & Time: 20090128224015

4 ETQ260 Starting batchjob "RSUVSAVE"

4 ETQ230 Starting RFC Login to: System = "PR1", GwHost = "prdb02", GwService = "sapgw02"

4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC

4 ETQ234 Call of function module "SUBST_START_BATCHJOB" by RFC succeeded

4 ETQ233 Calling function module "SUBST_CHECK_BATCHJOB" by RFC

4 ETQ010 Date & Time: 20090128224021

4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded

4 ETQ239 Logging off from SAP system

1EETQ242 Error code "-1" during analysis of logfiles matching "RSUVSAVE\.PR1"

2EETQ262 Batchjob "RSUVSAVE" aborted

4 ETQ359 RFC Login to: System="PR1", Nr="02", GwHost="prdb02", GwService="sapgw02"

4 ETQ232 RFC Login succeeded

1EETQ204 Upgrade phase "JOB_RSUVSAVE" aborted with severe errors ("20090128224022")

[prdb02:root] ll RSUVSAVE*

RSUVSAVE* not found

[prdb02:root]

Not sure what this Error code "-1" during analysis of logfiles matching "RSUVSAVE\.PR1" error message means, we checked in st22 the dump says

A RAISE statement in the program "SAPLSUGI " raised the exception

condition "WRITE_FAILED".

Since the exception was not intercepted by a superior program

in the hierarchy, processing was terminated.

We are running the background job in an application server.

Searched for notes and also in google, but the help is not relevant

Can anyone help

Thanks

Senthil

[prdb02:root] cat JOBLOG.LOG

  • Joblog *******************************

20090128 224015 Job started

20090128 224015 Step 001 started (program RSUVSAVE, variant , user name DDIC)

20090128 224015 ABAP/4 processor: RAISE_EXCEPTION

20090128 224015 Job cancelled

  • Syslog *******************************

System Log: Local Analysis of prdb02 1

From date/time............. 28.01.2009 / 22:30:15

To date/time............... 28.01.2009 / 22:40:15

User.......................

Transaction code...........

Terminal...................

Task.......................

Problem class..............

Further restrictions.......

Sorted ? ................ SOFI

Pages with single entries 00000003

With statistics............

-


System Log: Local Analysis of prdb02 2

-


Time

User

Program

MNo

Text Date : 28.01.09

-


22:32:46

SAPMSSY1

D01

Transaction termination 00 148 ( )

22:33:12

SAPSYS

SAPMSSY8

R49

Communication error, CPIC return code 002, SAP return code 679

22:33:12

SAPSYS

SAPMSSY8

R64

> CPI-C function: CMINIT(SAP)

22:38:14

SAPSYS

SAPMSSY8

R49

Communication error, CPIC return code 002, SAP return code 679

22:38:14

SAPSYS

SAPMSSY8

R64

> CPI-C function: CMINIT(SAP)

Reading:

Number of records read......... 2777

Number of records selected..... 6

Old records skipped............ 2771

Further selection:

Number of records read......... 6

Number of records selected..... 5

Parameter records suppressed... 1

Number of records printed...... 5

End of system log

System Log: Local Analysis of prdb02 3

C o n t e n t s

-


Contents Page Start End

Selection criteria 1

2 28.01.2009 22:32:46 - 22:38:14

Contents 3

-


End of program -


  • Jobdump ******************************

Exception condition "WRITE_FAILED" raised.

-


What happened?

-


The current ABAP/4 program encountered an unexpected

situation.

-


What can you do?

-


Note the actions and input that caused the error.

Inform your SAP system administrator.

You can print out this message by choosing "Print". Transaction ST22

allows you to display and manage termination messages, including keeping

them beyond their normal deletion date.

-


Error anal.

-


A RAISE statement in the program "SAPLSUGI " raised the exception

condition "WRITE_FAILED".

Since the exception was not intercepted by a superior program

in the hierarchy, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

-

-


How to correct the error

-


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:

-


"RAISE_EXCEPTION"

"SAPLSUGI " or "LSUGIU08 "

"SUBST_WRITE_PROTOCOL"

or

"SAPLSUGI " "WRITE_FAILED"

or

"RSUVSAVE " "WRITE_FAILED"

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

-

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

-


System env

-


SAP Release.............. "46C"

Application server....... "prap04"

Network address.......... "165.88.161.167"

Operating system......... "HP-UX"

Release.................. "B.11.31"

Hardware type............ "ia64"

Database server.......... "prdb02"

Database type............ "ORACLE"

Database name............ "PR1"

Database owner........... "SAPR3"

Character set............ "en_US.iso88591"

SAP kernel............... "46D"

Created on............... "Jul 6 2008 21:43:48"

Created in............... "HP-UX B.11.23 U ia64"

Database version......... "OCI_920__OCI_7_API "

Patch level.............. "2410"

Patch text............... " "

Supported environment....

Database................. "ORACLE 8.0.5.., ORACLE 8.0.6.., ORACLE

8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 10.2.0.."

SAP database version..... "46D"

Operating system......... "HP-UX B.10, HP-UX B.11, , System build information:,

-


, LCHN : "

-


User, transaction...

-


Client.............. 000

User................ "DDIC"

Language key........ "E"

Transaction......... " "

Program............. "SAPLSUGI "

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

-


Information on where terminated

-


The termination occurred in the ABAP/4 program "SAPLSUGI " in

"SUBST_WRITE_PROTOCOL".

The main program was "RSUVSAVE ".

The termination occurred in line 77

of the source code of program "LSUGIU08 " (when calling the editor 770).

The program "SAPLSUGI " was started as a background job.

-


Source code extract

-


000470 LV_FILENAME = 'UNKNOWN.+++'.

000480 REPLACE '+++' WITH SY-SYSID INTO LV_FILENAME.

000490 ENDCASE.

000500 * create complete path to the logfile

000510 CALL FUNCTION 'STRF_SETNAME'

000520 EXPORTING

000530 DIRTYPE = LC_PATHTYPE

000540 FILENAME = LV_FILENAME

000550 SUBDIR = LC_SUBPATH

000560 IMPORTING

000570 FILE = EFNAME.

000580

000590 ELSE. EFNAME = IFNAME.

000600 ENDIF.

000610 MEMFILE = EFNAME.

000620 * export memfile to memory id mem_id.

000630 GV_MEM_FILE = MEMFILE.

000640 EXPORT MEMFILE GV_MEM_FILE TO MEMORY ID MEM_ID.

000650 CALL FUNCTION 'APPEND_PROTOCOL'

000660 EXPORTING

000670 ACCEPT_NOT_INIT = ' '

000680 CLOSE_FILE = 'X'

000690 CONDENSE = 'X'

000700 MASTER_LANGU = 'D'

000710 OPEN_FILE = 'X'

000720 TABLES

000730 XMSG = P_TAB

000740 EXCEPTIONS

000750 OTHERS = 1.

000760 IF SY-SUBRC >< 0.

-


> RAISE WRITE_FAILED.

000780 ENDIF.

000790 REFRESH P_TAB.

000800

000810 ENDFUNCTION.

[prdb02:root]