SQL LOADER NOT GENERATING BAD,LOG FILES

Hi
I am calling sqlloader from sql script using host command.We are using parameter file to mention about bad,log,ctl files.sql loader is running successfully all the records are inserted.but the problem is ,it is not creating log file,bad files ....Please give me suggestions.
Thanks.

Hi,
As per ur saying the recodes are inserted successfully, so the bad file wont get created. And considering the log file, the path should mentioned in the CTL file and if not mentioned then the log file will created in the same area where the CTL file with the name of ctl file with extension .log instead of .ctl

Similar Messages

SQL Loader is creating a log file of 0 (zero) bytes.

Hello!!
I am using SQL Loader to load data from a .txt file to a Oracle table.
Following is the control file:
LOAD DATA
CHARACTERSET UTF8
CONTINUEIF LAST != "|"
INTO TABLE product_review_dtl
FIELDS TERMINATED BY '||' TRAILING NULLCOLS
indiv_review_id INTEGER EXTERNAL,
pid INTEGER EXTERNAL,
merchant_review_id INTEGER EXTERNAL,
merchant_user_id CHAR "SUBSTR(:merchant_user_id,1,20)",
review_status_txt CHAR "SUBSTR(:review_status_txt,1,20)",
review_create_date DATE "YYYY-MM-DD",
helpful_votes_cnt INTEGER EXTERNAL,
not_helpful_votes_cnt INTEGER EXTERNAL,
review_source_txt CHAR "SUBSTR(:review_source_txt,1,30)",
overall_rating_num INTEGER EXTERNAL,
comment_txt CHAR(4000) "SUBSTR(:comment_txt,1,4000)",
nickname CHAR "SUBSTR(:nickname,1,30)",
headline_txt CHAR "SUBSTR(:headline_txt,1,100)",
confirmed_status_grp INTEGER EXTERNAL "TO_NUMBER(SUBSTR(TO_CHAR(:confirmed_status_grp),1,5))",
location_txt CHAR "SUBSTR(:location_txt,1,100)"
Some records are loaded. A log file is also created but it is empty. Can you help me find out why the log file is empty?

user525235 wrote:
Hello Folks!!
I have 2 input files with different encoding (apparent in case of special characters).
File 1 loads successfully. For File 2 loader gives a memory fault while loading. Hence the log file is of 0 bytes. I still have no clue as to why is the loader giving a memory fault. It is not an OS level memory fault as analysed by the OS team. Please help!
Thanks in advance :)Unknown OS
Unknown database version
No details about what import command was used or the options specified
No samples / details of input files or their encoding
No details about exact error message of "memory fault"
No help is possible ;-)
Srini

MDIS failed to generate the Log file!!!

Hello All,
Having a issue where MDIS is not generating the log file..
The scenario is something like this-
The files are getting archived and the records not flowing into MDM
Basis team says-
2014-06-30T14:11:33.339,47083231971072,24,"[MDS=sapdpm1 Repository=REAL_ESTATE ClientSystem=MDM_REAL_ESTATE Port=Building]: Nigerian Building updates part 2 - SLKDDY.txt is empty, the file will be skipped
But the source file was having data it was not empty(bit strange!!)
Also its not generating the LOG to analyze
Regards,
Girish

Hi Shenoy,
Let me explain the scenario--
User uploads the file through Portal and through FTP records resides in MDM...the issues is when i tried to import through IM it worked and i tried manually push file through Filezilla FTP it worked.
But when we upload file through portal, the file resides in Archive and generating the message-
2014-06-30T14:11:33.339,47083231971072,24,"[MDS=sapdpm1 Repository=REAL_ESTATE ClientSystem=MDM_REAL_ESTATE Port=Building]: Nigerian Building updates part 2 - SLKDDY.txtis empty, the file will be skipped
But the file is having data.
Regards,
Girish

SQL Server not Starting Up - Could not open error log file system error = 5(Access is denied.)

Hi guys,
I am working on issue with SQL Server 2008 R2 .. we rebooted the server and after that all SQL services is not coming up. below is the error from eventlog...
SQL Server running under NetworkService account and has full control on this files..
from Config Manager ....
The request failed or the service did not respond in a timely fashion....
From Event log..
initerrlog: Could not open error log file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'. Operating system error = 5(Access is denied.).
Any idea or workaround..?
Thanks..
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

Finally I found solution and was able to bring back online the SQL Services...
I had a very similar issue with the following error (event log):
Description:
The SQL Server (MSSQLSERVER) service terminated with service-specific error 17058 (0x42A2).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17058
Date: 19/05/2012
Time: 10:20:14
User: N/A
Computer: NSQLXX
Description:
initerrlog: Could not open error log file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
Operating system error = 5(error not found).
In this case the ERRORLOG file had been marked as read only. This was following a scheduled automated boot. -This
was culprit
MSSQL wouldn't not start until this file had been changed.
http://www.experts-exchange.com/Database/MS-SQL-Server/Q_23951723.html
Thanks everyone for your kind replies and time...
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

SQl loader not loading records

I have my control file like this
options (skip=1)
LOAD DATA
INFILE xxx.csv
into table xxx
TRUNCATE
FIELDS TERMINATED BY ',' optionally enclosed by '"'
RECORD_STATUS,
ITEM_NUMBER,
Sql loader not loading records and giving error like .......
Commit point reached - logical record count 14
Commit point reached - logical record count 26
Commit point reached - logical record count 84
Commit point reached - logical record count 92
and successfully loaded only 41 records among 420 records
Plz help me

HI Phiri,
Thx for your reply.Here is the log file.
SQL*Loader: Release 8.0.6.3.0 - Production on Wed May 12 21:26:30 2010
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Control File: saba_price_break_allcur_test.ctl
Data File: saba_price_break_allcur_test.csv
Bad File: saba_price_break_allcur_test.bad
Discard File: none specified
(Allow all discards)
Number to load: ALL
Number to skip: 1
Errors allowed: 50
Bind array: 64 rows, maximum of 65536 bytes
Continuation: none specified
Path used: Conventional
Table SABA_PRICE_BREAK_ALLCUR_TEST, loaded from every logical record.
Insert option in effect for this table: TRUNCATE
Column Name Position Len Term Encl Datatype
RECORD_STATUS FIRST * , O(") CHARACTER
ITEM_NUMBER NEXT * , O(") CHARACTER
PA1 NEXT * , O(") CHARACTER
PA2 NEXT * , O(") CHARACTER
UOM_CODE NEXT * , O(") CHARACTER
RANGE_PRICING NEXT * , O(") CHARACTER
RANGE_FROM NEXT * , O(") CHARACTER
RANGE_TO NEXT * , O(") CHARACTER
PRICING_ATTRIBUTE NEXT * , O(") CHARACTER
PRICING_METHOD NEXT * , O(") CHARACTER
PRICE_BREAK_LINE_NO NEXT * , O(") CHARACTER
TEMPLATE_NAME NEXT * , O(") CHARACTER
ITEM_DESC NEXT * , O(") CHARACTER
PRICE_USD NEXT * , O(") CHARACTER
PRICE_EUR NEXT * , O(") CHARACTER
PRICE_GBP NEXT * , O(") CHARACTER
PRICE_JPY NEXT * , O(") CHARACTER
GL_ACCOUNT NEXT * , O(") CHARACTER
LONG_DESC NEXT * , O(") CHARACTER
STATUS NEXT * , O(") CHARACTER
MESSAGE NEXT * , O(") CHARACTER
Record 12: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 13: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 27: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 28: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 29: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 30: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 31: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 32: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 33: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 34: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 35: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 36: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 37: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 38: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 39: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 40: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 41: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 42: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 43: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 44: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 45: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 46: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 47: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 48: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 49: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 50: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 51: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 52: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 53: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 54: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 55: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 56: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 57: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 58: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 59: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 60: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 61: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 62: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 63: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 64: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 65: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 66: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 67: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 68: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 69: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 70: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 73: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 74: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 87: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 91: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
Record 92: Rejected - Error on table SABA_PRICE_BREAK_ALLCUR_TEST, column LONG_DESC.
Field in data file exceeds maximum length
MAXIMUM ERROR COUNT EXCEEDED - Above statistics reflect partial run.
Table SABA_PRICE_BREAK_ALLCUR_TEST:
41 Rows successfully loaded.
51 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
Space allocated for bind array: 65016 bytes(12 rows)
Space allocated for memory besides bind array: 0 bytes
Total logical records skipped: 1
Total logical records read: 92
Total logical records rejected: 51
Total logical records discarded: 0
Run began on Wed May 12 21:26:30 2010
Run ended on Wed May 12 21:27:06 2010
Elapsed time was: 00:00:36.08
CPU time was: 00:00:00.00

SQL LDR LKM generating incorrect CTL file

Hi,
The LKM for SQL LDR is generating incorrect CTL file for a fixed length data file. Due to this the ODI is erring out.
Here are the contents of the CTL file:
SnpsOutFile "-File=//Myserver/myfile.ctl"
OPTIONS (
     SKIP=0,
     ERRORS=0,
     DIRECT=TRUE
LOAD DATA
INFILE "//Myserver/myfile.RDY"
BADFILE "//Myserver/myfile.bad"
DISCARDFILE "//Myserver/myfile.dsc"
DISCARDMAX 1
INTO TABLE ORA_SCHEMA.C$_0RAW_TABLE
     C1_CHAR9     POSITION(:),
     C2_CHAR2     POSITION(:),
     C3_CHAR6     POSITION(:),
     C4_CODE          POSITION(:),
     C5_RAWG_CODE     POSITION(:),
     C6_E_NUMBER     POSITION(:),
     C7_T_NUMBER     POSITION(:),
     C8_C_COLOR     POSITION(:),
     C9_D_COLOR     POSITION(:),
     C10_R_CODE     POSITION(:)
Why is "POSITION(:)" not getting the numbers before and after ":" ?
I reverse engineered this file and have the correct values for "Physical Length" and "Logical Length"
TIA,
Ankit

Hi Ankit,
I think the column transformation mappings are set on the Source (radio button) in the Integration Interface Mapping window.
Change the column transformation mappings to be executed on STAGE .
It should resolve this issue.
Thanks,
Sutirtha

Generating rman log file

hi
How can I generate Rman log file? Oracle xe on windows
My rman backup script is like:
run{
backup device type disk tag '%TAG' database;
SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup device type disk tag '%TAG' archivelog all not backed up delete all input;
delete noprompt obsolete device type disk;
}

In addition to what Paul mentioned, you can also consider the LOG option from the command line.

Parameter issue - report not generating any pdf files

Hi All,
I'm trying to run a report which generates pdf files. Is there any limitation on the parameter string size? For one of the parameter values - '11F EA Accept nonhonor ASnSOMnSON_20091201090150846' the report is not generating any pdf files. I assumed the reason is of the keyword 'AS' in it and created another parameter value - '11F EA Accept nonhonor AnS-SOM-SON_20091202074331997', but it is also not generating any pdf files. I get this message from Adobe Reader " There was an error opening this document. This file cannot be opened because it has no pages. " The report is working normally when i hardcode the same parameter values into the logic. Any suggestions on this?
Thanks.
Edited by: user1049091 on Dec 2, 2009 9:17 AM
Edited by: user1049091 on Dec 2, 2009 12:37 PM

Tim,
That report is working normally for all the parameter values, except this one. It is not working only if i pass the value - ''11F EA Accept nonhonor ASnSOMnSON_20091201090150846' as a parameter. It is generating the pdf files when i hardcode the same value into sql query logic in the data template, instead of passing it as a parameter. Please advise.
Thanks.

Error for Generating a log file

Hi Cezar sanos,
i am trying to generate a log file for ODI with details like who logged in and what is is doing kind of things.
For this i am executing the command like
lagentscheduler.bat "-PORT=20910" "-NAME=localagent" "-V=2" > C:\OraHome_1\logs\agent1.log.
But its getting the error like
A JDK is required to execute Web Services with OracleDI. You are currently using a JRE.
OracleDI: Starting Scheduler Agent ...
Starting Oracle Data Integrator Agent...
Version : 10.1.3.5 - 10/11/2008
DwgJv.main: Exit. Return code:-1

Just in case,
the following message :
A JDK is required to execute Web Services with OracleDI. You are currently using a JRE.
is only a warning and not an error message....

Could not open error log file ''. Operating system error = 5(failed to retrieve text for this error. Reason: 15105).

Hello
When I try to start the SQl server service i get the following error:
Event id 17058
Could not open error log file ''. Operating system error = 5(failed to retrieve text for this error. Reason: 15105).
As a test I have made sure the errorlog file ,and the entire drive it is, has everyone full control permissions, but to no avail. Does anyone have any ideas to resolve this issue?
Thank you

Hi,
Try running:
SELECT SERVERPROPERTY('ErrorLogFileName')
Then verify that the account being used to run the SQL Server service account has access to the path output above. If possible, you could try logging onto the server with the same account used to run SQL Server then navigate to the errorlog folder.
Thanks,
Andrew Bainbridge
SQL Server DBA
Please click "Propose As Answer" if a post solves your problem, or "Vote As Helpful" if a post has been useful to you

SQL*Loader Error Field in data file exceeds maximum length", version 8.1.6

Hi All,
I am trying to load a data file into a database table using SQL loader. I
received the data in an data file but I saved it as a pipe delimited
file.
When I run the SQL Loader command no records are loaded - looking at the log
file I get the following error:
Rejected - Error on table FARESDATA, column FANOTESIN.
Then I tried with substr and doesnt seem to work for values greater than 4000 chars, it only works if the field value is below 4000 chars (say doing a substr for first 3000 chars).
see the code--------
LOAD DATA
INFILE 'p.dat'
APPEND INTO TABLE PROSPECTUS
FIELDS TERMINATED BY '|' OPTIONALLY ENCLOSED BY '"'
TRAILING NULLCOLS
Fanotesin char(4000) "substr(:fanotesin,1,4000)"
We get the error ORA-01461: can bind a LONG value only for insert into a LONG column when using substr for 4000 chars.
Please help!
Thanks,
Rajesh
null

I believe the problem here is that the ORACLE database regards anything > 4000chs as a CLOB (or LONG). 4000 is the maximum length of a varchar2 field in the database, although of course you can declare larger values in PL/SQL. (Since the incoming data is > 4000 chs it is regarded as a LONG and you cannot therefore use SUBSTR on it)
I think that you must either truncate your data before loading or load into a table with the offending field as a CLOB (or LONG)
and then use PL/SQL to recreate it in a table with a varchar2(4000) which is otherwise identical. (You can select from a LONG into a varchar2(32000) for example and then truncate before writing out to the new table).

Generating a log file from oracle db

I want to generate a log file in which i want to dump some useful messages, when anyone does a dml operation on a table, and also, i want to have a switch like YES or NO (may be an environment variable,,) if i switch it to YES the log file should get generated, if NO then, no log file will be generated..
can anyone help, how can you do this task ?
thanks a lot in advance..
srini

You can use a Trigger and UTL_FILE to write to a file (on the server).
Example:
create or replace trigger test_file
after insert or delete or update on test_case
for each row
declare
v_logfile utl_file.file_type;
begin
v_logfile := utl_file.fopen('\myfiles','test_file.log','a');
if inserting then
     utl_file.put_line(v_logfile,'Inserting to table');
elsif deleting then
     utl_file.put_line(v_logfile,'Deleting to table');
else
     utl_file.put_line(v_logfile,'Updating to table');
end if;
utl_file.fclose(v_logfile);
end test_file;
I want to generate a log file in which i want to dump some useful messages, when anyone does a dml operation on a table, and also, i want to have a switch like YES or NO (may be an environment variable,,) if i switch it to YES the log file should get generated, if NO then, no log file will be generated..
can anyone help, how can you do this task ?
thanks a lot in advance..
srini

After the last update that was pushed out by Adobe, my Acrobat 9 Pro will not generate a PDF file fr

After the last update that was pushed out by Adobe, my Acrobat 9 Pro will not generate a PDF file from; [right click], Combine files into one PDF multiple files chosen in the explorer. A message pops up asking if I want to run repair. Answering in the afirmative results in another message stating files are missing. And we are back at square one.

What is the exact error? Else you could always reinstall your software.

How To Generate Debug Log Files for ebs jsp?

hi How To Generate Debug Log Files for ebs r12 jsp?
and where i get the log .please help me thanks!

Please check following MOS Document
Oracle Application Server Diagnostic Tools and Log Files in Applications Release 12 (Doc ID 454178.1)

Idoc types that generate the log files

Hi All,
Can anybody provide me the list of IDOC types that generated application log files.
As I found that material master IDOCs generate log files. Is there IDOC types other
than material master that generate log files.
Regards,
Azra.

Hi Azra,
You can tell whether an IDOC does create the application log from the function module it uses.
Go to SE37, and type in IDOC_INPUT_<message_type> for inbound or IDOC_OUTPUT_<message_type> for outbound, and search for any function module which start with 'BAL_'. If you can find it, then it creates application log files.
Regards,
Lim...

SQL LOADER NOT GENERATING BAD,LOG FILES

Similar Messages

Maybe you are looking for