SAP - No logon possible after HSC

Michael Ebert

SAP - No logon possible after HSC
Cross-posted to SAPDB2OS390 and DB2-L.

DB2 V710 on zOS 1.4, SAP 4.6D with 6.20 kernel

Hello,

we've got a problem with a new SAP system. A week ago I created a new DB2
subsystem by doing a Homogeneous System Copy (HSC) from an existing small
SAP DB2 and then dropping every SAP DB. This empty system was then used by
the SAP admins to set up everything they needed on their side (application
servers and whatnot). After this was complete, we copied the Prod SAP DB
datasets to the new VCAT and I did everything that's needed to rename the
internal identifiers to the new VCAT. The new DB2 subsystem checks out ok
with every test (CHECKR, DSN1COPY CHECK, DSNTESQ pre-migration queries, IC
with CHECKPAGE...).

The problem is, it is not possible to logon to the new SAP. When I try, I
get a message on the bottom of the logon screen saying ">>>>>>>> DB Error
-0". After recycling the ICLI (and DB2 for good measure), I managed to
change this to -92551 and -92508 as well. I could not find any relevant
info on Google or the DB2 Online Library. When I restart the ICLI, try to
logon (resulting in the error), and stop the ICLI (to flush the log), then
the Log shows messages about ICLI clients connecting to DB2 and later of
ICLI threads being terminated but no error messages in between. If I
specify a client for which I'm not authorised, I get "name and/or password
incorrect". If I specify a non-existing client, I get "Client xxx is not
available". I do not know whether this info is retrieved from DB2.

Omegamon shows 8 ICLI threads connected to DB2 so the connection appears
ok.

According to the SAP Admin, it was possible to logon to the new system with
the SAP default ID which is valid only when no other users are defined.
Using this logon, they tried several things (I do not know details) which
resulted in various ICLI dumps and error messages. These related to
problems with creating indexes on MLICHECK ("object of the same name
already exists") and also many -204 SQLcodes (unknown tablename - for
tables like SAPR3.#LOB or DDNTT which definitely exist).

Currently the SAP Admins have sent a high-urgency OSS Note to SAP. In the
meantime, do you have any ideas what the problem might be or what else I
could check?

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Carol L Broyles

Re: SAP - No logon possible after HSC
(in response to Michael Ebert)
Michael,

Have you tried setting your ICLI_TRACE_LEVEL in the iclienv file to 3? If
so, what does the trace show? Also, have you installed a new SAPLICENSE
for your new system?

Carol

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service._______________________________________________________________

This electronic message contains information from MeadWestvaco
Corporation or subsidiary companies, which may be confidential,
privileged or otherwise protected from disclosure. The
information is intended to be used solely by the recipient(s)
named. If you are not an intended recipient, be aware that
any review, disclosure, copying, distribution or use of this
transmission or its contents is prohibited. If you have
received this transmission in error, please notify MeadWestvaco
immediately at [login to unmask email]
_______________________________________________________________________

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Michael Ebert

Re: SAP - No logon possible after HSC
(in response to Carol L Broyles)
Hi Carol, David,

the ICLI_TRACE_LEVEL is set to 0 but unfortunately I lack the permission to
change the ENV file. I will contact the MVS group, and the SAP Admins about
the license issue, but most likely I won't get a response before monday
(it's late friday evening here....).

There are no error messages in the MSTR. The previous HSC (+DB Drop) from
the small system was done only because I have a procedure for that and
didn't want to create a new one for creating a DB2 subsystem from scratch.
Todays HSC from PROD (actually from an offline dump taken a few days ago)
replaced the entire DB2 (BSDS, active logs, cat/dir, user data). I use a
cloning procedure that does not require any conditional restarts or the
like, so there is no question about RBA mismatches.

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: Carol L Broyles <[login to unmask email]>@IDUGDB2-L.ORG on
17-12-2004 15:42 EST

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec Re: SAP - No logon possible after
t: HSC









Michael,

Have you tried setting your ICLI_TRACE_LEVEL in the iclienv file to 3? If
so, what does the trace show? Also, have you installed a new SAPLICENSE
for your new system?

Carol

From: "Baldon, David" <[login to unmask email]>@LISTSERV.CAI.COM on
17-12-2004 15:04 CST

Please respond to SAPDB2OS390 - SAP for DB2 for OS/390 List
<[login to unmask email]>

Sent by: [login to unmask email]



To: [login to unmask email]


cc:






Subjec Re: SAP - No logon possible after
t: HSC








Hi Michael,
Are you seeing any error messages in the DB2 MSTR address space? Was the
high system RBA for the Prod SAP DB2 less than the high system RBA of the
small SAP DB2? I guess I don't understand the fundamental reason for doing
the HSC from a system other than the Prod SAP DB2 which is where your
"data"
is ultimately going to come from. I think you need to keep the DB2 catalog
and the "user" data in synch.

...David

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm