Error in log file CallbackDispather
We've been seeing a random occurance of the following error:
Thu May 17 04:27:12 EDT 2001:<I> <Kernel> Address: '39942' in use by: 'weblogic.common.CallbackDispatcher@9c06',
can not
install 'weblogic.rmi.internal.BasicRemoteInvokable@9c06'
Thu May 17 04:42:48 EDT 2001:<I> <Kernel> Address: '40135' in use by: 'weblogic.common.CallbackDispatcher@9cc7',
can not
install 'ClientContext - id: '#|website|19910.989894283938', bound: 'false', dead:
'false''
Thu May 17 07:19:22 EDT 2001:<I> <Kernel> Address: '42099' in use by: 'weblogic.common.CallbackDispatcher@a473',
can not
install 'ClientContext - id: '#|website|20892.989894283938', bound: 'false', dead:
'false''
I happens sometimes about an hour appart sometimes 12 hour or so hours aart. There
doesn't seem to be any pattern. What would cause this?
We are running on a
E450 4 Proc box, WLS 5.1 SP6
In front of it we have E250 2 proc, iPlanet 4.1 SP5
Behind it we have E4500 8 proc, Oracle 8.1.5
Were using the oci driver.
We started seeing these after making a code change, where we set the auto commit
to false and explictly committed all transactions. Obviously something with this
has an effect. Can anyone help us understand what and why.
Thanks in advance.
Did you promoted/demoted a server? ( like from consumer to master , master to consumer , hub to consumer/master OR disabled replication and re-enabled with another unique ID and recreated replication agreements again?
IF YES, find out the current Unique ID in all the related server and delete the old serverIDs in the nsslapd-rererral.
Also the error will tell you for which server it is trying to update the duplicate entry. Mostly , that entry will be the old value as I explained before.
I have seen this before and mostly by doing above it gets corrected. I recommend that you should think before doing it.
In any case dont forget to update us since this is a tricky situation to me.
-Kunal
Similar Messages
-
Error in log file of consumer.
hi
i have following error in log file of consumer. i have no idea why i appear.
[08/Oct/2003:10:56:00 -0500] - ERROR<5398> - Entry - conn=-1 op=-1 msgId=-1 - Duplicate value addition in attribute "nsslapd-referral" of entry "cn=\22dc=alltel,dc=com\22,cn=mapping tree,cn=config"
Thanking you,
kumarDid you promoted/demoted a server? ( like from consumer to master , master to consumer , hub to consumer/master OR disabled replication and re-enabled with another unique ID and recreated replication agreements again?
IF YES, find out the current Unique ID in all the related server and delete the old serverIDs in the nsslapd-rererral.
Also the error will tell you for which server it is trying to update the duplicate entry. Mostly , that entry will be the old value as I explained before.
I have seen this before and mostly by doing above it gets corrected. I recommend that you should think before doing it.
In any case dont forget to update us since this is a tricky situation to me.
-Kunal -
How to print only fatal error in log file in tomcat4.1
Hi all ,i m using tomcat4.1
1> i want to print only fatal error in log file ,but it print all thing in log file ,how i can avoid it(because i think this process is consuming my resource)
assume below ip address is corect:
this is exact printing in my log file
.12.2.3.3 - - [24/Oct/2007:00:00:00 5050] "GET /menu/ir.jsp HTTP/1.1" 200 2828
12.2.3.3 - - [24/Oct/2007:00:00:00 5050] "GET /menu/bottomAdv.jsp HTTP/1.1" 200 528
12.2.3.3 - - [24/Oct/2007:00:00:02 5050] "GET /menu/alerts.jsp HTTP/1.1" 200 323
12.2.3.3 - - [24/Oct/2007:00:00:02 5050] "GET /alerts/createAlertShow.jsp HTTP/1.1" 200 26140
123.2.3. - - [24/Oct/2007:00:00:05 5050] "GET /menu/getsensex.jsp HTTP/1.1" 200 642
12.2.3.3 - - [24/Oct/2007:00:00:05 5050] "GET /menu/latestRecommendation.jsp HTTP/1.1" 200 5210
12.2.3.3 - - [24/Oct/2007:00:00:05 5050] "GET /portfolio/watchlist/displayWatchlistItemsShow.jsp?watchlistId=20070509013642953_1&watchlistName=First&refreshRate=900&flag=1 HTTP/1.1" 500 7257
12.2.3.3 - - [24/Oct/2007:00:00:05 5050] "GET /menu/iwealthNewsScroller.jsp HTTP/1.1" 200 2828
112.23.3 - - [24/Oct/2007:00:00:06 5050] "GET /menu/alerts.jsp HTTP/1.1" 200 323
112.23.3 - - [24/Oct/2007:00:00:06 5050] "GET /menu/bottomAdv.jsp HTTP/1.1" 200 528
12.2.3.3 - - [24/Oct/2007:00:00:07 5050] "GET /menu/alerts.jsp HTTP/1.0" 200 323
12.2.3.3 - - [24/Oct/2007:00:00:09 5050] "POST /Transaction/equity/modifyConfirmShow.jsp?DelId=0 HTTP/1.1" 200 28661
12.2.3.3 - - [24/Oct/2007:00:00:09 5050] "GET /menu/getsensex.jsp HTTP/1.1" 200 6422>what will happen if i change timestamp="false" and what is the significance of verbosity="1" or "2" or "3" ,or "4" and what happen if i change debug="1" or other in below code
<Logger className="org.apache.catalina.logger.FileLogger" debug="0" directory="logs" prefix="www.xyz_log." suffix=".txt" timestamp="true" verbosity="4"/>Edited by: Deepak23 on Oct 24, 2007 10:41 PM
Edited by: Deepak23 on Oct 24, 2007 11:16 PMOne of my standard answers (which will explain the use of Directory Objects)...
The UTL_FILE_DIR parameter has been deprecated by oracle in favour of direcory objects because of it's security problems.
The correct thing to do is to create a directory object e.g.:
CREATE OR REPLACE DIRECTORY mydir AS 'c:\myfiles';Note: This does not create the directory on the file system. You have to do that yourself and ensure that oracle has permission to read/write to that file system directory.
Then, grant permission to the users who require access e.g....
GRANT READ,WRITE ON DIRECTORY mydir TO myuser;Then use that directory object inside your FOPEN statement e.g.
fh := UTL_FILE.FOPEN('MYDIR', 'myfile.txt', 'r');Note: You MUST specify the directory object name in quotes and in UPPER case for this to work as it is a string that is referring to a database object name which will have been stored in uppercase by default. -
Error in log file (WWC-41439)
Hi,
When i installed Oracle Portal, i had the error WWc-41439 when i tried log in Oracle Portal. I revised the log file and i saw the following error.(I have isntalled Oracle Portal 3.0., Oracle Database 8.1.7 on windows NT).
STEP 24 : Installing SSO packages to public
INSTALL_ACTION : installSSOLayer()..\..\bin\sqlplus portal30_sso/portal30_sso@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=or8i))) @..\..\portal30\admin\plsql\sso\ssoinsg.sql
STEP 25 : Associating Login Server & Oracle Portal
INSTALL_ACTION :assocNewLoginServer: Portal Url Prefix: http://pablo/pls/portal30/
INSTALL_ACTION :assocNewLoginServer: SSO URL Prefix: http://pablo/pls/portal30_sso/
INSTALL_ACTION : assocNewLoginServer: ..\..\bin\sqlplus portal30_sso/portal30_sso@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=or8i))) @..\..\portal30\admin\plsql\sso\ssoseedl.sql portal30 http://pablo/pls/portal30/ portal30_sso http://pablo/pls/portal30_sso/ NO
INSTALL_ACTION : assocNewLoginServer: ..\..\bin\sqlplus portal30_sso/portal30_sso@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=or8i))) @..\..\portal30\admin\plsql\sso\ssoinsgp.sql portal30
INSTALL_ACTION : assocNewLoginServer:..\..\bin\sqlplus portal30/portal30@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=or8i))) @..\..\portal30\admin\plsql\sso\ssoseedw.sql portal30 portal30_sso http://pablo/pls/portal30_sso/ http://pablo/pls/portal30/
INSTALL_ACTION : STEP 19 : assocNewLoginServer:..\..\bin\sqlplus portal30/portal30@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=or8i))) @..\..\portal30\admin\plsql\wwc\secpsr.sql
INSTALL_ACTION : STEP 19 : assocNewLoginServer:..\..\bin\sqlplus portal30/portal30@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=or8i))) @..\..\portal30\admin\plsql\wwc\secps.sql portal30_sso_PS N N N N
INSTALL_ACTION : assocNewLoginServer:..\..\bin\sqlplus portal30_sso/portal30_sso@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=or8i))) @..\..\portal30\admin\plsql\sso\ssoinsrp.sql portal30
INSTALL_ACTION : assocNewLoginServer:..\..\bin\sqlplus portal30_sso/portal30_sso@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=or8i))) @..\..\portal30\admin\plsql\sso\ssoseedu.sql portal30
Installing and running diagnostics
INSTALL_ACTION:installDiagnostics() : ..\..\bin\loadjava -resolve -verbose -thin -user portal30/portal30@localhost:1521:or8i ..\..\portal30\admin\plsql\wwc\Diagnose.class
C:\ORACLE\iSuites\assistants\opca>REM
C:\ORACLE\iSuites\assistants\opca>REM $Header: runljava.bat@@/main/3 \
C:\ORACLE\iSuites\assistants\opca>REM Checked in on Fri Nov 17 15:32:36 PST 2000 by meoropez \
C:\ORACLE\iSuites\assistants\opca>REM Copyright (c) 2000 by Oracle Corporation. All Rights Reserved. \
C:\ORACLE\iSuites\assistants\opca>REM $
C:\ORACLE\iSuites\assistants\opca>REM
C:\ORACLE\iSuites\assistants\opca>Rem For running the Loadjava from the Configuration Assistant.
C:\ORACLE\iSuites\assistants\opca>..\..\bin\loadjava -resolve -verbose -thin -user portal30/portal30@localhost:1521:or8i ..\..\portal30\admin\plsql\wwc\Diagnose.class
INSTALL_ACTION : Running Diagnostics ..\..\bin\sqlplus portal30/portal30@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SID=or8i))) @..\..\portal30\admin\plsql\wwc\secdiag.sql
SQL*Plus: Release 8.1.7.0.0 - Production on Dom Abr 20 20:23:37 2003
(c) Copyright 2000 Oracle Corporation. All rights reserved.
Conectado a:
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Creating Table 'wwsec_diagnostic$'
Creating Sequence 'wwsec_diagnostic_seq'
Diagnostics Report v 1.01: Oracle Portal v 3.0.9.8.0
As of 20-Abr-2003 20:23:41 Schema Name: PORTAL30 SSO Schema Name: portal30_sso
Proxy Server Settings:
HTTP Server:
HTTP Server Port:
No Proxy Servers for Domains beginning with:
URL Connection Time-Out (seconds):
PORTAL30.wwsec_enabler_config_info$
Login Server URL : http://pablo/pls/portal30_sso/portal30_sso.wwsso_app_admin.ls_login
DAD : portal30_sso
Host connection : *** FAILED ***
Unable to find the Schema Name for the Login Server
Recommendations:
Please check the DAD settings for the Login Server
Desconectado de Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
INSTALL_ACTION : End of Installation.
How i resolve the problem?
Is there somebody in the same situacion?
Thank youDid you promoted/demoted a server? ( like from consumer to master , master to consumer , hub to consumer/master OR disabled replication and re-enabled with another unique ID and recreated replication agreements again?
IF YES, find out the current Unique ID in all the related server and delete the old serverIDs in the nsslapd-rererral.
Also the error will tell you for which server it is trying to update the duplicate entry. Mostly , that entry will be the old value as I explained before.
I have seen this before and mostly by doing above it gets corrected. I recommend that you should think before doing it.
In any case dont forget to update us since this is a tricky situation to me.
-Kunal -
I am wondering if anyone has ever seen errors like this. They started showing up in our log file recently with the error below. Once this error starts, then tons of errors are generated and the log file grows exponentially.
2006-12-12 06:51:26,109 WARN [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl [FormatId=257, GlobalId=naap11//13513, BranchQual=] timed out. status=STATUS_ACTIVE
2006-12-12 06:51:26,124 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException in method: public abstract com.adobe.pof.omapi.POFObjectSet com.adobe.pof.omapi.POFObjectManagerLocal.retrieveObjectSet(com.adobe.pof.omapi.POFQuery, int,int,com.adobe.idp.Context) throws com.adobe.pof.POFException, causedBy:
org.jboss.util.NestedSQLException: Interrupted while requesting permit! Waited 0 ms; - nested throwable: (javax.resource.ResourceException: Interrupted while requesting permit! Waited 0 ms)
Eventually, we get the following message:
2006-12-12 06:51:30,622 WARN [org.jboss.ejb.plugins.jms.DLQHandler] Message resent too many times; sending it to DLQ; message id=ID:7-116593508609324
2006-12-12 06:51:30,622 WARN [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl [FormatId=257, GlobalId=naap11//17644, BranchQual=] timed out. status=STATUS_ACTIVE
2006-12-12 06:51:30,638 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Could not send message to Dead Letter Queue
We are using LiveCycle 7.2 (WF, FM, FS and RES). Any ideas are welcome.where i should place my .cgi files folder in apllication context
....i am using jboss server -
Error in log file - Row wrong informed
Hello. I have an error about the log file. Depending of the READ SIZE parameter, the number of the rows informed aren't correct. For example, if I set READSIZE parameter to 10000 and I try load an file with errors, the line informed in the log is 29 but it should be 28, the line informed in the log is 58 but it should be 59 and so.
Any help?
Thanks!file:
example de row:
AAAAAAAAAAAAAA#AAAAAAAAAA#AAAAAAAAAAAAA#AAAAAAAAAA#AAA#AAAAAAAA#AAAAAAAAAAAAAAAAAAAAAAAAAAAA#AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA#AAA#AAAAAAAAAA#AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA#AAAAAAAAAAAAAAAAAAAAAAAAA#AAAAAAAA#AAAA#AAAAA#AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
log:
LOG file opened at 01/25/13 11:02:49
Field Definitions for table TMP_401143
Record format DELIMITED BY NEWLINE
Data in file has same endianness as the platform
Reject rows with all null fields
Fields in Data Source:
UPLD_AUX_FLD_01 CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_DATADHSTART CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_INT_VL CHAR (255)
Terminated by "#"
Trim whitespace same as SQL Loader
PREMAMNTRCV CHAR (255)
Terminated by "#"
Trim whitespace same as SQL Loader
UPLD_AUX_FLD_15 CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_AUX_FLD_16 CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_NME CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_AUX_FLD_14 CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_AUX_FLD_04 CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_BTH_DT CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_ADR CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_ADR2 CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_CTY CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_ADR_CMP CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_ZIP CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_PHO_CMM_NBR CHAR (255)
Terminated by "#"
Trim whitespace from left and right
CLIENTBANKCODE CHAR (255)
Terminated by "#"
Trim whitespace from left and right
CLIENTAGENCYCODE CHAR (255)
Terminated by "#"
Trim whitespace from left and right
UPLD_CREDITCARNUM CHAR (255)
Terminated by "#"
Trim whitespace from left and right
CREDITCARDTYPE CHAR (255)
Terminated by "#"
Trim whitespace from left and right
CLIENTTYPE CHAR (255)
Terminated by "#"
Trim whitespace from left and right
error processing column PREMAMNTRCV in row 1 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 2 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 3 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 4 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 5 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 6 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 7 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 8 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 9 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 10 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 11 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 12 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 13 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 14 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 15 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 16 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 17 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 18 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 19 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 20 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 21 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 22 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 23 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 24 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 25 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 26 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 27 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 28 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 30 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 31 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 32 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 33 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 34 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 35 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 36 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 37 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 38 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 39 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 40 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 41 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 42 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 43 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 44 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 45 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 46 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 47 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 48 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 49 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 50 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 51 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 52 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 53 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 54 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 55 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 56 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 57 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 59 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 60 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 61 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 62 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 63 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 64 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 65 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 66 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 67 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 68 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 69 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 70 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 71 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 72 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 73 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 74 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 75 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 76 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 77 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 78 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 79 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 80 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 81 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 82 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 83 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 84 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 85 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 86 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 88 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 89 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 90 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 91 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 92 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 93 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 94 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 95 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 96 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 97 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 98 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 99 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 100 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 101 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 102 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 103 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 104 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 105 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 106 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 107 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 108 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 109 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 110 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 111 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 112 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 113 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 114 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 115 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 117 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 118 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 119 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 120 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 121 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 122 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 123 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 124 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 125 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 126 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 127 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 128 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 129 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 130 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 131 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 132 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 133 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 134 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 135 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 136 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 137 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 138 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 139 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 140 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 141 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 142 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 143 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 144 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 145 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 147 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 148 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 149 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 150 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 151 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 152 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 153 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 154 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 155 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 156 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 157 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 158 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 159 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 160 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 161 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 162 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 163 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 164 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 165 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 166 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 167 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 168 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 169 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 170 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 171 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 172 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 173 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 174 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 176 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 177 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 178 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 179 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 180 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 181 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 182 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 183 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 184 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 185 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
error processing column PREMAMNTRCV in row 186 for datafile c:\\INBOX1\prueba.PRO
ORA-01722: invalid number
script:
create table SCHE.Tmp_401135( UPLD_AUX_FLD_01 VARCHAR2 (50), UPLD_DATADHSTART VARCHAR2(20), UPLD_INT_VL VARCHAR2 (182), PREMAMNTRCV NUMBER (28,2), UPLD_AUX_FLD_15 VARCHAR2 (50), UPLD_AUX_FLD_16 VARCHAR2 (50), UPLD_NME VARCHAR2 (100), UPLD_AUX_FLD_14 VARCHAR2 (180), UPLD_AUX_FLD_04 VARCHAR2 (50), UPLD_BTH_DT VARCHAR2(20), UPLD_ADR VARCHAR2 (180), UPLD_ADR2 VARCHAR2 (180), UPLD_CTY VARCHAR2 (50), UPLD_ADR_CMP VARCHAR2 (40), UPLD_ZIP CHAR (15), UPLD_PHO_CMM_NBR VARCHAR2 (10), CLIENTBANKCODE VARCHAR2 (25), CLIENTAGENCYCODE VARCHAR2 (20), UPLD_CREDITCARNUM VARCHAR2 (25), CREDITCARDTYPE VARCHAR2 (15), CLIENTTYPE VARCHAR2 (20))
organization external (type oracle_loader default directory INBOX1 access parameters (records delimited by newline
badfile Loadfile1:'prueba.PRO.bad'
logfile Loadfile1:'prueba.PRO.log'
discardfile Loadfile1:'prueba.PRO.dsc'
READSIZE 10000 fields terminated by '#' missing field values are null REJECT ROWS WITH ALL NULL
FIELDS (UPLD_AUX_FLD_01 CHAR LRTRIM, UPLD_DATADHSTART CHAR LRTRIM, UPLD_INT_VL , PREMAMNTRCV , UPLD_AUX_FLD_15 CHAR LRTRIM, UPLD_AUX_FLD_16 CHAR LRTRIM, UPLD_NME CHAR LRTRIM, UPLD_AUX_FLD_14 CHAR LRTRIM, UPLD_AUX_FLD_04 CHAR LRTRIM, UPLD_BTH_DT CHAR LRTRIM, UPLD_ADR CHAR LRTRIM, UPLD_ADR2 CHAR LRTRIM, UPLD_CTY CHAR LRTRIM, UPLD_ADR_CMP CHAR LRTRIM, UPLD_ZIP CHAR LRTRIM, UPLD_PHO_CMM_NBR CHAR LRTRIM, CLIENTBANKCODE CHAR LRTRIM, CLIENTAGENCYCODE CHAR LRTRIM, UPLD_CREDITCARNUM CHAR LRTRIM, CREDITCARDTYPE CHAR LRTRIM, CLIENTTYPE CHAR LRTRIM) )
location ('prueba.PRO')) reject limit 250 -
SQLException Error in Log file
Does anyone know of the following error, and how to fix this? I keep getting it in my engine log file like every 30 mn.
Thank you,
-Lilach
--------------------------------------------- Error -----------------------------------------------------------------
Exception [java.sql.SQLException: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.].
Caused by: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.
Caused by: [BEA][SQLServer JDBC Driver][SQLServer]The statement has been terminated.
fuego.directory.DirectoryRuntimeException: Exception [java.sql.SQLException: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.].
at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
at fuego.directory.provider.jdbc.mssqlserver.MSSQLServerPersistenceManager.mapSQLException(MSSQLServerPersistenceManager.java:116)
at fuego.directory.provider.jdbc.JDBCServiceAccessor.mapSQLException(JDBCServiceAccessor.java:78)
at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipant(JDBCParticipantsAccessor.java:221)
at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipant(JDBCParticipantsAccessor.java:180)
at fuego.directory.hybrid.jdbc.DelegatorFuegoParticipantAccessor.updateOrPersistHumanParticipant(DelegatorFuegoParticipantAccessor.java:224)
at fuego.directory.hybrid.HybridParticipantAccessor.updateHumanParticipant(HybridParticipantAccessor.java:377)
at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
at $Proxy6.updateHumanParticipant(Unknown Source)
at fuego.directory.hybrid.HybridParticipantAccessor.fetchHumanParticipant(HybridParticipantAccessor.java:189)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
at $Proxy6.fetchHumanParticipant(Unknown Source)
at fuego.directory.provider.notifiers.DirObjectType$3.fetchDirObjectFor(DirObjectType.java:74)
at fuego.directory.provider.notifiers.DirectoryObjectProxy.getObject(DirectoryObjectProxy.java:160)
at fuego.directory.provider.notifiers.DirectoryObjectProxy.createAddEvent(DirectoryObjectProxy.java:91)
at fuego.directory.provider.notifiers.BasePollingEventGenerator.buildEvents(BasePollingEventGenerator.java:148)
at fuego.directory.hybrid.ldap.LDAPPollingEventGenerator.buildEvents(LDAPPollingEventGenerator.java:109)
at fuego.directory.provider.notifiers.BasePollingEventGenerator.generateEvents(BasePollingEventGenerator.java:51)
at fuego.directory.hybrid.HybridMultipleEventGenerator.generateEvents(HybridMultipleEventGenerator.java:43)
at fuego.directory.provider.notifiers.DirectoryNotifier.notifyChanges(DirectoryNotifier.java:403)
at fuego.server.service.DirectoryListener.updateEngineFromDirectoryImpl(DirectoryListener.java:328)
at fuego.server.service.DirectoryListener$DirectoryPollingItem.execute(DirectoryListener.java:381)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
at fuego.fengine.service.FEngineExecution.executeImmediate(FEngineExecution.java:65)
at fuego.server.execution.DefaultEngineExecution.executeWithoutComponentImmediate(DefaultEngineExecution.java:185)
at fuego.server.execution.EngineExecution.executeWithoutComponentImmediate(EngineExecution.java:86)
at fuego.server.execution.PollingDirectory.execute(PollingDirectory.java:46)
at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62)
at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:251)
at fuego.server.execution.ToDoItem.run(ToDoItem.java:536)
at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:775)
at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
at fuego.fengine.ToDoQueueThread$PrincipalWrapper.processBatch(ToDoQueueThread.java:446)
at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
Caused by: java.sql.SQLException: [BEA][SQLServer JDBC Driver][SQLServer]String or binary data would be truncated.
at albpm.jdbc.base.BaseExceptions.createException(Unknown Source)
at albpm.jdbc.base.BaseExceptions.getException(Unknown Source)
at albpm.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
at albpm.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
at albpm.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
at albpm.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
at albpm.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source)
at albpm.jdbc.base.BaseStatement.commonTransitionToState(Unknown Source)
at albpm.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
at albpm.jdbc.base.BasePreparedStatement.postImplExecute(Unknown Source)
at albpm.jdbc.base.BaseStatement.commonExecute(Unknown Source)
at albpm.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
at albpm.jdbc.base.BasePreparedStatement.executeUpdate(Unknown Source)
at fuego.jdbc.FaultTolerantPreparedStatement.executeUpdate(FaultTolerantPreparedStatement.java:623)
at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createParticipantInfo(JDBCParticipantsAccessor.java:1280)
at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipantInternal(JDBCParticipantsAccessor.java:1195)
at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.createHumanParticipant(JDBCParticipantsAccessor.java:217)
... 49 moreHi All ,
I having this error . Are there any fixes for this bug ?
my configuration file is like the following ;
+<?xml version="1.0" encodxxx="UTF-8"?>+
+<?fuego version="6.1 ALPHA" application="albpmenterprise"?>+
+<!-- This file contains the propper attribute mappxxx for the FDI Generic Ldap Provider usxxx Oracle Internet Directory.+
+ * Preference for group object+
+ <preference id="assignedParticipants.containsId" value="true"/>+
+ This preference is useful to speed up the provider and it can only be used if the assignedParticipant value is the dn of the user and the dn contains the participant id+
+ <preference id="assignedParticipants.containsId" value="true"/>+
+ This preference is useful to speed up the provider and it can only be used if the assignedGroup value is the dn of the group and the dn contains the group id+
+ <preference id="modifyTimeStamp.suffix" value="Z"/>+
+ This preference is useful when the suffix mofidyTimeStamp format of your ldap is not .OZ.+
-->
+<config>+
+ <object id="person">+
+ <object-filter>+
+ <![CDATA[+
+ (objectclass=person)+
+ ]]>+
+ </object-filter>+
+ <relative-dn>ou=xxxBANK,cn=Users</relative-dn>+
+ <attribute id="id" value="uid"/>+
+ <attribute id="lastName" value="sn"/>+
+ <attribute id="firstName" value="givenname"/>+
+ <attribute id="displayName" value="displayname"/>+
+ <attribute id="mail" value="mail"/>+
+ <attribute id="telephoneNumber" value="telephonenumber"/>+
+ <attribute id="employeeId" value="employeeNumber"/>+
+ <attribute id="thumbnailPhoto" value="thumbnailPhoto"/>+
+ <attribute id="manager" value="manager"/>+
+ <attribute id="modifyTimeStamp" value="modifyTimestamp"/>+
+ </object>+
+ <object id="group">+
+ <object-filter>+
+ <![CDATA[+
+ (objectclass=xxxGroupObject)+
+ ]]>+
+ </object-filter>+
+ <relative-dn>+
+ <!-- the relative dn for group --></relative-dn>+
+ <attribute id="id" value="cn"/>+
+ <attribute id="modifyTimeStamp" value="modifyTimestamp"/>+
+ <attribute id="displayName" value="cn"/>+
+ <attribute id="name" value="cn"/>+
+ <attribute id="description" value="description"/>+
+ <attribute id="assignedParticipants" value="uniquemember"/>+
+ <attribute id="assignedGroups" value="uniquemember"/>+
+ <attribute id="ou" value="distxxxuishedName"/>+
+ </object>+
+ <object id="ou">+
+ <object-filter>+
+ <![CDATA[+
+ (objectclass=xxxOUObject)+
+ ]]>+
+ </object-filter>+
+ <relative-dn>+
+ <!-- the relative dn for ous -->+
+ </relative-dn>+
+ <attribute id="name" value="ou"/>+
+ <attribute id="description" value="description"/>+
+ </object>+
+</config>+ -
I just updated an existing slide show that was created several months back. Since loading my new set of files to our web server, we keep getting the following error in our server log files when someone loads our page in IE8 and IE9:
File does not exist: /www/public_html/null, referer:
One of our programmers tracked the error to this line of code, but we're not sure what's causing it:
Muse.Utils.addSelectorFn('#slideshowu70', function(elem) { new WebPro.Widget.ContentSlideShow(elem, {autoPlay:true,displayInterval:6000,slideLinkStopsSlideShow:false,transitionStyle:'horizo ntal',lightboxEnabled_runtime:false,shuffle:false}); });/* #slideshowu70 */
Any suggestions?
Thanks!The errors aren't showing up on the client side, only in the server access logs. Every time the page is loaded with IE8 or IE9 and the Muse.Utils.addSelectorFn with the #slideshowu70 line is hit, it generates four errors in the server access logs.
Our admin guy pulled the errors from where it was clicked on from the Adobe forum. He said it also appeared that you tested it with www added to the url (if this was when you were testing it)...
[Mon Feb 04 13:58:57 2013] [error] [client 121.242.198.2] File does not exist: /www/public_html/null, referer:http://stingrayboats.com/
[Mon Feb 04 13:59:00 2013] [error] [client 121.242.198.2] File does not exist: /www/public_html/null, referer:http://stingrayboats.com/
[Mon Feb 04 13:59:08 2013] [error] [client 121.242.198.2] File does not exist: /www/public_html/null, referer:http://stingrayboats.com/
[Mon Feb 04 13:59:33 2013] [error] [client 121.242.198.2] File does not exist: /www/public_html/null, referer:http://www.stingrayboats.com/
[Mon Feb 04 13:59:43 2013] [error] [client 121.242.198.2] File does not exist: /www/public_html/null, referer:http://www.stingrayboats.com/
The reason we find it strange is because it did not result in errors with the previous version of the slideshow. The only thing that changed this time around is that I removed some slides and added additional ones, but I noticed that there is a lot of difference in the code and even the scripts that are used. And I did copy over all of the scripts, css files, etc., so it's using all of the new source files.
I was hoping it was something that you guys had noticed if you review the access logs when you're testing. While it works perfectly on the client side, the IT guys do go through our access logs, so it would be nice to eliminate the errors.
Thanks for looking at it! -
Error in Log file from a scheduled materialized view
Hi
Getting the following errors in the alert_xe.log file when refreshing a materialized view. The data from the materialized view seems fine.
ORA-12012: error on auto execute of job 1
ORA-12008: error in materialized view refresh path
ORA-01555: snapshot too old: rollback segment number 41 with name "_SYSSMU41$" too small
ORA-02063: preceding line from HRLIVE
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2566
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2779
ORA-06512: at "SYS.DBMS_IREFRESH", line 685
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
This is with XE Apex 4.1
Thanks for any suggestionsThanks - tried google and changing undo_retention but no luck.
We noticed something very odd...
TABLESPACE_NAME AUT
E:\ORACLEXE_11G\APP\ORACLE\ORADATA\XE\USERS.DBF
USERS YES
E:\ORACLEXE_11G\APP\ORACLE\ORADATA\XE\SYSAUX.DBF
UNDOTBS1 YES
E:\ORACLEXE_11G\APP\ORACLE\ORADATA\XE\UNDOTBS1.DBF
SYSAUX YES
E:\ORACLEXE_11G\APP\ORACLE\ORADATA\XE\SYSTEM.DBF
SYSTEM YES
The file SYSAUX.DBF has table space UNDOTBS1
and file UNDOTBS1.DBF has table space SYSAUX
This looks the wrong way around.
Any ideas how this could have happened and how this can be changed?
Thanks & regards
Edited by: rw on Jan 18, 2012 8:32 AM -
Cannot publish get error message - log file not being created
When trying to publish a FlashHelp project, I get an error
message window that says "Publishing has been cancelled. Failed to
create file: (project name).log "
When I click okay in the message window, the publishing
process stops. However, if I look in the SSL folder, I see the log
file. It is a text file.
I had this problem in January 09 but it seemed to be an issue
with the password and path in the FTP command window. I fixed it
and it worked fine. However, I haven't published since the end of
January. Now, when I try to publish, it is giving me the same error
message. I checked and reviewed the FTP window fields and they are
fine. But I'm still getting the error message and can't publish.
Why?
I need to get this problem fixed ASAP and ensure that it
doesn't occur again. What's strange is that I've got 3 other
projects and this is the only 1 that gets this error message.Yes, the generation worked. I checked the log file that
worked from the time it worked before and it seems to be the same
as the log file that is generated when I get the error message.
I created a new FlashHelp layout and got the same error
message. What's really weird is there is a log file in the SSL
folder but when you click OK in the error message, it stops the
publish function.
Last time I had to blow away the cpd file as if this was a
corrupt project. But that gets to be painful. As I use templates to
put change dates in the footers of topics and templates get lost
when you blow away the cpd.
Any other thoughts? -
When i try to install Oracle XE 64bit 11g on a windows 7, the installation ends correctly, but no database is created (no datafiles) and in the log file I find :
Oracle Database 11g Clusterware Release 11.2.0.2.0 - Production Copyright 1996, 2010 Oracle. All rights reserved.
2015-03-24 15:24:14.733: [ default][3316]ut_read_reg:2:ocr registry key SOFTWARE\Oracle\olr cannot be opened. error 2
[ CLSE][3316]clse_get_crs_home: Error retrieving OLR configuration [0] [Error opening olr registry key. Le fichier spécifié est introuvable.
What's the problem?Oracle XE 64bit 11g on a windows 7
Which edition ? -
Cannot Find Errors in Log File
I can't seem to find where the Errors are stored in the Log File, I am trying to write a DataPlugin in VBS, and I'm getting runtime errors at the end of my script. It says to refer to the log file, but there isn't anything in the log file about my error. Where is the error log that this is referring to? Someone help.....
Hi Garett,
You can view the log file directly in DIAdem-SCRIPT, it's the bottom-most window with the gray background. I always have to scroll up a few lines to see the error, and usually there are two or three error events stored in the log file each time the DataPlugin fails to load. The last event, located at the bottom, almost always contains no useful information for DataPlugin debugging. You have to find the first event by scrolling up to find a reference to a line number in the DataPlugin which caused the error.
Also note that the DataPlugin will throw an error if it runs through just fine but does not load any data. In other words, if you are building up your DataPlugin step by step (as you should), and are just at the early stages where you parse a few items in the file and look at their values, you can easily forget to create at least 1 group or channel. If the DataPlugin does not create at least 1 group or channel when it runs through, it will throw an error that the data loading failed, when really there is no error in the DataPlugin beyond that it loaded nothing.
I like to output metadata values I'm parsing from the binary or header file as group properties when I'm building up the DataPlugin step by step, like this:
Set ThisGroup = Root.ChannelGroups.Add(ThisGroupName)
ThisGroup.Properties.Add MetaDataName, MetaDataValue
Then I can look at a long list of metadata values in the Data Portal, and I never forget to load at least 1 group or channel in order to avoid that pesky error that nothing was loaded by the DataPlugin. You can also do the same thing with channel properties, of course:
Set ThisChannel = ThisGroup.Channels.AddImplicitChannel(Name, 0, 1, 2, eI32)
ThisChannel.Properties.Add MetaDataName, MetaDataValue
Let us know if this doesn't help with your current issue,
Brad Turpin
DIAdem Product Support Engineer
National Instruments -
Locum error in log file ? HELP
Hi.
When i look in my log file i keep getting a log error ever 10-20 min ?
It keeps comming.
Feb 7 16:44:42 Mugge com.apple.launchd[118] (0x409b60.Locum[482]): Exited: Terminated
Feb 7 16:46:55 Mugge com.apple.launchd[118] (0x4099f0.Locum[494]): Exited: Terminated
Feb 7 16:48:21 Mugge com.apple.launchd[118] (0x4099a0.Locum[497]): Exited: Terminated
Feb 7 16:50:53 Mugge com.apple.launchd[118] (0x4099f0.Locum[513]): Exited: Terminated
Feb 7 16:51:23 Mugge com.apple.launchd[118] (0x408c90.Locum[520]): Exited: Terminated
Feb 7 16:51:54 Mugge com.apple.launchd[118] (0x4099f0.Locum[523]): Exited: Terminated
Feb 7 16:52:12 Mugge com.apple.launchd[118] (0x4099f0.Locum[525]): Exited: Terminated
Feb 7 16:53:47 Mugge com.apple.launchd[118] (0x409800.Locum[530]): Exited: Terminated
Feb 7 16:54:11 Mugge com.apple.launchd[118] (0x409800.Locum[532]): Exited: Terminated
Feb 7 16:54:46 Mugge com.apple.launchd[118] (0x409800.Locum[536]): Exited:
Feb 7 17:01:10 Mugge com.apple.launchd[118] (0x4098a0.Locum[569]): Exited: Terminated
Feb 7 17:01:29 Mugge com.apple.launchd[118] (0x409870.Locum[571]): Exited: Terminated
Feb 7 17:01:39 Mugge hdiejectd[580]: running
Feb 7 17:01:59 Mugge com.apple.launchd[118] (0x40ac90.Locum[591]): Exited: Terminated
Feb 7 17:19:01 Mugge com.apple.launchd[118] (0x409800.Locum[644]): Exited: Terminated
Feb 7 17:19:06 Mugge com.apple.launchd[118] (0x409800.Locum[645]): Exited: Terminated
Feb 7 17:19:10 Mugge com.apple.launchd[118] (0x409800.Locum[647]): Exited: Terminated
Feb 7 17:21:58 Mugge com.apple.launchd[118] (0x40a780.Locum[772]): Exited: Terminated
Feb 7 17:22:03 Mugge com.apple.launchd[118] (0x40a780.Locum[773]): Exited: Terminated
Feb 7 16:51:28 mugge com.apple.launchd[118] (0x409790.Locum[929]): Exited: Terminated
Feb 7 16:51:50 mugge com.apple.launchd[118] (0x409830.Locum[930]): Exited: Terminated
Feb 7 16:52:11 mugge com.apple.launchd[118] (0x409830.Locum[937]): Exited: Terminated
Anybody know what that means ?Locum is a program that helps Finder delete some files when you empty the Trash.
It's normal to see that message in the log after the trash has been emptied. If it's showing up on its own every few minutes, I'd first try restarting the computer (in case something is causing Locum to launch), then try repairing permissions and restarting again. -
How to store SP2-0310: unable to open file errors in log file
We are using oracle 10g on Linux platform.
When we send scripts to the clients, then we also send a control file that executes all the sql files e.g.
control.sql
SPOOL test.log
SELECT 'Start of Control File at:'||systimestamp from dual;
SPOOL OFF
@./dbscripts/00_insert_scripts.sql
SPOOL test.log APPEND
SELECT 'End of Control File at:'||systimestamp from dual;
SPOOL OFFThe scripts are executed from SqlPlusW only by typing @control.sql
The problem is that when SP2-0310: unable to open file error comes, it appears on the screen only. It does not go in the test.log file. Is there any way to store these errors in a file from SQLPlusW.
Thanks.try mentioning full path....
try
@<fully qualified path>/00_insert_scripts.sql
also check if the file has necessary permission
ls -l <fully qualified path>/00_insert_scripts.sql -
Ping errors in Log files.
I am getting this in the log files at an alarming rate. Has
anyone encountered this before. Would it be okay, to comment out
this section of the connectionlight file?
2008-09-16 20:32:20 1388 (e)2641277 Sending error message:
Failed to execute method (ping). -
2008-09-16 20:32:20 1388 (e)2641277 Sending error message:
E:\Program Files\Adobe\Flash Media Server
3\scriptlib\components\connectionlight.asc: line 123: TypeError: s
has no propertiesNetweaver MDM 7.1 SP04 patch 10 resolved this issue.
Maybe you are looking for
-
ITunes 7.0 does not play my videos
When I upgraded to iTunes 7.0 it screwed up my videos. All of my music videos and almost all of my tv shows do not show the video. The sound is still there, but the screen is just a fuzzy green mess. How can I fix it?
-
I'm having some difficulty in using temporal reasoning, I believe I'm nearly there but not quite. Here's what I'm trying to work out: the applicant is spending time with the person for at least 10 hours a week for at least 9 weeks of the last 19 week
-
Actual Template Allocation - Process Order Handling
Hi all Could somebody give me some input to an issue I am facing. I am working on a best practice baseline for Chemicals and have setup a Template to allocate overheads to materials. The allocation is fixed no matter the lot size of the process order
-
How do I move pictures and videos from my ipad to my iCloud?
I need more space on my ipad!
-
EBusiness Suite User "Auto-provisioning" with Object Form
eBusiness Suite User RO has two forms, 1 Object Form and 1 Process Form I want to configure access policies to auto-provision EBS RO to OIM users (particularly Staff/Full-time users). On the Resource Object configuration, I checked Auto-Save. This en