In OFM (Oracle Fusion Middleware) apps, it seems the NLS_LENGTH_SEMANTICS need to be in BYTE, and by defaults it’s CHAR. According this knowledge base in Oracle. Do not forget to restart your DB after you alter the NLS_LENGTH_SEMANTICS setting.



The errors seen above are encountered because the NLS_LENGTH_SEMANTICS initialization parameter has been set to CHAR. This is not a supported setting for this parameter in an Oracle Fusion Middleware installation. This is documented in the Release Notes for each platform, an example for Linux is referenced below:

Oracle Fusion Middleware Release Notes
11g Release 1 (11.1.1) for Linux x86
Part Number E10133-14
2.1.10 Setting the nls_length_semantics Parameter in your Database

As stated in this document:

“Oracle Fusion Middleware only supports schemas in a byte-mode database. The nls_length_semantics initialization parameter on the database where the schemas reside must be set to BYTE; setting this parameter to CHAR is not supported.”

Solution 2:


To remove the ORA-01450 errors when creating the MDS and SOAINFRA components ensure that the requirement for NLS_LENGTH_SEMANTICS=BYTE is met.

To check the current setting of NLS_LENGTH_SEMANTICS, login to the target database as SYSDBA and issue the following command:
SQL> show parameters nls_length_semantics

To reset the parameter to BYTE, login to the target database as SYSDBA and issue the following command:
SQL> alter system set NLS_LENGTH_SEMANTICS=BYTE scope=both;

After resetting the parameter you should restart your database for the change to take effect.



Tinggalkan Balasan

Isikan data di bawah atau klik salah satu ikon untuk log in:

Logo WordPress.com

You are commenting using your WordPress.com account. Logout /  Ubah )

Foto Google+

You are commenting using your Google+ account. Logout /  Ubah )

Gambar Twitter

You are commenting using your Twitter account. Logout /  Ubah )

Foto Facebook

You are commenting using your Facebook account. Logout /  Ubah )


Connecting to %s