Error
Error Code:
712
SAP S/4HANA Error 712: Deprecated SQL Plan Migration
Description
This error indicates that the SAP S/4HANA system encountered a problem with a deprecated SQL plan stability feature during a migration or upgrade process. It typically occurs when an older, no longer supported plan stabilizer mechanism is still active or referenced within the database configuration after a system transition.
Error Message
ERR_SQL_PLAN_STABILITY_MIGRATION_DEPRECATED
Known Causes
4 known causesOutdated Database Configuration
The underlying database configuration still references or attempts to utilize a plan stability feature that has been deprecated.
Incomplete System Migration
The migration or upgrade process did not fully update or de-commission all legacy plan stability settings.
Legacy Component Interaction
An integrated legacy system or component is attempting to use older, unsupported plan stability mechanisms.
Manual Activation of Deprecated Features
A system administrator might have manually enabled or configured a feature that is no longer supported.
Solutions
3 solutions available1. Update SQL Plan Stability Settings easy
Adjusting the SQL plan stability configuration to accommodate the deprecated migration process.
1
Access the SAP S/4HANA system's transaction code ST05 (SQL Trace) or ST04 (Database Performance Analysis).
2
Navigate to the 'SQL Plan Stability' or 'SQL Plan Management' section. The exact path might vary slightly between S/4HANA versions.
3
Locate the parameter related to 'Deprecated SQL Plan Migration' or similar wording. This parameter controls how the system handles older SQL plans during upgrades or maintenance.
4
Set the parameter to a value that allows the migration of deprecated plans. This might involve setting it to 'ON', 'AUTO', or a specific value that signifies acceptance of the migration. Consult SAP Notes for the precise recommended setting for your S/4HANA version.
Example (conceptual - actual parameter name and values may differ):
SET PROFILE 'SQL_PLAN_STABILITY_MIGRATION' = 'AUTO';5
Save the changes. A system restart might be required for the changes to take full effect.
2. Review and Recreate Problematic SQL Plans medium
Manually address SQL plans that are causing the migration issue.
1
Use transaction ST05 or ST04 to identify the specific SQL statements that are triggering the error 712.
2
For each identified SQL statement, analyze its current execution plan. This can be done within ST04 or by using database-specific tools.
3
Determine if the current plan is indeed deprecated or outdated. SAP Notes often provide guidance on identifying such plans.
4
If a plan is deemed problematic, consider recreating it. This might involve forcing a new plan generation for the SQL statement. The method for this varies by database (e.g., HANA's `RECREATE PLAN` or similar functionalities in other supported databases).
Example for SAP HANA (conceptual):
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') SET ('trace.sqlplan.recreate_on_error') = 'true';5
Monitor the system after recreating the plan to ensure the error no longer occurs and performance remains acceptable.
3. Apply Relevant SAP Notes easy
Implement SAP's official corrections and recommendations for this error.
1
Access the SAP Support Portal (launchpad.support.sap.com).
2
Search for SAP Notes related to 'ERR_SQL_PLAN_STABILITY_MIGRATION_DEPRECATED', 'Error 712', or 'SQL Plan Stability Migration' for your specific SAP S/4HANA version.
3
Carefully review the prerequisites and recommendations of the relevant SAP Notes. These notes often contain detailed instructions, including code corrections or configuration changes.
4
Apply the recommended SAP Notes using transaction SNOTE. Ensure you follow the note's instructions precisely, including any manual steps or configuration adjustments.
5
After applying the note, perform a thorough test of the affected functionalities and monitor the system for recurrence of the error.