Of course.
This is a known and critical issue that can occur during a DB migration to SAP HANA if not
handled correctly. The tables aren't truly "deleted," but they become invisible to the standard ABAP
tools because their catalog information is missing in the ABAP Data Dictionary (DDIC).
Here’s a detailed explanation of why this happens and the step-by-step process to resolve it.
Root Cause: The SYBASE to HANA Schema Mismatch
The primary reason for this issue is the difference in how Sybase (ASE) and HANA handle database
schemas and case sensitivity.
1. CASE SENSITIVITY:
· Sybase ASE: By default, is case-insensitive. A table created as VBAK can be selected with SELECT *
from vbak.
· SAP HANA: Is case-sensitive. A table must be addressed with the exact case used during its
creation. The system tables in HANA store object names in UPPERCASE.
2. SCHEMA OWNERSHIP:
· In Sybase, tables are often owned by a specific database user (e.g., the <SID>adm equivalent
user).
· In SAP systems, the standard schema that the ABAP server uses to look for tables is almost always
the schema of the technical database user (e.g., SAP<SID> or SAPHANADB).
· During the migration, if the tables were not moved or registered into this specific technical
schema, the ABAP stack cannot "see" them. The physical tables exist in the database, but their
metadata is not present in the ABAP Dictionary's central table DD02L (the table that stores all SAP
table definitions).
---
How to Resolve the Issue: The SYSPACKAGE Import
The standard solution provided by SAP for this exact scenario is to run the SYSPACKAGE import. This
process reads the physical table structures directly from the HANA database and creates the
corresponding entries in the ABAP Data Dictionary (DD02L, DD03L, etc.).
⚠️Important Pre-Check: Before you begin, confirm the tables actually exist in the HANA database
but are missing in DDIC.
1. In HANA Studio / HANA Database Explorer: Connect with the technical user (SAP<SID>) and run:
sql
SELECT COUNT(*) FROM "SYS"."TABLES" WHERE SCHEMA_NAME='<YOUR_SCHEMA_NAME>';
(Replace <YOUR_SCHEMA_NAME> with your actual schema, e.g., SAPABP1). This should show a
count of your tables.
2. In ABAP (SE11/SE16): Check if a known standard table (like VBAK or MKPF) exists in DD02L:
sql
SELECT * FROM DD02L WHERE TABNAME = 'VBAK';
If it returns no results, the DDIC entry is missing.
Step-by-Step Solution: Running SYSPACKAGE
Transaction Code: DBACOCKPIT (Database Administration Cockpit)
1. Navigate: Go to your SAP system and launch transaction DBACOCKPIT.
2. Go to Diagnosis: In the left-hand menu, navigate to Diagnosis -> Database Object Support ->
SYSPACKAGE Import.
3. Start the Import:
· You will be presented with a selection screen.
· You can typically run it for the entire schema or for specific missing tables.
· For a full recovery, it's common to select the option to process all tables in the schema.
4. Execute: Start the process. The system will:
· Scan the physical HANA database schema.
· For each table found, it will check if a corresponding entry exists in DD02L.
· For any table missing a DD02L entry, it will create one.
· It will also populate the field catalog information in DD03L.
5. Monitor: The process might take a significant amount of time depending on the number of tables.
Monitor the job logs for any errors.
Alternative Method: Using SQL Console in DBACOCKPIT
If the GUI option is not available or you need more control, you can use the SQL Console within
DBACOCKPIT.
1. In DBACOCKPIT, go to SQL -> SQL Editor.
2. Connect to your HANA database.
3. Execute the stored procedure that triggers the SYSPACKAGE import. The standard procedure is
often:
sql
CALL "SYS"."SYSPACKAGE_IMPORT"('<YOUR_SCHEMA_NAME>', 'REFRESH');
(Replace <YOUR_SCHEMA_NAME> with your actual schema name).
---
Post-Recovery Steps
1. Verify: After the SYSPACKAGE import completes, immediately check a few critical standard tables
in SE11 (e.g., MARA, VBAK, BKPF). They should now be visible.
2. Activate Objects: Some custom (Z-/Y-) tables might need to be reactivated. Go to SE14 (Data
Dictionary Utility), enter the table name, and choose Activate.
3. Run ABAP Report: SAP sometimes recommends running report RDDENHANCE to perform a
consistency check on the Data Dictionary. You can run it in SE38.
4. Check for Errors: Review the job log from the SYSPACKAGE import carefully. While it fixes most
tables, there might be a few complex objects (like those with special data types) that require manual
intervention. These are usually rare.
If SYSPACKAGE Does Not Work or Tables are Truly Missing
In rare cases, if the migration itself failed to copy the table data:
1. Restore from Backup: This is the nuclear option. You would need to restore the pre-migration
Sybase database and meticulously re-plan the HANA migration, ensuring all steps in the DMO
(Database Migration Option) process of SUM (Software Update Manager) are followed correctly,
especially concerning schema mapping and case sensitivity settings.
2. Contact SAP Support: Immediately raise a critical incident with SAP. They have specialized tools
and expertise to handle corrupted migrations. Provide them with the logs from the SUM/DMO
process and the SYSPACKAGE import.
Summary: In 99% of cases, the SYSPACKAGE import via DBACOCKPIT is the solution. It bridges the
gap between the physical tables in the case-sensitive HANA database and the logical ABAP Data
Dictionary. Always perform this operation in consultation with your basis administrator and during a
scheduled maintenance window.
