Hi There,
I installed the preview edition on WAS 6.4 and upgraded it to SP9 successfully.
Everything was working fine, I developed the Welcome tutorial WebDynpro and deployed it successfully.
While preparing for the next tutorial (webdynpro accessing ABAP function), I was setting up the SLD and imported the CR_contect.zip and cimsap.zip. Import was successful and I could see all the software components avaliable for selection while setting up the technical system. At that time dabase was 89% full. I don't remember if the logs were full.
I then shutdown the SAP instance and rebooted the machine to start fresh. (A big mistake!!).
On starting up, the SAPDB: J2E service failed to start. This is what I see under the WebDBM -> Diagnosis file -> Database error file, .
........
2005-01-03 11:30:23 --- Starting GMT 2005-01-03 11:30:23
7.5.0 Build 007-123-057-359
....etc.
And this is what is under the Database messages file
...
2005-01-03 11:30:57 0x42C 7 Log 1 queues, flushmode is 'MinimizeSpace', devstate is 'HistoryLost'
2005-01-03 11:30:57 0x42C 8 Log Oldest not saved is ioseq 170558 @ off 4400
2005-01-03 11:30:57 0x42C 9 Log First known on LogVolume is ioseq 123291 @ off 4721
2005-01-03 11:30:57 0x42C 6 Log Restart from ioseq 170558 @ off 4400 to ioseq 172219 @ off 4720
2005-01-03 11:30:57 0x42C 11 Log Result after checking the log device: 'Ok'
2005-01-03 11:31:40 0x39C 19631 CONNECT Connect req., but UTILITY is busy
2005-01-03 11:31:40 0x39C 19628 CONNECT REQUESTOR is rejecting connect request
2005-01-03 11:31:46 0x39C 19631 CONNECT Connect req., but UTILITY is busy
2005-01-03 11:31:46 0x39C 19628 CONNECT REQUESTOR is rejecting connect request
2005-01-03 11:31:46 0x430 3 Restart recovering log from log_volume from IOSeq: '170558'
2005-01-03 11:31:46 0x430 ERR 18006 EXCEPT EXCEPTION:0xc0000005 Addr:0x6e5e59 ( 0:0:0:0 )
....etc.
Any clues what went wrong.
And how can I get the database to startup again.
I am guessing the logs are full and/or corrupt, but am not sure if that is the problem and how to fix it if it is true.
Help !!
Thanks
Devendra
Message was edited by: Devendra Shetye
3 Answers
-
Best AnswerPosted on Jan 06, 2005 at 01:24 PM
Dear Devendra,
I've discussed this issue again with the relevant developer. According to him, the situation of your MaxDB instance is not repairable.
I'm afraid we have to recommend to do either a recovery using a previously made MaxDB backup, or (if you've not made any MaxDB backups) a complete reinstallation.
For our understanding: did you you originally shutdown the database instance aswell before you rebooted the machine, or 'only' the SAP WAS 6.4 instance?
Kind regards,
Roland
Add a comment
-
Posted on Jan 04, 2005 at 03:33 PM
Dear Devendra,
I've moved your post to the MaxDB/liveCache forum, as it seems more appropriate to the error you're facing.
Could you please enter the first 10 to 20 lines from the knldiag.err file, starting from the ' -
> Symbolic Stack Back Trace <----' part of the stackback-trace?
You should be able to find the needed lines somewhat lower in the knldiag.err file than the lines you provided us with.
Regards,
Roland
Add a comment
-
Posted on Jan 05, 2005 at 01:01 PM
Hi Devendra,
thanks for the rest of the stackback trace. It seems to be an already known problem.
A solution would be to upgrade to a newer MaxDB version using SDBINST (NOT SDBUPD!), because currently your instance won't come into mode ONLINE.
I suggest to use the newest available version of MaxDB.
The issue itself should be fixed from MaxDB version 7.5.00 Build 11.
Should you need assistance performing the upgrade of the MaxDB software using SDBINST, then please don't hesitate to ask for it.
Kind regards,
Roland
[Internal info: PTS 1127884]
Add a comment
Add a comment