I am working on TPC-H workload on Oracle 19c database for the first time. Created a new database with Scale factor of 300 and executed the power test as per the HammerDB documentation. The driver output file is attached. Select the refresh function TRUE and executed the workload with one virtual user. As soon as the test begins, getting ORA-02291 error continuously.
Hammerdb Log @ Sun Oct 13 05:09:34 EDT 2019
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Vuser 1:New Sales refresh
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Vuser 1:Error in cursor 2:oratcl0.2 ORA-02291: integrity constraint (TPCH.LINEITEM_PARTSUPP_FK) violated - parent key not found
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Vuser 1:Error in cursor 2:oratcl0.2 ORA-02291: integrity constraint (TPCH.LINEITEM_PARTSUPP_FK) violated - parent key not found
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Vuser 1:Error in cursor 2:oratcl0.2 ORA-02291: integrity constraint (TPCH.LINEITEM_PARTSUPP_FK) violated - parent key not found
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Vuser 1:Error in cursor 2:oratcl0.2 ORA-02291: integrity constraint (TPCH.LINEITEM_PARTSUPP_FK) violated - parent key not found
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Tried the below options, but the issue still exists
1) Dropped the database and rebuild the TPCH schema, but the issue still exist.
2) Export and Import the TPCH schema, no luck.
I belive that the above error should not receive for new Oracle database build.
Has anyone seen this and were you able to resolve it? If so, can you share your experience and what you did to resolve this issue?
The refresh function will only work once per schema creation so make sure that if you want to use the refresh you backup and restore the tables being refreshed each also.
Also make sure that you set the scale factor in the driver script to the same value as the schema build.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did a mistake in setting the scale factor in the driver script to the same value as the schema build.
The scale factor set to 1 where as the scale factor for the schema build is 300.
Currently importing the tpch schema from export dump and will extecute the power test with refresh function and will set the correct scale factor as 300 .
Update you soon.
Regards
Sanjay
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
GEOMEAN is a standard function in any spreadsheet - so if you put the query times in a spreadsheet then you should be able to highlight them all and select GEOMEAN
Steve
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Steve ,
I am working on TPC-H workload on Oracle 19c database for the first time. Created a new database with Scale factor of 300 and executed the power test as per the HammerDB documentation. The driver output file is attached. Select the refresh function TRUE and executed the workload with one virtual user. As soon as the test begins, getting ORA-02291 error continuously.
Hammerdb Log @ Sun Oct 13 05:09:34 EDT 2019
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Vuser 1:New Sales refresh
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Vuser 1:Error in cursor 2:oratcl0.2 ORA-02291: integrity constraint (TPCH.LINEITEM_PARTSUPP_FK) violated - parent key not found
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Vuser 1:Error in cursor 2:oratcl0.2 ORA-02291: integrity constraint (TPCH.LINEITEM_PARTSUPP_FK) violated - parent key not found
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Vuser 1:Error in cursor 2:oratcl0.2 ORA-02291: integrity constraint (TPCH.LINEITEM_PARTSUPP_FK) violated - parent key not found
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Vuser 1:Error in cursor 2:oratcl0.2 ORA-02291: integrity constraint (TPCH.LINEITEM_PARTSUPP_FK) violated - parent key not found
Timestamp 1 @ Sun Oct 13 05:10:33 EDT 2019
Tried the below options, but the issue still exists
1) Dropped the database and rebuild the TPCH schema, but the issue still exist.
2) Export and Import the TPCH schema, no luck.
I belive that the above error should not receive for new Oracle database build.
Has anyone seen this and were you able to resolve it? If so, can you share your experience and what you did to resolve this issue?
Regards
Sanjay
The refresh function will only work once per schema creation so make sure that if you want to use the refresh you backup and restore the tables being refreshed each also.
Also make sure that you set the scale factor in the driver script to the same value as the schema build.
Steve,
Thanks for quick reply.
I did a mistake in setting the scale factor in the driver script to the same value as the schema build.
The scale factor set to 1 where as the scale factor for the schema build is 300.
Currently importing the tpch schema from export dump and will extecute the power test with refresh function and will set the correct scale factor as 300 .
Update you soon.
Regards
Sanjay
Steve,
Thank you very much.
Issue resolved after setting the scale factor in the driver script to the same value as the schema build.
I need one more help regarding How to calculate grometric mean ?
Please provide the details...
Regards
Sanjay
GEOMEAN is a standard function in any spreadsheet - so if you put the query times in a spreadsheet then you should be able to highlight them all and select GEOMEAN
Steve