Export from Oracle Application Does Not Show Save/Open Dialog – Complete Oracle E-Business Suite Troubleshooting Guide

📅 Last Updated: August 2026

This article has been completely reviewed and updated for Oracle E-Business Suite 11i, R12.1, and R12.2. It includes Oracle Forms export architecture, FND_GFM processing, FND_LOBS troubleshooting, Oracle HTTP Server (OHS), Oracle WebLogic Server, browser download behavior, production troubleshooting, Oracle Apps DBA best practices, and real-world production case studies.

Oracle E-Business Suite users occasionally encounter a situation where exporting data from an Oracle Forms window appears to start normally, but the expected Save/Open download dialog never appears.

Typically, users click File → Export, the export progress window flashes briefly, and then disappears without generating any file for download.

Although this appears to be a browser issue, the actual problem may originate anywhere within the Oracle Forms export process, including Oracle Forms Services, Oracle HTTP Server, Oracle WebLogic Server, the FND_GFM package, the FND_LOBS table, browser security settings, popup blocking, or storage-related problems inside the Oracle Database.

This guide explains how Oracle Forms exports files, how Oracle E-Business Suite delivers exported documents to the client browser, and the production-tested troubleshooting procedures used by experienced Oracle Apps DBAs.

Quick Solution

Verify that Oracle Forms Services, Oracle HTTP Server (OHS), and WebLogic Server are functioning correctly. Review the FND_GFM process, confirm that the FND_LOBS table accepts uploaded files, verify tablespace availability, check browser download and popup settings, review Forms log files, and execute AutoConfig if configuration inconsistencies are detected.

Typical Symptoms

Users usually report one or more of the following symptoms:

File → Export starts normally.
The Export progress window appears briefly.
The progress window disappears.
No Save/Open dialog appears.
No file is downloaded.
No obvious Oracle error message is displayed.
The export operation silently fails.
The problem affects multiple users.

Related Errors

FRM-92050
FRM-92101
FRM-92120
HTTP 500 Internal Server Error
Oracle Forms Session Terminated
Oracle HTTP Server unavailable
Popup blocked by browser
Browser download blocked

How Oracle Forms Export Works

When a user exports data from Oracle Forms, Oracle E-Business Suite performs several operations before the download reaches the user's browser.

A simplified workflow is shown below:

Oracle Forms

      │

      ▼

Generate Export File

      │

      ▼

FND_GFM Package

      │

      ▼

FND_LOBS Storage

      │

      ▼

Oracle HTTP Server

      │

      ▼

Browser Download

      │

      ▼

Save/Open Dialog

A failure anywhere in this sequence can prevent the Save/Open dialog from appearing.

Oracle Export Architecture

The Oracle Forms export mechanism depends on multiple Oracle E-Business Suite components working together.

Oracle Forms Runtime
Oracle Forms Services
Oracle HTTP Server (OHS)
Oracle WebLogic Server (R12.2)
FND_GFM package
FND_LOBS table
Oracle Database
Browser download manager

If any one of these components fails, the export process may terminate before the download begins.

Business Impact

Export functionality is widely used throughout Oracle E-Business Suite for reporting, reconciliation, auditing, and operational analysis.

When exports fail, organizations may experience:

Financial reports cannot be downloaded.
Inventory analysis is interrupted.
Purchasing reports cannot be exported.
Order management reports are unavailable.
Audit documentation cannot be generated.
Business users lose productivity.
Support calls increase significantly.
Critical reporting deadlines may be missed.

Common Root Causes

FND_GFM upload failure.
FND_LOBS insert failure.
FND_LOBS index corruption.
Tablespace full.
Temporary tablespace exhaustion.
Oracle HTTP Server problems.
Forms Services issues.
WebLogic Managed Server unavailable.
Browser popup blocker.
Browser download restrictions.
Corrupted browser cache.
Java cache corruption (legacy environments).
Incorrect Forms configuration.
AutoConfig inconsistencies.
Network interruptions.
Insufficient filesystem space.

Where Should You Start?

Rather than immediately restarting application services, determine where the export process is failing.

Begin by answering the following questions:

Does the issue affect one user or all users?
Does every responsibility experience the problem?
Are Oracle Forms functioning normally otherwise?
Are reports generated successfully?
Is the Save/Open dialog blocked by the browser?
Can files be downloaded from other Oracle EBS pages?
Were patches recently applied?
Has AutoConfig been executed recently?
Is the database tablespace healthy?
Do Forms or Apache logs report any errors?

Answering these questions significantly reduces troubleshooting time and helps identify whether the issue is related to the database, middleware, browser, or Oracle Forms configuration.

Production Oracle Apps DBA Recommendation

Treat export failures as an end-to-end workflow issue rather than a browser problem alone. Verify Oracle Forms Services, Oracle HTTP Server, WebLogic, FND_GFM processing, FND_LOBS storage, browser configuration, and database health before making configuration changes or restarting services.

Step-by-Step Production Troubleshooting

When Oracle E-Business Suite fails to display the Save/Open dialog after selecting File → Export, the objective is to determine where the export workflow stops. The failure may occur during file generation, database storage, middleware processing, or browser download handling.

Step 1 – Determine the Scope of the Problem

Before investigating technical components, determine whether the issue is isolated or system-wide.

Verify:

Does the problem affect one user or all users?
Does it occur in every responsibility?
Does it affect every Oracle Forms screen?
Can other users export successfully?
Did the issue begin after patching or maintenance?

This information helps determine whether the problem is client-side or server-side.

Step 2 – Verify FND_GFM Processing

Oracle E-Business Suite uses the FND_GFM package to prepare exported files before they are delivered to the browser.

If FND_GFM encounters an exception, the export operation may terminate before the browser receives the file. Review:

Application log files
Forms diagnostics
Concurrent processing logs (if applicable)
Unexpected database errors

Step 3 – Verify FND_LOBS

During export, Oracle E-Business Suite stores generated files in the FND_LOBS table before they are transmitted to the client.

Investigate:

Tablespace availability
Segment growth
Index health
Object validity
Storage-related errors

If inserts into FND_LOBS fail, the browser download cannot begin.

Step 4 – Check Tablespace Utilization

Insufficient database storage may prevent temporary export files from being created successfully.

Useful SQL:

SELECT tablespace_name,
       ROUND(SUM(bytes)/1024/1024) MB
FROM dba_free_space
GROUP BY tablespace_name;

Review:

System tablespaces
Application tablespaces
TEMP usage
UNDO usage (if relevant)

Resolve any storage shortages before continuing.

Step 5 – Validate Index Health

Corrupted or unusable indexes on application tables, including FND_LOBS-related indexes, may interrupt export processing.

Review invalid or unusable indexes:

SELECT owner,
       index_name,
       status
FROM dba_indexes
WHERE status <> 'VALID';

Rebuild indexes only after confirming that corruption or invalid status is the root cause.

Step 6 – Review Oracle Forms and Middleware Logs

Oracle Forms and middleware logs frequently contain the underlying exception that caused the export to fail.

Review logs for:

Java exceptions
Servlet failures
HTTP errors
Upload failures
Database exceptions
OutOfMemoryError
Connection timeouts

Always investigate the first reported error rather than the final symptom.

Step 7 – Verify Browser Download Settings

Modern browsers include security features that can silently block downloads.

Verify:

Popup blocker disabled for Oracle EBS.
Automatic downloads allowed.
Browser download permissions.
Trusted Sites configuration (where applicable).
No conflicting browser extensions.

Test using another supported browser to eliminate client-specific issues.

Step 8 – Clear Browser Cache

Cached Oracle Forms resources may interfere with download processing, particularly after patches or upgrades.

Recommended actions:

Clear browser cache.
Clear cookies for the Oracle EBS site.
Clear Java cache in legacy environments.
Restart the browser.

Step 9 – Verify Oracle HTTP Server and WebLogic

Ensure that middleware services responsible for delivering exported files are operating correctly.

Verify:

Oracle HTTP Server (OHS)
WebLogic Admin Server
Forms Managed Server
HTTP/HTTPS connectivity
Forms Servlet availability

Any interruption in the middleware stack can prevent the download dialog from appearing.

Step 10 – Execute AutoConfig

If Oracle E-Business Suite configuration files have been modified manually or after applying patches, regenerate them using AutoConfig.

Typical command:

adautocfg.sh

After AutoConfig completes successfully, restart the affected application services if required and retest the export functionality.

Real Production Case Study

Users in an Oracle E-Business Suite R12.2 production environment reported that every export operation completed instantly, but no Save/Open dialog appeared.

Oracle Forms, Oracle HTTP Server, and WebLogic Server were all operating normally.

Further investigation identified that inserts into FND_LOBS were failing because the application tablespace had reached 100% utilization.

After extending the tablespace and validating the affected objects, export functionality resumed immediately without restarting Oracle Forms Services.

Oracle Apps DBA Investigation Checklist

Verification	Status
Issue Scope Identified	☐
FND_GFM Verified	☐
FND_LOBS Reviewed	☐
Tablespace Capacity Verified	☐
Indexes Validated	☐
Forms Logs Reviewed	☐
Browser Download Settings Checked	☐
Browser Cache Cleared	☐
Oracle HTTP Server Verified	☐
WebLogic Verified	☐
AutoConfig Completed	☐
Export Tested Successfully	☐

Oracle E-Business Suite Version Considerations

The export mechanism is similar across Oracle E-Business Suite releases, but the middleware architecture differs significantly between versions. Understanding these differences helps Oracle Apps DBAs troubleshoot export failures more efficiently.

Oracle EBS Version	Primary Components	Export Considerations
Oracle EBS 11i	Oracle Forms, Oracle Application Server, Apache	Verify Forms Services, Apache, browser settings, and FND_GFM processing.
Oracle EBS R12.1	Oracle Forms, Oracle Application Server, AutoConfig	Validate AutoConfig configuration, FND_LOBS storage, and middleware health.
Oracle EBS R12.2	Oracle HTTP Server (OHS), Oracle WebLogic Server, Forms Managed Server	Verify OHS, WebLogic, Forms Services, FND_GFM, FND_LOBS, and online patching consistency.

Browser Considerations

Modern browsers implement strict download security policies that can affect Oracle Forms export operations.

Always verify:

Popup blocking is disabled for the Oracle EBS URL.
Automatic downloads are permitted.
The Oracle EBS site is trusted.
No download restrictions are configured by browser security policies.
Browser extensions are not interfering with downloads.
The browser version is supported for your Oracle EBS release.

Best Practices for Oracle Apps DBAs

Monitor FND_LOBS growth regularly.
Monitor tablespace utilization proactively.
Review Forms and WebLogic logs after applying patches.
Run AutoConfig whenever configuration templates change.
Verify export functionality after Oracle EBS maintenance.
Maintain healthy indexes on application objects.
Keep Oracle HTTP Server and Forms Services operational.
Validate browser compatibility before desktop rollouts.
Maintain sufficient TEMP and application tablespace free space.
Document middleware configuration changes.

Common Administrator Mistakes

Assuming the browser is always responsible.
Ignoring FND_LOBS storage issues.
Skipping tablespace verification.
Restarting middleware without reviewing log files.
Ignoring Forms log exceptions.
Failing to run AutoConfig after configuration changes.
Not testing exports after Oracle patches.
Ignoring browser download security settings.
Leaving invalid indexes unrepaired.
Overlooking WebLogic or OHS service health.

Useful Oracle Apps DBA Commands

Check Free Tablespace

SELECT tablespace_name,
       ROUND(SUM(bytes)/1024/1024) MB_FREE
FROM dba_free_space
GROUP BY tablespace_name;

Check Invalid Indexes

SELECT owner,
       index_name,
       status
FROM dba_indexes
WHERE status <> 'VALID';

Run AutoConfig

adautocfg.sh

Check Oracle HTTP Server

adapcctl.sh status

Check WebLogic and Forms Processes

ps -ef | grep AdminServer

ps -ef | grep WLS_FORMS

Troubleshooting Flowchart

Export Starts

        │

        ▼

No Save/Open Dialog

        │

        ▼

Determine Scope

        │

        ▼

Verify FND_GFM

        │

        ▼

Verify FND_LOBS

        │

        ▼

Check Tablespace

        │

        ▼

Validate Indexes

        │

        ▼

Review Forms Logs

        │

        ▼

Verify Browser Settings

        │

        ▼

Check OHS & WebLogic

        │

        ▼

Run AutoConfig

        │

        ▼

Export Successful

Frequently Asked Questions (FAQ)

Why does the export window appear briefly and then disappear?

This usually indicates that the export process started but failed before the browser received the generated file. Common causes include failures in FND_GFM processing, FND_LOBS storage, middleware communication, or browser download handling.

Can a full tablespace prevent Oracle Forms exports?

Yes. If Oracle E-Business Suite cannot store the generated export file because the required tablespace is full, the export operation may terminate without displaying the Save/Open dialog.

Can browser popup blockers cause this issue?

Yes. Browser security settings or popup blockers may prevent the download dialog from appearing even when the export is generated successfully.

Should I restart Oracle Forms Services immediately?

No. Review Oracle Forms, WebLogic, and Oracle HTTP Server logs first. Restarting services without identifying the underlying cause may not resolve the issue and can unnecessarily interrupt users.

Can AutoConfig resolve export problems?

Yes. If configuration files are inconsistent after patching or manual changes, AutoConfig can regenerate the correct Oracle E-Business Suite configuration and restore normal export functionality.

About the Author

Rana Abdul Wahid is an Oracle Database and Oracle E-Business Suite Consultant with more than 15 years of experience in Oracle Database Administration, Oracle E-Business Suite Application DBA, Oracle Cloud Infrastructure (OCI), Oracle RAC, Oracle Data Guard, RMAN Backup & Recovery, Linux/Unix Administration, MySQL, Microsoft SQL Server, PostgreSQL, and enterprise infrastructure management.

His expertise includes Oracle Forms, Oracle HTTP Server (OHS), Oracle WebLogic Server, Oracle E-Business Suite middleware, AutoConfig, performance tuning, backup and recovery, and enterprise production support. He regularly shares practical troubleshooting solutions based on real-world Oracle Apps DBA experience.

Learn more about the author →

Conclusion

When Oracle E-Business Suite exports fail without displaying the Save/Open dialog, the underlying cause is often deeper than a browser issue. Problems involving FND_GFM, FND_LOBS, tablespace availability, Oracle Forms Services, Oracle HTTP Server, WebLogic Server, AutoConfig configuration, or browser security settings can all interrupt the export workflow.

By following a structured troubleshooting methodology—verifying middleware services, checking database storage, reviewing Oracle Forms logs, validating browser settings, and ensuring configuration consistency—Oracle Apps DBAs can identify the root cause quickly and restore reliable export functionality with minimal disruption.

Final Oracle Apps DBA Recommendation

Treat export failures as end-to-end workflow issues. Investigate every stage of the export process—from Oracle Forms generation and FND_GFM processing to FND_LOBS storage, middleware delivery, and browser download behavior—before applying fixes or restarting services.

Found this guide helpful? Visit the Oracle Error Codes Guide for more production-tested Oracle Database, Oracle E-Business Suite, Oracle Forms, Linux, and middleware troubleshooting articles designed for Oracle DBAs and Oracle Apps DBAs.

Oracle Database Error Solutions & DBA Knowledge Base