The logging is based on msg_id, msg_ts, msg fields
It takes forever to retrieve logs from this table.
Explain plan suggests it does a full table scan on mylog table which contain log entries since Jul-2012, having 500,000 entries.
There are no partitions or index available on the table.
It is not possible to add partitions now as all programs in my project will have to be modified so that the partition key is also sent by mypkg.write_log(v_msg,v_date) everwhere.
Index on msg filed does not seem to be a proper way since there is no key field in it just text.
How can i pull the logs faster, what are my alternatives.
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
Including a date column may not help since log writing can overflow a day, ie my application can start writing logs on 2-jan-13 11:30 PM and continue till 3-jan-13 1:30 AM
gram77
ASKER
We have partition on DayOfMonth (1-30) and index on timestamp. selecting with these in the where clause make retrieval much faster.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
> i assume there is a date column ?