cancel
Showing results for 
Search instead for 
Did you mean: 

NW04s ODS (DSO) Activation failed, ran 29 BIBCTL_ Background jobs

former_member188886
Participant
0 Kudos

Is there any documentation on the NW04s Parallel ODS Activation?

- What determines the number of background / Dialogs it will run?

Is it the number of Characteristics that it has to get SIDS for?

- If there is no "maximum number of parallel processes" set, is there a default, or will it take all it can get?

*OUR ISSUE:*************************************

We ran an ODS activation job in background that ran program RSODSACT1.

That job then scheduled 29 BIBCTL_..... background jobs all named the same, running program RSBATCH_EXECUTE_PROZESS.

The activation failed, due to 2 of the 29 BIBCTL_..... jobs canceled with no information in the job logs.

However, in the main job log, it said "Resource error. No batch process available. Process terminated". (see job log below)

Log says it started 53 Processes for determining SID for InfoObjects.

**Questions:**************************

1. What determines how many BIBCTL_..... jobs it strarts? Why 29 on this one & less on other ODS's?

2. We have config set at this in Tran RSODSO_SETTINGS

a. Table RSBATCHPARALLEL Has 3 entries:

PROCESS_TYPE... PARALLEL_PROCS....BATCH_CLASS....PARALLEL_MODE

AGGRFILL..............03..............................C..........................B

STATMAN...............25..............................C..........................B

STATMANPSA .......25..............................C..........................B

Note: there is no entry for PROCESS_TYPE = ODSACTIVAT.

Does that mean there is NO Max Process is & it will use them all???

Note: Fields PC_VARIANT & SERIAL_FLAG are blank.

b. Table: RSODSO_SETTING

Only one entry, the defult:

> DATASTORE = _DEFAULT

> ACT_PACKAGESIZE = 20,000

> ACT_MAX_WAITTIME = 1,200

> SID_PACKAGESIZE = 20,000

> SID_MAX_WAITTIME = 1,200

> ROL_MAX_WAITTIME = 1,200

Thanks

Jay Roble

-


Jog Log:

-


Job started

Step 001 started (program RSODSACT1, variant LO_AC_ZSHPCON1, user ID BEW00)

Activation is running: Data target ZSHPCON1, from 684,311 to 684,311

Overlapping check with archived data areas for InfoProvider ZSHPCON1

Check not necessary, as no data has been archived for ZSHPCON1

Data to be activated successfully checked against archiving objects

SQL: 12/01/2006 02:30:58 BEW00

BEGIN DBMS_STATS.FLUSH_DATABASE_MONITORING_INFO;

END;

SQL-END: 12/01/2006 02:30:59 00:00:01

Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIBCTL_43ZNLH4... with ID 02315001

Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIBCTL_43ZNLH4... with ID 02322101

... (29 of these)

Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIBCTL_4... with ID 02390702

Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIBCTL_4... with ID 02394901

Parallel processes (for Activation); 000003

Timeout for parallel process (for Activation): 001200Timeout for parallel process (for Activation): 001200

Package size (for Activation): 020000

Task handling (for Activation): Backgr Process

Server group (for Activation): No Server Group Configured

Parallel processes (for SID Gener.); 000003

Timeout for parallel process (for SID Gener.): 001200

Package size (for SID Gener.): 020000

Task handling (for SID Gener.): Backgr Process

Server group (for SID Gener.): No Server Group Configured

Activation started (process is running under user BEW00)

,,,

All data fields updated in mode "overwrite"

Process 000001 for determining SID for InfoObject PROFSEGNR started

Process 000002 for determining SID for InfoObject PROFSEGNR started

Process 000003 for determining SID for InfoObject SHP_NBR started

...

Process 000052 for determining SID for InfoObject COUNTER started

Process 000053 for determining SID for InfoObject 0DOC_NUM started

SID determination finished for InfoObject PROFSEGNR

SID determination finished for InfoObject SHP_NBR

...

SID determination finished for InfoObject 0COSTCENTER

Resource error. No batch process available. Process terminated

Background process BCTL_4417VW59G9LCP0JSR44O94X8O terminated due to missing confirmation

Background process BCTL_4417VW59G9LCP0JSR44O94X8O terminated due to missing confirmation

Time limit exceeded. No return of the split processes

SID determination finished

Activation ended

Data pkgs 000001; Added records 1-; Changed records 0; Deleted records 0

Log for activation request ODSR_4417VVPWECDXNRGWFFZZP0ZT4 data package 000001...000001

Errors occured when carrying out activation

Analyze errors and activate again, if necessary

Activation of M records from DataStore object ZSHPCON1 terminated

Report RSODSACT1 ended with errors

Job cancelled after system exception ERROR_MESSAGE

-


Accepted Solutions (0)

Answers (4)

Answers (4)

robert_ketterer5
Discoverer
0 Kudos

use transaction RSBATCH and click buttone "Mass Maintenance of All Settings for Parallel Processing" to go and look at all variant settings for parallel processes, target servers.

Former Member
0 Kudos

any latest updates???

Chetan

@CP..

former_member188886
Participant
0 Kudos

For ODS Activation we have seen the following:

- We use program RSODSACT1 to activate the ODS (not process chains).

- After upgrading to NW04s BI SP8

- There is NO entry in table RSBATCHPARALLEL for PROCESS_TYPE = ODSACTIVAT

- Therfore no default for max processes for ODS Activation.

- Activating then uses background processes, as many as it can get (there maybe an inplied 25 max processes) as jobs named BIBCTL_.....

- If it can't get a background process, the parent activation job fails.

Our Plan:

- In tran RSODSO_SETTINGS, "Change Standard Values" for ODS activation _DEFAULT to: Dialog & 2 max processes

- Then increase as we see the behavior.

Here are the transactions to set default parameters for PROCESS_TYPE in table RSBATCHPARALLEL:

1. T-Code RSBATCH or T-Code RSODSO_SETTINGS (for individual ODS)

- ODSACTIVAT = ODS Activation

- ODSSID = ODS-SID Determination during ODS Activation

- ODSREQUDEL = Delete/Roll Back ODS Request

PS I have another theread on RSBATCH & Parallel Process settings.

Former Member
0 Kudos

Hi Jay Roble

I have same problem with you,

now we use BI netweaver 2004 and when i activate ods,

there are many BIBTCL jobs created,

and sometimes 2 of the jobs will be cancelled, have you solved this problem with setting in T-Code RSBATCH or T-Code RSODSO_SETTINGS ?

what must i have to changes ?

how many number of processes ?

which job class we must to choose, A or C ?

really appreciate your help

Best Kind Regards

JeiMing

Former Member
0 Kudos

Hello JeiMing,

In RSODSO_SETTINGS perform necessary changes.

what must i have to changes ? - There will be 3 settings.

Param for Activation,SID Gen, Rolback Param.

U need to change - Maximum Package Size and Maximum Wait Time for Process.

how many number of processes ? - Please ensure u'r number of process for these 3 params should not go beyond available processes. e.g. if u select 3 for 1st 2 params, then ensure u have 3x3 processes available.

which job class we must to choose, A or C ? Preferebly Class A.

    • Plz assign points if helpful**

Regards,

Mainak

Former Member
0 Kudos

correct from NW2004s you need to follow

RSODSO_SETTINGS functionality ;however if you are making settings here its GLOBAL settings for all ODS ,if you want to execute changes only for certain ODS and that too during RUNTIME than you have to follow the process chain settings as aforementioned in my post above.

Check the number of processes available to you in SM50/SM51 which is more vital as other wise for both the settings you can have 3+3 =6 processes required which your system may not have during the period of execution /activation of ODS

Hope it Helps

Chetan

@CP..

former_member188886
Participant
0 Kudos

You can maintain the runtime parameter DataStore-specific withOUT process chains, see note 1118205.

<a href="http://service.sap.com/sap/support/notes/1118205">Note 1118205 - RSODSO_SETTINGS Maintain runtime parameter of DataStore obj.</a>

In transaction RSODSO_SETTINGS, you can maintain the runtime parameter Cross-DataStore or DataStore-specific.

Also see these notes:

<a href="http://service.sap.com/sap/support/notes/25528">Note 25528 - Parameter rdisp/max_wprun_time</a>

<a href="http://service.sap.com/sap/support/notes/192658">Note 192658 - Setting parameters for BW systems</a>

Former Member
0 Kudos

Hi,

Thanks for your response, I have checked the partitions and there are no partitions in F table and there are 37 partitions in E table.

Error Message:

Table /BIC/FSDSAI_C11 contains 55630 data records with an incorrect

partition column.

Those 55630 records are the newly loaded records and right now as a work around, we are doing repairs in RSRV and deleting the Cache every day.

Please help me with this issue.

Regards,

Raghu Reddy

Former Member
0 Kudos

Hello Jay,

In case u r not using a process chain and activating the data manually, then execute RSODSO_SETTINGS transaction (RSCUSTA2 in BW3.5) and give your ODS technical name. Select 1st Radio Button against Change Runtime Parameter and execute. There r 3 setings which u can change. Select each one and individually change the number of work processes depending on available DIA processes (SM50).U can also set Maximum Package Size and Maximum Wait Time for Process.

Plz assign points if helpful.

Thanks,

Mainak

Former Member
0 Kudos

Are you using Process Chain

in that case go to the process type = "Activate datastore data" -->maintain variant --->Hit " Parallel Processing " button change it to dialog process,select" parallel generators "option

Number of processes = 2

For

1)DS-Activation

2)DS-Sid generation

Above activity must be done separately for every single ODS you have.

In addition there is an OSS which is in german

Hinweis 993272 - P11:DSO:Parallelitätseinstellungen DSO-Aktivieren/Versidden

Hope it Helps

Chetan

@CP..

Hope it Helps

Chetan

@CP..