Why does 3scale (system component) require "MAX_STRING_SIZE=EXTENDED" in Oracle Deployment?
Issue
- Our DBAs have an issue with running the following instruction as it has wider implications on other applications.
ALTER SYSTEM SET max_string_size=extended SCOPE=SPFILE;
- We need an alternate workaround for
max_string_size=extendedwhile preparing Oracle database for 3scale deployment.
Environment
- Red Hat 3scale API Management Platform
- 2.15 On Premise
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
