top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Reduce sessions' log size

+1 vote
354 views

We have a session that process a millions of rows. The problem is that it creates a huge log with two main issues:
1.Log size makes it hard to handle and analize.
2.Log size slows down the process (we guess, since the log is >55 GB).

There is a way to reduce the size of the log? We don't need to know every time the application does a commit for instance.

posted Apr 15, 2014 by Madhavi Kumari

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

You can set the log level to Terse, which will get your log size to minimal. (setting in session configuration).

The downside of setting Terse is that you wont get lot of information when something goes wrong and you want to find something in log.

To change the log level:
•Open your session (double click on it in your workflow, unless its a reusable session)
•Go to the Config Object tab
•Select appropriate value from the Override tracing drop-down list (it allows you to control the logging level of the session as a whole; if you want, you can override the individual components' log level in the Components tab)

answer Apr 17, 2014 by Shweta Singh
Similar Questions
+2 votes

Currently, we have a lot of ETLs developed and the underlying table and column names are going to change. For example, the physical names used abbreviated names rather than full names since we wanted to deploy on Oracle, but for now, we decided we will use only SQL Server, hence there is a discussion on using full names at the DB level. This will impact the ETLs that we have already developed.

I was just wondering whether there is any efficient way to remap the ETL to the changed column names? I can provide a file with old and new table/column names as input.

Any help on this will be really appreciated.

...