issue with /SAPAPO/OM_LC_UPGRADE_70 in SCM 7.0 prepare

[Former Member]

Hi,

We are running an SCM upgrade from 5.1-> 7.0

We upgraded our dev system fine. We are now in QA and running the prepare at phase PREP_CNVCHECKS/REQ_APOUPG0.

Option # 3 of section A of /SAPAPO/OM_LC_UPGRADE_70 runs job name SYNC_LC_DB_DP, program /SAPAPO/OM_SYNC_LC_DB. Most planning versions run ok, but for ZDP01, this one has been running for over 30,000 seconds and it looks like it is not doing anything in liveCache or the SCM database.

Is there some way to determine what is going on with this job? We'd like to move on with the prepare...

Thanks,

Margaret

[former_member229109 · Accepted solution]

Hello Margaret ,

1. As SAP customer you could create the SAP message and get SAP support.

2. You could check the job SYNC_LC_DB_DP, if it's running.

With more details on this job in /nsm37 => identify the applicaion server and WP number, user name to run the job.

Go to this application server and run /nsm50 , then check the activities trigged by this user.

Check the active taskes in the liveCache. Monitore the liveCache tasks activities.

Check the dev log of WP.

3. Run the check on Time series - superfluous objects exist or not.

Run /SAPAPO/TS_LCM_REORG with removed check for lock for the Pl. version to check only.

!!! Please pay attention that if you run with REPEAR check you must to check the lock for the Pl. version !!

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi Natalia,

thanks for your response.

1. We have opened message 35265

2. the job is running in sm37 start time 01-13-2011, 14:51:42

a. sm50 information shows program /SAPAPO/SAPLOM_SYNC in DB-PROC SAPTS_OBJECTS_GET_ALL

b. liveCache IO operations do not show any significant change since start of this job

c. There are liveCache SQL locks for the application server PID that is running the background job

521 10158214 us6qa1a02.na.cokecce.com row_share

521 10158214 us6qa1a02.na.cokecce.com row_share

521 10158214 us6qa1a02.na.cokecce.com tab_share

521 10158214 us6qa1a02.na.cokecce.com tab_share

521 10158214 us6qa1a02.na.cokecce.com tab_share

521 10158214 us6qa1a02.na.cokecce.com tab_share

521 10158214 us6qa1a02.na.cokecce.com tab_share

521 10158214 us6qa1a02.na.cokecce.com tab_share

521 10158214 us6qa1a02.na.cokecce.com tab_share

d There is a task in liveCache

521 10,158,214 us6qa1a02.na.cokecce.com share 00018AE98905 17,152,861 01-13-2011 14:51:42

e. The dec_w36 file is contains information just from the initial connection u2013 no errors

A Thu Jan 13 14:51:42 2011

A **GENER Trace switched off ***

M SosICreateNewAnchorArray: sos_search_anchor_semantics = 1

E Profile-Parameter: enque/deque_wait_answer = FALSE

E Profile-Parameter: enque/sync_dequeall = 0

B dbtran INFO (init_connection '<DEFAULT>' [DB2:700.08]):

B max_blocking_factor = 10, max_in_blocking_factor = 35,

B min_blocking_factor = 3, min_in_blocking_factor = 6,

B prefer_union_all = 1, prefer_join = 0,

B prefer_fix_blocking = 1, prefer_in_itab_opt = 1,

B convert AVG = 1, alias table FUPD = 0,

B escape_as_literal = 0, opt GE LE to BETWEEN = 0,

B select * =0x0b, character encoding =SBCS / <none>:-,

B use_hints = abap->1, dbif->0x3, upto->2147483647, rule_in->0,

B rule_fae->0, concat_fae->0, concat_fae_or->0

M SecAudit(RsauShmInit): WP attached to existing shared memory.

M SecAudit(RsauShmInit): addr of SCSA........... = 700000040000000

M SecAudit(RsauShmInit): addr of RSAUSHM........ = 700000040000450

M SecAudit(RsauShmInit): addr of RSAUSLOTINFO... = 700000040000488

M SecAudit(RsauShmInit): addr of RSAUSLOTS...... = 700000040000494

B create_con (con_name=LCA)

B Loading DB library '/usr/sap/QA1/SYS/exe/run/dbsdbslib.o' ...

B Library '/usr/sap/QA1/SYS/exe/run/dbsdbslib.o' loaded

B Version of '/usr/sap/QA1/SYS/exe/run/dbsdbslib.o' is "700.08", patchlevel (0.247)

B New connection 1 created

B Connect to LCA as SAPPL1 with us6pa1d02.na.cokecce.com-PL1

C

C DBSDBSLIB : version 700.08, patch 0.247 (Make PL 0.254)

C MAXDB shared library (dbsdbslib) patchlevels (last 10)

C (0.247) Use SCHEMANAME instead of OWNER for MaxDB 7.8 (note 1353266)

C (0.211) MVCC support for MaxDB (note 1332203)

C (0.204) Sapinst on windows/maxdb stop with error (note 1323436)

C (0.202) NUMC conversion corrected (note 1288313)

C (0.189) Default value for max. input variables is 2000 (note 655018)

C (0.189) Profile parameter to define max. input variables (note 655018)

C (0.188) Switch SQLMODE after CREATE INDEX SERIAL (note 1267841)

etc....

3. the user reports that the program was run with repair option. We will also submit one to do just checking, no repair.

[former_member192350]

Margaret, did SAP ever provide you with a resolution?  We've had a check job running for 19 hours now....

Thanks,

Rich

[satish_waghmare3]

Hello All,

We have exactly same issue with our SCM system. SYNC_LC_DB_DP job runs forever.  We are using SAP SCM 7.0 (With Support Pack : SAPKY70005)

Any input in this regard will be highly appreciated.

Thank you

Satish Waghmare

[Former Member]

Hi Margret,

Whenevr consistency checks runs for longer duration , please make sure  there is a quite time and lock the user  for running the consistency check from OM17  in section A .

recently we have faced similar kind of issue ,  before starting section B is started , we have run OM17 from sectiona A and then our consistency checks had fineshed in 5 minutes  due to quiet time in system .

Regards

Zia

[former_member229109]

Hello Satish,

the issue was solved via SAP message created by customer in 2011. There were too many Superfluous TS objects on the system recommended to be deleted with /SAPAPO/TS_LCM_REORG report, some SAP notes recommended to be applied & the TS checks reports recommended to run in sequence to avoid locking issues.

Please create the new thread for your issue or create the SAP message and get SAP support.

Regards, Natalia Khlopina

[satish_waghmare3]

Hello Natalia,

Thanks for the details.

Could you please let me know what was SAP Note# which was implemented?

Is it  SAP Note #1853627 (Long runtime in consistency check of DP time series)?

Please check and confirm.

Thank you

Satish Waghmare

[former_member229109]

Hello Satish,

as I wrote you that the best will be to create the SAP message & get SAP support for your issue.

The analysis has to be done on the system to get clear on the root case  of the long running transaction/report.

Regards, Natalia Khlopina