How do you create, process, check and store adpatch logs?
I'm interested in knowing how Customers process adpatch logs, from creation to disposal.
For example.. starting with naming the logs (during creation, when adpatch prompts you) - what is the naming convention you use?
When adpatch fails out to a command prompt, when restarting the failed session - do you use the same log name or rename it? For example..
The first adpatch session is "u1234.log". A failure occurs, adpatch is restarted. Do you then name it something like "u1234-1.log?"
After a patching session is complete and successful, what do you do with the logs? Delete, move, nothing?
For example.. starting with naming the logs (during creation, when adpatch prompts you) - what is the naming convention you use?
When adpatch fails out to a command prompt, when restarting the failed session - do you use the same log name or rename it? For example..
The first adpatch session is "u1234.log". A failure occurs, adpatch is restarted. Do you then name it something like "u1234-1.log?"
After a patching session is complete and successful, what do you do with the logs? Delete, move, nothing?
Tagged:
0