Add issue descriptions for autonomous proprietary database testing workflows

[Copilot]

Oracle, SQL Server, and DB2 tests are currently disabled in Main CI due to licensing constraints—we cannot commit their JDBC drivers to the repository. This PR provides three detailed issue descriptions to implement separate CI workflows that dynamically inject drivers during execution.

Files Added

• issue-oracle-autonomous-testing.md (155 lines) - Oracle XE workflow, 2-5 min startup
• issue-sqlserver-autonomous-testing.md (201 lines) - SQL Server 2022 workflow, requires DB initialization
• issue-db2-autonomous-testing.md (260 lines) - DB2 workflow, 15+ min startup, privileged mode + 6GB RAM
• AUTONOMOUS-TESTING-ISSUES-README.md - Implementation guide and comparison table

Approach

Each workflow:

1. Adds placeholder comment in ojp-server/pom.xml after PostgreSQL dependency
2. Uses sed to inject driver dependency at CI runtime (never committed)
3. Follows existing main.yml structure with same Java matrix (11, 17, 21, 22)
4. Runs database service with appropriate health checks and startup times
5. Executes tests with -Denable{Database}Tests flag

Example driver injection:

ORACLE_DEPENDENCY='<dependency>\n  <groupId>com.oracle.database.jdbc</groupId>\n  <artifactId>ojdbc11</artifactId>\n  <version>23.8.0.25.04</version>\n</dependency>'
sed -i "/<!-- PROPRIETARY DATABASE DRIVERS PLACEHOLDER -->/a\\$ORACLE_DEPENDENCY" ojp-server/pom.xml

Issue Content

Each includes:

• Workflow configuration based on main.yml
• Database service setup with health checks
• Driver injection strategy
• Build/test steps
• Acceptance criteria
• Test class inventory (~11-12 classes per database)
• Special considerations (LOB handling, startup times, resource limits)
• Effort estimates

Implementation Order

Recommended: Oracle (simplest) → SQL Server (adds DB init) → DB2 (most complex)

Original prompt

I want you to analise the source code and create the title and text for 3 separated issues to implement autonomous testing for proprietary databases.
Currently Oracle, SQL Server and DB2 tests are disabled in the Main CI workflow because we do not have licences for these products so we cannot keep their drivers in the ojp server module.
Each issue shall implement a new workflow (one for Oracle, one SQL and one DB2) each shall add the driver of the respective database in the ojp server pom.xml and compile the code just for the test. Create a new placeholder comment in the ojp server pom.xml to know where to seed the driver.
Follow instructions for Oracle from here: https://github.com/Open-J-Proxy/ojp/blob/main/documents/environment-setup/oracle-testing-guide.md
For SQL Server from here: https://github.com/Open-J-Proxy/ojp/blob/main/documents/environment-setup/sqlserver-testing-guide.md
And for DB2 from here: https://github.com/Open-J-Proxy/ojp/blob/main/documents/environment-setup/db2-testing-guide.md

Note that for SQL server and for DB 2 there are extra steps to setup the database and that these databases take longer to start up, specially DB2 which might take 15 minutes or more to start the first time.

This task is not to do any code changes but to generate 3 rich issues descriptions, one for each database oracle, sql server and db2.

any questions?

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.