CPF9897 tp issue after 720 to 721 kernel upgrade

[Former Member]

Hi,

I replaced a ECC 7.0 system kernel that was 720 nonEXT unicode patch 800 with 721 nonEXT unicode patch 624 according to the note 1097751 section 6.  Saphostagent was also updated beforehand from 720 to 721 patch 12. After that the system started and SGEN was run, however the TP is reporting errors on the domain controller (system that was upgraded) as follows: The APYSIDKRN upgrade and system was started as DEVADM. The log says Switch to DEVOFR failed ?

This is tp version 380.40.04 (release 721, unicode enabled)

ERROR: Connect to DEV failed (20160330184032, probably wrong environment

Wed Mar 30 18:40:31 2016

DlLoadLib() success: dlopen("/usr/sap/DEV/SYS/exe/run/dbdb4slib.o”), hdl 0

DB4 SQL Reparse Activated

dbsldb4utl:sappfpar(DEFAULT.PFL): dbs/db4/driver_type=

dbsldb4utl:sappfpar(DEFAULT.PFL): dbs/db4/xdn_port=

Wed Mar 30 18:40:32 2016

dbsldb4utl:sappfpar(DEFAULT.PFL): dbs/db4/xdn_trace_file=

as4IsHostLocal: SAPDBHOST 'sapdev' is local

dbsldb4utl:sappfpar(DEFAULT.PFL): dbs/db4/use_lock_queue=

dbsldb4utl:sappfpar(DEFAULT.PFL): dbs/db4/sql_deflate_table=

  *** ERROR => RetrieveMessage: Unable to retrieve message description for

  *** ERROR => Call to _GetAuthDB4(DEVOFR    ) failed

  Exception text could not be retrieved: CPF9897

  *** ERROR => Switch to DEVOFR     failed.

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0232

Check Transport Tool

RFC Link  tp was started successfully

Tp Version 380.40.04

DB connect Link to database failed

Offline call  connect failed

Thanks

Michael

[Former Member]

I've also checked these suggestions from a 2013 post with the same symptoms:

1)  In /usr/sap/DEV/SYS/exe/run  and in /usr/sap/DEV/SYS/exe/run/uc there is

.ilelibSAPDEVIND

(Also under the directory /usr/sap/DEV/SYS/exe/run_sec I have some .txt STMF files;  ticket and Ver555.pl24 from 2008 which is a SAPCRYPOLIB.)

2)  DBCON table in R3DEVDATA s empty

[rdiger_hckel]

Hello Michael,

have you checked these two things?

1.) Is the content of the directory /usr/sap/DEV/DV.../exe the same as in

/usr/sap/DEV/DV.../exe_ (if it exists)

2.) Are you already using the "new user concept"? What is the value of the environment variable:

WRKENVVAR ENVVAR(CLASSICUSERCONCEPT)

More information on the new user concept can be found here:

1149318 - User concept conversion using the tool CONVUSRCPT

Kind regards

Rüdiger Höckel

apetito AG

[Former Member]

Hello Rüdiger,  Thank you,

1) There is not an exe directory under /usr/sap/DEV/DVEBMGS00, only data, igs, log, sec and work.  Under /usr/sap/DEV/SYS/exe there is run directory which is SYMLNK to /sapmnt/DEV/exe and a run_sec directory as described.   There are 4 other SIDs (systems are ABAP only central instance ECC7.0).that are similar but without the run_sec directory, i.e. just /usr/sap/<SID>/SYS/exe that is a SYMLNK to /sapmnt/<SID>/exe.    PRD is still at 720 Kernel and also has just the /usr/sapPRD/SYS/exe SYMLNK to /sapmnt/PRD/exe.

2) The ECC systems are Classic user concept at present. Although have run the reports successfully to start the conversions once I have replaced 5 other Netweaver double stack kernel 700 systems in the landscape (BI/XI) with 721 kernels .  The CONVUSRCPT can't be run on kernel release 700.

Cheers, Michael.

[Former Member]

I have also confirmed that when signed on at OS level as DEVOFR the tp connect DEV works fine, but as DEVADM the errors above occur (QASOFR and QASADM similarly succeed and fail and QAS is also on 721 kernel level).

DEVOFR and from QP2TERM or QSH

  $             

> cd /usr/sap/trans/bin

  $ 

> tp connect DEV pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL  

  This is tp version 380.40.04 (release 721, unicode enabled)                 

  This is /usr/sap/DEV/SYS/exe/run/R3trans version 6.24 (release 721 - 01.02.16

   - 13:15:00).      

  unicode enabled version    

  /usr/sap/DEV/SYS/exe/run/R3trans finished (0000).

  Connection to Database of DEV was successful.  

  tp finished with return code: 0    

  meaning:            

    Everything OK

DEVADM:

QP2TERM or QSH

> cd /usr/sap/trans/bin

  $  

> tp connect DEV pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL

  This is tp version 380.40.04 (release 721, unicode enabled)                 

  ERROR: Connect to DEV failed (20160331004229, probably wrong environment).  

  TRACE-INFO: 1:  [     dev trc,00000]  Thu Mar 31 00:42:27 2016              

  TRACE-INFO: 2:  [     dev trc,00000]  DlLoadLib() success: dlopen("/usr/sap/D

  EV/SYS/exe/run/dbdb4slib.o"), hdl 0                                         

  TRACE-INFO: 3:  [     dev trc,00000]  DB4 SQL Reparse Activated             

  TRACE-INFO: 4:  [     dev trc,00000]  dbsldb4utl:sappfpar(DEFAULT.PFL): dbs/d

  b4/driver_type=                                                             

  TRACE-INFO: 5:  [     dev trc,00000]  dbsldb4utl:sappfpar(DEFAULT.PFL): dbs/d

  b4/xdn_port=                                                                

TRACE-INFO: 6:  [     dev trc,00000]  Thu Mar 31 00:42:28 2016              

TRACE-INFO: 7:  [     dev trc,00000]  dbsldb4utl:sappfpar(DEFAULT.PFL): dbs/d

b4/xdn_trace_file=                                                          

TRACE-INFO: 8:  [     dev trc,00000]  as4IsHostLocal: SAPDBHOST 'sapdev' is l

ocal                                                                        

TRACE-INFO: 9:  [     dev trc,00000]  dbsldb4utl:sappfpar(DEFAULT.PFL): dbs/d

b4/use_lock_queue=                                                          

TRACE-INFO: 10:  [     dev trc,00000]  dbsldb4utl:sappfpar(DEFAULT.PFL): dbs/

db4/sql_deflate_table=                                                      

TRACE-INFO: 11:  [     dev trc,00000]  Thu Mar 31 00:42:29 2016             

TRACE-INFO: 12:  [dbsldb4utl.c,00000]  *** ERROR => RetrieveMessage: Unable t

o retrieve message description for                                          

TRACE-INFO: 13:  [dbsldb4.cpp ,00000]  *** ERROR => Call to _GetAuthDB4(DEVOF

R    ) failed                                                               

TRACE-INFO: 14:  [     dev trc,00000]  Exception text could not be retrieved:

CPF9897                                                                    

TRACE-INFO: 15:  [dbsldb4.cpp ,00000]  *** ERROR => Switch to DEVOFR  failed.

tp returncode summary:        

TOOLS: Highest return code of single steps was: 0 

ERRORS: Highest tp internal error was: 0232     

tp finished with return code: 232     

meaning:   connect failed

Apart from the home directory the user profiles have same groups etc. and WRKENVVAR parameters

CPIC_MAX_CONV	'2000'
LANG	'/QSYS.LIB/EN_US.LOCALE'
SAPPARAM700	'1'
QIBM_USE_DESCRIPTOR_STDI >  'N'
USER	'DEVADM'
HOME	'/home/DEVADM'
SECUDIR	'/home/DEVADM/sec'
CLASSICUSERCONCEPT	'Y'
DIR_LIBRARY	'/usr/sap/DEV/SYS/exe/run'
PASE_LIBPATH	'/usr/sap/DEV/SYS/exe/run'
QIBM_PASE_MAP_SIGNALS	'I'
PASE_LOCPATH	'/usr/lib/nls/loc'
ILE_PATH	'/usr/sap/DEV/SYS/exe/run:/usr/bin:' >
PATH	'/usr/sap/DEV/SYS/exe/run:/usr/bin:' >
PASE_PATH	'/usr/sap/DEV/SYS/exe/run:/QOpenSys' >
QIBM_JAVA_PASE_STARTUP	'/usr/lib/start64'
QIBM_JAVA_PASE_ALLOW_PRE >  '1'
PASE_THREAD_ATTACH	'Y'
QIBM_MULTI_THREADED	'Y'
SAPSYSTEMNAME	'DEV'
PASE_STDIO_ISATTY	'N'
SAPSYSTEM_MAIN	'00'
PASE_TZ	'<AEST>-10<AEDT>,M10.1.0,M4.1.0/03:' >
dbms_type	'db4'
INSTANCE_MAIN	'DVEBMGS00'
SAPDBHOST	'sapdev'
SAPLOCALHOST	'sapdev'

[joachim_kern]

Hi Michael,

please provide the part of the content of file

/usr/sap/tmp/dev_sapauth

with the corresponding timestamp to your error.

Best regards,

Joachim

[Former Member]

Hi Joachim, Thank you , but I cant see that dev_sapauth file in the /usr/sap/tmp directory or under /usr/sap/DEV/..?

cd '/usr/sap/tmp'

WRKLNKSAP

Object link	Type	Owner	Size  Date
coll.put	*STMF	DEV00	1365628  Mar 31 07:00
dspptf.txt	*STMF	QSECOFR	381074  Mar 31 02:05
grpptf.txt	*STMF	QSECOFR	757  Mar 31 02:05
dev_flipexe_DEV00	*STMF	DEVADM	4176  Mar 30 16:36
dev_flipexe_JV130	*STMF	JV1ADM	720  Mar 29 09:35
dev_flipexe_QAS10	*STMF	QASADM	4032  Mar 29 09:33
dev_coll	*STMF	QSECOFR	7383  Mar 29 08:01
saposcol.pid	*STMF	QSECOFR	8  Mar 29 08:01
dev_coll.tmp	*STMF	DEV00	6519  Mar 29 08:01
dev_coll.old	*STMF	QSECOFR	6636  Mar 29 07:56
dev_signal	*STMF	QSECOFR	730  Mar 29 07:56

Under /sapmnt/DEV/ I can see  /exe (721 kernel objects) and /exe$  (which I think is the old 720)

exe	*DIR	DEVADM	118784  Mar 29 09:23
exe$	*DIR	DEVADM	118784  Feb 15 00:41

Best regards, Michael.

[joachim_kern]

Hi Michael,

ok something went wrong during the _GetAuthDB4() call.

Unfortunately there is still a problem in the error handling (the solution is on the way to a patch), so we see only the meta error 'Exception text could not be retrieved' and not the real error text.

So I can't help you there.

But the original problem with _GetAuthDB4 should not occur using the new user concept.

Nevertheles I would ask you to open a ticket, so you get informed as soon as the patch fixing the error handling is available.

Best regards

Joachim

[Former Member]

Hi Joachim,

Thanks a ticket has been raised for the issue, the problem also occurs with the 720 level kernel (I reverted the system back from the 721 release hostagent patch 12/721 kernel patch 624, to 720 hostagent patch 205/kernel720 patch 800) which made no difference.  Unfortunately the issue prevents change requests from being released in DEV, or imported via STMS so the transport system is broken. 

When you say the new user concept should not have this problem, I would like to run the user conversion for all the ECC 7.0 720 kernel systems (5 dev/test+1 production), but they share a global transport directory on sapdev with the Dev/Prod BI and XI 700 kernel systems- which can't be converted to new user concept.

Best regards, Michael.

[Former Member]

Joachim,  Ticket with the details is SAP Message Number  0120050410

Thanks, Michael.

[joachim_kern]

Hi Michael,

to analyze the _GetAuthDB4() problem please set the environment variable
sacladopttrc to 1 systemwide.

ADDENVVAR ENVVAR(sacladopttrc) VALUE(1) LEVEL(*SYS)

Then please relogon and call the failing tp again.

Afterwards please delete the environment variable again.

Now a file /usr/sap/tmp/dev_sapauth should have been generated.

I need all the content belonging to the timeframe where the error occured.

Best regards

Joachim

[joachim_kern]

By the way, the incident id consist of 3 parts. You only gave me the first.

Joachim

[Former Member]

Hi Joachim,

Thank you, I added the system wide variable, logged in as DEVADM and repeated the tp connect test, the  /usr/sap/tmp/dev_sapauth file was then created. When I ran the STMS Transport tool test for DEV nothing was logged into the file when the error appeared. I have attached the file to the reply.

Ive asked for the full SAP message number, customer no is 814811.

thanks

Best regards, Michael

dev_sapauth.txt.zip

connect to DEV failed.txt.zip

[joachim_kern]

Hi Michael,

the dev_sapauth file shows an error. 'ReturnPath err'

It is a known problem by our dbsl developers and a patch is already under construction.

Meanwhile you could start the system and the tp as DEVOFR (i suppose you have old user concept active). This should prevent from calling _GetAuthDB4()

Joachim

[Former Member]

Hi,

This was finally resolved by running the conversion to new user concept throughout all systems in the landscape.   Immediately that was done, the STMS Check Transport tool succeeded without error.

regards, Michael.

[Former Member]

Hi Joachim,

I'm having same situation and just wondering if note 2306443 has the correction to this or lib_dbsl patch 121?

- and this is 7.22 EXT UC kernel

By the way that note is not released yet so can't verify this.

Cheers,

Mika

[former_member192743]

Hi Mika,

My apologies. I just released the note. Though, the associated patch should have been out for a while...

If you still have issues after applying the patch specified in the note, please do open a ticket to BC-DB-DB4 and request the ticket be sent directly to development support, referencing this thread. 

... Eric

[Former Member]

Hi Eric,

Applying the patch helped us.

Thanks,

Mika