BW NW 7.0 SPs 21 to Upgrade to EHP2 SPs09

[Former Member]

Hi

ABAP: Phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC is running ...since last 4 hours

Phase Status

Imports included Add-on and Support Packages into the shadow tables and the new tables

Any idea why it is taking time?

Thanks,

Sameer

[sunny_pahuja2 · Accepted solution]

Hi,

This phase takes very long time. So, you need to wait some more time to finish.

Thanks

Sunny

[Former Member · Accepted solution]

Thanks Sunny

I got this error earlier

"Checks after phase MAIN_SHDRUN/ACT_UPG were negative!

I had 4 options -

1) Repeat phase MAIN_SHDRUN/ACT_UPG to continue at the point it stopped

2) Initialize phase MAIN_SHDRUN/ACT_UPG to restart it from the beginning

3) Accept non-severe errors and repeat phase MAIN_SHDRUN/ACT_UPG

4) Exit this program

I selected 3) & went ahead. Is it ok?

Thanks,

Sameer

[nicholas_chang · Accepted solution]

Hi Sameer,

You should look at the log to find out what's the error about. I rather spend a couple of mins to investigate to mitigate the possibility of broken upgrade, than spend longer time for troubleshooting for any error occurs later, or post upgrade problem.

If i not mistaken, the error should talk about inactive object found in your system. If that's the case, it should be safe to proceed, but however, this is not the best way of doing upgrade. In fact, you should check the object on the system based on the log.

Hope it helps,

Cheers,

NIcholas Chang

[Former Member · Accepted solution]

Hi Nicholas,

But I did not find any objects in SPDD or repair objects to be modified so I went ahead.

Anywhere else to check?

Thanks,

Sameer

[nicholas_chang · Accepted solution]

Hi Sameer,

Nothing relate to SPDD & SPAU here.

Yes, it should be one of the logs, but i can't recall as i don't have the system with me. You can try to look for logs generated at the same timstamp If you can remember the time where SAPEHPI stopped and prompted you the error just now.

Thanks,

Nicholas Chang

[Former Member · Accepted solution]

Hi Nicholas,

I went ahead with this option however. Will take a note of it in the next BW system

3) Accept non-severe errors and repeat phase MAIN_SHDRUN/ACT_UPG

Thanks,

Sameer

[Former Member · Accepted solution]

Hi,

I am in the Downtime phase of the Upgrade & getting the following error -

Checks after phase MAIN_NEWBAS/TABIM_POST were negative!

I checked the error in 'TABUPOST.ELG'

The error below says for me to login to the SAP BW system & check these steps. But when I login to SAP BW system I get a message - "Login not possible due to Upgrade in progress"

This is the Error coming in 'TABUPOST.ELG'

TABLE CONVERSION ERRORS and RETURN CODE in N111221.BWT

System Response

The system created a job log for the terminated program.

What to do

Proceed as follows:

Log onto the system in which the program was executed. The system is

specified at the beginning of the transport log.

Then call transaction SM37 to display the job log.

Enter "&V#&" as job name and "DDIC" as user name.

Restrict the starting date to the starting date specified in the

transport log.

[nicholas_chang · Accepted solution]

Hi Sameer,

Have you try to login as DDIC user? keep me posted if you can't login as DDIC user.

Thanks,

Nicholas Chang

[Former Member · Accepted solution]

Hi Nicholas,

In 000 client or my regular BW client 220?

As when I login to BW system screen by default it takes me 000 client

Thanks,

Sameer

[nicholas_chang · Accepted solution]

000, as long as you can log in to check your error.

[Former Member · Accepted solution]

Ok went ahead and after dealing with a few more errors cannot find a solution for this error

ERROR: RFC of "SUBST_START_BATCHJOB" failed.

key : RFC_ERROR_SYSTEM_FAILURE

message : Time limit exceeded.

Thanks,

Sameer

[nicholas_chang · Accepted solution]

Hi Sameer,

Could you please paste your error in more detailed and explicit way? We can't simply guess what's happening in your end. Also, i wish you've performed your search in SMP and SDN before posting.

Thanks,

Nicholas Chang

[Former Member · Accepted solution]

In the downtime phase, I got this error

ERROR: RFC of "SUBST_START_BATCHJOB" failed.

key : RFC_ERROR_SYSTEM_FAILURE

message : Time limit exceeded.

I searched SDN and I have got mixed answers for this so want to ask you experts on this.

The background job BTCTRNS1 is scheduled and got finished so that does not look a problem for me

Thanks,

Sameer

[nicholas_chang · Accepted solution]

Could you please check log files in your EHPI directory -> /abap/logs for more info?

[Former Member · Accepted solution]

Hi,

I have completed the EHP2 installations.

But one strange thing is observed. There are 2 App servers for BW system

Kernel upgrade on one app server works fine. All looks good in SAP MMC

However when I try & do the same Kernel Upgrade to the 2nd App server and try & start SAP MMC, sapcpe.EXE is not working & turns RED.

Please suggest

Thanks,

Sameer

[nicholas_chang · Accepted solution]

Hi Sameer,

Please extract also the binary to /usr/sap/SID/D**/exe manually and try.

at the same time, please check and compare your DIR_CT_RUN & DIR_EXECUTABLE parameter for your instances.

Thanks,

Nicholas Chang

[Former Member · Accepted solution]

Hi Nicholas,

APP1 is working absolutely fine

Getting this message now when I try to start the services it is not working & SAP MMC also do not show up the APP2 server.

Error 14001: This application has failed to start because the application configuration is incorrect.

I checked the profile parameters after the upgrade and all looks ok. Something is not correct on APP2.

I am further searching in SDNs

Thanks,

Sameer

[nicholas_chang · Accepted solution]

Hi Sameer,

Please follow Note 1375494 - SAP system does not start after applying SAP kernel patch and install the vcredist package accordingly. It should solves your problem.

Thanks,

Nicholas Chang