Skip to Content

Strange behavior using hdbuserstore

Greetings experts,

We are in an upgrade/migration to Solution Manager 7.2 on HANA. In step

STARTSAP_NBAS the start of the shadow instance fails because it is unable to connect to the HANA db. HANA Studio shows the schema user is locked. When I unlock the schema user I can give R3trans -d and a select statement using "hdbsql -U DEFAULT" with no problems. When I try to start the shadow instance manually or in SUM the schema user becomes locked again. I want to blame hdbuserstore, but wondering if startsap (windows) uses a different connection tool. It's obviously hitting the db as the user gets locked each attempt to start it.

Any input would be appreciated.


Mike Dumas

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Apr 17, 2017 at 02:19 PM

    I'm moving this to the Software Provisioning - System Maintenance area as the current state is a result of using the SUM tool.

    Add comment
    10|10000 characters needed characters exceeded