Skip to Main Content

ORDS, SODA & JSON in the Database

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORA-00600 Error on ORDS_SELF_SERVICE_SCHEMA during installation of ORDS 23.2.x

aweeks007Aug 30 2023

I'm installing a new instance of ORDS in a Oracle 19.20 database.

I started with the latest version, ords-23.2.2.208.1534, and ran

./ords install --interactive --log-folder ${ORDS_LOGS}

When the installation procedure was complete, I was left with an error on validation, noting that the package ORDS_SELF_SERVICE_SCHEMA was invalid with the following error:

Package Body ORDS_SELF_SERVICE_SCHEMA compiled

LINE/COL ERROR
--------- -------------------------------------------------------------
1686/7 PL/SQL: SQL Statement ignored
1702/41 PL/SQL: ORA-00600: internal error code, arguments: [qctbyt : bfc], [65535], [18446744073709551615], [1], [873], [1], [1], [0], [], [], [], []

As a sort of sanity check, I went back to previous versions of ORDS and tried installing each of those, dropping the ords_public_user, ords_metadata user, and ords_administrator_role and ords_runtime_role between each. What I found as that the following versions all install without error, deploy correctly and are usable:

ords-19.4.6.142.1859
ords-20.4.3.050.1904
ords-22.4.4.041.1526
ords-23.1.4.150.1808

However the following versions all give me the same ORA-00600 error in ORDS_SELF_SERVICE_SCHEMA:

ords-23.2.0.177.0931
ords-23.2.1.200.1208
ords-23.2.2.208.1534

Other than the validation script errors at the end of the installation which tell me there is an invalid object, the above quoted ORA-00600 error is the only error related to installation found in the installation log.

It's worth noting that I am running all of these installs with a privileged user since we don't have SYS access to the database. I used the same privileged user with the grants from the 23.2.2 version of ords_installer_privileges.sql for all of these attempts, so this user has the latest privileges applied.

Any suggestions for how to troubleshoot this issue?

Worst case, I figure 23.1.4 is recent enough (June 2023) to work with. I've deployed that war to my tomcat and successfully went through the examples in the documentation, just to validate that everything about it works.

Comments
Post Details
Added on Aug 30 2023
9 comments
190 views