cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to get database information from system landscape directory for newly restored DB

david_engelhart
Explorer
0 Kudos
346

I saw a few questions for the same error but not exactly my situation.

I just restored an external database (using MS SSMS), and upgraded it successfully using the SAP setup wizard.

When I try to login using the SBO app, I get this message. 

I noticed that when I entered incorrect credentials, I received the appropriate error message. When the credentials were correct, I was stopped because of the "failed to get database information" message.

How can I fix this?

seanarchernz
Explorer

Log in to the System Landscape Directory (SLD), select the restored Company Database in question and click the Refresh Database User button.

seanarchernz
Explorer
0 Kudos

Hi David,

Did you get this resolved?  The SAP Note requires the SDRQ table be created in the SBO-COMMON database rather than the Company Databases.

The following is the contents of the table from one of our environments...looks like it has some SQL and HANA versions of query joins...not sure what they are used for.

seanarchernz_0-1722887273903.png

I've never encountered this issue before but I wonder if restoring SBO-COMMON from a backup before the issue occurred would work if you have a copy.

Cheers,

Sean

david_engelhart
Explorer
0 Kudos
Thanks for your comment. I have not resolved it. I see that I do have that table in the SBOCOMMON DB and it is quite populated. Again, all other databases seem to work fine, it is just this new one that I restored. Could it be a problem with that specific database?
View Entire Topic
nidhisingh14
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi david_engelhart 

In note 3451882, it is mentioned how you could create missing SDRQ table so please create table with help of this and check issue again after this.

Thank You.

Kind Regards
Nidhi

david_engelhart
Explorer
0 Kudos
Thank you Nidhi, though the table is not missing, it exists in SBOCOMMON. Only this one database causes that error, other databases on the server work fine.