Skip to Content
0
Former Member
Oct 10, 2005 at 06:56 PM

Upgrade 6.20->6.40 Phase DBCHK

138 Views

Hello,

After the phase or in the phase DBCHK the upgrade process stalled.

DBINFO.LOG says:

R3up> Starting subprocess tp.exe with id 1812 at 20051010135004

EXECUTING E:\usr\sap\AXA\SYS\exe\run\tp.exe pf=E:\usr\sap\put\bin\DEFAULT.TPP getdbinfo AXA

Environment: dbs_ada_schema=SAPAXA

Environment: dbms_type=ada

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBHOST is no longer used.

KERNVER=620

SAPVERS=620

DOKVERS=620

COMPVERS=ABA_PLUS 100 0009

COMPVERS=EA-APPL 200 0007

COMPVERS=EA-DFPS 200 0007

COMPVERS=EA-FINSERV 200 0007

COMPVERS=EA-GLTRADE 200 0007

COMPVERS=EA-HR 200 0011

COMPVERS=EA-IPPE 200 0013

COMPVERS=EA-PS 200 0007

COMPVERS=EA-RETAIL 200 0007

COMPVERS=PI 2004_1_4700001

COMPVERS=PI_BASIS 2004_1_6200003

COMPVERS=SAP_ABA 620 0055

COMPVERS=SAP_APPL 470 0024

COMPVERS=SAP_BASIS 620 0055

COMPVERS=SAP_HR 470 0030

DBAVERS=7.6.00.012

DBASUBTYPE=STANDARD

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

But CONNECT.LOG says:

1 ETQ201XEntering upgrade-phase "DBCHK_PRE" ("20051010135003")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '00', GwService = 'sapgw00'

4 ETQ399 Environment variables:

4 ETQ399 dbs_ada_schema=<null>

4 ETQ399 auth_shadow_upgrade=0

4 ETQ399 SQLOPT=DEFAULT

4 ETQ380 computing toolpath for request "TP_DEFAULT"

4 ETQ382 translates to group "R3UP_TOOL_GROUP_OLD"

4 ETQ383 translates to path "E:\usr\sap\AXA\SYS\exe\run"

4 ETQ383 translates to path "exe"

4 ETQ399 Set environment for standard connect:

4 ETQ399 ENV: dbs_ada_schema=SAPAXA

4 ETQ399 ENV: auth_shadow_upgrade=0

4 ETQ399 Set RFC variables for standard connect:

4 ETQ399 System-nr = '00', GwService = 'sapgw00'

4 ETQ399 Set tool parameters for standard connect:

4 ETQ399 default TPPARAM: DEFAULT.TPP

1 ETQ202 Upgrade phase "DBCHK_PRE" completed sucessfully ("20051010135003")

And R3upchk.log:

[........]

UPGRADEPHASE DBCHK_PRE

...started at 20051010135003

  1. Condition #if -1 >= 0

  2. is evaluated as a FALSE expression, total status is FALSE, stack level 1

  3. Condition #if -1 >= 0

  4. is evaluated as a FALSE expression, total status is FALSE, stack level 1

  5. DB Environment for R3up:

  6. DBATYPE SAPDB

  7. DBAHOME

  8. DBAEXE \pgm

  9. DBACONN "AXA"

  10. DBAVERS 7.6.00.012

  11. KERNVERS 620

  12. SAPVERS 620

  13. DOKVERS 620

  14. DBASUBTYPE STANDARD

  15. DBAOPSYS SAME_SYS

  16. DBA2CONN ""

  17. COMPRELS "ABA_PLUS=100,EA-APPL=200,EA-DFPS=200,EA-FINSERV=200,EA-GLTRADE=200,EA-HR=200,EA-IPPE=200,EA-PS=200,EA-RETAIL=200,PI=2004_1_470,PI_BASIS=2004_1_620,SAP_ABA=620,SAP_APPL=470,SAP_BASIS=620,SAP_HR=470"

..finished at 20051010135004 with SEVERE ERROR(S).

...begin dialogue at 20051010135004

...end dialogue at 20051010203118

...begin dialogue at 20051010203118

It sound a little contradictory!

Has someone an idea?

Now I have 2 R3up.exe processes and prepare does not go on...

Regards,

Tommaso