oracle / oracle/oracle-database-operator

Memory Target - Parameter in singleinstancedatabase.yaml

Open
#208 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
192
Forks
69
Avg merge
16h 13m
Merged PRs (30d)
1

Description

Please provide support for setting Memory Target in singleinstancedatabase.yaml
This will simplify the deployment and user don't need to provide the SGA or PGA.
The end user can simply provide the Memory Target value like 20GB 50 GB 80 GB for their Oracle SIDB PODs and let Oracle manage everything internally.

It will also help if after deployment, I need to change the memory target, I simple patch the YAML and with new value say from 20 GB to 30 GB and restart the POD and then it takes care of related parameters.

Currently in init parameter section, we have below only:

##  N/A for createAs clone or standby
## Specify Non-Zero value to use
## sgaTarget and pgaAggregateTarget must be in MB
## You cannot change these initParams for Oracle Database Express (XE) and Oracle Database Free edition
initParams:
  cpuCount: 0
  processes: 0
  sgaTarget: 0
  pgaAggregateTarget: 0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with singleinstancedatabase.yaml and its initParams section, then trace how these values are passed into the Oracle database deployment. Add support for a Memory Target value that can be changed through the YAML and applied after restarting the pod. Verify the resulting deployment behavior and update or add tests for the new parameter.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
databases, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.