I questioned and searched the solution.
I found some referring documents in Tivoli KnowledgeBase.
below
1)
---------------------------------------------------------------------------------------------------
"Exception:UserException:SysAdminException::ExException:RIM::ExRIMError:R" ...
is received in the dblog file.The complete error message is as
follows:IM::ExRIMRDBMSCallFailed:RIM::ExRIMSQLParseFailed /* 2001-05-24
17:46:03 nvColToSQL */ Line 303 File snmpColapi/nl_snmpColRIMDML.c 51: SQL
Server Error: Please see Server Error Message. /* 2001-05-24 17:46:03
nvColToSQL */ Line 102 File trapapi/nl_rimerr.c /* 2001-05-24 17:58:48
nvColToSQL */ Line 107 File trapapi/nl_rimerr.c Exception:
Solution
Product: TDS Guides for NetViewOS=AIXDB=OracleWhen running dataPush, it
processes smaller collections fine. When it encounters a larger collection, it
stops converting the collection files to sql and throws the following in the
dblog
file:Exception:UserException:SysAdminException::ExException:RIM::ExRIMError:R
IM::ExRIMRDBMSCallFailed:RIM::ExRIMSQLParseFailed /* 2001-05-24 17:46:03
nvColToSQL */ Line 303 File snmpColapi/nl_snmpColRIMDML.c 51: SQL Server Error:
Please see Server Error Message. /* 2001-05-24 17:46:03 nvColToSQL */
Line 102 File trapapi/nl_rimerr.c /* 2001-05-24 17:58:48 nvColToSQL */ Line 107
File trapapi/nl_rimerr.c Exception: "dataPush" uses at its root the traptosql
RIM tool. This tool has an upper limit of what size file it will convert. The
number is not the same for all systems. This is because, to increase
performance, RIM caches the entire file while converting it. So when it gets to
a file that is very large it eventually chokes on it. Use smaller collection
files and try different time parameters in the "snmpCollect" tool.
----------------------------------------------------------------------------------------------------
2)NV/NVCOLTOSQL-ERRORS IN /USR/OV/LOG/DBLOG SHOW GARBLED CHARACTERS : %7$S
Solution
Error Description: NV 6.0.1/nvColToSQL -error messages in /usr/OV/log/dblog:
Error no 0: Sev 0 Msg Default
Message: The RDBMS server call has faile The operation was: %7$s
The RDBMS server call's return code was:
%8$d Verified with L3 that messages will not cause data to
not be pushed into the RDBMS. If user sees messages stating data
has been inserted then the nvColToSQL is working properly. Local fix Message in
dblog is negligible in that it will not interfere with the data being pushed
into the database
----------------------------------------------------------------------------------------------------
Anybody have other idea?
Sincerely yours.
----- Original Message -----
From: bart@isiskorea.com
To: bart@isiskorea.com
Date: 2003-03-27 11:22:00
Subject: [nv-l] dblog error
Hi,there
I am using Tivoli NetView v7.1.3for Unix on AIX 4.3.3.
I collect some MIB instances(eg:BitsIn,BitsOut,avgBusyy5.etc..)evenry 5 minutes
and I tried to migrate flat data to RDBMS(Oracle 9i) in archive mode.
When I execute mvColToSQL command like this
nvColToSQL f BitsIn.1 -a
nvColToSQL f BitsIn.2 -a
nvColToSQL f BitsIn.3 -a
....
The excuted commands are successfully done. but When I see teh
dblog(/usr/OV/log/dblog),
There are many errors occurred like this
------------------------------------------------------------------------------------------
* 2003-03-26 16:48:43 nvColToSQL */
Application Id: nvColToSQL, Logfile name: /usr/OV/log/dblog, Tracefile
name: /usr/OV/log/dbtrace, Tracemask: 0
/* 2003-03-26 16:48:44 nvColToSQL */
Error no 51: Msg SQL Server Error: Please see Server Error Message.
/* 2003-03-26 16:48:44 nvColToSQL */
Error no 0: Sev 0 Msg Exception Name:
Exception:UserException:SysAdminException::ExException:RIM::ExRIMError:RIM::ExRIMRDBMSCallFailed:RIM::ExRIMSQLParseFailed
/* 2003-03-26 16:48:44 nvColToSQL */
Error no 51: Msg SQL Server Error: Please see Server Error Message.
/* 2003-03-26 16:48:44 nvColToSQL */
Error no 0: Sev 0 Msg Catalog: rim_errors
/* 2003-03-26 16:48:44 nvColToSQL */
Error no 51: Msg SQL Server Error: Please see Server Error Message.
/* 2003-03-26 16:48:44 nvColToSQL */
Error no 0: Sev 0 Msg Key: 17
/* 2003-03-26 16:48:44 nvColToSQL */
Error no 51: Msg SQL Server Error: Please see Server Error Message.
/* 2003-03-26 16:48:44 nvColToSQL */
Error no 0: Sev 0 Msg Default Message: The RDBMS server failed to
parse a SQL command string.
The operation was: %7$s
The RDBMS server call's return code was: %8$d
The SQL command string was:
<%9$s>
The error was at offset: %10$s
-------------------------------------------------------------------------------------------
Checking the RDBMS, almost data are inserted successfully but some are not.
How can I resolve this? This is related to RIM?
I anticipate the answer. :-)
Thanks in advance.
==================================================
KiYoul,Kong ,孔 棋 烈
Tivoli Consultant, MCSE .
10F,ShinSong Bld.YoidoDong,YoungDeungPo Province,Seoul,Korea.
Tel:82-2-3787-0250 Mobile:82-16-245-2491
E-Mail: bart@isiskorea.com
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
==================================================
KiYoul,Kong ,孔 棋 烈
Tivoli Consultant, MCSE .
10F,ShinSong Bld.YoidoDong,YoungDeungPo Province,Seoul,Korea.
Tel:82-2-3787-0250 Mobile:82-16-245-2491
E-Mail: bart@isiskorea.com
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|