Log files information

An user identification was used by several persons logged in different terminals.
I need to know what he did and in what terminal during a certain period.
Probably this information exists in a log file.
How can I know that?

Hi,
To trace what a user has done from different terminals you can use the SM19/SM20 audits. more over you can also check SUIM for more information. I doubt whether it would be available in the file system level.
Please check out help.sap.com for more information.
Regards,
sree

Similar Messages

Publisher log file

Hi all, I'm having issues with the email setup in 11g Publisher. Does anyone know where I would find log file information to get further insight into the error of 'deliver failed'? I assumed it would be in the NQSERVER log now that Publisher and BI is so integrated but it doesn't appear to be. Thanks!

Found it. BIEE_HOME\user_projects\domains\bifoundation_domain\servers\bi_server1\logs\bipublisher

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

One or more required office component failed to complete successfully for more information, consult the setup log file. while uninstallation of sharepoint 2013

One or more required office component failed to complete successfully for more information, consult the setup log file. while uninstallation of sharepoint 2013

go to start > run > type %temp% > here check for latest file and provide us details in that log file
If this helped you resolve your issue, please mark it Answered

Windows 8 installation error: "We couldn't create a new partition or locate an existing one. For more information, see the Setup log files."

I recently tried testing Server 2012 for installation and I had a major issue. Windows 8 also uses the same method for installation so this should also apply to Windows 8. I thought this might be helpful for other people who have the same
problem. My setup is a 1U server with no DVD drive, no hard drives, and only USB. I have a new hard drive that I wanted to install Server onto, so I put it in and ran the installer off a thumb drive. I kept receiving the following error when
I tried to format the hard drive and proceed with the installation:
"We couldn't create a new partition or locate an existing one. For more information, see the Setup log files."
After hours of troubleshooting, I determined my problem was I was using a thumb drive to install it, and Windows didn't like it. Some people had similar issues when similar devices were plugged in (i.e. external hard drives, SD cards, CF cards, etc).
In my case, it was the installation drive itself was a thumb drive. I ended up digging up an external DVD drive and placed the installation onto a DVD. Worked flawlessly. Now I am up and running.
I tried
the steps here to no avail.
Hope this helps anyone else with the same problems.

Hi,
Thanks for sharing. We really appreciate your time and efforts. Hope your experience will help other community members facing similar problems.
Leo Huang
TechNet Community Support

Will the informations be recorded in the alert.log file? -----No.168

will the informations about the loss of a temporary file be recorded in the alert.log file?

Yes, because whe your database starts needs to "mount" a tablespace with temporary files (case of tablespace "TEMP"). But don't worry with a loss of this tablespace because doesn't contain nothing when database starts.

User Information in the log file

Hi All,
Customer wants to know if it is possible to get information in the log files as to which users have accessed the documents.
Any help would be much appreciated
Regards,
Geeta

You may also want to look at using the Auding framework that was introduced in Content Services patch 10.1.2.3.
The Content DB development kit has various information present that describes how to leverage this functionality.
-Matt.

Putting header information on access log files

Can anybody suggest how to put a Apache Extended with Cookies LogFormat(i.e. "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"{User-Agent} i\"\"{Cookie}i\"") information in access log file headers in Oracle10g application server probably for webcache. I also want to know the location in which and where this configuration files resides.
Thanks,
Kamal

Are You using IronPort URL Filters or Cisco IronPort Web Usage Controls.
I'm using Cisco IronPort Web Usage Controlsand it shows:
IW_csec,-,"Unknown","-","Unknown","Unknown","-","-",462.00,0,-,"-","-">
Seems Your does not handle categorization and skips that part.

Job number from alert log file to information

Hello!
I have a question about job numbers in alert log file. Today one of our Oracle 10g R2 [10.2.0.4] RAC nodes crashed. After examining alert log file for one of the nodes I saw a lot of messages like:
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j002_28952.trc:
ORA-12012: error on auto execute of job *20627358*
ORA-12705: Cannot access NLS data files or invalid environment specified
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j001_11018.trc:
ORA-12012: error on auto execute of job *20627357*
ORA-12705: Cannot access NLS data files or invalid environment specified
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j000_9684.trc:
ORA-12012: error on auto execute of job *20627342*
ORA-12705: Cannot access NLS data files or invalid environment specified
After examining trc files I have found no further information about error except session ids.
My question is: how to find what job caused these messages to appear in alert log file.
How do I map number in alert log file to some "real" information (owner, statement executed, schedule)?
Marx.

Sorry for the delay
Try this to find the job :
select job, what from dba_jobs ;
How do I find NLS_LANG version?SQL> show parameter NLS_LANG
Do you mean ALTER SESSION inside a job?I meant anywhere, but your question is better.
ORA-12705 - Common Reasons and How to Resolve Them [ID 158654.1]
If OS is Windows lookout for NLS_LANG=NA in the registry
Is it possible you are doing this somewhere ?
ALTER SESSION SET NLS_DATE_FORMAT = 'RRRR-MM-DD\"T\"HH24:MI:SS';NLS database settings are superseded by NLS instance settings
SELECT * from NLS_SESSION_PARAMETERS;
These are the settings used for the current SQL session.
NLS_LANG could be set in a profile for example.
NLS_LANG=_AMERICA.WE8ISO8859P1 ( correct )
NLS_LANG=AMERICA.WE8ISO8859P1 ( Incorrect )
you need to set the "_" as separator.
Windows
set NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
Unix
export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
mseberg
Edited by: mseberg on Jul 28, 2011 3:51 PM
Edited by: mseberg on Jul 29, 2011 4:05 AM

Need information from the .log file

Hi,
This is a sample log file:
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Trace/0/Build-EIS93130B006
ODBC Database termination - started.
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Trace/0/Build-EIS93130B006
ODBC Database termination - completed.
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Trace/0/Build-EIS93130B006
ODBC Database termination - started.
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Trace/0/Build-EIS93130B006
ODBC Database termination - completed.
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Trace/0/Build-EIS93130B006
ODBC Database termination - started.
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Trace/0/Build-EIS93130B006
ODBC Database termination - completed.
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Trace/0/Build-EIS93130B006
ODBC Database termination - started.
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Trace/0/Build-EIS93130B006
ODBC Database termination - completed.
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Trace/0/Build-EIS93130B006
Terminating Analytic Services API.
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Informational/0/Build-EIS93130B006
Terminated Analytic Services API.
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Trace/1051037/Build-EIS93130B006
Terminating Analytic Services API.
[Tue May 24 10:27:53 2011] /IS//0x0/1306229361/Informational/1051037/Build-EIS93130B006
Terminated Analytic Services API.
[Tue May 24 10:27:53 2011] /IS/Coordinator/0/Informational/0/Build-EIS93130B006
Executed client request 'Logout' in 0 seconds
[Tue May 24 10:27:53 2011] /IS/Coordinator/0/Trace/0/Build-EIS93130B006
Coordinator Service is waiting...
[Tue May 24 10:27:53 2011] /IS/Listener/0/Trace/1051001/Build-EIS93130B006
Service is waiting for client request...
[Tue May 24 10:27:53 2011] /IS/Coordinator/0/Trace/0/Build-EIS93130B006
Service is busy processing 'The service is now available.'.
[Tue May 24 10:27:53 2011] /IS/Coordinator/0/Trace/0/Build-EIS93130B006
Coordinator Service is waiting...
[Tue May 24 10:27:53 2011] /IS/Listener/0/Trace/1051001/Build-EIS93130B006
Received client request Disconnect
[Tue May 24 10:27:53 2011] /IS/Coordinator/0/Trace/0/Build-EIS93130B006
Service is busy processing 'The service is busy.'.
[Tue May 24 10:27:53 2011] /IS/Coordinator/0/Trace/0/Build-EIS93130B006
Coordinator Service is waiting...
[Tue May 24 10:27:53 2011] /IS/Coordinator/0/Trace/0/Build-EIS93130B006
Service is busy processing 'The service is now available.'.
[Tue May 24 10:27:53 2011] /IS/Coordinator/0/Trace/0/Build-EIS93130B006
Coordinator Service is waiting...
[Tue May 24 10:27:53 2011] /IS/Listener/0/Trace/1051001/Build-EIS93130B006
Waiting for Essnet client connections.
What is this number 'EIS93130B006' present in this line and how to get the number for a perticular metamodel and metaoutline?
Regards
Shakti

Hi Shakti
Tagging on to what Glenn is saying (FWIW I agree with his theory), What Glenn means is the number EIS93130B006 translates to:
EIS v9.3.1.3(the EIS9313 part) Build 6 (the "B006" part)
These are debug log statements coming out of EIS "trace" is generally the most verbose & chatty level of logging. everything any developer has written to be logged will show up in the log if the log level is at TRACE. I think you might want to check the logging level of your EIS and raise it to something akin to "Warning" to eliminate these log entries.
Regards,
Robb Salzmann

Retrive User & Cookie Information Using Apache Access Log Files

Hi All
The following information are not showing under Apache access log files that is used with Oracle Appserver (10g 10.1.2) given below.
1)User Informations
2)Cookie Informations
We are using below Commands in the httpd.conf File that have specified in the documents link given below
http://download-west.oracle.com/docs/cd/B31017_01/web.1013/q20201/logs.html#accesslog
LogFormat "%h %l %u %t \"%r\" %>s %b %v \"%{Referer}i\" \"%{User-Agent}i\" \"%{cookie}n\"" combined
Please anyone can tell what are the necessary informations that we have to specified in the httpd.conf file to retrive Cookie and user Informations.
Thanks to all
Sona

Thanks for your reply
Can u please check the below link for the cookie flag information
http://download-west.oracle.com/docs/cd/B31017_01/web.1013/q20201/mod/mod_usertrack.html
For your information i have logged in already.
Our Sample O/p is given below
151.146.191.186 - - [28/Dec/2006:10:13:05 +0530] "GET /Tab_files/lowerbox.gif HT
TP/1.1" 200 150 - "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows)"
We are using the below command format
LogFormat "%h %l %u %t \"%r\" %>s %b %{cookie}n \"%{Referer}i\" \"%{User-Agent}i\"" combined
But User and Cookie informations is not displaying.
what steps should i follow.
Looking for the favourable reply
Thanks

Retrive Cookie Information in the Apache Access Log Files

Hi All,
Can anyone give me the solution or any link to follow the steps for retriving cookie information and user information in the Apache Access log files using httpd.conf file.
we are using Oracle Appserver 10.1.2 Version and we have specfied below commands in httpd.conf file.
LogFormat "%h %l %u %t \"%r\" %>s %b %v \"%{Referer}i\" \"%{User-Agent}i\" \"%{cookie}n\"" combined
But it failed to retrive cookie and user informations
Looking forward any one help.....
Thanks
Regards
Sona

Thanks for your reply
Can u please check the below link for the cookie flag information
http://download-west.oracle.com/docs/cd/B31017_01/web.1013/q20201/mod/mod_usertrack.html
For your information i have logged in already.
Our Sample O/p is given below
151.146.191.186 - - [28/Dec/2006:10:13:05 +0530] "GET /Tab_files/lowerbox.gif HT
TP/1.1" 200 150 - "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows)"
We are using the below command format
LogFormat "%h %l %u %t \"%r\" %>s %b %{cookie}n \"%{Referer}i\" \"%{User-Agent}i\"" combined
But User and Cookie informations is not displaying.
what steps should i follow.
Looking for the favourable reply
Thanks

Database Log file Shrink information

Hello Team,
Database log file shrink information: Due to space problem
One of my database having 600 gb,under 600 gb log file having 260 gb, in this database we take full backup daily no log backup. If we shrink the log file any impact is happen?
We shrink the log file internally what will happen?
One of my database having 600 gb,log file having 260 gb, in this database we take full backup daily and every 15 min take log backup.
This is scenario we shrink the log file what will happen.

Hello,
You should not try to shrink the log file regularly, because is resource intensive, it takes a lot of time and it creates fragmentation on the disk storage.
If you don’t backup the log files of the databases (option 1) you don’t have the ability to restore to a point in time between backups full and differential. If
you don’t want to backup files then it makes sense to change the recovery model to simple.
Backing up the logs regularly minimize the risk of the logs getting filled and extending their size.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How do I update the file where log in information is kept?

Log in information occasionally changes and I would like to know how to delete the old information and add the current info. The updated info doesn't support the Norton Toolbar which contained an easy to use program for this purpose which I was using. If there is a way to directly access the location that has this info, then I could make whatever changes are necessary.
Thank you.

See:
* http://kb.mozillazine.org/Deleting_autocomplete_entries
* http://kb.mozillazine.org/Password_Manager

Log console information to a log file

I am using the latest plug-in from sun (1.4) and I set the plugin.trace and plugin.logging options in the Java run time parameters of the console using the Control Panel as follows.
-Djavaplugin.trace=true -Djavaplugin.trace.option=5 -Djavaplugin.trace.filename=test.trace -Djavaplugin.logging=true -Djavaplugin.log.filename=test.log -Djavaplugin.outputfiles.overwrite=false
I do not see the message getting logged or the log file being created.
Any suggestions would help
Thanks
ah

akpattuka, having tried your run time parameters with plugin 1.4.2, i can tell you that they do not work here either. I have even tried setting -Djavaplugin.trace.option=ext as suggested by online help (not with numbers). Nothing. What does work for me is the following. While running your applet open the console window. Hit 'o' to enable logging, hit '5' to set the trace level. Hit the refresh button inside your browser. This will create a trace file and a log file.
HTH, Markus

Log files information

Similar Messages

Maybe you are looking for