Hello Bart,

please notice, that this is

A) a mailing list about the database SAP DB not the database ORACLE
B) not a mailing list for support of SAP customers, because SAP has set up support 
structures and systems for that purpose, that should match your support needs much 
better than this mailing list.

Regarding your question. What about setting USERPROFILE to an adequate value in the 
system environment or wrapping BRBACKUP in a batch file or program, that sets 
USERPROFILE if it is not set already and calling the original BRBACKUP after that?

To justify this post on this list, another solution would be of course to dump Oracle 
and the NetWorker SAP Module and switch to SAP DB, as we have a working backup connect 
to NetWorker, based on NetWorkers standard command line tools save, recover and 
mminfo. 

Best Regards,
Tilo Heinrich
SAP Labs Berlin




-----Original Message-----
From: Renty, Bart [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 27. Februar 2003 11:41
To: [EMAIL PROTECTED]
Subject: SAP backint backups on Windows 2000 failing to write logfile to
...%USERPROFILE%... (Networker)


Hello,

We have a problem with SAP backups to our Networker backup server.
The problem seems to be related to the TMP/TEMP/USERPROFILE variables on Windows 2000 
: 
backint tries to write its logfile to a location ...%USERPROFILE%...
As the backup isn't running in a user context, it hasn't the variable USERPROFILE 
defined, and the backup is failing.

Because the error message comes from BACKINT, trying to open a faulty directory, we 
suppose the problem or solution should be within backint.exe, or in the way it is 
called.  As the BACKINT.EXE is provided by legato, we suppose that it is up to Legato 
to tell us how me must resolve this problem.
Although Legato claims (despite our Premium support contract) that this is an SAP 
problem.  After 1 month of discussions, they even seem to have no 
SAP/Win2000/Networker configuration available to test these things out.  
On the other hand, SAP claims it is a Legato problem...

The problem :

The backups are sheduled via SAPDB (DB13), where BRBACKUP immediatly calls Networker's 
BACKINT image.
(for Networker specialists : the backups are NOT scheduled via Networker's 
nsrsapsv.exe).
In the logfile we can see that BACKINT.EXE is called as 
        'backint -u S01 -f backup -i D:\oracle\S01\sapbackup\.bdjuoegt.lst -t file -p 
D:\oracle\S01\817\DATABASE\initS01on.utl -c' 
which fails with an error 'Unable to open 
D:\usr\sap\S01\DVEBMGS00\work\%USERPROFILE%\Local Settings\Temp\\backintS01.log' 
because it hasn't the variable USERPROFILE defined :

BR315I 'Alter tablespace SYSTEM begin backup' successful
BR280I Time stamp 2003-01-20 14.09.39
BR229I Calling backup utility...
BR278I Command output of 'backint -u S01 -f backup -i 
D:\oracle\S01\sapbackup\.bdjuoegt.lst -t file -p 
D:\oracle\S01\817\DATABASE\initS01on.utl -c':
Unable to open D:\usr\sap\S01\DVEBMGS00\work\%USERPROFILE%\Local 
Settings\Temp\\backintS01.log as log file.
Backint exiting at Jan 20 14:09:39 with fatal error
Open log file: No such file or directory
BR280I Time stamp 2003-01-20 14.09.39
BR279E Return code from 'backint -u S01 -f backup -i 
D:\oracle\S01\sapbackup\.bdjuoegt.lst -t file -p 
D:\oracle\S01\817\DATABASE\initS01on.utl -c': 2
BR232E 0 of 13 files saved by backup utility
BR280I Time stamp 2003-01-20 14.09.39
BR231E Backup utility call failed
BR280I Time stamp 2003-01-20 14.09.42
BR317I 'Alter tablespace PSAPROLL end backup' successful

If we create the directory "D:\usr\sap\S01\DVEBMGS00\work\%USERPROFILE%\"   (thus 
exactly with "%USERPROFILE%), the backups are succeeding, but we wish to have a more 
transparant solution.

Most probably backint builds the directory using the TMP or TEMP symbols, this is why 
it worked perfectly on NT4, but no more on Windows 2000.

In an SAP manual, I found some information on Networker Backups, which might be 
related :
- DBMCLI command to define variables (like TMP and TEMP)
- variable NSR_ENV to give more parameters
- backint -o to define the output
However I can't find anything about these in the Networker manuals...

As I don't know anything about SAP, is there anybody who can help me how to resolve 
this (stupid) problem...?

Is there anybody using SAPDB DB13 backups successfully on Windows 2000 ?

Thanks for any help,

Bart

PS: we're using         Windows 2000 
                SAP V6.10 
                Oracle 8.1.7.4.1 
                Networker V6.2 on Client and V6.0.1 on the server 
                Networker SAP Module V2.1-001




_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to