ULOG File Name Is Not Correct When Using ULOG Rotaion
(Doc ID 2867999.1)
Last updated on MAY 18, 2023
Applies to:
Oracle Tuxedo - Version 12.2.2 and laterInformation in this document applies to any platform.
Symptoms
When setting ULOGRTNSIZE, sometimes ULOG rotation file name(backup number sequence) is not correct.
For example, backup file name of 4/11 is correct, but 4/12 is not correct, started from 4, it should be started from 1
2022/04/11 09:41 644 ULOG.041122
2022/04/11 09:39 10,033 ULOG.041122.1
2022/04/11 09:39 10,022 ULOG.041122.2
2022/04/11 09:39 10,022 ULOG.041122.3
2022/04/11 09:39 10,022 ULOG.041122.4
2022/04/12 09:39 542 ULOG.041222
2022/04/12 09:39 10,029 ULOG.041222.4
2022/04/12 09:39 10,022 ULOG.041222.5
2022/04/12 09:39 10,022 ULOG.041222.6
2022/04/12 09:39 10,022 ULOG.041222.7
2022/04/11 09:39 10,033 ULOG.041122.1
2022/04/11 09:39 10,022 ULOG.041122.2
2022/04/11 09:39 10,022 ULOG.041122.3
2022/04/11 09:39 10,022 ULOG.041122.4
2022/04/12 09:39 542 ULOG.041222
2022/04/12 09:39 10,029 ULOG.041222.4
2022/04/12 09:39 10,022 ULOG.041222.5
2022/04/12 09:39 10,022 ULOG.041222.6
2022/04/12 09:39 10,022 ULOG.041222.7
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |