This appendix provides procedures to troubleshoot a migrated BI instance from 11g to 12c.
The 12c configuration might fail with a TRANSFORMBAREEXCEPTION error, if any objects in the catalog are older than Release 220.127.116.11. You can confirm the need to update the catalog items by viewing the metrics in Oracle Enterprise Manager Fusion Middleware Control. In the Catalog folder, find a metric called Reads Needing Upgrade with the description "The number of objects read that required upgrading." If the number is large, then you can resolve this issue by updating objects in the catalog using the Administration page in Presentation Services.
This task requires that you manually edit the configuration files to instruct Oracle BI Server and Oracle BI Presentation Server to regenerate the GUIDs on restart. Once completed, you edit these files again to remove the modification.
FMW_UPDATE_ROLE_AND_USER_REF_GUIDSparameter in the 11g NQSConfig.INI file.
FMW_UPDATE_ROLE_AND_USER_REF_GUIDSparameter and set it to YES, as follows
FMW_UPDATE_ROLE_AND_USER_REF_GUIDS = YES;
<Catalog> <UpgradeAndExit>false</UpgradeAndExit> <UpdateAccountGUIDs>UpdateAndExit</UpdateAccountGUIDs> </Catalog>
cd ORACLE_HOME/admin/instancen/bin ./opmnctl stopall ./opmnctl startall
FMW_UPDATE_ROLE_AND_USER_REF_GUIDSparameter in the NQSConfig.INI file back to NO.
Important:You must perform this step to ensure that your system is secure.
cd ORACLE_HOME/admin/instancen/bin ./opmnctl stopall ./opmnctl startall
When migrating from 11g, you must manually update your Oracle BI Presentation Services Catalog.
UpgradeAndExitoption to true in the instanceconfig.xml file.
<ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1"> <ps:UpgradeAndExit>false</ps:UpgradeAndExit> </ps:Catalog>
Change it to the following:
<ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1"> <ps:UpgradeAndExit>true</ps:UpgradeAndExit> </ps:Catalog>
opmnctl startproc ias-component=coreapplication_obipsn
./opmnctl startproc ias-component=coreapplication_obips1
opmnctl startproc ias-component=coreapplication_obips1
UpgradeAndExitoption back to false.
\AnalyticsResdirectory on the 11g system.
\AnalyticsResdirectory to the 12c
The EVALUATE function in your analyses is not enabled by default in Logical SQL queries because it exposes the database to SQL injection attacks. If you encounter any error while generating any views after migrating to Oracle BI 12c, then you must set the value of the EVALUATE_SUPPORT_LEVEL parameter appropriately in the NQSConfig.INI file.
The default value of the EVALUATE_SUPPORT_LEVEL parameter is "0", which means that evaluate is not supported.
# 1: evaluate is supported for users with manageRepositories permission
# 2: evaluate is supported for any user.
# other: evaluate is not supported if the value is anything else.
EVALUATE_SUPPORT_LEVEL = 0;
Manually set the value of the EVALUATE_SUPPORT_LEVEL parameter same as it is in the 11g NQSConfig.INI file or as required by your organization.
The NQSConfig.INI file is located at the following location:
If you have set the value of the DISPLAY variable manually or the system has manipulated it automatically, you can encounter the java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11GraphicsEnvironment error . In case you change the value of the DISPLAY variable to a Windows-client system IP, to run the 64-bit Linux installer through a Windows client, reset it to its original value after the installation is complete. If you generate an analysis that contains graphs without resetting the value of the DISPLAY variable, you can get this error.
While generating reports, if you encounter an error stating oracle.xdo.XDOException: File does not exist or is not readable:..., you might not have copied the supporting XML files to the 12c system. To solve this issue, manually validate that the path for each data source points to the appropriate directory on the 12c system.
You see the [nQSError: 43119] Query Failed: [nQSError: 46168] Operation RawFile::checkSoftLimit failed, it'll exceed the current limitation. 1073758528 error if the query requires more temporary space to complete than the BI Administrator has allocated.
[General] WORK_DIRECTORY_SIZE_GLOBAL_LIMIT = 100 GB; # No temporary file will be allowed to exceed this percentage of the global work # directory limit. MAX_WORK_FILE_SIZE_PERCENT = 5;
The maximum size allowed for any single temporary file is determined by multiplying the total size limit of the temporary directory set in the
WORK_DIRECTORY_SIZE_GLOBAL_LIMIT parameter by the percentage specified in
MAX_WORK_FILE_SIZE_PERCENT. By default the temporary file size limit is 100 GB * 5% = 5 GB. This per-file limit applies to each temporary file individually, while the total
WORK_DIRECTORY_SIZE_GLOBAL_LIMIT applies collectively to all the temporary files created by the BI Server.
You must increase the
MAX_WORK_FILE_SIZE_PERCENT parameter cautiously. Setting a large percentage can allow a single request to consume a large portion of the total temporary space, possibly causing the system and other BI requests to run out of temporary space and fail. Increasing the
WORK_DIRECTORY_SIZE_GLOBAL_LIMIT is safer as long as there is sufficient disk space. However, you must observe caution while increasing the value of the
WORK_DIRECTORY_SIZE_GLOBAL_LIMIT parameter. Setting a large value can cause the system to run out of disk space or allow BI requests to consume too many system resources.
The Act As functionality allows you to act for another user in Oracle BI EE. This functionality is useful, for example, when you need to work on another user's dashboard or content, or when IT support staff wants to troubleshoot another user's account. If you have migrated from Oracle BI 11g to 12c and cannot configure the Act As functionality on the 12c instance, you must first copy a file from the 11g instance.
After migrating to Oracle BI 12c, you might notice that links that you had added to the global header in the 11g instance are no longer available. The links are missing because the customlinks.xml file isn't migrated from the 11g to the 12c instance. You must manually copy the file to the 12c instance and enable the Custom Links functionality in the instanceconfig.xml file.
See Providing Custom Links in Presentation Services in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
<CustomLinks> <Enabled>true</Enabled> </CustomLinks>
After migrating from 11g to 12c, you must manually migrate the WebLogic users in to your 12c domain. You can do this by exporting the security data from a security realm and importing it in to another security realm. Security data includes authentication, authorization, credential map, and role data.
Understand when you would want to migrate security data. See Overview of Security Data Migration.
Understand the concepts associated with importing and exporting security data. See Migration Concepts.
Understand which formats and constraints are supported by the WebLogic Security providers. See Formats and Constraints Supported by WebLogic Security Providers.
Note:You can only export and import security data between security realms in the same WebLogic Server release.
Note:The directory and file into which you export the security data should be carefully protected with operating system security as they contain secure information about your deployment.
You might see a View Display Error message that states that an invalid column was encountered when loading the Orders Outstanding Report in 12c. This error is displayed because the ID of the column that causes the error exists in the XML definition of the report, but not in the subject area table. You must manually edit the XML definition and remove the invalid column.
If you see the following error message while generating Oracle R-based Advanced Analytic reports after you have upgraded to Oracle BI 12c, see the procedure in this topic to fix the issue. View Display Error: Odbc driver returned an error (SQLExecDirectW). Error codes: OPR4ONWY, U9IM8TAC, U9IM8TAC, U9IM8TAC, OI2DL65P.