cancel
Showing results for 
Search instead for 
Did you mean: 

24985,ERR_MENOTFOUND: medium not found error while applying transaction log

Former Member
0 Kudos

Hi,

We are in process of creating a standby database for our maxdb system.

We have backed up & restored the database (OS level) to the standby system and the standby database is up & running in admin state. Now I want to apply the transaction logs to the standby system. I have copied all the logs from the OS level & transfered to the standby system. Now, with the recover_start command I get the error

ERR

-24985,ERR_MENOTFOUND: medium not found

Will it not work if I copy the logs from OS level???

Please let me know, how to proceed further

Thanks,

Salman Qayyum

Accepted Solutions (1)

Accepted Solutions (1)

lbreddemann
Active Contributor
0 Kudos

> ERR

> -24985,ERR_MENOTFOUND: medium not found

>

> Will it not work if I copy the logs from OS level???

>

> Please let me know, how to proceed further

>

> Thanks,

>

> Salman Qayyum

Sure it will work.

But still you need to have a backup medium definition that points to the location of the log files.

As this is the very basic level of how to perform backup/recovery action in MaxDB, I'd propose you check the documentation and tutorials on this important topic, before trying to setup a stand-by database...

regards,

Lars

Former Member
0 Kudos

Hi,

I have moved one step ahead....however I get a new error this time

dbmcli on LCP>recover_start AUTO-LOG-DISK 335

ERR

-24988,ERR_SQL: SQL error

-8,Execution failed, parse again

3,Database state: OFFLINE

Internal errorcode, Error code 1500 "old_fileversion"

20017,RestartFilesystem failed with 'Execution failed, parse again'

20020,PAM::GetPage was called with error. It might be an unhandled error.

, Error code 1500 "old_fileversion"

Data_BaseFile: filetype=HistoryDirectory root=14889 (perm)

HistDir: registered files 445, max used are 445

I had brought the DB to admin mode & when I try to apply the log 335 , it crashes the database with the error mentioned above.

Thanks,

Salman

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

"old file version"? Are you sure, you have the same release in both systems?

Please try: "dbmcli db_enum" on both nodes and post the output.

Thanks.

Regards,

Dirk

Former Member
0 Kudos

Hi,

Yes, they are of same version...I have copied the binaries from primary to standby

Primary

dbmcli on LCP>db_enum

OK

LCP /sapdb/LCP/db 7.7.04.38 fast running

LCP /sapdb/LCP/db 7.7.04.38 quick offline

LCP /sapdb/LCP/db 7.7.04.38 slow offline

LCP /sapdb/LCP/db 7.7.04.38 test offline

---

Standby

dbmcli on LCP>db_enum

OK

LCP /sapdb/LCP/db 7.7.04.38 fast running

LCP /sapdb/LCP/db 7.7.04.38 quick offline

LCP /sapdb/LCP/db 7.7.04.38 slow offline

LCP /sapdb/LCP/db 7.7.04.38 test offline

---

dbmcli on LCP>

Thanks,

Salman

Former Member
0 Kudos

Hi,

not sure, if this is the solution, but you missed the backup type:

recover_start <medium> log <log_number>

Regards,

Dirk

Former Member
0 Kudos

Hi,

No it does not work....I get the same error...

Thanks,

Salman