从OBIEE11g迁移至OBIEE12c的报表未在Catalog中显示问题排查

Hey there, let's dig into why your migrated report isn't appearing in the OBIEE12c catalog—this is a super common issue, so let's walk through the most likely reasons one by one:

• Migration Tool Execution Failures
  If you used the official OBIEE Migration Utility or LCM (Life Cycle Management) tool, chances are the migration didn't complete successfully for that specific report. Check your migration logs (usually named migration.log or in the LCM job history) for errors like missing dependencies (e.g., related analyses, dashboard prompts, or variables), permission issues during import, or incomplete object selection. Maybe you forgot to include the parent folder of the report in your migration scope?

• Permission & Visibility Mismatches
  OBIEE12c tweaked the permission model compared to 11g. Even if the report migrated, your user might not have the right access to see it. Try logging in as a BI Administrator to check if the report exists—if it does, verify the folder and report-level permissions: maybe the original 11g user/group permissions didn't sync over, or the folder was marked as hidden in 12c. You can use the Catalog Manager tool to inspect and adjust permissions easily.

• Object Compatibility or Corruption
  Some 11g report features don't translate cleanly to 12c. For example, outdated custom SQL functions, legacy view types, or 11g-specific formatting might cause the report to get corrupted during migration. Open the 12c catalog with Catalog Manager and search for the report name—if you find it but it throws errors when opening, you'll need to repair the object (e.g., rework the SQL, update views) or recreate it from scratch in 12c.

• Incorrect Directory Path Mapping
  If you configured custom path mappings during migration, the report might have landed in a different folder than you expected. For example, your 11g report was in /Shared Folders/Sales/QuarterlyReport, but the migration tool mapped it to /Shared Folders/MigratedContent/Sales/QuarterlyReport instead. Use the Catalog Manager's search function to look for the report by name, or double-check your migration path configuration.

• Catalog Cache or Index Issues
  OBIEE12c's catalog relies on indexes and caching to display objects. Sometimes newly migrated items don't show up because the cache hasn't refreshed or the index is out of date. Try restarting the BI Presentation Services component, or use Catalog Manager to run the Update Catalog Index operation—this forces the system to re-scan and recognize new objects.

• Manual Migration Gone Wrong
  If you tried copying catalog files directly from 11g's file system (e.g., instance/bifoundation/OracleBIPresentationServicesComponent/coreapplication_obips1/catalog) to 12c, that's a big no-no. 12c uses a different catalog storage structure, so manual copies often result in unrecognizable or corrupted objects. Always use the official migration tools provided by Oracle for this task.

If none of these fix it, dive into the OBIEE diagnostic logs (check bi_server1/logs or the Presentation Services logs) for specific error messages—they'll usually point you to the exact problem.

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