At startup of InConcert server gives DBMS error 12705 with Oracle.May also have problem storing and retriving diacritical or accented charachers.
Article ID: KB0084922
Updated On:
| Products | Versions |
|---|---|
| TIBCO InConcert | - |
| Not Applicable | - |
Description
Resolution:
Description:
There are two known causes of this. In the first case the 12705 is masking another Oracle error of 2289. The 2289 error will only show after you set the InConcert debug log, i.e. 'setenv IC_SERVER_DEBUG $IC_HOME/logs/debug.log'.
The 2289 error translates to:, "sequence does not exist"
*Cause: The specified sequence does not exist, or the user does
not have the required privilege to perform this operation.
*Action: Make sure the sequence name is correct, and that you have
the right to perform the desired operation on this sequence.
What has happen is the owner of the InConcert database, by default icdbown, was not granted the necessary rights. To change this do in sqlplus 'SQL> grant connect, resource to icdbown'.
Another cause of the 2289 error is not having the correct compatible setting in the init<oracle sid>.ora file. For InConcert 6.2 and above a setting of the init*.ora of 'compatible=8.0.5' and below will cause a failure on the installation. This will show up in the debug.log as a 2289 DBMS error and a uniquness violation error. Compatible must be set to 8.1.0 or above. The required setting is in the 6.2 release notes. BW WF GA release installer will display the compatibility error and allow you to exit the installation.
The second cause is an actual NLS_LANG setting problem:
oerr ora 12705
12705, 00000, "invalid or unknown NLS parameter value specified"
// *Cause: The NLS parameter value specified in an alter session statement
// is not valid or not implemented.
// *Action:
NOTE when doing the installation of InConcert you must have the NLS_LANG setting specified. If the character set of the database is say AMERICAN_AMERICA.WE8ISO8859P1 but you do not have NLS_LANG specified in the environment the data initially written will be in US7ASCII. When you then specify NLS_LANG when running the server you will then get the error.
Assuming you have correctly specified NLS_LANG environmental setting and the database was created using that setting you still have to do the following to get InConcert server to correctly start and read and write accented characters.
Set the environmental variable ORA_NLS33 pointing to $ORACLE_HOME/app/product/8.0.6/ocommon/nls/admin/data. For Oracle 8.1.6 and above this becomes ORA_NLS33 and for Oracle 7.x this would be ORA_NLS32.
On windows you have to check the NT registry. Each Oracl home has it own setting for NLS_LANG. Don't change the ones which are set to NA but the Oracle home IC uses will need to have a NLS_LANG setting which agrees with the character set of the database.
Description:
There are two known causes of this. In the first case the 12705 is masking another Oracle error of 2289. The 2289 error will only show after you set the InConcert debug log, i.e. 'setenv IC_SERVER_DEBUG $IC_HOME/logs/debug.log'.
The 2289 error translates to:, "sequence does not exist"
*Cause: The specified sequence does not exist, or the user does
not have the required privilege to perform this operation.
*Action: Make sure the sequence name is correct, and that you have
the right to perform the desired operation on this sequence.
What has happen is the owner of the InConcert database, by default icdbown, was not granted the necessary rights. To change this do in sqlplus 'SQL> grant connect, resource to icdbown'.
Another cause of the 2289 error is not having the correct compatible setting in the init<oracle sid>.ora file. For InConcert 6.2 and above a setting of the init*.ora of 'compatible=8.0.5' and below will cause a failure on the installation. This will show up in the debug.log as a 2289 DBMS error and a uniquness violation error. Compatible must be set to 8.1.0 or above. The required setting is in the 6.2 release notes. BW WF GA release installer will display the compatibility error and allow you to exit the installation.
The second cause is an actual NLS_LANG setting problem:
oerr ora 12705
12705, 00000, "invalid or unknown NLS parameter value specified"
// *Cause: The NLS parameter value specified in an alter session statement
// is not valid or not implemented.
// *Action:
NOTE when doing the installation of InConcert you must have the NLS_LANG setting specified. If the character set of the database is say AMERICAN_AMERICA.WE8ISO8859P1 but you do not have NLS_LANG specified in the environment the data initially written will be in US7ASCII. When you then specify NLS_LANG when running the server you will then get the error.
Assuming you have correctly specified NLS_LANG environmental setting and the database was created using that setting you still have to do the following to get InConcert server to correctly start and read and write accented characters.
Set the environmental variable ORA_NLS33 pointing to $ORACLE_HOME/app/product/8.0.6/ocommon/nls/admin/data. For Oracle 8.1.6 and above this becomes ORA_NLS33 and for Oracle 7.x this would be ORA_NLS32.
On windows you have to check the NT registry. Each Oracl home has it own setting for NLS_LANG. Don't change the ones which are set to NA but the Oracle home IC uses will need to have a NLS_LANG setting which agrees with the character set of the database.
Issue/Introduction
At startup of InConcert server gives DBMS error 12705 with Oracle.May also have problem storing and retriving diacritical or accented charachers.
Environment
Product: TIBCO InConcert
Version: All
OS: All
--------------------
Feedback
Yes
No
Powered by
