topic Re: Runtime Version showing 'Inactive' in Application Development and Automation Discussions

Runtime Version showing 'Inactive'

Former Member — Thu, 08 Dec 2011 15:47:09 GMT

Hi All,

We have upgraded our BW systems from 7.0 to 7.3. We have run the Migration of Authorization Analysis in transaction RSECADMIN. We have applied note 1621223 -'RSEC 730: After Import Transport function Missing' But when we transport (via STMS), our Authorizations are coming across with the Runtime Version showing Inactive. Has anyone else seen this?

Thanks!

Diana

Re: Runtime Version showing 'Inactive'

Former Member — Thu, 08 Dec 2011 17:51:01 GMT

Is there anything in the transport log about after-import methods or short-dumps in ST22 (function group RSAG or similar?)

Cheers,

Julius

Re: Runtime Version showing 'Inactive'

Former Member — Thu, 08 Dec 2011 17:55:07 GMT

Hi Julius,

No, the transport logs are clean. No errors.

Thanks,

Diana

Re: Runtime Version showing 'Inactive'

Former Member — Thu, 08 Dec 2011 18:07:18 GMT

Here is my transport log:

######################################

Execution of programs after import (XPRA)

Transport request : BIDK901534

System : BIQ

tp path : tp

Version and release: 380.03.36 720

Post-import methods for change/transport request: BIDK901534

Post-import method RS_AFTER_IMPORT started for ASOB L, date and time: 20111208130203

Start of the after-import method RS_ASOB_AFTER_IMPORT for object type(s) ASOB ( )

Starting after import method RS_ASOB_AFTER_IMPORT for object type(s) ASOB in delete mode

Post-import methods of change/transport request BIDK901534 completed

Start of subsequent processing ... 20111208130203

End of subsequent processing... 20111208130208

Execute reports for change/transport request: BIDK901534

Reports for change/transport request BIDK901534 have been executed

Start of................ 20111208130208

End of.................. 20111208130208

Execution of programs after import (XPRA)

End date and time : 20111208130208

Ended with return code: ===> 0 <===

Re: Runtime Version showing 'Inactive'

Former Member — Thu, 08 Dec 2011 18:47:02 GMT

Hmm...

Any ST22 dumps in the transport target or source BW system?

If there are too many dumps (?) then focus on BWREMOTE, or ALEREMOTE (default names).

Cheers,

Julius

Re: Runtime Version showing 'Inactive'

Former Member — Thu, 08 Dec 2011 18:50:17 GMT

Hi,

Nope there are actually no dumps in either BID or BIQ.

Thanks,

Diana

Re: Runtime Version showing 'Inactive'

Former Member — Fri, 09 Dec 2011 07:46:35 GMT

Hi Diana,

After you re-import the transports, please check if RSECTXT table is correctly updated or not? If text is missing it will cause inactive objects.

Regards,

Ananth

Re: Runtime Version showing 'Inactive'

Former Member — Sat, 10 Dec 2011 00:28:14 GMT

Hi Ananth,

I checked table RSECTXT and everything looks fine there.

Thanks,

Diana

Re: Runtime Version showing 'Inactive'

Former Member — Tue, 13 Dec 2011 12:37:18 GMT

Hi,

I faced this issue during the upgrade from BI 7.0 to BI 7.3 and according to SAP, this is how you should resolve.

1. Need to run the analysis authorization migration step in all the systems Dev, QA and Prod.

T-Code RSECADMIN -> Extras -> Migrations -> Migration Release 7.0 to 7.3

2. After doing the above step, activate all analysis auths in Dev system and Transport it across.

Also on the safer side, please implement the below notes:

1636563, 1625127, 1621223, 1616753

Thanks Deb.