Re: Error Tk2-00001,

From: Oracle DBA <oracle_at_nightmare.com>
Date: 1996/07/04
Message-ID: <4rgrdg$s6_at_news.iag.net>#1/1


In article <31D3C66D.62AB_at_online.ru>, romas_at_online.ru says...
>
>Bob Poortinga wrote:
>>
>> pawel thommee <pawelt_at_interlog.com> reports:
>>
>> > I installed Oracle 7.3.2 on AIX 3.2.5 . This is the
 server configuration.
>> > We can access the database using PC connected to a
 network. Svrmgrl is
>> > operational.
>> >
>> > The graphical environment of AIX is Motif 1.2.3 ,
 xdm is operational.
>> > We used X-win32 package on PC conected to AIX,
 X-windows works, aixterm
>> > is operational. But I dont have svrmgrm operational.
 I have got an error
>> > message Tk2-00001.
>> >
>> > The question : how to get svrmgrm operational ?
>>
>
>also look at you NLS_LANG. Should be

 american_america.us7ascii
>fonts subs ;-( i things.
>
>
>> We had the same error and scratched our heads for a
 while. We finally
>> discovered that the Oracle Toolkit II Motif libraries
 are very picky
>> about the configuration of your X server. You must
 run your X server
>> in PseudoColor (256) color mode only. You cannot use
 TrueColor.
>>
>> This affects 'svrmgrm', 'orainst /m', and 'oradocm'.
>>
>> --
>> Bob Poortinga (mailto:bobp_at_tsc.com)
>> Senior Database Consultant
>> Technology Service Corp. (http://www.tsc.com)
>> Bloomington, Indiana USA
>
>--
> Sovam
 Teleport
>Roman L. Podshivalov phone (+7-501)
 258-4170
><mailto:romas_at_online.ru> fax (+7-501)
258-4133

Some other things to check would include:  

  Is MOTIF 1.2.3 supported for your OS. Check the ICG.   Are you using a valid terminal type. There needs to    be .res files for the ORACLE_TERM that you are using.    If you are do not have this set make sure your TERM is    valid.
  Not sure if your OS cares, but check to see if the    LD_LIBRARY_PATH includes the path where libXm.a is.   Is libXm.a readable by oracle. Does oracle have    permission to display on this xterminal. Ie... are    loggin in as another user then su to oracle. If so    the oracle user might not have permission to output to    the device. This will usually give you a different    error though.

oracle_at_nightmare.com Received on Thu Jul 04 1996 - 00:00:00 CEST

Original text of this message