on 11-09-2014 3:14 AM
Hi Members,
I am installing BW 7.40 on HANADB and getting below error while SAPINST bring up SAP, work process is died due to not able to connect thr SYSTEM.
Try to connect via secure store (DEFAULT) on connection 0 ...
C Attach to HDB : 1.00.82.00.394270 (NewDB100_REL)
C Database release is HDB 1.00.82.00.394270
C INFO : Database 'H10/00' instance is running on 'hana01'
C INFO : Connect to DB as 'SYSTEM', connection_id=300040
C INFO : set parameter for SQLSCRIPT, Enable_Select_Into_Scalar_UDF
C INFO : DATA AGING feature is supported by HANA
C INFO : FDA feature is supported by HANA
C INFO : FAE with FDA feature is supported by HANA
C DB max. input host variables : 32767
C DB max. statement length : 104857600
C DB max. array size : 100000
C use decimal precision as length
C ABAPVARCHARMODE is used
C *** ERROR => the connected user (SYSTEM) does not work with the right user/schema
[dbhdbsql.cpp 204]
C *** ERROR => application has to work with schema SAPBWT (dbs/hdb/schema)
[dbhdbsql.cpp 206]
C Disconnecting from connection 0 ...
C Now I'm disconnected from HDB
M ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 79]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c 2356]
M
M Info for wp 0
hana01:bwtadm 51> R3trans -x
This is R3trans version 6.24 (release 742 - 11.08.14 - 17:21:00).
unicode enabled version
R3trans finished (0000).
hana01:bwtadm 52> R3load -testconnect
R3load=>sapparam(1c): No Profile used.
R3load=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
R3load: START OF LOG: 20141108223623
R3load: sccsid @(#) $Id: //bas/742_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
R3load: version R7.42/V1.8 [UNICODE]
Compiled Sep 1 2014 18:12:24
R3load -testconnect
-------------------- Start of patch information ------------------------
patchinfo (patches.h): (0.013) R3load dependency loop if calles with -o V option (note 2044380)
DBSL patchinfo (patches.h): (0.026) Use prepared statements for R3szchk (note 1952609)
--------------------- End of patch information -------------------------
process id 18876
DbSl Trace: prepare() of C_0000, rc=1, rcSQL=259
DbSl Trace: PREPARE C_0000 on connection 0, rc=259
(DB) INFO: connected to DB
(DB) INFO: NewDB Kernel version 1.00.82.00.394270
SQLDBC 1.00.81.00.0392776
(DB) INFO: disconnected from DB
R3load: job completed
(STAT) DATABASE times: 5.173/0.008/0.020 100.0%/100.0%/100.0% real/usr/sys.
R3load: END OF LOG: 20141108223628
hana01:bwtadm 53>
Regards,
Amit Lal
Message was edited by: Amit Lal
Hi Amit,
During our system copy to HANA DB we have also received the same error you faced.
Applied the solution you have applied but still we didnt able to progress.
R3load -testconnect
R3load: START OF LOG: 20150326155831
(BLD) INFO: sccsid "@(#) $Id: //bas/742_REL/src/R3ld/R3load/R3ldmain.c#7 $ SAP"
(BLD) INFO: kernel release 742 [UNICODE]
(BLD) INFO: data format 1.8
(BLD) INFO: patch number 38
(BLD) INFO: compiled on "Mar 4 2015 20:41:36"
(PRC) INFO: called "R3load -testconnect"
(PRC) INFO: process id 28291
DbSl Trace: prepare() of C_0000, rc=1, rcSQL=259
DbSl Trace: PREPARE C_0000 on connection 0, rc=259
(DB) INFO: connected to DB
(DB) INFO: NewDB Kernel version 1.00.85.01.399276
SQLDBC 1.00.85.01.0399276
(DB) INFO: disconnected from DB
R3load: job completed
(STAT) DATABASE times: 0.059/0.003/0.012 100.0%/100.0%/100.0% real/usr/sys.
R3load: END OF LOG: 20150326155831
Kernel Details:
kernel release 742
kernel make variant 742_REL
DBMS client library HDB_1.00.63.381310
DBSL shared library version 742.06
compiled on Linux GNU SLES-11 x86_64 cc4.3.4 use-pr150211 for linuxx86_64
compiled for 64 BIT
compilation mode UNICODE
compile time Mar 12 2015 18:24:09
update level 0
patch number 110
Please help us with your solution.
Regards,
Prasenjit Roy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe you are doing system Copy/ DB refresh . During refresh you have used the Schema name as SYSTEM. You should use the schema name as SAPSID of your existing system
C *** ERROR => the connected user (SYSTEM) does not work with the right user/schema
[dbhdbsql.cpp 204] -- >
C *** ERROR => application has to work with schema SAPBWT (dbs/hdb/schema)
[dbhdbsql.cpp 206]
Also, on your application server you should update the secure store usign the below commands.
sidadm> hdbuserstore delete DEFAULT
sidadm? hdbuserstore SET Default <hostname>:3<nr>15 SAP<SID> <passowrd>
If the above doestn resolve then, Send me the output of
sidadm> hdbuserstore LIST
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Pavan,
Thanks a lot!
I moved ahead with SAPINST, disp+work started successfully but now facing another minor error. I did applied two points
1. Cmd ran for secure store config> hdbuserstore SET DEFAULT xxxxxx:30015 SAPBWT pawd
Now HDB and Application time is not sync on Linux, that's reason SAP BW is not coming
A *** ERROR => AppServerTimeSync, zdate_gettime():
Service for ABAP time in EMERGENCY MODE.
Returning local machine time plus emergency bias
Plus --
M ThSick: work process services check skipped.
M *** ERROR => ThSick: The UUID daemon (uuidd) is not active (code 30256). Check SAP note 1391070. [thxxsick.c 653]
M {root-id=000C290CF3C31EE49AC42E3D8BDC05FA}_{conn-id=00000000000000000000000000000000}_0
A *** ERROR => The UUID daemon (uuidd) is not active (code 30256). Check SAP note 1391070. [sapicc.c 1330]
I'll fix these issue and update the thread accordingly.
Thanks again,
Amit Lal
Hi Christina,
Kernel Details:
kernel release 742
kernel make variant 742_REL
DBMS client library HDB_1.00.63.381310
DBSL shared library version 742.06
compiled on Linux GNU SLES-11 x86_64 cc4.3.4 use-pr150211 for linuxx86_64
compiled for 64 BIT
compilation mode UNICODE
compile time Mar 12 2015 18:24:09
update level 0
patch number 110
Please help us with your solution.
Regards,
Prasenjit Roy
User | Count |
---|---|
90 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.