Skip to Main Content
Forums

Analytics Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Migration of FDMEE Artifacts from QA to PROD

3979789May 31 2019 — edited May 31 2019

Hi Team,

We have created Import formats, Locations, Data Load Rules, Scripts in Qa and now we are planning to migrate it to PROD.

I am performing this activity through LCM but i can't see any Import Formats, Locations, Data Load Rules in LCM. PFB screenshot

FDMEE SS.PNG

Could you please let me know how we can do it? Is there any way we can migrate artifacts of FDMEE from QA to PROD? Thanks in advance!

Comments

That's fixed in v4.0.2

Gamblesk

Just installed 4.0.2.15 and the same thing happens.

I put a select sysdate from dual into the child report and I get a new cursor for every refresh when the parent refreshes.

Maybe this will help. This does not appear to happen when the child is set to refresh. Only when the parent is.

I'm not seeing that behavior. I'm counting open cursors by going against v$statname where name = 'opened cursors current'

Gamblesk

I am not sure what is different about what I am doing but here is a child report showing the value of opened cursors current and it count goes up with refreshes.

This also only happens when the type is set to table. It does not happen if the type is set to script.

I can gather anything else you think would be useful but I am not sure what else to add.

cursor_count_1.png

cursor_count_2.png

Parent query

select \* from v$session where username = 'DBA\_MONITOR'

Child query - Hardcoded SID to make sure it was showing right one.

select sysdate, stat.sid,

stat.value, statname.name

from v$sesstat stat,

    v$session sess,

    v$statname statname

where stat.sid = 617

and stat.sid = sess.sid

and statname.statistic# = stat.statistic#

and statname.name = 'opened cursors current'

It took a few minutes to find the exact reproducible scenario - a bit different than the one originally reported that we did FIX.

But, two things:

  1. thanks for the effort here and reporting this
  2. I've reopened the bug with a high priority and hope to have it addressed for our next update
1 - 5

Post Details

Added on May 31 2019
#business-intelligence-applications, #financial-data-management, #performance-management-applications
1 comment
180 views