Tēmas : Trace File analyzer, live demo.
Valoda: Latviešu
Ar katru jaunu versiju Oracle ģenerē vairāk un vairāk diagnostiskās informācijas un bieži ir grūti sekot, kur tiek ierakstīta atbilstoša informācija. Vēlāk arī parādās jautājums, kā šo visu uzkopt, lai visa pieejamā vieta neaizietu nevajadzīgām lietām. Parādīšu un pastāstīšu par savu pieredzi ar TFA rīku trace/log failu pavaldīšanā, konfigurēšanā, kā arī par citām tā iespējām un zemūdens akmeņiem.
9. managelogs -purge
• TFA invokes adrci to purge files.
• Slow ADRCI Execution When Purging Files
After Upgrade to 12.2 (Doc ID 2335738.1).
• Workaround doesn’t work for TFA.
• Purge logs manually before scheduling
cleanup in TFA.
10. Schema version
• Purge Does Not Work In 12.2 If ADRCI Is Used
To Access An Older ADR Home (Doc ID
2341825.1)
Nedaudz par mani...
Sākumā es gribētu nedaudz iepazīties ar auditoriju – cik no jums ir dba un cik cilvēki, kuri traucē dba dzīvot? Piemēram, power users, vai cilvēki no drošības departamenta, vai vadītāji, kuri nosaka attīstības virzienus vai biznesa prasības
Nedaudz par mani...
Sākumā es gribētu nedaudz iepazīties ar auditoriju – cik no jums ir dba un cik cilvēki, kuri traucē dba dzīvot? Piemēram, power users, vai cilvēki no drošības departamenta, vai vadītāji, kuri nosaka attīstības virzienus vai biznesa prasības
First of all I would like to stress out the reasons we have behind that tedious patching process – why do we have to do that. What will happen when we do, and most important – what will happen if we do not. Then I will outline some technical details I find interesing and worth mentioning. The changes we have in the patching process with the new versions of database software – 18c, and so on
First of all I would like to stress out the reasons we have behind that tedious patching process – why do we have to do that. What will happen when we do, and most important – what will happen if we do not. Then I will outline some technical details I find interesing and worth mentioning. The changes we have in the patching process with the new versions of database software – 18c, and so on
First of all I would like to stress out the reasons we have behind that tedious patching process – why do we have to do that. What will happen when we do, and most important – what will happen if we do not. Then I will outline some technical details I find interesing and worth mentioning. The changes we have in the patching process with the new versions of database software – 18c, and so on
First of all I would like to stress out the reasons we have behind that tedious patching process – why do we have to do that. What will happen when we do, and most important – what will happen if we do not. Then I will outline some technical details I find interesing and worth mentioning. The changes we have in the patching process with the new versions of database software – 18c, and so on
First of all I would like to stress out the reasons we have behind that tedious patching process – why do we have to do that. What will happen when we do, and most important – what will happen if we do not. Then I will outline some technical details I find interesing and worth mentioning. The changes we have in the patching process with the new versions of database software – 18c, and so on
First of all I would like to stress out the reasons we have behind that tedious patching process – why do we have to do that. What will happen when we do, and most important – what will happen if we do not. Then I will outline some technical details I find interesing and worth mentioning. The changes we have in the patching process with the new versions of database software – 18c, and so on
First of all I would like to stress out the reasons we have behind that tedious patching process – why do we have to do that. What will happen when we do, and most important – what will happen if we do not. Then I will outline some technical details I find interesing and worth mentioning. The changes we have in the patching process with the new versions of database software – 18c, and so on