Доброго всем дня!

В цепочке загрузок в процессе формирования индекса в инфо-кубе периодически происходит ошибка DBIF_DSQL2_SQL_ERROR.

Ошибка в SM21:
10:22:22 BTC 003 400 BWREMOTE BY 2 Database error 3106 at FET
10:22:22 BTC 003 400 BWREMOTE BY 0 > ORA-03106: fatal two-task communication protocol erro
10:22:22 BTC 003 400 BWREMOTE AB 0 Run-time error "DBIF_DSQL2_SQL_ERROR" occurred
10:22:23 BTC 003 400 BWREMOTE AB 1 > Short dump "120807 102222 ubp_UBP_ 75 " generated
10:22:23 BTC 003 400 BWREMOTE D0 1 Прерывание транзакции 00 (DBIF_DSQL2_SQL_ERROR ).

Дамп:

Динамическая ошибка DBIF_DSQL2_SQL_ERROR
ОсобСит CX_SY_NATIVE_SQL_ERROR
Дата и время 07.08.2012 10:22:22



Краткий текст
An SQL error occurred when executing Native SQL.



Что произошло?
The error 3106 occurred in the current database connection "DEFAULT".


Указания по устранению ошибки
Database error text........: "ORA-03106: fatal two-task communication protocol
error"
Database error code........: 3106
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).

If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:

"DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
"SAPLRSDU_PART_ORA" or "LRSDU_PART_ORAF03"
"GET_PARTITION_INFO"

If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File
(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which
actions and input led to the error.

The exception must either be prevented, caught within proedure
"GET_PARTITION_INFO" "(FORM)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
To prevent the exception, note the following:


Пользователь, транзакция...

Client.............. 400
User................ "BWREMOTE"
Language key........ "R"
Transaction......... " "
Transactions ID..... "5020B2ABB2E0418CE1000000C0A8A41C"

Program............. "SAPLRSDU_PART_ORA"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6

Информация о месте прерывания
Termination occurred in the ABAP program "SAPLRSDU_PART_ORA" - in
"GET_PARTITION_INFO".
The main program was "RSPROCESS ".

In the source code you have the termination point in line 53
of the (Include) program "LRSDU_PART_ORAF03".
The program "SAPLRSDU_PART_ORA" was started as a background job.
Job Name....... "BI_PROCESS_INDEX"
Job Initiator.. "PI_UBP_400"
Job Number..... 10133300
The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred
in
procedure "GET_PARTITION_INFO" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.

The procedure is in program "SAPLRSDU_PART_ORA "; its source code begins in
line
35 of the (Include program "LRSDU_PART_ORAF03 ".

Фрагмент исходного текста программы

Строк ИсхднТкст

23 IF sy-subrc <> 0.
24 CLEAR e_part_key.
25 ENDIF.
26
27 ENDFORM. " GET_PARTITION_KEY
28
29
30 *---------------------------------------------------------------------*
31 * FORM GET_PARTITION_INFO *
32 *---------------------------------------------------------------------*
33 * Read information about partitions of a table
34 *---------------------------------------------------------------------*
35 FORM get_partition_info
36 USING
37 i_tablnm TYPE rsd_tablnm
38 CHANGING
39 e_ts_part_info TYPE rsdu_ts_part_info.
40
41 DATA:
42 l_s_part_info TYPE rsdu_s_part_info.
43
44 EXEC SQL.
45 open csr for
46 select partition_name, high_value
47 from user_tab_partitions
48 where table_name = :i_tablnm
49 ENDEXEC.
50
51 DO.
52 EXEC SQL.
>>>>> fetch next csr into :l_s_part_info-partition_name,
54 :l_s_part_info-high_value
55 ENDEXEC.
56
57 IF sy-subrc <> 0.
58 EXIT.
59 ENDIF.
60
61 * Special treatment of upper limit (highvalue) in Oracle
62 IF l_s_part_info-high_value EQ 'MAXVALUE'.
63 l_s_part_info-high_value = rsdu_c_max_value.
64 ENDIF.
65
66 INSERT l_s_part_info INTO TABLE e_ts_part_info.
67 ENDDO.

есть подобное http://sapboard.ru/forum/viewtopic.php?f=14&t=46832&start=0

В теме говорится о загрузке данных. У меня при формировании индекса.

Цепочка:
Загрузка пакетом данных в DSO (успешно) - > активация DSO (успешно) - > удаление индексов из инфо-куба (успешно) - > процесс переноса данных в инфо-куб (успешно) -> Создание индексов в инфо-кубе (Дамп DBIF_DSQL2_SQL_ERROR)

Причем самое неприятное, что при ошибке не отправляет сообщение, хотя оно настроено.

Лог в мониторе цепочек процессов:

10.08.2012 06:00:36 Задание запущено.
10.08.2012 06:00:36 Шаг 001 запущен (прогр. RSPROCESS, вариант &0000000739136, пользов. BWREMOTE)
10.08.2012 06:00:37 Запустить процесс INDEX DEL_INDEX_COPTY_GR в прогоне 7TYZVU8V0EL3JSXDP3SMQ9EL8 цепочки PC_TR_CRM_PDS
10.08.2012 06:00:42 SQL:: 10.08.2012: 06:00:42: BWREMOTE
10.08.2012 06:00:42 ALTER TABLE "/BIC/FCOPTY_GR" MONITORIN: : :
10.08.2012 06:00:42 SQL-END:: 10.08.2012: 06:00:42: 00:00:00
10.08.2012 06:00:43 SQL:: 10.08.2012: 06:00:43: BWREMOTE
10.08.2012 06:00:43 CREATE BITMAP INDEX: : :
10.08.2012 06:00:43 "SAPSR3"."/BIC/FCOPTY_GR~010" ON "/BIC/FCOPTY_GR": : :
10.08.2012 06:00:43 ( "KEY_COPTY_GRP" ) PCTFREE 10 INITRANS: : :
10.08.2012 06:00:43 2 MAXTRANS 255 STORAGE ( INITIAL 16 K NEXT: : :
10.08.2012 06:00:43 2560 K MINEXTENTS 1 MAXEXTENTS UNLIMITED: : :
10.08.2012 06:00:43 PCTINCREASE 0 FREELISTS 4 FREELIST GROUPS 1: : :
10.08.2012 06:00:43 BUFFER_POOL DEFAULT ) LOCAL PARALLEL TABLESPACE: : :
10.08.2012 06:00:43 "PSAPSR3" NOLOGGING COMPUTE STATISTIC: : :
10.08.2012 06:01:09 SQL-END:: 10.08.2012: 06:01:09: 00:00:26
10.08.2012 06:01:09 SQL:: 10.08.2012: 06:01:09: BWREMOTE
10.08.2012 06:01:09 ALTER INDEX "/BIC/FCOPTY_GR~010" NOPARALLEL: : :
10.08.2012 06:01:09 SQL-END:: 10.08.2012: 06:01:09: 00:00:00
10.08.2012 06:01:09 SQL:: 10.08.2012: 06:01:09: BWREMOTE
10.08.2012 06:01:09 CREATE BITMAP INDEX: : :
10.08.2012 06:01:09 "SAPSR3"."/BIC/FCOPTY_GR~020" ON "/BIC/FCOPTY_GR": : :
10.08.2012 06:01:09 ( "KEY_COPTY_GRT" ) PCTFREE 10 INITRANS: : :
10.08.2012 06:01:09 2 MAXTRANS 255 STORAGE ( INITIAL 16 K NEXT: : :
10.08.2012 06:01:09 2560 K MINEXTENTS 1 MAXEXTENTS UNLIMITED: : :
10.08.2012 06:01:09 PCTINCREASE 0 FREELISTS 4 FREELIST GROUPS 1: : :
10.08.2012 06:01:09 BUFFER_POOL DEFAULT ) LOCAL PARALLEL TABLESPACE: : :
10.08.2012 06:01:09 "PSAPSR3" NOLOGGING COMPUTE STATISTIC: : :
10.08.2012 06:01:31 SQL-END:: 10.08.2012: 06:01:31: 00:00:22
10.08.2012 06:01:31 SQL:: 10.08.2012: 06:01:31: BWREMOTE
10.08.2012 06:01:31 ALTER INDEX "/BIC/FCOPTY_GR~020" NOPARALLEL: : :
10.08.2012 06:01:31 SQL-END:: 10.08.2012: 06:01:31: 00:00:00
10.08.2012 06:01:31 SQL:: 10.08.2012: 06:01:31: BWREMOTE
10.08.2012 06:01:31 CREATE BITMAP INDEX: : :
10.08.2012 06:01:31 "SAPSR3"."/BIC/FCOPTY_GR~030" ON "/BIC/FCOPTY_GR": : :
10.08.2012 06:01:31 ( "KEY_COPTY_GRU" ) PCTFREE 10 INITRANS: : :
10.08.2012 06:01:31 2 MAXTRANS 255 STORAGE ( INITIAL 16 K NEXT: : :
10.08.2012 06:01:31 2560 K MINEXTENTS 1 MAXEXTENTS UNLIMITED: : :
10.08.2012 06:01:31 PCTINCREASE 0 FREELISTS 4 FREELIST GROUPS 1: : :
10.08.2012 06:01:31 BUFFER_POOL DEFAULT ) LOCAL PARALLEL TABLESPACE: : :
10.08.2012 06:01:31 "PSAPSR3" NOLOGGING COMPUTE STATISTIC: : :
10.08.2012 06:01:53 SQL-END:: 10.08.2012: 06:01:53: 00:00:22
10.08.2012 06:01:53 SQL:: 10.08.2012: 06:01:53: BWREMOTE
10.08.2012 06:01:53 ALTER INDEX "/BIC/FCOPTY_GR~030" NOPARALLEL: : :
10.08.2012 06:01:53 SQL-END:: 10.08.2012: 06:01:53: 00:00:00
10.08.2012 06:01:54 SQL:: 10.08.2012: 06:01:54: BWREMOTE
10.08.2012 06:01:54 CREATE BITMAP INDEX: : :
10.08.2012 06:01:54 "SAPSR3"."/BIC/FCOPTY_GR~040" ON "/BIC/FCOPTY_GR": : :
10.08.2012 06:01:54 ( "KEY_COPTY_GR1" ) PCTFREE 10 INITRANS: : :
10.08.2012 06:01:54 2 MAXTRANS 255 STORAGE ( INITIAL 16 K NEXT: : :
10.08.2012 06:01:54 2560 K MINEXTENTS 1 MAXEXTENTS UNLIMITED: : :
10.08.2012 06:01:54 PCTINCREASE 0 FREELISTS 4 FREELIST GROUPS 1: : :
10.08.2012 06:01:54 BUFFER_POOL DEFAULT ) LOCAL PARALLEL TABLESPACE: : :
10.08.2012 06:01:54 "PSAPSR3" NOLOGGING COMPUTE STATISTIC: : :
10.08.2012 06:02:14 SQL-END:: 10.08.2012: 06:02:14: 00:00:20
10.08.2012 06:02:14 SQL:: 10.08.2012: 06:02:14: BWREMOTE
10.08.2012 06:02:14 ALTER INDEX "/BIC/FCOPTY_GR~040" NOPARALLEL: : :
10.08.2012 06:02:14 SQL-END:: 10.08.2012: 06:02:14: 00:00:00
10.08.2012 06:02:14 SQL:: 10.08.2012: 06:02:14: BWREMOTE
10.08.2012 06:02:14 CREATE BITMAP INDEX: : :
10.08.2012 06:02:14 "SAPSR3"."/BIC/FCOPTY_GR~050" ON "/BIC/FCOPTY_GR": : :
10.08.2012 06:02:14 ( "KEY_COPTY_GR2" ) PCTFREE 10 INITRANS: : :
10.08.2012 06:02:14 2 MAXTRANS 255 STORAGE ( INITIAL 16 K NEXT: : :
10.08.2012 06:02:14 2560 K MINEXTENTS 1 MAXEXTENTS UNLIMITED: : :
10.08.2012 06:02:14 PCTINCREASE 0 FREELISTS 4 FREELIST GROUPS 1: : :
10.08.2012 06:02:14 BUFFER_POOL DEFAULT ) LOCAL PARALLEL TABLESPACE: : :
10.08.2012 06:02:14 "PSAPSR3" NOLOGGING COMPUTE STATISTIC: : :
10.08.2012 06:02:36 SQL-END:: 10.08.2012: 06:02:36: 00:00:22
10.08.2012 06:02:36 SQL:: 10.08.2012: 06:02:36: BWREMOTE
10.08.2012 06:02:36 ALTER INDEX "/BIC/FCOPTY_GR~050" NOPARALLEL: : :
10.08.2012 06:02:36 SQL-END:: 10.08.2012: 06:02:36: 00:00:00
10.08.2012 06:02:38 Внутренний режим прерван с динамической ошибкой (см. ST22).
10.08.2012 06:02:38 Задание отменено.


Ошибка возникает не всегда, может раз в сутки, может через несколько дней.