| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Database Insertion Problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| contactop |
 Posted: Fri Oct 22, 2004 6:51 am Post subject: Database Insertion Problem |
 |
|
Acolyte
Joined: 26 Jun 2003
Posts: 50
|
hi,
I am unable to insert into Oracle Database.
Basic problem is - i am inserting records into Oracle, but some inserts get through and some fail.
But when i copy the same insert stmt fromtrace and paste on SQL prompt, i see that the Insert stmt works.
Thanks |
|
| Back to top |
|
 |
| kirani |
| Posted: Fri Oct 22, 2004 8:36 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Can you post your error message (ExceptionList)?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| contactop |
| Posted: Fri Oct 22, 2004 9:49 am Post subject: |
|
|
Acolyte
Joined: 26 Jun 2003
Posts: 50
|
2004-10-22 13:27:56.948704 33 UserTrace BIP4040I: The Execution Group 'GENESIS_METRIX' has processed a configuratio
n message successfully.
A configuration message has been processed successfully. Any configuration changes hav
e been made and stored persistently.
No user action required.
2004-10-22 13:27:56.951732 33 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempte
d to write a message to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' connected to queue manager 'AH300D001'. The MQCC was '0' a
nd the MQRC was '0'.
2004-10-22 13:27:56.951804 33 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageF
low.outputNode' to queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on queue manager 'AH300D001'.
2004-10-22 13:28:01.913522 37 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input nod
e 'OAG_FIXEDASSETTRANSACTION_ORACLE.OAG.ORACLE.FIXEDASSETTRANSACTION.IN'.
2004-10-22 13:28:01.913835 37 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'OAG_FIXEDASSE
TTRANSACTION_ORACLE.OAG.ORACLE.FIXEDASSETTRANSACTION.IN' to handle portion of incoming message of length 0 bytes beginning at
offset '0'.
2004-10-22 13:28:01.914312 37 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'OAG_FIXEDASSETTRANS
ACTION_ORACLE.OAG.ORACLE.FIXEDASSETTRANSACTION.IN' to handle portion of incoming message of length '364' bytes beginning at o
ffset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-10-22 13:28:01.914833 37 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'OAG_FIXEDASSETTRANSA
CTION_ORACLE.OAG.ORACLE.FIXEDASSETTRANSACTION.IN' to handle portion of incoming message of length '4' bytes beginning at offs
et '364'. Parser type selected based on value 'XML' from previous parser.
2004-10-22 13:28:02.391666 37 UserTrace BIP2537I: Node 'OAG_FIXEDASSETTRANSACTION_ORACLE.test': Executing statement
'BEGIN ... END;' at (.OAG_FIXEDASSETTRANSACTION_ORACLE_Compute4.Main, 2.2).
2004-10-22 13:28:02.392944 37 UserTrace BIP2537I: Node 'OAG_FIXEDASSETTRANSACTION_ORACLE.test': Executing statement
'PASSTHRU('INSERT INTO SAPINT.TEST
(TRAN_APPLD_IND,TRAN_TYPE,BOOK,ASSET_NUMBER, DATE_EFFECTIVE, SAP_TRAN_RETIRE_
VALUE,
SAP_TOTAL_VALUE, CORP, DIV, PLANT, DEPT, PROJ, PROD, LOC_CODE, COUNTRY, STATE
, COUNTY,
CITY, LOCATOR, INTERFACE_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY)
VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)', '
NEW', 'TRAN_TO', 'US CORP BOOK', 'SAP631000048', TIMESTAMP '2004-10-20 00:00:00', 1E+0, 1.00, 'PCO', 'PRI', '613', '2221', 'a
aa', '0000', 'A004', 'USA', 'TN', 'LEXINGT', 'HENDERS', '', TIMESTAMP '2004-10-21 17:22:17', TIMESTAMP '2004-10-21 17:22:17',
'-1')' at (.OAG_FIXEDASSETTRANSACTION_ORACLE_Compute4.Main, 3.3).
2004-10-22 13:28:02.393998 37 UserTrace BIP2544I: Node 'OAG_FIXEDASSETTRANSACTION_ORACLE.test': Executing database
SQL statement 'INSERT INTO SAPINT.TEST
(TRAN_APPLD_IND,TRAN_TYPE,BOOK,ASSET_NUMBER, DATE_EFFECTIVE, SAP_TRAN_RETIRE_
VALUE,
SAP_TOTAL_VALUE, CORP, DIV, PLANT, DEPT, PROJ, PROD, LOC_CODE, COUNTRY, STATE
, COUNTY,
CITY, LOCATOR, INTERFACE_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY)
VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)' de
rived from (.OAG_FIXEDASSETTRANSACTION_ORACLE_Compute4.Main, 3.3); expressions ''NEW', 'TRAN_TO', 'US CORP BOOK', 'SAP6310
00048', TIMESTAMP '2004-10-20 00:00:00', 1E+0, 1.00, 'PCO', 'PRI', '613', '2221', 'aaa', '0000', 'A004', 'USA', '
TN', 'LEXINGT', 'HENDERS', '', TIMESTAMP '2004-10-21 17:22:17', TIMESTAMP '2004-10-21 17:22:17', '-1''; resulting param
eter values ''NEW', 'TRAN_TO', 'US CORP BOOK', 'SAP631000048', TIMESTAMP '2004-10-20 00:00:00', 1E+0, 1.00, 'PCO', 'P
RI', '613', '2221', 'aaa', '0000', 'A004', 'USA', 'TN', 'LEXINGT', 'HENDERS', '', TIMESTAMP '2004-10-21 17:22:17',
TIMESTAMP '2004-10-21 17:22:17', '-1''.
2004-10-22 13:28:46.765688 33 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input nod
e 'ConfigurationMessageFlow.InputNode'.
2004-10-22 13:28:46.767288 33 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'Configuration
MessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-10-22 13:28:46.767960 33 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessag
eFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected ba
sed on value 'MQHMD' from previous parser.
2004-10-22 13:28:46.770148 33 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessage
Flow.InputNode' to handle portion of incoming message of length '239' bytes beginning at offset '364'. Parser type selected b
ased on value 'XML' from previous parser.
2004-10-22 13:28:46.830728 34 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input nod
e 'PubSubControlMsgFlow.InputNode'.
2004-10-22 13:28:46.833256 34 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'PubSubControl
MsgFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-10-22 13:28:46.833780 34 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'PubSubControlMsgFlo
w.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based
on value 'MQHMD' from previous parser.
2004-10-22 13:28:46.834164 34 UserTrace BIP6061I: Parser type 'MQRFH2' created on behalf of node 'PubSubControlMsgF
low.InputNode' to handle portion of incoming message of length '184' bytes beginning at offset '364'. Parser type selected ba
sed on value 'MQHRF2' from previous parser.
2004-10-22 13:28:46.834632 34 UserTrace BIP7079I: Node 'PubSubControlMsgFlow.ControlNode': The Publish/Subscribe se
rvice has received a message of type Publish.
The Publish/Subscribe service has started processing a control message.
No user action required.
2004-10-22 13:28:46.836308 34 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'PubSubControlMsgFlow
.InputNode' to handle portion of incoming message of length '1017' bytes beginning at offset '548'. Parser type selected base
d on value 'XML' from previous parser.
the problem is in the asset number, as we have defined length of 15, but it doesnot take more than length 11. But when inserted in to SQL prompt with 15 or 14 characters, it inserts. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
