Use Logrotator for managing slony files.

Logrotator is a small C program which is well written and available on most of the UNIX based OS. It allows automatic rotation, compression of logfiles and removal of old logfiles. This small file can be use to manage applications logfiles. It can also use for managing slony logfiles.

For managing logfiles using logrotator user has to make a logrotator conf file, and can be scheduled in crontab for managing logile.

Let see how you can make a logrotator configuration file for slony.

I have slony master/slave daemon running on my slave maching has following location for slony logfiles:
/opt/PostgresPlus/9.0AS/slony_test/slony1/node1 -- For master
/opt/PostgresPlus/9.0AS/slony_test/slony1/node2 -- For slave.
For managing logfile, user can make logrotator configuration file similar to given below:
Configuration filename: /etc/logrotate.d/slonylogfiles

"/opt/PostgresPlus/9.0AS/slony_test/slony1/node[12]/*.log"  {
       rotate 5
       mail vibhor.aim@gmail.com
       size 1k
       copytruncate
       delaycompress
       compress
       notifempty
       missingok
       }
Above configuration file has been made to rotate the logfiles of slony as the size of logfile exceeds 1kilo bytes.

Following are the description of parameters used in configuration file:
rotate 5: this parameter directs logrotator to remove/mail to specified address/directory. If value is 0 then, logrotate will remove the old version of logfile at the place of rotate.

mail: this parameter tells logrotator about command which it can use to mail logfiles.

size: this parameter tells logrotator to rotate the logfile when logfile grow bigger than size mentioned with this parameter.

copytruncate: this parameter tells, logrotator to truncate the original logfile after creating a copy of the logfile.

delaycompress: This parameter is for postponing the compression of previous log file to the next rotation cycle.

compress: this tells logrotator to compress the old logfile using gzip.

notifempty: This parameter makes logrotator not to rotate the logfile if it is empty.

missingok: This parameter is for making logrotator to continue for the next logfile, if logfile is missing.

After making above logrotator configuration file, user can schedule logrotator in crontab as given below:
00 00 * * * logrotate -s /opt/PostgresPlus/9.0AS/slony.status //etc/logrotate.d/slonylogfiles

Other form of configuration file is given below:
For daily Logrotator:
"/opt/PostgresPlus/9.0AS/slony_test/slony1/node[12]/*.log"  {
       daily
       rotate 5
       mail vibhor.aim@gmail.com
       size 1k
       copytruncate
       delaycompress
       compress
       notifempty
       missingok
       }
For monthly logrotator
"/opt/PostgresPlus/9.0AS/slony_test/slony1/node[12]/*.log"  {
       monthly
       rotate 5
       mail vibhor.aim@gmail.com
       size 1k
       copytruncate
       delaycompress
       compress
       notifempty
       missingok
       }
similarly user can make weekly slony configuration file.

Comments

Post a Comment

Popular posts from this blog

xDB Replication from Oracle to PPAS

EnterpriseDB Replication tool has been now modified and add new functionality in it. Previous Replication Console, which had been made, was using the DBA Management server and Publication & Subscriptions were dependent. Now, xDB Replication has been divided into two components: 1. Publication Server : (Master Server) 2. Subscription Server: (Slave Server) Some Background of Publication Server. Publication Server has following components: 1. JAVA Based Daemon. 2. MetaDatabase of Publication Server. Publication Server keeps its information (Information about the Primary Database, Tables Details etc.) in the MetaDatabase under schema _edb_replicator_pub Publication server is independent and has no dependency on Subscriptions Server. By default publication server uses the 9011 port. However, if user wants, [S]he can use different ports too. For running Publication Server on different port, use the following command: $EDBHOME/jre/bin/java -Djava.awt.headless=true -jar $...
Read more

Does UPDATE Change ROWID in Oracle?

Yesterday, there was a discussion which was going on OTN (Oracle Forum). I was also part of that discussion. Discussion was about the "Does UPDATE statement change rowid in Oracle?" As per my comment of "UPDATE does not change rowid", one of the user has pointed me that UPDATE statement sometime changes the rowid in Oracle and given me following example. SQL> ed Wrote file afiedt.buf 1 create table moving_rowid ( 2 col1 number primary key, 3 col2 number, 4 col3 number, 5 col4 varchar2(10) 6 ) 7* organization index SQL> / Table created. SQL> insert into moving_rowid values( 1, 2, 3, 'foo' ); 1 row created. SQL> insert into moving_rowid values( 2, 3, 4, 'bar' ); 1 row created. SQL> select rowid, col1, col2, col3, col4 2 from moving_rowid; ROWID COL1 COL2 COL3 COL4 ---------------- ---------- ---------- ---------- ---------- *BAEADxsCwQL+ 1 2 ...
Read more

PostgreSQL Database Link to Oracle Database on Linux

I have seen question, like "How to make Database Link from PostgreSQL to Oracle?", always floats in PostgreSQL Community Forum. So, I thought to do some research on it and write a Blog. Cybertec (One of The PostgreSQL Database Company) has released a PostgreSQL Module ODBC Link, using which user can make Database link to any other database, including Oracle, MS SQL Server, PostgreSQL etc, which have ODBC compliant Data source. Lets see how you can make ODBC Connection from PostgreSQL to any ODBC compliant data source and fetch data. Installation of this module is very simple. Following are the steps which user can follow: 1. Install the unixODBC driver on your linux machine. user can use following useful link for Downloading and Installing the unixODBC Driver: http://www.unixodbc.org/ 2. Download ODBC-Link from following location: http://www.cybertec.at/download/odbc_link/ODBC-Link-1.0.4.tar.gz 3. Untar the downloaded file as given below: tar -zxvf ODBC-Link-1.0.4....
Read more