Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 396 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
ORA-56752: Oracle Database Express Edition (XE) memory parameter invalid or not specified
With sga_target=2G
XE 18c instance cannot startup:
ORA-56752: Oracle Database Express Edition (XE) memory parameter invalid or not specified
What is the memory limit?
Best Answer
-
it seems PGA+SGA counted both and should not exceed 2G total. Any proportions can be set between them
Answers
-
Oracle 18c XE has FIXED limits on memory. SGA_MAX_SIZE = 2G. Due to limitations of XE you can not do things like add that parameter to XE.Set sga_target back to zero and restart your db.
-
it seems PGA+SGA counted both and should not exceed 2G total. Any proportions can be set between them
-
Thank you for reply.
User can change memory components anyhow on XE.
Total of all is <= 2G.
-
Thank you for reply.User can change memory components anyhow on XE.Total of all is <= 2G.
Indeed. To fix your original problem how ever, it would have been necessary to set sga_target back to 0. You did not mention you were setting other memory parameters.
-
Instead of showing an error message when trying to initialize a new database exceeding the XE limits or to warn when trying to change these values afterwards the DBMS will just not work properly. User/Operator friendliness is not something Oracle cares about.
