Networker

Re: [Networker] Once again: SAP client problem...

2003-08-04 05:38:14
Subject: Re: [Networker] Once again: SAP client problem...
From: "Renty, Bart" <bart.renty AT HP DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Mon, 4 Aug 2003 11:37:34 +0200
Frank,


This seems to be the problem that I discussed before on your thread "SAP
backup trouble"

>> In other words: It seemed that SAP is able to store and retrieve some
of its settings from the >> registry database. As you probably expect, i
found an entry under 
>> HKEY_LOCAL_MACHINE\SOFTWARE\SAP\B10\Environment
>> for TEMP and TMP which contained "%USERPROFILE%\Local Settings\Temp".

Are you sure that this solution will survive a reboot ?

We also tried different solutions, and found out that when SAP is
started, it writes out its environment variables to a registry key
(don't know if it is the same key which you're mentioning).  When it
later creates a child process, it reads out this registry to reproduce
the environment variables for the child process, but apparently forgets
about the USERPROFILE variable. This way it is causing the error message
because backint tries to write it to TMP, which is referencing
USERPROFILE.

If this was the same key, it might be that you solution is overwritten
again by SAP startup...?

Bart





-----Original Message-----
From: Renty, Bart 
Sent: donderdag 22 mei 2003 15:30
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] SAP backup trouble


Some time ago, we also got SAP logfile problems on Windows 2000 with SAP
610/620. The problem seems to be caused because backint tries to write
its logfile using the environment variable TMP, which isn referencing
the USERPROFILE variable on Windows 2000 (TMP = %USERPROFILE%\Local
Settings\Temp). We found out that any process (like backint) created by
SAP 610/620 is missing the USERPROFILE variable, and thus any use of the
TMP variable is stuck.

To know if this is your problem, check for the following message in
NSR\APPLOGS\backint*.log :

        Filename D:\usr\sap\S01\DVEBMGS00\work\%USERPROFILE%\Local
Settings\Temp\.nsr.backint.S01
        Backint exiting at Jan 22 11:25:01 with fatal error
        creating directive file: No such file or directory

SAP support claims this isn't an SAP problem , because SAP has no
problems at all ?! Legato claims this is not a Legato problem, because
it is SAP which should pass the USERPROFILE variable...

I finally could convice Legato to create an RFE (request for
enhancement) LGTpa53548, in order to replace the references in
backint.exe from TMP to TEMP. Because the TEMP symbol is NOT referencing
the USERPROFILE variable, I hope this would solve the problem.
 
The customer finally found a worksaround be redefining the TMP (eg. to
C:\TEMP) symbol prior to starting backint.  I don't have more details
how they achieved this (procedure or registry ?)

Earlier, he also found out that by creating the directory
"D:\usr\sap\S01\DVEBMGS00\work\%USERPROFILE%\" - thus exactly with the
"%USERPROFILE%", the backups also were succeeding.

Bart

HP Services 
Networker Support

-----Original Message-----
From: Frank Altpeter [mailto:f.altpeter AT BROADNET-MEDIASCAPE DOT DE] 
Sent: woensdag 21 mei 2003 16:50
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] SAP backup trouble


Hello!

(Don't wonder that i'm answering on behalf of Olaf, we're working
together on this problem).


Jody Gregersen wrote on 2003-05-21 10:40:53 -0400:
> This may be the log that is written in the /tmp directory.  If it is,
> you need to turn off the sticky bit on /tmp on the client (if your 
> client is running Unix).  To do this (in Unix) just chmod 777 /tmp.
Well, it's a Windows 2000 Server, so no sticky bit :-)

The temp dir is set to E:\TEMP und is available. The files nsrsapsv.cfg
an initB10.utl have been checked and we can't find anything suspicious
in them.

The output of a manual execution of "nsrsapsv -f
d:\oracle\b10\817\initB10.utl" is exactly the following:

C:\Program Files\nsr\bin>nsrsapsv -f d:\oracle\b10\817\initB10.utl
Backup Failed. Could not find the log file Backup Failed. Could not find
the log file
backup: 1053528567 failed.
backup: 1053528567 failed.

And the double lines are no mistake by my client :)



With kind regards,

        Frank Altpeter

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=