cancel
Showing results for 
Search instead for 
Did you mean: 

all jobs (webi instance promotion job, publicatiion...) are time consuming to start

Former Member
0 Kudos

Hi expert,

I have a problem with a new installation of SAP BI4 SP5 patch 3 in AIX OS with 24 GO memory and 4 core cpu.

all work well,  only a jobs ( all kind of jobs promotion, scheduling webi, publication...) take many time to start

I have did many action but they did not solved my issue

  1. Duplicate APS and AJS
  2. Create a new APS and AJS
  3. Create a new SIA with default servers
  4. Increase the number of Max concurent jobs in AJS to 15

I have the issue in both DEV and QUAL servers.

Any idea please

Accepted Solutions (1)

Accepted Solutions (1)

former_member185603
Active Contributor
0 Kudos

There are some known issues with Promotion management in SP5, Patch1-3. Your issue may be related to that. SAP recommended to apply the patch4 or above or just SP5.

Former Member
0 Kudos

I will install patch 4  and will test...

This issue is very strange

Former Member
0 Kudos

I removed patch 3 and  I tested with only SAP BI 4.1 SP5 but the issue didn't resolved

Answers (2)

Answers (2)

former_member182521
Active Contributor
0 Kudos

How mig is your promotion jobs in terms of BI Contents?

Former Member
0 Kudos

its  a very samll job it contain one simple folder

denis_konovalov
Active Contributor
0 Kudos

your CMS is busy doing something else and is not able to quickly manage your jobs.

how is your platform search configured ?

Former Member
0 Kudos


Hi,

The searsh is disabled also crystal report and dashboard server are disbled

denis_konovalov
Active Contributor
0 Kudos

enable End to End trace and review resulting logs fo the clues as to why it take so long, following 2 KBA's will help you with that :

1861180 - Customer instructions and best practice for collecting a BI Platform 4.x end to end trace

  1922012 - Where can I download the SAP BI Platform Support Tool so that a report may be generated for the BI landscape

Former Member
0 Kudos

I don't see any message with can help me

denis_konovalov
Active Contributor
0 Kudos

you did the end to end trace ?
if so you can look at the timing and see where time is being spent.

Also, why are you concentrating on Promotion management when you mentioned that all jobs have same problem ?

The only common component between all the JOB types is the CMS server and APJ (splitting APJ is not recommended 'cause it brings no value, compared to APS splitting)

So you should look into what CMS is doing and what APJ is doing after the job is scheduled to run.

Former Member
0 Kudos

Also, why are you concentrating on Promotion management when you mentioned that all jobs have same problem ?

I do not focus on the promotion (this is an example of even palnification webi does not work.

The only common component between all the JOB types is the CMS server and APJ (splitting APJ is not recommended 'cause it brings no value, compared to APS splitting)

I traced CMS, APS AJS and CMC apllication logs, but I don't see any strange message about promotion job...

these are logs off CMS  AJS

Also I removed patch 3 and  I tested with only SAP BI 4.1 SP5 but the issue didn't resolved

Former Member
0 Kudos

here my logs CMS and AJS after launching promotion

jobserver_frdgobobd018.JobServer_LCMSchedulingService_CHILD0_gc.log.b00*****

0,570: [GC [PSYoungGen: 4608K->512K(5120K)] 4608K->1207K(10752K), 0,0078030 secs] [Times: user=0,00 sys=0,00, real=0,00 secs]


1,075: [GC [PSYoungGen: 5120K->496K(9728K)] 5815K->2142K(15360K), 0,0081170 secs] [Times: user=0,01 sys=0,01, real=0,01 secs]


1,725: [GC [PSYoungGen: 9712K->480K(9728K)] 11358K->4371K(15360K), 0,0161710 secs] [Times: user=0,01 sys=0,00, real=0,02 secs]


1,741: [Full GC [PSYoungGen: 480K->0K(9728K)] [ParOldGen: 3891K->3104K(13312K)] 4371K->3104K(23040K) [PSPermGen: 7557K->7552K(21504K)], 0,0473500 secs] [Times: user=0,03 sys=0,00, real=0,04 secs]


2,388: [GC [PSYoungGen: 9216K->485K(13824K)] 12320K->5317K(27136K), 0,0120870 secs] [Times: user=0,00 sys=0,00, real=0,02 secs]


3,015: [GC [PSYoungGen: 13796K->512K(18944K)] 18629K->13753K(32256K), 0,0337070 secs] [Times: user=0,03 sys=0,00, real=0,04 secs]


3,049: [Full GC [PSYoungGen: 512K->0K(18944K)] [ParOldGen: 13241K->11713K(31744K)] 13753K->11713K(50688K) [PSPermGen: 10469K->10468K(21504K)], 0,1010470 secs] [Times: user=0,05 sys=0,00, real=0,10 secs]


4,107: [GC [PSYoungGen: 18432K->3229K(28160K)] 30145K->14942K(59904K), 0,0133300 secs] [Times: user=0,02 sys=0,00, real=0,02 secs]


4,569: [GC [PSYoungGen: 23709K->6307K(27648K)] 36990K->19597K(59392K), 0,0317480 secs] [Times: user=0,03 sys=0,00, real=0,03 secs]


5,869: [GC [PSYoungGen: 26787K->7698K(36352K)] 40080K->20992K(68096K), 0,0377000 secs] [Times: user=0,03 sys=0,00, real=0,03 secs]


6,692: [GC [PSYoungGen: 35858K->8643K(37376K)] 49152K->21937K(69120K), 0,0361720 secs] [Times: user=0,02 sys=0,00, real=0,03 secs]


7,199: [GC [PSYoungGen: 36803K->6164K(46080K)] 50097K->19457K(77824K), 0,0502820 secs] [Times: user=0,03 sys=0,00, real=0,05 secs]


9,892: [GC [PSYoungGen: 41492K->10035K(46080K)] 54785K->23329K(77824K), 0,0496180 secs] [Times: user=0,02 sys=0,00, real=0,05 secs]


10,354: [GC [PSYoungGen: 45363K->8774K(56320K)] 58657K->22076K(88064K), 0,0571030 secs] [Times: user=0,04 sys=0,00, real=0,06 secs]


Heap


PSYoungGen      reserved 175104K, committed 73216K, used 43910K [0x0000000052580000, 0x0000000056d00000, 0x000000005d080000)


  eden space 44544K, 78% used [0x0000000052580000,0x00000000547d00d8,0x0000000055100000)


  from space 11776K, 74% used [0x0000000055d80000,0x0000000056611af0,0x0000000056900000)


  to   space 12800K, 0% used [0x0000000055100000,0x0000000055100000,0x0000000055d80000)


ParOldGen       reserved 349184K, committed 31744K, used 13301K [0x000000003d080000, 0x000000003ef80000, 0x0000000052580000)


  object space 31744K, 41% used [0x000000003d080000,0x000000003dd7d648,0x000000003ef80000)


PSPermGen       reserved 196608K, committed 21504K, used 14791K [0x0000000031080000, 0x0000000032580000, 0x000000003d080000)


  object space 21504K, 68% used [0x0000000031080000,0x0000000031ef1d88,0x0000000032580000)

cms_xxxxxx.CMS_trace.000047.glf

FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2


ENCODING:UTF-8


RECORD_SEPARATOR:30


COLUMN_SEPARATOR:124


ESC_CHARACTER:27


COLUMNS:Location|Guid|Time|Tzone|Trace|Log|Importance|Severity|Exception|DeviceName|ProcessID|ThreadID|ThreadName|ScopeTag|MajorTick|MinorTick|MajorDepth|MinorDepth|RootName|RootID|CallerName|CallerID|CalleeName|CalleeID|ActionID|DSRRootContextID|DSRTransaction|DSRConnection|DSRCounter|User|ArchitectComponent|DeveloperComponent|Administrator|Unit|CSNComponent|Text


SEVERITY_MAP: |None| |Success|W|Warning|E|Error|A|Assertion


HEADER_END


sisecserver_impl.cpp:366:-: TraceLog message 185605


|75f0b82b-ad22-c0df-b426-f63476534ec4|2015 06 19 14:05:26:692|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|14144|| |58|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:11|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:14144.6904:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185606


|869be1dc-fbab-c2ca-9b6d-38a107eee0d0|2015 06 19 14:05:26:692|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|14144|| |58|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:11|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:14144.6904:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185607


|70f3a931-49ac-b6f0-c7fa-a9bf7173152a|2015 06 19 14:05:26:692|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|14144|| |58|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:11|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:14144.6904:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185608


|64c7c910-0da3-24e8-c932-846a9c861b29|2015 06 19 14:05:26:693|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|14144|| |58|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:11|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:14144.6904:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185609


|7968371f-1094-2d6d-2afd-447c1a31c7a0|2015 06 19 14:05:26:696|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|14144|| |58|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:11|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:14144.6904:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185610


|34864f04-1949-47d3-9cae-8dc564de60b1|2015 06 19 14:05:26:697|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|14144|| |58|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:11|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:14144.6904:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185611


|8a60337c-75ca-734f-d0d2-126c543affeb|2015 06 19 14:05:26:697|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|14144|| |58|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:11|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:14144.6904:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185612


|85697f9f-a576-e15a-2371-6d003887bc36|2015 06 19 14:05:26:697|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|14144|| |58|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:11|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:14144.6904:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185613


|1f860a39-37da-d649-8d52-096deb813e77|2015 06 19 14:05:36:699|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|11831|| |190|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:74|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:11831.6912:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185614


|66296965-51f4-d4f9-e927-7707c88c9750|2015 06 19 14:05:36:700|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|11831|| |190|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:74|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:11831.6912:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185615


|0f329f65-f251-3f83-22cc-c66e9151e11d|2015 06 19 14:05:36:700|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|11831|| |190|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:74|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:11831.6912:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185616


|8eb1ac86-2ef2-7a84-c5ce-52590fe1fe65|2015 06 19 14:05:36:702|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|11831|| |190|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:74|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:11831.6912:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185617


|a56a42a0-c9b4-6e65-3829-1ebf3bfca55e|2015 06 19 14:05:36:702|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|11831|| |190|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:74|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:11831.6912:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


sisecserver_impl.cpp:366:-: TraceLog message 185618


|a5635920-92ba-1053-52e5-e56dd76bbcf2|2015 06 19 14:05:36:703|+0000|Error| |>>|E| |cms_frdgobobd018.CMS|8781890|11831|| |190|0|2|0|CMC.WebApp|frdgobobd018:6684708:38.1552:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|frdgobobd018:6684708:38.1552:74|cms_frdgobobd018.CMS.processSerializedBatch|localhost:8781890:11831.6912:1|CgBb_tkmQE4osLKjnTolTU860e|||||||||||assert failure: (sisecserver_impl.cpp:366). (wireProps != NULL : no message).-


denis_konovalov
Active Contributor
0 Kudos

In that case I suggest opening support Incident with SAP, so they can analyze the logs properly.

denis_konovalov
Active Contributor
0 Kudos

pieces of logs here are useless, the end to end trace allows SAP to view the entire workflow based on business transaction , removing non-related entries. Its impossible to do in SCN.

Former Member
0 Kudos

Ok thanks Denis

Former Member
0 Kudos

a last question...

I discovered that my client use a temporary licence key while expecting his permanent licence key, is this configuration affect my plateform  and specially all jobs?

Thanks

Former Member
0 Kudos


hi,

the issue was resolved, I increase the nomber of core cpu and it works.