Bab 9.x patch 5 (qo56904) oracle backup error E8604

[fabio9]

Hi all.
After intalling the bab patch 5 (qo56904- 07/08/04) all our 3 oracle db fails to backup the archive log.The error is E8604 Failed to start backup (Dbname=~archive log, EC=backup agent error -- (277) 'agent can not find next archive log to back up')
In the ca support site this error is referred to a bad upper/lowercase sigle word in the init(sid).ora, BUT for the oracle 7.3.3, and we run oracle 8.1.7

I'm not sure that this is a "real" error, because until yesterday all works fine, only after this patch we have this problem.

3 different oracle db all with this error after apply this patch.

Any idea ?

Tnx in advance.

 

[ACiDelic]

What are the values of your LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT parameters?

 

[fabio9]

log_archive_dest_1 = "location=E:\dbhalhal\archive"
log_archive_format = "ARC%s.%T"

standard, I suppose.
the "s" in in correct lowercase, but BEFORE the patch 5 the backup was perfect....

I also opened an issue with ca....

 

[ACiDelic]

Those look fine to me.

Let us know what they say.

 

[fabio9]

They ask to me to put the oracle backup agent in debug mode, and send the output to the support, with the brighstor.log, dbora.log, dbora.trc and the job log.
Then the support call me back, and told me that "it's an oracle problem", because the archive logs are not aligned.
?? All our FOUR db after the patch 5 have the archive log not aligned ?? So I ran the changelog archivelog all crosscheck from rman , no errors, of course.
New backup, same problems.

Another call, the support told me that the problem is now in the usa (before was in france). They say "try to downgrade the agent".
What a answer ! The oracle cluster are a production itemes !
In any case in ONE machine I downgraded the agent, and the backup was done without problems !


What a nightmare...

To downgrade the agent I have to uninstall it, reinstall from the 9.0 bab cd and upgrade to patch 1, what needs to stop and restar oracle service.

 

[erikw]

We have the same problem after installing SP5, but with MS-SQL 2000. It seems to be an Arcserve reporting error, as the log on the SQL-server says the databases were backuped.
I also tried to Scan the tape, and it reported that there was 9GB out of 11GB data for that one database, on the tape.
(I guess this can be if the SQL server reoprts allocated space but Arcserve only backups real data).
Please inform me if You find a solution to this!!

 

[fabio9]

No, I was not able to find a solution.
I decided to jump to bab 11.1 because of the instability of patch5.
Right now I have an issue opened in c.a. because bab 11.1 does not assign the just backupped media to his pool...
There was also a problem with the sql agent too, resolved by c.a. . The problem is in some circumstances (?) you have to submit the backup job with the user who have the security rights to the machine.

Can you try this ? just make an interactive local logon with this user, resubmit (an save) the job and then logoff..

Fabio