Database Error Messages

SQL*Plus was unable to find a message file during program initialization, and could not display error messages or text required for normal operation. The most common cause is that ORACLE_HOME has not been set. For Instant Client, the common cause is that LD_LIBRARY_PATH has not been set to the Instant Client directory or libsqlplusic.so is missing. Other possible causes are a corrupt or unreadable message file. On Windows the environment variable called "SQLPLUS" may be invalid.

This message is hard coded (in English) in the SQL*Plus source code so it can be displayed on message file error. It could never be read from this message file because the error occurs only when the message files cannot be opened. This entry in the message file is for documentation purposes only.

Make sure that all environment variables or registry entries needed to run SQL*Plus are set. The variables are platform specific but may include ORACLE_HOME, ORACLE_SID, NLS_LANG, and LD_LIBRARY_PATH.

For Instant Client,make sure LD_LIBRARY_PATH, PATH and SQLPATH are set to location where Instant Client libraries are and libsqlpusic.so exists.

On Windows if the environment variable called "SQLPLUS" is set, it must contain the directory name of the SQL*Plus message files. For example %ORACLE_HOME%\sqlplus\mesg.

Also check that the file sp1XX.msb is in the $ORACLE_HOME/sqlplus/mesg or %ORACLE_HOME%\sqlplus\mesg directory. The "XX" stands for the country prefix associated with your NLS_LANG environment variable. SQL*Plus reads only one of the sp1XX.msb files. For example sp1ja.msb is read if NLS_LANG is JAPANESE_JAPAN.JA16EUC. If NLS_LANG is not set, then the default (English language) sp1us.msb is used. Check that the appropriate file is of non-zero size and that the file permissions allow it to be read. Note that ".msb" files are binary. The contents may be meaningless when viewed or printed. If you are unsure which language file is being used, unset NLS_LANG and run SQL*Plus to verify it can read the sp1us.msb file.

SQL*Plus was unable to find a message file during program initialization, and could not display error messages or text required for normal operation. The most common cause is that ORACLE_HOME has not been set. For Instant Client, the common cause is that LD_LIBRARY_PATH has not been set to the Instant Client directory or libsqlplusic.so is missing. Other possible causes are a corrupt or unreadable message file. On Windows the environment variable called "SQLPLUS" may be invalid.

This message is hard coded (in English) in the SQL*Plus source code so it can be displayed on message file error. It could never be read from this message file because the error occurs only when the message files cannot be opened. This entry in the message file is for documentation purposes only.

Make sure that all environment variables or registry entries needed to run SQL*Plus are set. The variables are platform specific but may include ORACLE_HOME, ORACLE_SID, NLS_LANG, and LD_LIBRARY_PATH.

For Instant Client,make sure LD_LIBRARY_PATH, PATH and SQLPATH are set to location where Instant Client libraries are and libsqlpusic.so exists.

On Windows if the environment variable called "SQLPLUS" is set, it must contain the directory name of the SQL*Plus message files. For example %ORACLE_HOME%\sqlplus\mesg.

Also check that the file sp1XX.msb is in the $ORACLE_HOME/sqlplus/mesg or %ORACLE_HOME%\sqlplus\mesg directory. The "XX" stands for the country prefix associated with your NLS_LANG environment variable. SQL*Plus reads only one of the sp1XX.msb files. For example sp1ja.msb is read if NLS_LANG is JAPANESE_JAPAN.JA16EUC. If NLS_LANG is not set, then the default (English language) sp1us.msb is used. Check that the appropriate file is of non-zero size and that the file permissions allow it to be read. Note that ".msb" files are binary. The contents may be meaningless when viewed or printed. If you are unsure which language file is being used, unset NLS_LANG and run SQL*Plus to verify it can read the sp1us.msb file.

SQL*Plus was unable to find a message file during program initialization, and could not display error messages or text required for normal operation. The most common cause is that ORACLE_HOME has not been set. For Instant Client, the common cause is that LD_LIBRARY_PATH has not been set to the Instant Client directory or libsqlplusic.so is missing. Other possible causes are a corrupt or unreadable message file. On Windows the environment variable called "SQLPLUS" may be invalid.

This message is hard coded (in English) in the SQL*Plus source code so it can be displayed on message file error. It could never be read from this message file because the error occurs only when the message files cannot be opened. This entry in the message file is for documentation purposes only.

Make sure that all environment variables or registry entries needed to run SQL*Plus are set. The variables are platform specific but may include ORACLE_HOME, ORACLE_SID, NLS_LANG, and LD_LIBRARY_PATH.

For Instant Client,make sure LD_LIBRARY_PATH, PATH and SQLPATH are set to location where Instant Client libraries are and libsqlpusic.so exists.

On Windows if the environment variable called "SQLPLUS" is set, it must contain the directory name of the SQL*Plus message files. For example %ORACLE_HOME%\sqlplus\mesg.

Also check that the file sp1XX.msb is in the $ORACLE_HOME/sqlplus/mesg or %ORACLE_HOME%\sqlplus\mesg directory. The "XX" stands for the country prefix associated with your NLS_LANG environment variable. SQL*Plus reads only one of the sp1XX.msb files. For example sp1ja.msb is read if NLS_LANG is JAPANESE_JAPAN.JA16EUC. If NLS_LANG is not set, then the default (English language) sp1us.msb is used. Check that the appropriate file is of non-zero size and that the file permissions allow it to be read. Note that ".msb" files are binary. The contents may be meaningless when viewed or printed. If you are unsure which language file is being used, unset NLS_LANG and run SQL*Plus to verify it can read the sp1us.msb file.