Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unexplained archive logs

Status
Not open for further replies.

bookouri

IS-IT--Management
Feb 23, 2000
1,464
US
We had a strange thing happen on a production database over night. From 10:20pm to 10:23pm the database created 32 full archive logs for no apparent reason. There's no errors in the alert log and no other indication i can find to explain what happened. The log files started at 10:20 and a new one was created about every 15 to 20 seconds until 32 archives had been created and then everything went back to normal. We dont have any jobs running or anything else unusual going at during this time. It has only happened this one time and Ive never seen anything like it before.

Can anybody suggest anything on this one???

 
Bookouri,

Typically, high rates of archive log generation result from an import or a new software deliver.
Bookouri said:
We dont have any jobs running or anything else unusual going during this time.
What proof have you that nothing significant was running?...an import?...an Oracle Job running under the scheduler, et cetera?

[santa]Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
“Beware of those that seek to protect you from harm or risk. The cost will be your freedoms and your liberty.”
 

Some job on another server using db_link? [3eyes]


----------------------------------------------------------------------------
The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb
 
Do you have Grid Control or dbcontrol set up? If so can you review database activity for that time?
 
My experience is that such huge logs may be created by multiple operations NOT CHANGING DATA. Note, that even rolled back transaction may produce archive log, to say nothing about statements like
Code:
update table set field=field

Regards, Dima
 
the only thing going on other than ongoing manual data entry that never causes those kinds of log switches. We have some jobs that run and spool off some text files but i dont think that kind of activity would generate log files. This hasnt happened before or since that one event so I dont expect Ill ever be able to explain it.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top