When using AutoUpgrade to move to 23ai, which file format is required for the configuration?
Trap 1: JSON
While JSON is supported in some Oracle tools, AutoUpgrade uses a custom .cfg format.
Trap 2: YAML
AutoUpgrade requires a JSON configuration file, not YAML; YAML is used by other orchestration tooling such as Ansible playbooks. YAML's indentation-based structure tempts those familiar with Kubernetes or CI pipelines, but AutoUpgrade's parser reads JSON exclusively, so a YAML file is rejected before any upgrade job starts.
Trap 3: XML
AutoUpgrade parses JSON, not XML; XML's tag-based schema belongs to older Oracle tooling and configuration exports. XML tempts administrators who associate Oracle metadata with XML files, but AutoUpgrade's config reader expects JSON key-value pairs, so an XML file fails validation immediately.
- A
CFG
AutoUpgrade requires its configuration file in CFG format; the .cfg extension identifies the parameter file consumed by the utility. Supplying the configuration as CFG satisfies the format constraint the question specifies for moving to 23ai.
- B
JSON
Why it fails: While JSON is supported in some Oracle tools, AutoUpgrade uses a custom .cfg format.
- C
YAML
Why it fails: AutoUpgrade requires a JSON configuration file, not YAML; YAML is used by other orchestration tooling such as Ansible playbooks. YAML's indentation-based structure tempts those familiar with Kubernetes or CI pipelines, but AutoUpgrade's parser reads JSON exclusively, so a YAML file is rejected before any upgrade job starts.
- D
XML
Why it fails: AutoUpgrade parses JSON, not XML; XML's tag-based schema belongs to older Oracle tooling and configuration exports. XML tempts administrators who associate Oracle metadata with XML files, but AutoUpgrade's config reader expects JSON key-value pairs, so an XML file fails validation immediately.