- 论坛徽章:
- 0
|
错误00387是什么原因引起的？
Solution Description: ===================== Oracle Forms-based applications such as SQL*DBA and SQL*Forms use the environment variable TERM, or ORACLE_TERM, if it is set, to determine keyboard mapping. SQL*Reports does things a bit differently, and more information on how it handles keyboard mapping can be found in PRE 1010098.6 and in the second solution to this entry.
Keyboard Mapping is an Operating Specific issue that is controlled by resource files. Refer to the Oracle Tools for Unix Administrator's Reference Guide sections on Oracle*Terminal, and the application you are using for details.
Below is a list of common resource files and TERM/ORACLE_TERM settings:
vt100
vt220
ncd
sun/xsun
sun5/xsun5
hft
hp
wyse
If ORACLE_TERM is set, then the resource file for that value is used; otherwise, the resource file for TERM is used.
To view environment variables, type:
% env
To see their values, type:
% echo $TERM
% echo $ORACLE_TERM
To set environment variables in borne or korn shell, type:
% TERM=<terminal type>;; export TERM
% ORACLE_TERM=<terminal type>;; export ORACLE_TERM Examples:
% TERM=vt100; export TERM
% ORACLE_TERM=vt100; export ORACLE_TERM
To set environment variables in c shell, type:
% setenv TERM <terminal type>;
Example:
% setenv TERM vt100
Use the 'oraterm' tool to re-map the keys for a resource file. In 7.0.x SQL*DBA does not have a vt220 resource file.
The workaround is to use another value, such as vt100 There are 2 resources for each terminal type: dbac<terminal type>;.res and tk2c<terminal type>;.res
example: dbacvt100.res, tk2cvt100.res
These files should be in $ORACLE_HOME/rdbms/admin/terminal.
If they are not there, try copying them from $ORACLE_HOME/orainst.
For Sun4 (PORT 451), refer to bug:180225 -- some of the resource files are missing. |
|
免费注册
发表于 2003-07-01 21:57