Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Importing page results in Bad Request

Geert01Jan 30 2025 — edited Jan 30 2025

Issue with Importing a Single Page in Oracle ATP

Yesterday, we cloned our Oracle ATP database from Production to our Test environment. After that, we made a minor change to one of the pages, exported it (using the options Readable Format and Split into Multiple Files), and attempted to import only that page into the Production environment. However, we encountered a Bad Request error. Retrying produced the same result.

To troubleshoot, we then exported the entire application from our Test environment and imported it into Production, using the option to auto-assign a new application number. This worked without any issues.

However, this is not our preferred approach. We do not want to:

  1. Import the entire application and assigning it a new number.
  2. Import the entire application while replacing the existing one (keeping the same application number).

Instead, we only want to import modified components.

Question:

How can we debug this issue on an ATP environment to determine why importing a single page fails while importing the full application works?

Apex version: 24.1.7

Database version 23AI

Comments
Post Details
Added on Jan 30 2025
1 comment
151 views