nv-l
[Top] [All Lists]

Netview RIM problems, using Oracle DB with other that US7 NLS char set I

To: nv-l@lists.tivoli.com
Subject: Netview RIM problems, using Oracle DB with other that US7 NLS char set I?
From: sopee@WMDATA.DK
Date: Mon, 15 Nov 1999 10:40:43 +0100
I?m running Netview 5.1.1 (Framework 3.6) on AIX 4.3.2. We are currently working
on making the applications in our FM center highly available. One of the steps
that we are taking, besides from HACMP, is to move Netview to a DB platform.

The Environment:
       AIX 4.3.2
       Oracle 8.0.5
       Netview 5.1.1
       Framework 3.6

When I create the DB with a NLS character set, other than the default (US7), I
am unable to do the conversion from the flat files to the DB using the
ovtopoconv -R -v command. The only error description that I get is "Unable to
update topology tables". There is no relevant information in the dbtrace and
dblog, even when full tracing turned on. Then I tried to run a full RIM trace.
The trace returns the following error codes:

--------------------------------------------------------------------------------------------------------------------------------------
00023300 [Sun Nov 14 08:02:46 1999] Trace Message - Connection ID::
IOM Command: INSERT
row_param: <NULL>
rows: No. of Rows: 1
First Row : Table Name : topoinfo Columns:
        objid(S): 1014
        ctime(D): 1999.11.14 02:52:49
        mtime(D): 1999.11.14 07:54:54
        stime(D): 1999.11.14 02:52:49
        flags(L): 0
        gwcnt(L): 21
        nnmtype(L): 0
        topm_network_ct(L): 80
        topm_segment_ct(L): 85
        topm_node_ct(L): 85
        topm_interface_ct(L): 162
        scale_x(L): 0
        scale_y(L): 0
        extra0(L): 0
        extra1(L): 0

SQL Command: insert into topoinfo (objid, ctime, mtime, stime, flags, gwcnt, nnm
type, topm_network_ct, topm_segment_ct, topm_node_ct, topm_interface_ct, scale_x
, scale_y, extra0, extra1) values (:objid, TO_DATE('1999.11.14 02:52:49', 'YYYY.
MM.DD HH24:MI:SS'), TO_DATE('1999.11.14 07:54:54', 'YYYY.MM.DD HH24:MI:SS'), TO_
DATE('1999.11.14 02:52:49', 'YYYY.MM.DD HH24:MI:SS'), :flags, :gwcnt, :nnmtype,
:topm_network_ct, :topm_segment_ct, :topm_node_ct, :topm_interface_ct, :scale_x,
 :scale_y, :extra0, :extra1)
        ORA-01461: can bind a LONG value only for insert into a LONG column

00023300 [Sun Nov 14 08:02:46 1999] Trace Message - Connection ID:: The RDBMS se
rver failed to parse a SQL command string.
The operation was:  ORALIB:oexec
The RDBMS server call's return code was:  0
The SQL command string was:
    <insert into topoinfo (objid, ctime, mtime, stime, flags, gwcnt, nnmtype, to
pm_network_ct, topm_segment_ct, topm_node_ct, topm_interface_ct, scale_x, scale_
y, extra0, extra1) values (:objid, TO_DATE('1999.11.14 02:52:49', 'YYYY.MM.DD HH
24:MI:SS'), TO_DATE('1999.11.14 07:54:54', 'YYYY.MM.DD HH24:MI:SS'), TO_DATE('19
99.11.14 02:52:49', 'YYYY.MM.DD HH24:MI:SS'), :flags, :gwcnt, :nnmtype, :topm_ne
twork_ct, :topm_segment_ct, :topm_node_ct, :topm_interface_ct, :scale_x, :scale_
y, :extra0, :extra1) >
The error was at offset:  0

--------------------------------------------------------------------------------------------------------------------------------------

As you can see in the trace above, there is an error when doing the insert. The
error describes that an attempt has been made to insert a long field into
another type of field, witch doesn?t make a lot on sense.

As I mentioned there is no problem when running Oracle with the default NLS char
set US7. Could the problem be related to some missing environment in the RIM
setup ?

Any suggestions will be appreciated.

Regards

S. Bonde Pedersen
Systems Management WM-data/Denmark


<Prev in Thread] Current Thread [Next in Thread>
  • Netview RIM problems, using Oracle DB with other that US7 NLS char set I?, sopee <=

Archive operated by Skills 1st Ltd

See also: The NetView Web