| Archive log file's sequence number reduced. [message #549072] |
Wed, 28 March 2012 01:10  |
muktha_22
Messages: 527
Registered: December 2009
|
Senior Member |
|
|
Hi All,
We are facing a different issue in our database, need your help ASAP.
From yesterday night, the archivelog generated with 5 digit. But it supposed to be 6 digit.
Hence we are not able to apply the logs in DR Location.
Thanks in advance.
Regards
Muktha
|
|
|
|
|
|
| Re: Archive log file's sequence number reduced. [message #549091 is a reply to message #549076] |
Wed, 28 March 2012 02:39  |
John Watson
Messages: 8927
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
Michel, I don't think so: in the screen shot (which I know you probably haven't been able to view) Oracle is looking for a filename with the 6 digits. The screen shot shows several filenames that look like archive logfiles, with dates and sizes. There is a group of consecutively named files numbered up to 226509 then another group numbered from 26510. Furthermore, file 226510 is only a few K, the others are several M.
My guess would be that a DBA or an SA made some mistake that crashed the database, and then tried to cover up.
Muktha, you had better post the alert log entries from around that time, they may help.
|
|
|
|
| Re: Archive log file's sequence number reduced. [message #549344 is a reply to message #549091] |
Thu, 29 March 2012 13:47 |
muktha_22
Messages: 527
Registered: December 2009
|
Senior Member |
|
|
Hi Michel, John,
Thanks for your replay.
What actually happened was, the database in the cluster environment was slipped from the cluster node and became a standalone mode, after that the format of the archive log got generated from %s to %S. which means %S (capital letter) has some thing. Now the problem have resolved.
Regards
Muktha
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
