3 Known Issues in OPLA 3.5

The following issues are known to exist in OPLA 3.5 for Agile PLM. These were deferred from this release, but may be fixed in a future release.

Important You need to execute a Full Load after any Agile PLM configuration changes.

FULL LOAD ETL FAILED.

• Issue: Cannot use lower-case letters for the USERNAME field located in the Source Database Details window for OPLA 3.5.

• Workaround: While installing OPLA 3.5 you will have to enter information in the Source Database Details window. One field you will have to enter information is the Username field. You must enter your Username in capital letters.

WHEN YOU USE THE ACTIVITY_TYPE DIMENSION YOU GET AN ERROR.

• Issue: When you use the ACTIVITY_TYPE dimension you get an error. This is because the NQ_SESSION.ACTIVITY_TYPE is not present in the rpd.

• Workaround: If you receive this error, follow these steps:

  1. Connect to the Oracle BI Administration Tool - PLMA9_11g.rpd.

  2. Select Manage --> Variables.

  3. From the Variable Manager window, select Session --> Initialization Blocks.

  4. Double-click ACT_TYPE.

  5. Select Row-wise initialization in the Variable Target section of the Session Variable Initialization Block - ACT_TYPE window.

  6. Under Variable in the Session Variable Initialization Block Variable Target - ACT_TYPE window, type ACTIVITY_TYPE, and click OK.

  7. Save the rpd.

MDS CDC IS TAKING ALMOST SAME TIME AS MDS FULL

• Issue: In some scenarios with large datasets MDS CDC ETL takes the same amount or more time than FULL MDS ETL load time.

• Workaround: We recommend to run full load of ETL when your use case is to run both Operational Schema and MDS.