Manual Dimension Processing Required in the Target Environment after Transport

[Former Member]

Dear BPC Community,

After transporting dimension and new members to the target environment, the new members are visible in the web admin console immediately after transport, but not in EPM until the dimension is manually processed.

Question - Does the transport process automatically handle dimension processing or manual processing is required in the target?

Some additional information - we are collecting dimension and members in the same transport, and moving to target in overwrite mode. Versions: BW 7.5 SP07, BPC 10.1, EPM 30.

Thank you!

Regards,

Bijay Kuwar

[Former Member · Accepted solution]

The cause was incorrect size for buffer parameter ""rsdb/obj/buffersize”. We had to increase it from 40MB to 1.5GB to resolve this issue.

[Former Member]

Yes, and no warnings in transport log either.

[former_member186338]

And in EPM - More -> refresh connection metadata - any effect?

[Former Member]

No effect of refresh connection metadata or program UJA_REFRESH_DIM_CACHE.

[former_member186338]

And the dimension is green after transport?