How To Fix SOI1058 - DB Indexname for Index &1-&2 cannot be retrieved

SAP Error Message - Details

• Message type: E = Error

• Message class: SOI1 - Safe Online Import/Upgrade Messages continued

• Message number: 058

• Message text: DB Indexname for Index &1-&2 cannot be retrieved

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SOI1058 - DB Indexname for Index &1-&2 cannot be retrieved ?

  The SAP error message SOI1058 indicates that the system is unable to retrieve the database index name for a specific index. This can occur in various scenarios, often related to database operations or when working with database indexes in SAP.
  Cause:
  
  Missing Index: The specified index may not exist in the database.
  Corrupted Index: The index might be corrupted or not properly defined.
  Database Configuration Issues: There could be issues with the database configuration or connectivity.
  Authorization Issues: The user may not have the necessary permissions to access the index.
  Transport Issues: If the index was recently transported, it may not have been properly activated or created in the target system.
  
  Solution:
  
  Check Index Existence: Verify if the index exists in the database. You can do this by checking the database directly or using transaction codes like SE11 (Data Dictionary) or SE14 (Database Utility).
  Rebuild Index: If the index is missing or corrupted, you may need to recreate or rebuild it. This can often be done using transaction codes like SE14 or through SQL commands, depending on your database.
  Check Authorizations: Ensure that the user has the necessary authorizations to access the index. You may need to consult with your security team to verify this.
  Database Consistency Check: Run a consistency check on the database to identify and fix any issues. This can be done using transaction DB02 or similar tools.
  Transport Management: If the issue arose after a transport, ensure that all objects were properly transported and activated in the target system.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: SE11 (Data Dictionary), SE14 (Database Utility), DB02 (Database Performance Monitor).
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal using the error message or related keywords.
  Database Documentation: Refer to the documentation for your specific database (e.g., Oracle, HANA, SQL Server) for additional troubleshooting steps related to indexes.
  
  If the problem persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.