Hello,

I am upgrading SAP on Win2000/UDB, and the following error occurs
when I try to log into SAP. One of the SAP notes (#412677 for anybody
who is interested), indicates that for the main SAP user (<sid>adm),
the environment variables TEMP and TMP must be changed so that they
do not reference '%USERPROFILE%'. I did this, but the error persists.

From what I understand, the error CLI0157E indicates an inability
to read some temporary file.

Also, what is meant by SQL state=HY507?

Any other ideas or solutions?



C Mon Aug 18 16:46:38 2003
C *** ERROR in DB6PutLobPiece[dbdb6.c, 5118]
C &+*** DbSlLobPutPieceDB6( SQLPutData ): [IBM][CLI Driver]
CLI0157E Error opening a file. SQLSTATE=HY507 col=1
C &+***
C &+*** UPDATE "REPOLOAD" SET "LDATA" = ? WHERE "PROGNAME" = ?
AND "R3STATE" = ? AND "MACH" = ?
C &+*** cursor type=NO_HOLD, isolation=UR, cc_release=NO,
optlevel=0, query degree=1
C &+***
C &+*** Input SQLDA:

Hi Rhino,

Thanks for the reply. Let's forget about the 'SQLSTATE=HY507'
message. I would like to concentrate on the CLI0157E error
message.

As somebody more familiar with Oracle than DB2, a few
questions:

(i) In a previous thread discussing the message 'CLI0157E',
somebody suggested using the TEMPDIR directory in the
DBICLI.INI file to control the location and name of the
temp. file which seems to be causing this problem.
(I cannot see the contents of DBICLI.INI now). Does
it make sense to add a TEMPDIR entry to DBICLI (From
my home now, I cannot see if such an entry now exists).

SAP indicated that the problem stemmed from issues
associated with the TEMP and TMP environment variables,
but perhaps a TEMPDIR entry in DBICLI.INI overwrites
the environment variables.

(ii) The data is updated from CD-ROM files. Why the
need for temp. files? Could the problem stem from the
fact that DB2 perceives the Windows directory containing
the temp. file lacks sufficient disk space?

(iii) In a previous thread, somebody mentioned that the
problem may stem from previous temp. files that have
not been cleaned up. Could this be case? If so, what
are the names of the temp. files that I should erase?

(iv) I have searched Google with 'CLI0157E', but I have
not found much. Does anybody recommend any Websites
describing this problem in greater detail?



Thanks in Advance,
SAP BASIS Consultant


C Mon Aug 18 16:46:38 2003
C *** ERROR in DB6PutLobPiece[dbdb6.c, 5118]
C &+*** DbSlLobPutPieceDB6( SQLPutData ): [IBM][CLI Driver]
CLI0157E Error opening a file. SQLSTATE=HY507 col=1
C &+***
C &+*** UPDATE "REPOLOAD" SET "LDATA" = ? WHERE "PROGNAME" = ?
AND "R3STATE" = ? AND "MACH" = ?
C &+*** cursor type=NO_HOLD, isolation=UR, cc_release=NO,
optlevel=0, query degree=1







"Rhino" <rhino1 (AT) NOSPAM (DOT) sympatico.ca> wrote

created; if you're using an extender, this may well be the case.

The SQLSTATE message is from ODBC (or CLI) [SQLStates are defined by X/Open
/ ISO]. HY states reflect environmental conditions. In general, the SQLState
is a normed equivalent of the SQL message, it means the same, the text of
the message seems clear enough to me.

Given the SAP recommendation (and I do not know SAP) I would recommend your
following their guideline. Aim all of the user profile TMP, TEMP, TMPDIR,
DB2TEMPDIR and DB2DXXTEMP environment variables (where existent, ignore the
rest) at a local drive, ensuring that the relevant user has full control on
the directory. Do this for all applicable users (the instance owner,
extender owner and SAP owner). Ensure that TEMP and/or TMP is also defined
as a system environment variable, and satisfy the above conditions. Repeat
for TEMPDIR in db2cli.ini, if present. Finally, reboot to ensure that the
services pick up the change (the SCM does not reread the registry once the
system has been booted).

"SAP BASIS Consultant" <basis_consultant (AT) hotmail (DOT) com> wrote