Discussions
Categories
- 385K All Categories
- 2.6K Data
- 595 Big Data Appliance
- 2K Data Science
- 452.1K Databases
- 222.4K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 32 Multilingual Engine
- 576 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 575 SQLcl
- 4K SQL Developer Data Modeler
- 187.7K SQL & PL/SQL
- 21.5K SQL Developer
- 12 Data Integration
- 12 GoldenGate
- 297.7K Development
- 3 Application Development
- 18 Developer Projects
- 140 Programming Languages
- 294.3K Development Tools
- 118 DevOps
- 3.1K QA/Testing
- 646.5K Java
- 30 Java Learning Subscription
- 37K Database Connectivity
- 185 Java Community Process
- 107 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 174 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 206 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 584 LiveLabs
- 41 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 191 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 240 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.
-
I was using the Oracle Database Configuration Assistant tool to create a new Oracle 21c XE (Express) database. Memory parameters are never requested. i.e. there is no place to enter the parameters. The assumption is that the configuration assistant will set that for me. Apparently it does not.
