cancel
Showing results for 
Search instead for 
Did you mean: 

LOG BZA=>table PATCHHIST does not exist on database

Former Member
0 Kudos

Dear Friends,

I am installing SAP R/3 4.7 using import method and in the last step of the installation RFC logon module (post procesing) getting the error FRF-00063 RFC logon failed with invalid interface.

below is the R3trans log

4 ETW000 Connected to DBMS = DB6 --- DB2DBDFT = 'TST' --- SYSTEM = 'SPP'.

4 ETW000 [dev trc ,00000] { db_rtab( fcode = 'RT_INSERT', tname = 'PATCHHIST' ) {saprel.c:1350}

4 ETW000 163 0.755328

4 ETW000 [dev trc ,00000] *** ERROR in prepareStatement[dbdb6.c, 12112] CON = 0 (BEGIN)

4 ETW000 1743 0.757071

4 ETW000 [dev trc ,00000] &+ DbSlModifyDB6( SQLExtendedPrepare 😞 [IBM][CLI Driver][DB2/AIX64] SQL0204N "SAPTST.PATC

HHIST" is an undefined nam

4 ETW000 32 0.757103

4 ETW000 [dev trc ,00000] &+ e. SQLSTATE=42704

4 ETW000 19 0.757122

4 ETW000 [dev trc ,00000] &+

4 ETW000 19 0.757141

4 ETW000 [dev trc ,00000] &+ INSERT INTO "PATCHHIST" ( "EXECUTABLE", "SAPRELEASE", "HOSTNAME", "PLATFORM", "DBVENDOR"

, "TIMESTAMP", "PATCHNO",

4 ETW000 20 0.757161

4 ETW000 [dev trc ,00000] &+ "DBSLPATCHN" ) VALUES( ?, ?, ?, ?, ?, ?, ?, ? )

4 ETW000 29 0.757190

4 ETW000 [dev trc ,00000] &+ cursor type=NO_HOLD, isolation=UR, cc_release=NO, optlevel=5, degree=1, op_type=15, re

opt=0

4 ETW000 33 0.757223

4 ETW000 [dev trc ,00000] &+ ABAP location info: '', 0

4 ETW000 30 0.757253

4 ETW000 [dev trc ,00000] &+

4 ETW000 19 0.757272

4 ETW000 [dev trc ,00000] &+

4 ETW000 19 0.757291

4 ETW000 [dev trc ,00000] *** ERROR in prepareStatement[dbdb6.c, 12112] (END)

4 ETW000 28 0.757319

4 ETW000 [dbtrtab ,03967] ***LOG BZA=>table PATCHHIST does not exist on database [dbtrtab#5 @ 3967]

4 ETW000 38 0.757357

Kindly help me in resolving the issue.

Thanks and Regards,

Seshu

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Seshu,

the table should be there, so maybe there was an earlier problem durint the installation.

Go to the directory containing the installation logs and search for errors, e.g.

grep -i PATCHHIST *.log

Regards,

Mark

Former Member
0 Kudos

Not exactly sure but either kernel might be the issue.

Thanks