Reports Builder With NLS_LANG Set To UTF8 May Crash on Opening Report (Doc ID 283898.1)

Last updated on JULY 02, 2016

Applies to:

Oracle Reports Developer - Version 6.0.8.26 to 11.1 [Release 6i to 11g]
Microsoft Windows (32-bit)
Checked for relevance on 17-Jun-2013


Symptoms

Reports Builder with NLS_LANG set to characterset UTF8 may crash when
attempting to open up a report ( rdf ) module.

The Report Builder may 'abnormally exit' giving no errors or the end user may
see a MS Windows dialogue like:

Reports 6i (6.0.8)

*********************************************
RWBLD60.exe has generated errors and
will be closed by Windows
You will need to restart the program

An error log is being created
*********************************************

Reports 9i (9.0.2) / Reports 10g (9.0.4)

*********************************************
rwbuilder.exe has generated errors and
will be closed by Windows
You will need to restart the program

An error log is being created
*********************************************

If NLS_LANG is to set to another characterset like WE8MSWIN1252 which is not unicode,
the report opens up in Report Builder and no crash occurs.

The problem does not occur for all reports; some reports will open up fine in Report Builder
even with NLS_LANG = .. UTF8.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms