Hi Doug,
To access KBAs, you need to use an SAP S-User, which is registered with a valid and active SAP support account (the same account you would use to open a technical support incident with us at http://support.sap.com/ ). This is not the same login you would use for the SCN.
For more information, see: User Data Administration - Help | SAP Support Portal
Back to my issue... Say there is no valid backup and that the assertion error was reported on the schedules table--which contains most of the application's data.
Would it be possible to recover the database and most of the data in the schedules table?
Possibly. You need to use "dbunload -e schedules" and then see if you can select any remaining data using available keys/indexes on that table. e.g. for "SalesOrderItems" in the demo database:
UNLOAD
SELECT * FROM "GROUPO"."SalesOrderItems"
ORDER BY "ID" ASC
TO 'c:\\unload\\SalesOrderItems.dat';
UNLOAD
SELECT * FROM "GROUPO"."SalesOrderItems"
ORDER BY "ID" DESC
TO 'c:\\unload\\SalesOrderItems.dat'
APPEND ON;
If "SalesOrderItems" was corrupted, both of these commands will create the assertion error again and you will need to restart the database each time.
The KBA linked goes into the details about the entire process to use and how to try and restore the database from this data.
If 'schedules' is the main table of the database though, I imagine you will have lots of foreign key relationships that are now broken and you will have to resolve these manually...
Regards,
Jeff Albion
SAP Active Global Support
