Home > Error Code > Error Code 9050 Disk_not_accessible

Error Code 9050 Disk_not_accessible

So the question is: I create standby using the scripts below. I don't the commands that it is executing behind the scenes). Next, when I try to restore log backup,I get thiserror:dbmcli on STANDBY>recover_start burvlog LOGERR-24988,ERR_SQL: SQL error-9407,System error: unexpected error3,Database state: OFFLINE20040,Logrecovery is not allowed, because state of log volume is'HistoryLost' (log Then I restore data backup usingcommand line client. this content

You onlyhave to take care that you change some paths (e.g. Garima replied Jan 13, 2011 Hello everyone , Thanks for all your suggestions , but I already tried ,restarting NFS server ,but that din't worked , Also I tried rebooting my Some components may not be visible. I checked via lsof but din't got any clue . https://archive.sap.com/discussions/thread/2120366

You'll be able to > do this using the installation wizard of the dbmgui. This is probably thecause of this error that I mentioned:... [stuff deleted]echo "recover database"_o=`cat <&1recover_start burvisrecover_start burvlog LOG 001... [stuff deleted]Hi Eduard,you did't I don't the commands that it is executing behind the scenes). Toolbox.com is not affiliated with or endorsed by any company listed at this site.

However I don't know why > > that is. Then I restoredata backup usingcommand line client. So the question is: I create standby using the scripts below.Why is log volume (LOG_001) not being created? RUNDIRECTORYand DIAG_HISTORY_PATH).

That's why I suggested to explore the scripts solutionfirst.EduardOn 1/22/07, Brunzema, Martin wrote:-----Original Message-----From: Eduard MSent: Monday, January 22, 2007 3:30 PMTo: Brunzema, MartinCc: [email protected]: Re: I/O error trying to recover Otherwise a log- > recovery is not possible. > The best way to ensure a working shadow database is to create > it from a databackup of the master database. I want to activate it only in case of a hardware error on master instance. http://sap.ittoolbox.com/groups/technical-functional/sap-basis/disk-not-available-error-during-maxdb-start-3972633 This is probably the cause of this error that I mentioned: ERR -24988,ERR_SQL: SQL error -902,I/O error 3,Database state: OFFLINE 6,Internal errorcode, Errorcode 9050 Eduard M at Jan 22, 2007 at

But the physical hostname is different and both of them are pointing to same IP . Thereis also no log volume file (physically) on my masterdatabase, although I'vecreated it in Database Manager and it shows there in the GUI.------medium_put burvlog BURVIS_LOG FILE [email protected]:~/maxdb> dbmcli -d STANDBY -u I have a suspicion that this is because there is no log volume fileitself in the directory (LOG_001). However I don't know whythat is.

  1. Otherwise a log-recovery is not possible.The best way to ensure a working shadow database is to createit from a databackup of the master database.
  2. You onlyhave to take care that you change some paths (e.g.
  3. You onlyhave to take care that you change some paths (e.g.
  4. Community Data Protector Practitioners Forum CommunityCategoryBoardUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches
  5. Then you are able to recover the logbackups as you > need. > > Kind regards, Martin > Thread• I/O error trying to recover log backupEduardM17Jan • RE: I/O error

Use (1) db_warm (mandatory!) and thenload_systab -u dba,dba (must include the user!).Eduard reply | permalink Eduard M Hi Martin, Maybe let us continue with trying to solve this using command line, http://comments.gmane.org/gmane.comp.db.maxdb/9972 I want to activate it only in case of ahardware error on master instance. Content reproduced on this site is the property of the respective copyright holders. At least do not restart the database but only recover the > databackup.

Kind regards, Martin Brunzema, Martin at Jan 22, 2007 at 4:11 pm ⇧ -----Original Message-----From: Eduard MSent: Monday, January 22, 2007 3:30 PMTo: Brunzema, MartinCc: [email protected]: Re: I/O error trying to news I didn't restore data backup thru GUI. We get the following error message:af4lm139:sm2adm 93> dbmcli -d SM2 -u control,tsyst001 db_warmERR-24988,ERR_SQL: SQL error-902,I/O error3,Database state: OFFLINEInternal errorcode, Error code 9050 "disk_not_accessible"20017,RestartFilesystem failed with 'I/O error'Content of the knldiag:Thread - Thereis also no log volume file (physically) on my master database, although I'vecreated it in Database Manager and it shows there in the GUI.------medium_put burvlog BURVIS_LOG FILE [email protected]:~/maxdb> dbmcli -d STANDBY

continue with logrecover (if the backuphistory contains some)3. Then I restore data backup using command line client. At least do not restart the database but only recover thedatabackup. have a peek at these guys SolutionsBrowse by Line of BusinessAsset ManagementOverviewEnvironment, Health, and SafetyAsset NetworkAsset Operations and MaintenanceCommerceOverviewSubscription Billing and Revenue ManagementMaster Data Management for CommerceOmnichannel CommerceFinanceOverviewAccounting and Financial CloseCollaborative Finance OperationsEnterprise Risk and ComplianceFinancial Planning

That's why I suggested to explore thescripts solutionfirst.Even with DBMGui it's no problem:Start a Recovery with Initialization, recover the databackup.After this you can choose either to1. RUNDIRECTORY > and DIAG_HISTORY_PATH). I want to activate it only in case of a hardware error on master instance.

I have a suspicion that this is because there is no log > > volume file > > itself in the directory (LOG_001).

You'll be able todo this using the installation wizard of the dbmgui. I have a suspicion that this is because there is no logvolume fileitself in the directory (LOG_001). Maybe there is some conrent of a previous try in the logvolume, which prevents now a recovery. You can intialize the logvolumein admin mode with the commandutil_execute clear logBut be careful: Any data on the logvolume will be lost forever.Kind regards, Martin reply | permalink Eduard M OK,

Otherwise a log- recovery is not possible. mridulg replied Jan 12, 2011 Hi Garima, The error says: 2011-01-07 09:37:18 14334 ERR 11000 d0_vatta volume '/sapdb/KBP/sapdata1/DISKD0001' locked by process 0 Can you please kill that process and try it I don't the commands that it is executing behind the scenes). check my blog I don't the commands that it is executing behind thescenes).

Garima replied Jan 11, 2011 URL ?