Failure on Log Backup

[Former Member]

Hello,

We do a "Log Backup" with TR db13 on our Maxdb (version 7.7.07.12). The logs are writen to pipe and goes with backint for oracle to our backup server.

All is working fine. The logs are writen to our backupserver and after the log area is empty.

But into TR db13 the result for this action is: Finished with error !!!

I have found into the logfile the following error:

2010-01-11 14:04:13

Freeing log pages from 1872659 to 2704947 for overwriting.

Requesting 'DELETE LOG FROM 1872659 TO 2704947' from db-kernel.

The database is working on the request.

Receiving a reply from the database kernel.

Got the following reply from db-kernel:

SQL-Code :-9209

Could not free logpages.

What's is wrong? The database studio result the log backup action as "OK".

Can somebody help me.

Regrads

Carlos Chatelain

[lbreddemann]

> Freeing log pages from 1872659 to 2704947 for overwriting.

> Requesting 'DELETE LOG FROM 1872659 TO 2704947' from db-kernel.

> The database is working on the request.

> Receiving a reply from the database kernel.

> Got the following reply from db-kernel:

> SQL-Code :-9209

> Could not free logpages.

>

> What's is wrong? The database studio result the log backup action as "OK".

>

Please do open a support message for this!

regards,

Lars

[Former Member]

Sehr geehrter Herr Lars Breddemann

Wir sind als Kunde "nur" Oracle lizenziert.

Wir haben aber zur Zeit eine officielle Testinstallstion maxdb (Installationsnummer 0020581553, System SD1). Ich weis nicht aus welchem Grund, aber ich kann zu dieser Installationsnummer leider keine Supportmeldungen verschicken.

Darum habe ich mich hier im Forum an Sie gewendet.

Wir möchten uns aber 100% sicher sein, dass das Backint for Oracel auch verhebt.

Mit freundlichen Grüssen

Chatelain Carlos

[lbreddemann]

Wir haben aber zur Zeit eine officielle Testinstallstion maxdb (Installationsnummer 0020581553, System SD1). Ich weis nicht aus welchem Grund, aber ich kann zu dieser Installationsnummer leider keine Supportmeldungen verschicken.

As this is a english forum, I switch back to english now.

When this is a official test installation you should be able to open a support message for it.

Meanwhile you may take a workaround and open the message for a different system.

Darum habe ich mich hier im Forum an Sie gewendet.

Wir möchten uns aber 100% sicher sein, dass das Backint for Oracel auch verhebt.

Backint for Oracle is supported and works for many customers without problems.

The issue here is not caused by the external backup but due to some problem within the database kernel.

Had this database been on a version <=7.6.06.04 or 7.6.05.15 ?

Did it ran on Log mode overwrite before?

regards,

Lars

[Former Member]

Dear Mr. Lars Breddemann

The answer to your questions:

- We have Installed directly maxDB 7.7.4.28, so she newer run on 7.6.

- Log mode overwrite was't activ on this system

Please say me if I can do something for you.

Regards

Carlos Chatelain

[lbreddemann]

> The answer to your questions:

> - We have Installed directly maxDB 7.7.4.28, so she newer run on 7.6.

> - Log mode overwrite was't activ on this system

In that case we need to have a support message for this issue!

> Please say me if I can do something for you.

Well, besides opening a support message, there's not much you can do right now.

regards,

Lars

[Former Member]

Answer form Lars Breddemann on SAPNET:

the cause for the problem is that you're using a third party tool

for the log backups but have set the parameter

EnableLogBackupToPipe=YES

As you can see in the documentation

http://maxdb.sap.com/doc/7_7/44/d97d157a012754e10000000a1553f6/content.htm

this parameter should only be set when you're NOT using a third party

tool to perform log backups to pipes.

After you changed that parameter restart the database and then the

backed up logs should be correctly released.

Regards

Carlos