on 04-24-2007 4:04 AM
Hi:
I am trying to run RS02 (DataSource creation) in NW2004s and after a few moments I get a SAP GUI windows error with the text: "DB error: SQL error -602 occurred".
I have checked the status of MaxDB and is up and running. What else could I check? Any idea?.
Thanks for your replies.!
Hi,
is there an error in the MaxDB error logfile (knldiag or knldiag.err) at that exact timepoint?
Do you have a Shortdump and if yes, maybe you can use that and any relevant information gathered from the Appl. Server's system log (TA SM21) to find out if there's more detailed error information inside the relevant Workprocess tracefile (dev_wX).
Regards,
Roland
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Roland:
Thanks for your help.
1) These are the three messages showed by SM21 at timepoint of the error:
- Database error -602 requires intervention by the db administrator
- Database error -602 at SEL access to table DD04T
- Transaction canceled 00 951 ( -602)
2) These are the entries in knldiag for the error:
2007-04-24 20:21:41 0x16BC ERR 20008 Data Bad page - page type 'UNDEF' is invalid
2007-04-24 20:21:41 0x16BC ERR 20026 IOMan Bad page on data volume 4 blockno 41596
2007-04-24 20:21:43 0x16BC ERR 20008 Data Bad page - page type 'UNDEF' is invalid
2007-04-24 20:21:43 0x16BC ERR 20026 IOMan Bad page on data volume 4 blockno 41596
2007-04-24 20:21:45 0x16BC ERR 20008 Data Bad page - page type 'UNDEF' is invalid
2007-04-24 20:21:45 0x16BC ERR 20026 IOMan Bad page on data volume 4 blockno 41596
2007-04-24 20:21:47 0x16BC ERR 20039 IOMan Bad data page - Requested pageno 285827 (perm) read pageno -1185906184
2007-04-24 20:21:47 0x16BC ERR 20020 Data Bad data page 285827 belongs to root 205406 which is of filetype 'Table'
2007-04-24 20:21:47 0x16BC ERR 53021 B*TREE Bad File: 205406 (Root)
2007-04-24 20:21:47 0x16BC ERR 51080 SYSERROR -9026 BD Bad datapage
Any idea?.
Thanks
Hi,
as it seems you're an official SAP customer, I strongly suggest you open an official ticket for your issue (BC-DB-SDB queue).
It seems you have at least one bad data page in your system, which involves a table. More information about bad pages can be found in FAQ note <a href="https://service.sap.com/sap/support/notes/839333">839333</a>.
It could result in you having to recover from the latest backups, but please create the official message first and have your system analyzed by support.
Please also make sure your hardware is checked, as these kind of corruptions are mostly caused by hardware issues (harddisk-, controller- or driverissues).
Regards,
Roland
Hi Roland:
Actually we are testing NetWeaver 2004s (TE), so it's not an official customer site.
However we have registered the installation following the instructions in the trial package.
If there is something I could do on the DB side, please let me know. e.g. Is it possible to reinstall DB only.?
Gruessen.
Hm,
well, you would need to figure out which database objects are corrupted, i.e. which tables, indexes are involved.
I would suggest you perform a Verify of the database, which can take some time, but we should have a better overview of how many corruptions are there. Please take a look at note <a href="https://service.sap.com/sap/support/notes/940420">940420</a>.
Can you tell me which exact MaxDB version you are using (incl. Build-nr.) and on which OS?
Did you make some database backups?
Regards,
Roland
OK Roland:
- Will proceed with Verify.
- DB version is: 7.6.00.36 (Build 036-123-140-088) (which is the one included in the NW2004s ABAP installation package).
- OS: Windows XP SP2 (WIN32), NTFS.
- Path: c:\sapdb\data\wrk\NSP
- About backups: Not yet. (because is a new installation with default data).
Thanks
Best Regards,
Hi,
hm, I think it's always a good idea to make a backup of the database just after a system has been installed.
During the dropping of the DB, did you also drop the volumes? If yes, I'd say you'd have to reinstall the whole system, but maybe somebody has another idea.
After the installation there's an initial data load (tables and such) that's needed and when you simply recreate the database with new volumes, that data is gone.
In short, I'd recommend to:
a) perform a hardware check of the machine
b) if point a) shows no signs of hardware corruption, start from scratch with the installation.
Regards,
Roland
Regards,
Roland
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.