What Should I Do If Data Collection Fails or Is Slow Due to the Small Values of Certain Oracle SGA Parameters?
If data collection fails or is slow because certain parameters in the Oracle system global area (SGA) are set to small values, run the following command:
show parameter SGA;
Command output:
NAME TYPE VALUE ---------------------------- ----------- ------- sga_max_size big integer 796M sga_target big integer 0
Contact the database administrator to increase the values of the SGA parameters.
ALTER SYSTEM SET sga_max_size=5G scope=spfile;
ALTER SYSTEM SET sga_target=5G scope=spfile;
The preceding parameter values are for reference only. If their value is too large, more resources are occupied. Contact the database administrator to set the parameters to appropriate values.
For details about the parameters, see the Oracle official documentation.
Product Consulting FAQs
- Instance Freezing, Release, and Deletion
- Which Schemas in Source Databases Are Ignored for Migration?
- What Are the Differences Between Syntax Conversion and Migration & Verification in a Migration Project?
- What Are the Database Schema Changes After an Oracle Database Is Migrated to the Target Database?
- Why Cannot I Use Some Functions?
- What Is the Function of the dsc_ora_ext Schema Generated After Migration to the Target Database?
- What Should I Do If Data Collection Fails or Is Slow Due to the Small Values of Certain Oracle SGA Parameters?
- What Should I Do If Data Collection Fails and a Message SNAPSHOT TOO OLD Is Displayed?
- What Is the Mapping Between the GaussDB Versions Displayed on the UGO Console and Self-built GaussDB Versions?
- What Are VPCEP Resource Quotas?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore