7.3.0 -8 Execution failed, parse again

Question

Hello,
We have a customer still using an old 7.3.0 SAPDB installation.
We modified the schema a couple of days ago to handle some new functionality.
Now we try to use the newly created tables we get.
432.488.0 16:41:00.265 (DS) Exception in commit (E_DATABASE Error executing "INSERT INTO C_PinRecord SET oid = ?,type = ?,acl = ?,version = ?,chipType = ?,cardNumber = ?,pin1 = ?,pin2 = ?,puk = ?": [SAP AG][SQLOD32 DLL][SAP DB] General error;-8 POS(1) Execution failed, parse again.)
The error is repeatable for every try.
My conclusion is that the catalog data is left in a bad state somehow. The customer is of course in another country
and I need to send some kind of procedure to try to recover.
Does anyone have any hints of the best procedure to follow to try to fix the error?
We have tried doing a database check without finding any problems.
Best Regards,
Stefan Gustafsson

Answer 1

Thank you for your help.
The database version reports:
Kernel                7.3.0 Build 025-000-085-923
Runtime environment     7.3.0 Build 025-000-085-923
I know this is an old version, but all our customers is using the exact same version. We are now working on the
next version of our software there we use 7.7.06.09 instead.
In our system we use an ODMG mapping that creates tables and view for all classes we use. The problems started then
we added a new class in an update a couple of days ago.
During this update one new table and one new view was created in the database as:
CREATE TABLE T_PinRecord (
    oid FIXED(10) KEY NOT NULL,
    chipType VARCHAR(64),
    cardNumber VARCHAR(64),
    pin1 VARCHAR(32),
    pin2 VARCHAR(32),
    puk VARCHAR(32),
    FOREIGN KEY (oid) REFERENCES T_Object (oid) ON DELETE CASCADE
CREATE VIEW C_PinRecord AS SELECT T_Object.oid,T_Object.type,T_Object.acl,T_Object.version,T_PinRecord.chipType,T_PinRecord.cardNumber,T_PinRecord.pin1,T_PinRecord.pin2,T_PinRecord.puk FROM T_Object,T_PinRecord WHERE T_Object.oid = T_PinRecord.oid AND T_PinRecord.oid = T_Object.oid WITH CHECK OPTION
The T_Object table is one of the main tables of the OR mapping and has been there since the installation.
CREATE TABLE T_Object (
     oid  FIXED (10,0) KEY NOT NULL,
     type  FIXED (21,11),
     acl  FIXED (21,11),
     version  FIXED (10,0),
     FOREIGN KEY oid REFERENCES T_Oid (oid) ON DELETE CASCADE
CREATE TABLE T_Oid (
     oid  FIXED (10,0) KEY NOT NULL
We don't use dbprocedures and no other triggers except the ON DELETE CASCADE stuff.
I asked the customer to run two commands:
check table so.t_object catalog
check table so.t_pinrecord catalog
The first command failed with the -9404 error but the second one succeeded.
This was somewhat unexpected since the T_Object table is part of all views and I have no reports
that the system fails for normal use.
My plan was to drop the T_PinRecord table and view and recreate them, but now I'm not sure this will help.
Dropping the T_Object table is not possible since it will delete all objects in database.
I have asked the customer to take a complete data backup and send to us, hopefully we can export out
the data and reload it into a working instance.
Best Regards,
Stefan Gustafsson