Ansicht
Dokumentation
06408 - SPAM 46B/032 update error
ROGBILLS - Synchronize billing plans CPI1466 during BackupThis documentation is copyright by SAP AG.
SPAM 46B/032 update error
Dear Betsy,I've had the same problem (but on 4.6C).
I had to go back from R3trans version 1041 to R3trans version 963.
But I recently managed to implement spam with the newest r3trans patch.
Did you aply also the r3trans patch to PRD, and was it the most current?
Good luck,
Paul Hoogendoorn
"Betsy Strebe" <bstrebeZt...>
06-06-2002 21:23
Please respond to SAP on System i
To: DoNotReply@consolut.eu
cc:
Subject: SPAM 46B/032 update error
I am having a problem applying a 46B SPAM update 32 in PRD. DEV and TST
went just fine. The SPAM update in PRD hung and I had to cancel the job -
this may have caused even more problems. I have looked through SAP Notes
and our group's messages and nothing I can think of works. Here is where
I
sit:
DEV (our name is VGR), and TST reside on the same LPAR. PRD is on a
separate LPAR. The transport domain is VGR, and I have check the
/usr/sap/trans link on PRD to make sure it points point through
QfileSvr.400. All three systems are at 4.6D kernel patch 1017.
SPAM update aborts in PRD with the message:
The following entries will help you analyze the problem:
- Error in step: DISASSEMBLE
- Cause of error: CANNOT_CREATE_COFILE
- Return code: 7
- Error message: Support Package: SAPKD00030
where ...
o CANNOT_CREATE_COFILE: The cofile could not be created from the
corresponding data file. Possible causes of error:
- The data file is not available or was not disassembled. Check
the settings (Menu: Extras->Settings) if the option 'Recreate
the data files' is switched on.
- The <sys>adm has not write authorization for the directory
/usr/sap/trans/cofiles.
I have checked the settings and the option to recreate is checked. So I'm
thinking it must be an authorization problem.
The SLOG is reporting this error:
HALT 20020606104155
ERROR: /usr/sap/trans/sapnames/ : cant open
: Specified target is a directory.
ERROR: EXIT(16) -> process ID is: 774
I have checked the profiles on both systems, I can log on the PRD system
as
PRDOFR and access and open QfileSvr.400/PHXV0/usr/sap/trans/sapnames just
fine on the transport domain (VGR) system. The RFC connections look good
(STMS transports work fine), the RFC connection check in SPAM works okay.
STMS passes all the connection tests.
Any ideas on why I'm having problems with SAPNAMES? I am really stumped.
thanks in advance,
Betsy Strebe
Manager, Information Technology
Trinchero Family Estates
Office: 707-963-5928 ext. 2439
Cell: 707-529-4305
Fax: 707-963-9264
e-mail: bstrebeZt...
web: www.tfewines.com
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
[Non-text portions of this message have been removed]
Durban Tours - Südafrika Safari
BAL_S_LOG - Application Log: Log header data CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.
Length: 4091 Date: 20240602 Time: 212558 sap01-206 ( 3 ms )
