Expired subscription clean up job failing

the history message from the step:
Date 19/11/2014 08:41:11
Log Job History (Expired subscription clean up)
Step ID 1
Server TV-SQL1
Job Name
Expired subscription clean up
Step Name Run agent.
Duration 00:00:01
Sql Severity 16
Sql Message ID 1934
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: IBA\xxx. DELETE failed because the following SET options have incorrect settings: 'ANSI_NULLS, QUOTED_IDENTIFIER'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or
query notifications and/or XML data type methods and/or spatial index operations. [SQLSTATE 42000] (Error 1934). The step failed.
when I run the step manually I get:
Msg 1934, Level 16, State 1, Line 1
DELETE failed because the following SET options have incorrect settings: 'ANSI_NULLS, QUOTED_IDENTIFIER'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or
XML data type methods and/or spatial index operations.
Msg 20709, Level 16, State 1, Procedure sp_MScleanup_conflict, Line 66
The merge process could not clean up the conflict table "[MSmerge_conflict_recordings_items]" for publication "recordings".
I think I know which table (items in db recordings). it has a computed field with a replicated text index on it.
the computed field definition is:
(ltrim(isnull([item_title],'')+' ')+isnull([item_desc],'')) which are 2 other fields in the table nvarchar allowing nulls.
what do I need to do to stop the cleanup job from crashing.
thanx
david

Which version of SQL are you using?
Did you check this article -
http://blogs.msdn.com/b/sqlserverfaq/archive/2014/11/13/merge-replication-expired-subscription-clean-up-job-sp-expired-subscription-cleanup-sp-mscleanup-conflict-fails-with-error-msg-1934-level-16-state-1-and-msg-20709-level-16-state-1-procedure-sp-mscleanup-conflict.aspx
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Similar Messages

Every day Expired subscription clean up job fails on publisher server

Dear All,
Few days back I configured transactional replication b/w 2 server after that every day I noticed
Expired subscription clean up job fails on publisher server but not any effect to replication it's going smooth.
ERROR MESSAGE:
Only functions and some extended stored procedures can be executed from within a function. [SQLSTATE 42000] (Error 557). The step failed
please help me!!!
Thank In Advance!!!
mastanvali shaik

Actuvally already I configured replication for this server 3 database after we moved to another server for some h/w issue.
that time we deleted subscriber and publisher and break transaction replication.
after new server configuration it's allow to configure replication for 2 databases only.
as per above query I found category 1 for 3 databases but 2 databases are in replication.
the another databases that showing category 1 is past in replication, but it doesn't allow to configure replication.
please give me solution for same .
Db name
dbid
sid
mode
status
status2
category
cmptlevel
version
ABCD
7
0x010500000000000515000000C953D90F09EF4A00F4EBEF3281230000
0
65536
1090519040
1
100
661
-replication running
FGH
11
0x010500000000000515000000C953D90F09EF4A00F4EBEF3281230000
0
65536
1090519040
1
100
661
- not allowing for replication
XYZ
12
0x0105000000000005150000006FE21C5B049413F15AD147AEF4010000
0
65536
1090519040
1
100
661
-replication running
past replication working for three databases
mastanvali shaik

Background job failing - ECC 6.0, Solution Manager 7.0

Dear All,
Four days back, I have installed the Solution Manager 7.0 and ECC 6.0 on
HPUX IA64 hardware with database as Oracle 10.2.0.2.0 (Unicode).
In both server, latest kernel patch has been applied.
The Support package versions are (both server):
KERNEL (Release 700)      146
SAP_BASIS           0014
SAP_ABA           0014
PI_BASIS(2005_1_700)      0014
ST-PI                0005
SAP_BW                0016
While checking the the jobs from SM37, in both the server,
I am observing that following jobs are always failing with
same reason:
SAP_COLLECTOR_FOR_PERFMONITOR
=============================
Date       Time     Message text                                                           Message class Message no. Message type
========== ======== ====================================================================== ============= =========== ============
15.05.2008 06:25:12 Job started                                                                 00           516          S
15.05.2008 06:25:12 Step 001 started (program RSCOLL00, variant , user ID BGDUSER)              00           550          S
15.05.2008 06:25:18 Clean_Plan:Cleanup of DB13 Plannings                                       DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:started by RSDBPREV                       on server gcbeccd     DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:Cleaning up jobs of system RD3                                  DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:finished                                                        DB6PM         000          S
15.05.2008 06:25:18 Database system not supported                                               S1           101          S
15.05.2008 06:25:36 ABAP/4 processor: DBIF_DSQL2_SQL_ERROR                                      00           671          A
15.05.2008 06:25:36 Job cancelled                                                               00           518          A
SAP_REORG_UPDATERECORDS
=======================
Date       Time     Message text                                                          Message class Message no. Message type
========== ======== ===================================================================== ============= =========== ============
14.05.2008 00:31:01 Job started                                                                00           516          S
14.05.2008 00:31:01 Step 001 started (program RSM13002, variant SAP&001, user ID BGDUSER)      00           550          S
14.05.2008 00:31:01 Reorganization of update date not allowed in batch                         15           100          A
14.05.2008 00:31:02 Job cancelled                                                              00           518          A
SAP_WP_CACHE_RELOAD_FULL
========================
Date       Time     Message text                                                                                Message class Message no. Message type
========== ======== ============================================================================================ ============= =========== ============
15.05.2008 00:30:11 Job started                                                                                00           516          S
15.05.2008 00:30:11 Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID BGDUSER)      00           550          S
15.05.2008 00:30:11 No component system chosen                                                                   URL_GEN_MSGS      031          E
15.05.2008 00:30:11 Job cancelled after system exception ERROR_MESSAGE                                                00           564          A
Please help to resolve this issue.
Thanks in advance.
Regards
Sudip Ghosh

Hi Markus,
Thanks for the reply.
Below is the dump:
======
======
Runtime Errors         DBIF_DSQL2_SQL_ERROR
Date and Time          15.05.2008 06:25:36
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error 3113 occurred in the current database connection "DEFAULT".
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel"
Database error code........: 3113
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" " "
"RSORAVSH" or "RSORAVSH"
"FILL_DBVSE"
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.
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 15
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 1117216
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 695792
MM Free. 400816
User and Transaction
Client.............. 000
User................ "BGDUSER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "482B8A4C89F0442BE10000000A0A049E"
Program............. "RSORAVSH"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAVSH" - in "FILL_DBVSE".
The main program was "RSORAVSH ".
In the source code you have the termination point in line 48
of the (Include) program "RSORAVSH".
The program "RSORAVSH" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BGDUSER"
Job Number..... 05251100
Source Code Extract
Line
SourceCde
18
INCLUDE STRUCTURE v_system_event_struc.
19
DATA: END OF v_system_event_tab .
20
21
check sy-dbsys(3) = 'ORA' .
22
23
Get the new snapshots
24
25
PERFORM fill_dbvse TABLES v_system_event_tab.
26
27
28
Get the old snapshots from database table MONI
29
30
startday = sy-datum - days_to_keep .
31
32
33
Save new data now (otherwise these data will be selected twice)
34
35
CONCATENATE 'SYSEVENT' sy-datum sy-uzeit INTO   monikey .
36
37
EXPORT sy-datum
38
sy-uzeit
39
v_system_event_tab
40
TO DATABASE moni(db) ID monikey .
41
42
*&      Form FILL_DBVSE
43
44
FORM fill_dbvse TABLES v_system_event_tab.
45
date = sy-datum .
46
time = sy-uzeit .
47
EXEC sql performing append_v_system_event .
>>>>>
select event,
49
total_waits,
50
total_timeouts,
51
time_waited * 10,
52
average_wait * 10
53
into :v_system_event_struc
54
from v$system_event
55
ENDEXEC .
56
ENDFORM.                               " FILL_DBVSE
57
58
59
*&      Form APPEND_V_SYSTEM_EVENT
60
61
FORM append_v_system_event.
62
v_system_event_tab-date = date .
63
v_system_event_tab-time = time .
64
65
MOVE-CORRESPONDING v_system_event_struc TO v_system_event_tab.
66
APPEND v_system_event_tab .
67
ENDFORM.                               " APPEND_V_SYSTEM_EVENT
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
16
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report for Collecting Data from V$SYSTEM_EVENT Hourly
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080515
SY-UZEIT
062520
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
2 FORM         RSORAVSH                            RSORAVSH                               48
FILL_DBVSE
1 EVENT        RSORAVSH                            RSORAVSH                               25
START-OF-SELECTION
Chosen variables
Name
Val.
No.       2 Ty.          FORM
Name FILL_DBVSE
SY-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
V_SYSTEM_EVENT_STRUC
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222222222222222220000000000000000
0000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
%_SPACE
0
0
2
0
SY
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
No.       1 Ty.          EVENT
Name START-OF-SELECTION
SY-LDBPG
SAPDB__S
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
SY-DBSYS+0(6)
ORA
000
000
454
F21
SYST
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
V_SYSTEM_EVENT_TAB[]
Table[initial]
V_SYSTEM_EVENT_TAB
00000000000000                                                                ################
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333322222222222222222222222222222222222222222222222222222222222222220000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
SY-DATUM
20080515
00000000
00000000
33333333
20080515
DAYS_TO_KEEP
30
0001
000E
STARTDAY
00000000
00000000
00000000
33333333
00000000
MONIKEY
0000000000000000000000
0000000000000000000000
2222222222222222222222
0000000000000000000000
SY-UZEIT
062520
000000
000000
333333
062520
SYST-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
MONI-CLUSTR
0
00
00
MONI
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222220022000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ExecuteCall"
of the SAP kernel, in line 1190 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080515062520.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x40000000047b51e0 Z10abdbdserriPKtiS0_P9DS_HEADERS0_iPv + 0x470 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000003d777f0 Z11ExecuteCallv + 0x11f0 [dw.sapRD3DVEBMGS00]
(5) 0x4000000003d7e7b0 Z8abjdsqlv + 0x1b0 [dw.sapRD3_DVEBMGS00]
(6) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(7) 0x4000000003f53bc0 Z9abxeventPKt + 0x3c0 at abrunt1.c:339 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003d9f210 Z8abtriggv + 0x110 at abrunt1.c:58 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003d9ebe0 ab_run + 0xc0 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001caa820 N_ab_run + 0x20 at dymainstp.c:4739 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cb40f0 dynpmcal + 0x3f0 at dymainstp.c:2281 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001caf260 dynppai0 + 0xcb0 at dymainstp.c:1107 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001fb54e0 TskhLoop + 0x5520 at thxxhead.c:3945 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(20) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(21) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAVSH
0
30.03.2005
10:21:59
19456
E
1
Prg
SAPMSSY0
1
17.12.2007
15:41:05
92160
E
2
Prg
SAPMSSYD
1
12.09.2006
11:33:31
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
8192
E
4
Prg
RSDBRUNT
0
17.12.2007
16:04:40
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
12.09.2006
11:25:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Prg
SAPLSABE
11
09.09.2004
14:18:36
13312
E
12
Prg
SAPLSECU
12
17.12.2007
15:31:45
87040
E
13
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
14
Prg
SAPLSTUP
14
17.12.2007
15:29:58
74752
E
15
Prg
SAPLCNDP
15
11.09.2007
15:24:45
195584
E
16
Prg
SAPLSCNT
16
18.02.2005
14:16:06
30720
E
17
Prg
SAPSHDTV
16
05.01.2005
16:26:16
33792
E
18
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
19
Prg
SAPLOLEA
19
11.09.2007
11:17:30
96256
E
20
Prg
SAPLSGUI
20
17.12.2007
15:41:05
84992
E
21
Prg
SAPLSTTM
21
05.07.2005
13:10:18
69632
E
22
Prg
SAPLSBDC
22
17.12.2007
15:30:54
44032
E
23
Prg
SAPLSFES
23
17.12.2007
16:04:40
260096
E
24
Prg
SAPLTHFB
24
17.12.2007
15:41:05
394240
E
25
Typ
WPINFO
0
26.02.1999
14:49:01
6144
26
Prg
SAPLURFC
26
17.12.2007
15:37:35
22528
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
29
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
30
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
31
Typ
SYST
0
09.09.2004
14:18:12
31744
32
Typ
MONI
0
31.03.2004
16:41:21
5120
Directory of Application Tables
Name                                     Date       Time       Lngth
Val.
Program RSORAVSH
SYST                                     09.09.2004 14:18:12   00004612
\0\0\0\0\0\x0010\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
MONI                                       . .       : :     00002944
\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
71
PAR2
03
0000
0014
002B
RSORAVSH
37
73
PAR2
03
0000
0015
002D
RSORAVSH
37
75
PAR2
03
0000
0016
0026
RSORAVSH
37
77
00
0000
RSORAVSH
37
78
PERP
00
0002
RSORAVSH
44
79
PERP
1C
0000
RSORAVSH
44
80
PERP
04
0000
RSORAVSH
44
81
mvqk
10
0005
0044
04EC
RSORAVSH
45
83
mvqk
0C
0005
0054
052E
RSORAVSH
46
85
DSQL
00
0017
RSORAVSH
48
86
DSQL
01
0018
RSORAVSH
48
87
DSQL
04
0025
RSORAVSH
48
>>>>>
DSQL
16
0025
RSORAVSH
48
89
BRAN
05
0004
RSORAVSH
48
90
perf
00
000A
RSORAVSH
48
91
PERP
80
0000
RSORAVSH
48
92
BRAX
00
FFFC
RSORAVSH
48
93
DSQL
23
0000
RSORAVSH
48
94
ENDF
00
0000
RSORAVSH
56
95
00
0000
RSORAVSH
56
===========
===========
Please check and advise.
Also, I am trying to search for the note 6083 in market place, but not getting the same.
Please advise.
Thanks & Regards
Sudip

Some jobs fail BackupExec, Ultrium 215 drive, NW6.5 SP6

The OS is Netware 6.5 SP6.
The server is a HP Proliant DL-380 G4.
The drive is a HP StorageWorks Ultrium LTO-1 215 100/200GB drive.
The drive is connected to a HP PCI-X Single Channel U320 SCSI HBA, which I recently installed, in order to solve slow transfer speeds, and to solve CPQRAID errors which stalled the server during bootup (it was complaining to have a non-disk drive on the internal controller).
Backup Exec Administrative Console is version 9.10 revision 1158, I am assuming that this means that BE itself has this version number.
Since our data is now more than the tape capacity I have recently started running two jobs interleaved, to backup (around) half of the data at night. One which runs Monday, Wednesday and Friday and one which runs Tuesday and Thursday.
My problem is that while the Tue/Thu job completes succesfully every time, the Mon/Wed/Thu job fails every time.
The jobs have identical policies (except for the interleaved weekdays), but different file selections.
The job log of the Mon/Wed/Thu job fails with this error:
##ERR##Error on HA:1 ID:4 LUN:0 HP ULTRIUM 1-SCSI.
##ERR##A hardware error has been detected during this operation. This
##ERR##media should not be used for any additional backup operations.
##ERR##Data written to this media prior to the error may still be
##ERR##restored.
##ERR##SCSI bus timeouts can be caused by a media drive that needs
##ERR##cleaning, a SCSI bus that is too long, incorrect SCSI
##ERR##termination, or a faulty device. If the drive has been working
##ERR##properly, clean the drive or replace the media and retry the
##ERR##operation.
##ERR##Vendor: HP
##ERR##Product: ULTRIUM 1-SCSI
##ERR##ID:
##ERR##Firmware: N27D
##ERR##Function: Write(5)
##ERR##Error: A timeout has occurred on drive HA:1 ID:4 LUN:0 HP
##ERR##ULTRIUM 1-SCSI. Please retry the operation.(1)
##ERR##Sense Data:
##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
##NML##
##NML##
##NML##
##NML## Total directories: 2864
##NML## Total files: 23275
##NML## Total bytes: 3,330,035,351 (3175.7 Megabytes)
##NML## Total time: 00:06:51
##NML## Throughput: 8,102,275 bytes/second (463.6 Megabytes/minute)
I am suspecting the new controller, or perhaps a broken drive?
I have run multiple cleaning jobs on the drive with new cleaning tapes. The cabling is secured in place.
I have looked for firmware updates, but even though theres a mentioning of a new firmware on hp's site (see http://h20000.www2.hp.com/bizsupport...odTypeId=12169), I can't find the firmware for netware HP LTT (the drive diagnosis / update tool).
I'm hoping someone can provide me some useful info towards solving this problem.
Regards,
Tor

My suggestion to you is to probably just give up on fixing this. I
have the same DL380, but a slightly newer drive(Ultrium 448). After
working with HP, Adaptec, & Symantec for over a year I gave up. I've
tried different cards (HP-LSI, Adaptec) , cables, and even swapped the
drive twice with HP but was never able to get it to work.
In the end I purchased a new server, moved the card and tape drive,
and cables all over to the new server and the hardware has been
working fine in the new box for the last year or so. Until I loaded l
SP8 the other day.
My guess is that the PCI-X slot used for these cards isn't happy with
the server hardware.
On Tue, 27 Jan 2009 11:16:02 GMT, torcfh
<[email protected]> wrote:
>
>The OS is Netware 6.5 SP6.
>
>The server is a HP Proliant DL-380 G4.
>
>The drive is a HP StorageWorks Ultrium LTO-1 215 100/200GB drive.
>
>The drive is connected to a HP PCI-X Single Channel U320 SCSI HBA,
>which I recently installed, in order to solve slow transfer speeds, and
>to solve CPQRAID errors which stalled the server during bootup (it was
>complaining to have a non-disk drive on the internal controller).
>
>Backup Exec Administrative Console is version 9.10 revision 1158, I am
>assuming that this means that BE itself has this version number.
>
>Since our data is now more than the tape capacity I have recently
>started running two jobs interleaved, to backup (around) half of the
>data at night. One which runs Monday, Wednesday and Friday and one which
>runs Tuesday and Thursday.
>
>My problem is that while the Tue/Thu job completes succesfully every
>time, the Mon/Wed/Thu job fails every time.
>
>The jobs have identical policies (except for the interleaved weekdays),
>but different file selections.
>
>The job log of the Mon/Wed/Thu job fails with this error:
>
>##ERR##Error on HA:1 ID:4 LUN:0 HP ULTRIUM 1-SCSI.
>
>##ERR##A hardware error has been detected during this operation. This
>
>##ERR##media should not be used for any additional backup operations.
>
>##ERR##Data written to this media prior to the error may still be
>
>##ERR##restored.
>
>##ERR##SCSI bus timeouts can be caused by a media drive that needs
>
>##ERR##cleaning, a SCSI bus that is too long, incorrect SCSI
>
>##ERR##termination, or a faulty device. If the drive has been working
>
>##ERR##properly, clean the drive or replace the media and retry the
>
>##ERR##operation.
>
>##ERR##Vendor: HP
>
>##ERR##Product: ULTRIUM 1-SCSI
>
>##ERR##ID:
>
>##ERR##Firmware: N27D
>
>##ERR##Function: Write(5)
>
>##ERR##Error: A timeout has occurred on drive HA:1 ID:4 LUN:0 HP
>
>##ERR##ULTRIUM 1-SCSI. Please retry the operation.(1)
>
>##ERR##Sense Data:
>
>##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
>
>##ERR##00 00 00 00 - 00 00 00 00 - 00 00 00 00 - 00 00 00 00
>
>##NML##
>
>##NML##
>
>##NML##
>
>##NML## Total directories: 2864
>
>##NML## Total files: 23275
>
>##NML## Total bytes: 3,330,035,351 (3175.7 Megabytes)
>
>##NML## Total time: 00:06:51
>
>##NML## Throughput: 8,102,275 bytes/second (463.6
>Megabytes/minute)
>
>I am suspecting the new controller, or perhaps a broken drive?
>
>I have run multiple cleaning jobs on the drive with new cleaning tapes.
>The cabling is secured in place.
>
>I have looked for firmware updates, but even though theres a mentioning
>of a new firmware on hp's site (see http://tinyurl.com/d8tkku), I can't
>find the firmware for netware HP LTT (the drive diagnosis / update
>tool).
>
>I'm hoping someone can provide me some useful info towards solving this
>problem.
>
>Regards,
>Tor

Backup Job Fails

Dear All,
I received an error in maintenace plan regarding the backup Job Fails.
Executed as user: IPROINDIA\sqlservice. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 1:30:27 AM Could not load
package "Maintenance Plans\Daily_BACKUP" because of error 0xC0014062. Description: The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Login timeout expired). The SQL statement that was issued has failed.
Source: Started: 1:30:27 AM Finished: 1:30:43 AM Elapsed: 15.297 seconds. The package could not be loaded. The step failed.
Anyone please Help What is the issue

Can you log in as PROINDIA\sqlservice to SQL Server and issue BACKUP DATABASE dbname ........? Still
have a error?
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

FEP_GetNewData_FEPDB_ Job fails

Every Day FEP_GetNewData_FEPDB_ job fails from 8:00 to 9:00 AM. The rest of the day is OK. I think this job runs every 15 minutes.
We upgraded FEP 2010 to Rollup 1, but the problem is not solved. we have SCCM 2007 R2 SP2.
I've seen a lot forums, but I can't see which is the solution exactly

Yes, I know this is an old post, but I’m trying to clean them up.
I hate to say it but this is likely a problem within your environment. Particularly if you haven’t seen anyone else report it. As such, I recommend that you contract CSS directly, they will work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

ERROR VNIC creation job failed

Hello All,
I have brought oracle VM X86 manager into ops center 12c control. When I try to create a new virtual machine it is throwing the ‘ERROR VNIC creation job failed’ error. Can anybody throw some light over this issue.
Thanks in advance.
Detailed log is
44:20 PM IST ERROR Exception occurred while running the task
44:20 PM IST ERROR java.io.IOException: VNIC creation job failed
44:20 PM IST ERROR VNIC creation job failed
44:20 PM IST ERROR com.sun.hss.services.virtualization.guestservice.impl.OvmCreateVnicsTask.doRun(OvmCreateVnicsTask.java:116)
44:20 PM IST ERROR com.sun.hss.services.virtualization.guestservice.impl.OvmAbstractTask.run(OvmAbstractTask.java:560)
44:20 PM IST ERROR sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
44:20 PM IST ERROR sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
44:20 PM IST ERROR sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
44:20 PM IST ERROR java.lang.reflect.Method.invoke(Method.java:597)
44:20 PM IST ERROR com.sun.scn.jobmanager.common.impl.TaskExecutionThread.run(TaskExecutionThread.java:194)
Regards,
george

Hi friends
I managed to find the answer. Internally it is has some indexes in the data base level. It still maintains the indexes in the shadow tables. Those all need to be deleted. With our Basis team help I have successfully deleted those and recreated the indexes.
As Soorejkv said sap note 1283322 will help you on this to understand the scenarios.
Thank you all.
Regards
Ram

Hi Post Upgrade Job Failing

HI All,
We have recently done the Upgrade from BW 3.1 to BI 7.0
There is a issue regarding the POST Upgrade
One Job is failing every day
The name of the JOB is BI_WRITE_PROT_TO_APPLLOG
And the Job log is
06/18/2008 00:04:55 Job started                                                          00           516          S
06/18/2008 00:04:55 Logon of user PALAPSJ in client 200 failed when starting a step      00           560          A
06/18/2008 00:04:55 Job cancelled
                                                       00           518          A
This Job is actually running the program
RSBATCH_WRITE_PROT_TO_APPLLOG
when i try to run this program with my user id its working
but with the other user id which it is schedule its failing giving the messages as mentioned in the job log
Kindly suggest me
REgards
janardhan K

Maybe it's a dialog and no system or background user. so the job fails.
Regards,
Juergen

Background job failing

Experts,
We have background job running as part of the daily load. The user who created and scheduled the job, his account diabled recently and that makes job failing. I need to keep that job running but can not figure out how to change the user name in the job. For example, 0EMPLOYEE_CHANGE_RUN job based on event 'zemployee' triggers at the end of employee data load. Can you please provide any hint what should I do to change user name or take the ownership to keep this job running. Thanks.
Regards,
Nimesh

Hello,
Go to SM37--> put job name "0EMPLOYEE_CHANGE_RUN" and user as "*" to get all users.
Now select the job with released status>(Menu)Job>change->Steps-> select 1st row > change(pencil icon)>now you see the user name here.
Change the user name to the user name used for all background job and save.
Done.
Happy Tony

Error in Control Framework: Background job failed

Hi Experts,
One background job failed with job log: Error in Control Framework in ECC 6.0 system; the job is supposed to produce a XML report. Can anyone please give some idea on this why it could happen? One SAP note 893534 has described same kind of issue but in CRM system. That note even cant be implemeneted in ECC 6.0. Any workaround? Is it a BASIS issue here?
Thanks & Regards,
SKB

Hello,
please check the variant. We had this problem, and when checking the variant I got a shortdump because the variant did not fit to the program (there were problems with subscreens in the selection screen). After adjusting the variant with program RSVARDOC_610 the variant was ok.
I can not check if this solved the problem because the job runs weekly, and the next job is on Monday. But give it a try...
HTH,
Jens Hoetger

User, Role, Profile Synchronization Job Fails

Hi Gurus,
When I am scheduling a job the User, Role, and Profile Sync. job fails giving an error
"Cannot assign a java.lang.String object of length 53 to host variable 5 which has JDBC type VARCHAR(40)."
This happens when the synchronization happens with a portal system. We dont have a ruleset for the portal system, So if I put in a "*", it includes this system and results in the error, If I manually select all other system, it works fine. Is there any way to remove this error so that I can schedule the jobs without having to select every system manually.
Regards,
Chinmaya

Hi,
As per my knowledge, in the Portal system, you should perform only user sync. Roles/profile sync will not work since portal will have workset roles.
Please refer SAP Note 1168120, which may help you to understand the limitations
Hope this helps!!
Rgds,
Raghu
Edited by: Raghu Boddu on Nov 4, 2010 7:39 PM

Code in before report getting executed but "Job error is: BIP job failed."

Customer is executing a BIP job that fires a pl/sql procedure via before report trigger. Procedure is completing successfully. But the BIP report is not getting generated. ESS process ends in error with the following error:
oracle.as.scheduler.ExecutionErrorException: ESS-07033 Job logic indicated a system error occurred while executing an asynchronous java job for request 604103. Job error is: BIP job failed.
     at oracle.as.scheduler.rp.AsyncFinalizeProcessor.processFinalizeRequest(AsyncFinalizeProcessor.java:131)
     at oracle.as.scheduler.rp.AsyncJavaSysExecWrapper.finalizeExecution(AsyncJavaSysExecWrapper.java:250)
     at oracle.as.scheduler.rp.EndpointProcessor.finalizeExecute(EndpointProcessor.java:1018)
     at oracle.as.scheduler.rp.EndpointProcessor.finalizeExecuteWrapper(EndpointProcessor.java:980)
     at oracle.as.scheduler.adapter.EndpointImpl.finalizeExecute(EndpointImpl.java:561)
     at oracle.as.scheduler.ejb.EssAppEndpointBean.finalizeExecute(EssAppEndpointBean.java:162)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
     at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
     at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy197.finalizeExecute(Unknown Source)
     at oracle.as.scheduler.ejb.ESSAppEndpoint_t596cy_MDOImpl.__WL_invoke(Unknown Source)
     at weblogic.ejb.container.internal.MDOMethodInvoker.invoke(MDOMethodInvoker.java:35)
     at oracle.as.scheduler.ejb.ESSAppEndpoint_t596cy_MDOImpl.finalizeExecute(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.invokeFinalizeExecute(RequestProcessor.java:8133)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.execStage_Finalize(RequestProcessor.java:7331)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.process_execute(RequestProcessor.java:4813)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.dispatchHandler(RequestProcessor.java:2833)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.processExecuteEvent(RequestProcessor.java:696)
     at oracle.as.scheduler.adapter.ra.rdp.RequestProcessor.processUpdateEvent(RequestProcessor.java:1345)
     at oracle.as.scheduler.adapter.ra.WorkUnitWorkerBase.processWork(WorkUnitWorkerBase.java:199)
     at oracle.as.scheduler.adapter.ra.WAWorker.run(WAWorke...
Any tips/pointers on possible issues? Could this be a template corruption?

Any reply for the above error please.I do have the same issue.
Please suggest.

Report Job failed when Bursting is used in BI Publisher 11.1.1.5

The Report Job failed when Bursting is used.
error message:
[INSTANCE_ID=aimedap1s.1347261753557] [OUTPUT_ID=1421][ReportProcessor]Error rendering documentoracle.xdo.servlet.scheduler.ProcessingException: [ReportProcessor]Error rendering document
at oracle.xdo.enterpriseScheduler.bursting.BurstingReportProcessor.renderReport(BurstingReportProcessor.java:455)
at oracle.xdo.enterpriseScheduler.bursting.BurstingReportProcessor.onMessage(BurstingReportProcessor.java:127)
at oracle.xdo.enterpriseScheduler.util.CheckpointEnabl
the reproduce steps :
1. Create a Bursting query in the Data Model
2. Create Report Job with the option
"Use Bursting Definition to Determine Output & Delivery Destination" enabled
3.Schedule the report Job
4. run the report and found the status of it is problem, the error message above can be found.
*Note:not all the report job failed when bursting is used, in step1 when set OUTPUT_FORMAT as PDF,HTML,RTF,PowerPoint 2007,
the report will be run successfully,but when set other OUTPUT_FORMAT that list in the following document, the report can not run successfully.
http://docs.oracle.com/cd/E21764_01/bi.1111/e18862/T527073T555155.htm
Adding Bursting Definitions>>Defining the Query for the Delivery XML
>>OUTPUT_FORMAT
Can anyone give some advice on how to troubleshooting it?
Looking forward for your reply
Regards

Hello vma.
I happened to find the solution on 11.1.1.3. With xdo-server.jar, you can use DataProcessor class.
For details and sample source code:
http://blog-koichiro.blogspot.com/2011/11/bi-publisher-java-apigenerate-pdf-with.html
* Not sure if it works on 11.1.1.5 though, I hope this gonna help you.

After Applying 11.1 PSU4/5 the Cognos Enterprise Planner Job fails

We have recently applied Oracle 11.1 PSU5 to our Dev environment. The Application is IBM Cognos Enterprise Planner 8.4 version. The import_queue_tidy job fails with NO ROWS returned. If we use the new DLL to retry within 5 seconds, the job succeeds.
Error Number: -2147220665
Line Number: 220
Description: Unable to get Job Item
The Job management step failed. An attempt has been made to mark the 'IMPORT_QUEUE_TIDY' Job as CANCELLED. Please rectify the problem and re-create a similar Job.
No rows returned by statement
SELECT jobitemguid, identifier, jobitemstateid, sequence FROM indemplwf.P_JOBITEM WHERE jobguid = '{6C44B8D4-AD8F-45E6-9405-EA25E7C2C37F}' ORDER BY sequence
when executed on connection created with connection string of
Provider=OraOLEDB.Oracle;Data Source=****;User ID=******;Password=*********;
See the log file for further details.
After we retry the job succeeds. This error is happening only after we applied the patches. Has any one seen this happening?
The wierd thing is we cannot reproduce this error, it happens randomly. The error didn't happen until 5th run. We had same exact issue when we applied PSU4 and due to schedule conflict we had to rollback. Not sure how to track this issue down. Any help is appreciated.
Edited by: user1260385 on Jan 12, 2011 2:24 PM
Edited by: user1260385 on Jan 12, 2011 2:29 PM

Thanks for Responding Sri.
Yes I did. Just thought to check with the community if they have seen such issues and any idea as to how to troubleshoot this.

SQL Server Agent Job Failing on Job Step

Hi,
Firstly, apologies if this post has been made in the wrong group. Running SQL Server 2012. I'm attempting to add a SQL Server Agent Job which calls a stored procedure that sends a Database Mail message. The SQL Server and SQL Server Agent
both run under the NT AUTHORITY\NETWORK SERVICE account. The Database Mail service has been enabled, and a public profile created. When running the stored procedure manually, I receive no errors - everything runs as expected and I do receive an
email containing the expected information.
I've created the job, job step, job schedule, attached the schedule to the job, and assigned the job to server, all using T-SQL without error. I've also enabled the mail profile on the SQL Server Agent, and I know that part is working because when
the job fails, I get an email notification of the failure.
I've checked the command text in the job step and parsed it within the SQL Job Step Edit window to confirm, it shows as parsing correctly. However, when I manually run the job itself, I get the following:
Execution of job failed. See the history log for details.
I check the history log and it shows:
[474] Unable to refresh Database Mail profile Database Mail Profile. (reason: ) (Not a typo, the history log shows no reason)
[260] Unable to start mail session.
[396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
The command text on the failing job step is as follows:
DECLARE @date [varchar](10)
SET @date = CAST(GETDATE() AS [varchar](10))
EXEC [dbo].[GetExceptions]
@company = 'MyCompany',
@checkDate = @date
With regard to the date value being passed as varchar: This stored procedure is used to check for exceptions against multiple databases on this server (hence the company parameter) via dynamic SQL. I'd much prefer to use proper data typing but this
is the only way I could get it to work.
Does anyone have any suggestions on anything else I could check, or insights into why this is failing? Any help is greatly appreciated!
Best Regards
Brad

I am not sure if this really helps but I would do follow the below steps:
1. make sure sql server agent has database mail enabled(rigt click on server agent--properties--alert system--enable database mail and choose right profile.) and RESTART THE SQL SERVER AGENT.(i know you said it i working, but sometimes, restart the
sql server agent might fix)
2. check agent error log and check if any error messages.
3. run the command text you mentioned in sql server and see if it is working.(i know you said it is working but just to make sure).
4. make sure sql server agent service user has permissions to run database mail in msdb. check this https://msdn.microsoft.com/en-us/library/ms186358.aspx
5. Check the output from select * from msdb.dbo.sysmail_log and if it says anything
6.it does not look like the job log is getting truncated but to make sure, get the job step output to a text file.to do this, edit the job step and on the job step properties click on advanced, enter path to the output file. this will give the complete
output for the step.
Hope it Helps!!

Expired subscription clean up job failing

Similar Messages

Maybe you are looking for