Hey there, let's tackle this ORA-00600 internal error you're hitting when running LogMiner queries with the ojdbc8 driver on your Database App Development VM. The specific argument [krvrdgpm_getpdbmap:2] points to an issue related to PDB (Pluggable Database) mapping within LogMiner—this is common in multitenant (CDB/PDB) environments.

Here are actionable steps to troubleshoot and fix this:

• Verify Oracle Database Patch Level
  This error is often tied to known bugs in Oracle's multitenant LogMiner implementation. Check if your Database App Development VM has the latest Release Update (RU) applied. For example, certain 19c and 21c versions have patches addressing PDB mapping failures in LogMiner. You can query your current patch level with:

  SELECT version, patch_id FROM v$instance;
  

  If patches are missing, apply the latest compatible RU for your database version.

• Validate LogMiner Configuration for Multitenant
  Ensure you're starting LogMiner correctly in the CDB context:

  • If you're analyzing logs from a specific PDB, make sure you've set the correct container before initializing LogMiner.
  • When building the LogMiner dictionary, use the DBMS_LOGMNR_D.BUILD procedure with appropriate parameters for your CDB/PDB setup. For example:

    EXEC DBMS_LOGMNR_D.BUILD(dictionary_filename => 'logminer_dict.ora', dictionary_location => '/path/to/dir', options => DBMS_LOGMNR_D.STORE_IN_FLAT_FILE);
    

• Check ojdbc8 Driver Compatibility
  Mismatched driver and database versions can trigger unexpected internal errors. Confirm your ojdbc8 driver version matches the major version of your Oracle Database (e.g., 19c driver for 19c database). You can check the driver version via:

  System.out.println(OracleDriver.getDriverVersion());
  

  If there's a mismatch, upgrade to the ojdbc8 version corresponding to your database release.

• Test with Archived Logs Instead of Online Logs
  Sometimes, using online redo logs directly with LogMiner in a PDB can hit this bug. Try switching to archived logs for your LogMiner session:

  EXEC DBMS_LOGMNR.ADD_LOGFILE(logfilename => '/path/to/archived_log.log', options => DBMS_LOGMNR.NEW);
  

• Collect Diagnostics for Oracle Support
  If none of the above resolve the issue, ORA-00600 is an internal error that requires Oracle's official support. Gather the following information to submit a ticket:

  • Full error stack trace (including the T4CTTIoer11 lines you provided)
  • Alert log from your database VM
  • Trace files generated from the error (located in the database's trace directory)
  • Exact steps to reproduce the LogMiner session

内容的提问来源于stack exchange，提问作者naresh meena