SQL*Plus (MOSC)

MOSC Banner

Keeping track of crontab changes

BrunoVroman
BrunoVroman Posts: 3,968 Gold Crown
edited Apr 6, 2010 9:21PM in SQL*Plus (MOSC) 3 comments
Tagged:

Comments

  • Manoj Sam
    Manoj Sam Posts: 1,787 Silver Trophy
    Hi Bruno,

    Did not try the script but it is a good idea and  will be useful.

    Regards,

    Sam. 

  • BrunoVroman
    BrunoVroman Posts: 3,968 Gold Crown
    Hi Bruno,

    Did not try the script but it is a good idea and  will be useful.

    Regards,

    Sam. 

    Hi Sam,

    the good point with keeping a (long) history is that we can track when a change occured. For example, it can take a long time before I realize that a script supposed to be run 1 / week is not active anymore. Then I "grep" the command in the history files and it reveals on which day the line was commented or removed (or added).

    Thanks for the comment,

    Bruno.

  • Raja Mohan Ivaturi
    Raja Mohan Ivaturi Posts: 893 Bronze Badge
    Hi Sam,

    the good point with keeping a (long) history is that we can track when a change occured. For example, it can take a long time before I realize that a script supposed to be run 1 / week is not active anymore. Then I "grep" the command in the history files and it reveals on which day the line was commented or removed (or added).

    Thanks for the comment,

    Bruno.

    Thanks Bruno. 

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center