|
Сервер не может бекапить логические журналы
#36170303
Ссылка:
Ссылка на сообщение:
Ссылка с названием темы:
Ссылка на профиль пользователя:
|
Участник
Откуда: г.Киев
Сообщения: 362
|
|
Добрый день.
Подскажите может кто сталкивался с проблемой. В какой то момент времени , сервер перестает бекапить логические журналы и уходит в чек поинт из за их нехватки.
При детальном анализе видно что сервер их правильно заполняет , но вот заархивировать почему то не может и пишет
Команда ontape -a выдает следующее
1.
2.
3.
4.
5.
6.
7.
8.
[root@onldb2 /]# ontape -a
Performing automatic backup of logical logs.
Please mount tape 1 on /usr/informix_log/log.bkp and press Return to continue ...
This tape contains no log data
При этом скрипт аларм шела начинает их писать но доходя до 32 к перестает, с выше названной ошибкой.
Сервер на котором это все происходит
IBM Informix Dynamic Server Version 11.10.UC1 -- On-Line -- Up 03:09:25 -- 480744 Kbytes
конфиг
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
66.
67.
68.
69.
70.
71.
72.
73.
74.
75.
76.
77.
78.
79.
80.
81.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
98.
99.
100.
101.
102.
103.
104.
105.
106.
107.
108.
109.
110.
111.
112.
113.
114.
115.
116.
117.
118.
119.
120.
121.
122.
123.
124.
125.
126.
127.
128.
129.
130.
131.
132.
133.
134.
135.
136.
137.
138.
139.
140.
141.
142.
143.
144.
145.
146.
147.
148.
149.
150.
151.
152.
153.
154.
155.
156.
157.
158.
159.
160.
161.
162.
163.
164.
165.
166.
167.
168.
169.
170.
171.
172.
173.
174.
175.
176.
177.
178.
179.
180.
181.
182.
183.
184.
185.
186.
187.
188.
189.
190.
191.
192.
193.
194.
195.
196.
197.
198.
199.
200.
201.
202.
203.
204.
205.
206.
207.
208.
209.
210.
211.
212.
213.
214.
215.
216.
217.
218.
219.
220.
221.
222.
223.
224.
225.
226.
227.
228.
229.
230.
231.
232.
233.
234.
235.
236.
237.
238.
239.
240.
241.
242.
243.
244.
245.
246.
247.
248.
249.
250.
251.
252.
253.
254.
255.
256.
257.
258.
259.
260.
261.
262.
263.
264.
265.
266.
267.
268.
269.
270.
271.
272.
273.
274.
275.
276.
277.
278.
279.
280.
281.
282.
283.
284.
285.
286.
287.
288.
289.
290.
291.
292.
293.
294.
295.
296.
297.
298.
299.
300.
301.
302.
303.
304.
305.
306.
307.
308.
309.
310.
311.
312.
313.
314.
315.
316.
317.
318.
319.
320.
321.
322.
323.
324.
325.
326.
327.
328.
329.
330.
331.
332.
333.
334.
335.
336.
337.
338.
339.
340.
341.
342.
343.
344.
345.
346.
347.
348.
349.
350.
351.
352.
353.
354.
355.
356.
357.
358.
359.
360.
361.
362.
363.
364.
365.
366.
367.
368.
369.
370.
371.
372.
373.
374.
375.
376.
377.
378.
379.
380.
381.
382.
383.
384.
385.
386.
387.
388.
389.
ROOTNAME rootdbs # Root dbspace name
ROOTPATH /usr/informix_chunk/rootdbs
# Path for device containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
ROOTSIZE 2000000 # Size of root dbspace (Kbytes)
# Disk Mirroring Configuration Parameters
MIRROR 0 # Mirroring flag (Yes = 1 , No = 0 )
MIRRORPATH # Path for device containing mirrored root
MIRROROFFSET 0 # Offset into mirrored device (Kbytes)
# Physical Log Configuration
PHYSDBS physfiledbs #rootdbs # Location (dbspace) of physical log
PHYSFILE 1900000 # 2000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 218 # Number of logical log files
LOGSIZE 20000 # Logical log size (Kbytes)
# Tablespace Tablespace Configuration in Root Dbspace
TBLTBLFIRST 0 # First extent size (Kbytes) ( 0 = default)
TBLTBLNEXT 0 # Next extent size (Kbytes) ( 0 = default)
# Security
# DBCREATE_PERMISSION:
# By default any user can create a database. Uncomment DBCREATE_PERMISSON to
# limit database creation to a specific user. Add a new DBCREATE_PERMISSION
# line for each permitted user.
#DBCREATE_PERMISSION informix
# DB_LIBRARY_PATH:
# When loading a (C or C++) shared object (for a UDR or UDT), IDS checks that
# the user-specified path starts with one of the directory prefixes listed in
# the comma-separated list of prefixes in DB_LIBRARY_PATH. The string
# "$INFORMIXDIR/extend" must be included in DB_LIBRARY_PATH in order for
# extensibility and IBM supplied blades to work correctly.
# DB_LIBRARY_PATH $INFORMIXDIR/extend
# IFX_EXTEND_ROLE:
# 0 (or off) => Disable use of EXTEND role to control who can register
# external routines.
# 1 (or on) => Enable use of EXTEND role to control who can register
# external routines. This is the default behaviour.
#
IFX_EXTEND_ROLE 1 # To control the usage of EXTEND role.
# EILSEQ_COMPAT_MODE:
# When processing characters, IDS checks if the characters are valid
# for the locale and returns error - 202 if they are not. This causes
# problems in some applications. This parameter preserves the old
# behavior and permits these characters.
# 0 => Disallow illegal characters. This is the default behavior.
# 1 => Allow illegal characters.
#
EILSEQ_COMPAT_MODE 0
#
# ADMIN_MODE_USERS
# This is a comma separated list of those users who can connect to the
# IDS server while it is in single user mode. This list of users is in
# addition user informix.
#
# Example:
# ADMIN_MODE_USERS usera,userb,userc
#
# ADMIN_MODE_USERS
# Diagnostics
MSGPATH /usr/informix/online.log # System message log file path
CONSOLE /dev/console # System console message path
# To automatically backup logical logs, edit alarmprogram.sh and set
ALARMPROGRAM /usr/informix/bin/alarm.sh # Alarm program path
ALRM_ALL_EVENTS 1 # Triggers ALARMPROGRAM for any event occur
TBLSPACE_STATS 1 # Maintain tblspace statistics
# System Archive Tape Device
TAPEDEV /usr/informix_bkp/online.bkp # Tape device path
#TAPEDEV /dev/null # Tape device path
TAPEBLK 512 # Tape block size (Kbytes)
TAPESIZE 50000000 # Maximum amount of data to put on tape (Kbytes)
# Log Archive Tape Device
LTAPEDEV /usr/informix_log/log.bkp # Log tape device path
#LTAPEDEV /dev/null # Log tape device path
LTAPEBLK 32 # Log tape block size (Kbytes)
LTAPESIZE 30000 # Max amount of data to put on log tape (Kbytes)
# Optical
STAGEBLOB # Informix Dynamic Server staging area
# System Configuration
SERVERNUM 0 # Unique id corresponding to a OnLine instance
DBSERVERNAME back_db # Name of default database server
DBSERVERALIASES #
DBSERVERALIASES onldb2 # List of alternate dbservernames
DBSERVERALIASES onl_sec # List of alternate dbservernames
DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env.
RESIDENT 2 # Forced residency flag (Yes = 1 , No = 0 )
MULTIPROCESSOR 1 # 0 for single-processor, 1 for multi-processor
NUMCPUVPS 15 # Number of user (cpu) vps
SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to one
NOAGE 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
# Shared Memory Parameters
LOCKS 2000000 # Maximum number of locks
NUMAIOVPS # Number of IO vps
PHYSBUFF 256 # Physical log buffer size (Kbytes)
LOGBUFF 64 # Logical log buffer size (Kbytes)
CLEANERS 8 # Number of buffer cleaner processes
SHMBASE 0x44000000 # Shared memory base address
SHMVIRTSIZE 65536 # initial virtual shared memory segment size
SHMADD 8192 # Size of new shared memory segments (Kbytes)
EXTSHMADD 8192 # Size of new extension shared memory segments (Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes). 0 =>unlimited
SHMVIRT_ALLOCSEG 0 . 000000 # Values between 0 and . 99 are %, values > 1 are
# KB - when this much virtual memory is used we
# try to get a new segment. 0 means "off". 2nd
# parameter is alarm level
CKPTINTVL 300 # Check point interval (in sec)
TXTIMEOUT 0x12c # Transaction timeout (in sec)
STACKSIZE 256 # Stack size (Kbytes)
# Dynamic Logging
# DYNAMIC_LOGS:
# 2 : server automatically add a new logical log when necessary. (ON)
# 1 : notify DBA to add new logical logs when necessary. (ON)
# 0 : cannot add logical log on the fly. (OFF)
#
# When dynamic logging is on, we can have higher values for LTXHWM/LTXEHWM,
# because the server can add new logical logs during long transaction rollback.
# However, to limit the number of new logical logs being added, LTXHWM/LTXEHWM
# can be set to smaller values.
#
# If dynamic logging is off, LTXHWM/LTXEHWM need to be set to smaller values
# to avoid long transaction rollback hanging the server due to lack of logical
# log space, i.e. 50 / 60 or lower.
#
# In case of system configured with CDR, the difference between LTXHWM and
# LTXEHWM should be atleast 30 % so that we could minimize log overrun issue.
DYNAMIC_LOGS 2
LTXHWM 70
LTXEHWM 80
# System Page Size
# BUFFSIZE - OnLine no longer supports this configuration parameter.
# To determine the page size used by OnLine on your platform
# see the last line of output from the command, 'onstat -b'.
# Recovery Variables
# OFF_RECVRY_THREADS:
# Number of parallel worker threads during fast recovery or an offline restore.
# ON_RECVRY_THREADS:
# Number of parallel worker threads during an online restore.
OFF_RECVRY_THREADS 10 # Default number of offline worker threads
ON_RECVRY_THREADS 1 # Default number of online worker threads
# Data Replication Variables
# DRAUTO: 0 manual, 1 retain type, 2 reverse type
DRAUTO 0 # DR automatic switchover
DRINTERVAL 30 # DR max time between DR buffer flushes (in sec)
DRTIMEOUT 30 # DR network timeout (in sec)
DRLOSTFOUND /usr/informix/etc/dr.lostfound # DR lost+found file path
DRIDXAUTO 0 # DR automatic index repair. 0 =off, 1 =on
LOG_INDEX_BUILDS 0 # logically log content of indexes
# CDR Variables
CDR_EVALTHREADS 1 , 2 # evaluator threads (per-cpu-vp,additional)
CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue (Kbytes)
CDR_NIFCOMPRESS 0 # Link level compression (- 1 never, 0 none, 9 max)
CDR_SERIAL 0 , 0 # Serial Column Sequence
CDR_DBSPACE # dbspace for syscdr database
CDR_QHDR_DBSPACE # CDR queue dbspace (default same as catalog)
CDR_QDATA_SBSPACE # List of CDR queue smart blob spaces
# CDR_MAX_DYNAMIC_LOGS
# - 1 => unlimited
# 0 => disable dynamic log addition
# > 0 => limit the no. of dynamic log additions with the specified value.
# Max dynamic log requests that CDR can make within one server session.
CDR_MAX_DYNAMIC_LOGS 0 # Dynamic log addition disabled by default
# Backup/Restore variables
BAR_ACT_LOG /usr/informix/bar_act.log # ON-Bar Log file - not in /tmp please
BAR_DEBUG_LOG /usr/informix/bar_dbug.log
# ON-Bar Debug Log - not in /tmp please
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_NB_XPORT_COUNT 20
BAR_XFER_BUF_SIZE 31
RESTARTABLE_RESTORE on
BAR_PROGRESS_FREQ 0
# Informix Storage Manager variables
ISM_DATA_POOL ISMData
ISM_LOG_POOL ISMLogs
# Read Ahead Variables
RA_PAGES # Number of pages to attempt to read ahead
RA_THRESHOLD # Number of pages left before next group
# DBSPACETEMP:
# OnLine equivalent of DBTEMP for SE. This is the list of dbspaces
# that the OnLine SQL Engine will use to create temp tables etc.
# If specified it must be a colon separated list of dbspaces that exist
# when the OnLine system is brought online. If not specified, or if
# all dbspaces specified are invalid, various ad hoc queries will create
# temporary files in /tmp instead.
DBSPACETEMP tempdbs1 # Default temp dbspaces
# DUMP*:
# The following parameters control the type of diagnostics information which
# is preserved when an unanticipated error condition (assertion failure) occurs
# during OnLine operations.
# For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.
DUMPDIR /tmp # Preserve diagnostics in this directory
DUMPSHMEM 0 # Dump a copy of shared memory
DUMPGCORE 0 # Dump a core image using 'gcore'
DUMPCORE 0 # Dump a core image (Warning:this aborts OnLine)
DUMPCNT 1 # Number of shared memory or gcore dumps for
# a single user's session
FILLFACTOR 90 # Fill factor for building indexes
# method for OnLine to use when determining current time
USEOSTIME 0 # 0 : use internal time(fast), 1 : get time from OS(slow)
# Parallel Database Queries (pdq)
MAX_PDQPRIORITY 100 # Maximum allowed pdqpriority
DS_MAX_QUERIES # Maximum number of decision support queries
DS_TOTAL_MEMORY # Decision support memory (Kbytes)
DS_MAX_SCANS 1048576 # Maximum number of decision support scans
DS_NONPDQ_QUERY_MEM 128 # Non PDQ query memory (Kbytes)
DATASKIP off # List of dbspaces to skip
# SDS Configuration Items
SDS_ENABLE 0 # SDS Activation 0 - no, 1 - yes
# Set this value in a SDS node after setting up the
# SDS primary.
# Warning: Always verify ROOTPATH before performing
# disk initialization (oninit -i/-iy) to
# avoid disk corruption of another instance
SDS_TIMEOUT 20 # Time Delay that Primary will wait for any ACK
# while perform page flushing before making
# SDS Server as down
# <dbspace Name>,<path>,<pagesize>,<offset>,<size> ...
SDS_PAGING # Paging File Location
# <paging File 1 path>,<paging File 2 path>
# OPTCOMPIND
# 0 => Nested loop joins will be preferred (where
# possible) over sortmerge joins and hash joins.
# 1 => If the transaction isolation mode is not
# "repeatable read", optimizer behaves as in ( 2 )
# below. Otherwise it behaves as in ( 0 ) above.
# 2 => Use costs regardless of the transaction isolation
# mode. Nested loop joins are not necessarily
# preferred. Optimizer bases its decision purely
# on costs.
OPTCOMPIND 2 # To hint the optimizer
DIRECTIVES 1 # Optimizer DIRECTIVES ON ( 1 /Default) or OFF ( 0 )
ONDBSPACEDOWN 2 # Dbspace down option: 0 = CONTINUE, 1 = ABORT, 2 = WAIT
OPCACHEMAX 0 # Maximum optical cache size (Kbytes)
# HETERO_COMMIT (Gateway participation in distributed transactions)
# 1 => Heterogeneous Commit is enabled
# 0 (or any other value) => Heterogeneous Commit is disabled
HETERO_COMMIT 0
SBSPACENAME # Default smartblob space name - this is where blobs
# go if no sbspace is specified when the smartblob is
# created. It is also used by some datablades as
# the location to put their smartblobs.
SYSSBSPACENAME # Default smartblob space for use by the Informix
# Server. This is used primarily for Informix Server
# system statistics collection.
BLOCKTIMEOUT 3600 # Default timeout for system block
SYSALARMPROGRAM /usr/informix/etc/evidence.sh # System Alarm program path
# Optimization goal: - 1 = ALL_ROWS(Default), 0 = FIRST_ROWS
OPT_GOAL - 1
ALLOW_NEWLINE 0 # embedded newlines(Yes = 1 , No = 0 or anything but 1 )
#Create Index Online Shared Memory usage limitation
ONLIDX_MAXMEM 5120 # Per pool per index (Kbytes)
#Timeout for client connection request
LISTEN_TIMEOUT 10 # Timeout (in Seconds)
#Following are the deprecated configuration parameters, instead of these
#use BUFFERPOOL configuration parameter
#BUFFERS, LRUS, LRU_MIN_DIRTY, LRU_MAX_DIRTY
IFX_FOLDVIEW 0 # fold multiple tables or union all view with ansi joins
EXPLAIN_STAT 0 # Enable Query Statistics in EXPLAIN file.
RTO_SERVER_RESTART 0 # Recovery Time Objective for IDS restart after
# a server crash; specified in seconds
# 0 =OFF, ( 60 - 1800 )
RAS_PLOG_SPEED 13888 # IDS RAS param; do not change; auto updated
RAS_LLOG_SPEED 513 # IDS RAS param; do not change; auto updated
AUTO_CKPTS 1 # Monitor critical resources and trigger
# checkpoints more frequently if there is a
# chance txn blocking might occur
AUTO_LRU_TUNING 1 # If unable to find low priority buffer for
# page fault, increase LRU flushing
AUTO_AIOVPS 1 # When using cooked file chunks, if AIO VPs
# too busy, increase number of flushers and
# AIO VPs
AUTO_REPREPARE 1 # Automatically re-optimize stored procedures and
# re-prepare prepared statements when tables
# referenced directly and indirectly by them change
# thereby minimizing the occurence of - 710 error
# Last Committed Isolation usage as default
# None: Dont use LC as default
# Committed Read: Use LC as default for Committed Read isolation level
# Dirty Read: Use LC as default for Dirty Read isolation level
# All: Use LC as default for Committed Read and Dirty Read isolation levels
USELASTCOMMITTED NONE
DIRECT_IO 0 # Use direct I/O for chunks (Yes = 1 , No = 0 )
MAX_FILL_DATA_PAGES 0 # Fill data pages maximally (Yes = 1 , No = 0 )
#
# The following are default settings for enabling Java in the database.
# Replace all occurrences of /usr/informix with the value of $INFORMIXDIR.
#VPCLASS jvp,num= 1 # Number of JVPs to start with
JVPJAVAHOME /usr/informix/extend/krakatoa/jre
# JRE installation root directory
JVPHOME /usr/informix/extend/krakatoa # Krakatoa installation directory
JVPPROPFILE /usr/informix/extend/krakatoa/.jvpprops # JVP property file
JVPLOGFILE /usr/informix/jvp.log # JVP log file.
JDKVERSION 1 . 3 # JDK version supported by this server
# The path to the JRE libraries relative to JVPJAVAHOME
JVPJAVALIB /bin
# The JRE libraries to use for the Java VM
JVPJAVAVM jsig:hpi:jvm:java:net:zip:jpeg
# use JVPARGS to change Java VM configuration
#To display jni call
#JVPARGS -verbose:jni
# Classpath to use upon Java VM start-up (use _g version for debugging)
#JVPCLASSPATH /usr/informix/extend/krakatoa/krakatoa_g.jar:/usr/informix/extend/krakatoa/jdbc_g.jar
JVPCLASSPATH /usr/informix/extend/krakatoa/krakatoa.jar:/usr/informix/extend/krakatoa/jdbc.jar
# The following parameters are related to the buffer pool
BUFFERPOOL size=2K,buffers= 5000 ,lrus= 8 ,lru_min_dirty= 50 . 000000 ,lru_max_dirty= 60 . 000000
Все это начало происходить после следующего сообщения в логе
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
08 : 21 : 16 Logical Log 17532 Complete, timestamp: 0xa69ae82a.
08 : 21 : 18 Logical Log 17532 - Backup Started
08 : 21 : 18 Adjusting LRU for bufferpool - id 0 size 2k
08 : 21 : 18 Old max 60 . 0 min 50 . 0 New max 59 . 4 min 49 . 5
08 : 21 : 19 Logical Log 17532 - Backup Completed
08 : 21 : 19 Performance Advisory: Logical log file size might be too small for a
checkpoint to complete.
08 : 21 : 19 Results: The size of individual logical log files is too small for
the current workload, resulting in each log file filling very
quickly. If log files fill in less than 30 seconds, the checkpoint
might remain blocked because the last log file fills during the time
needed to perform the checkpoint.
08 : 21 : 19 Action: Increase the size of the individual logical log files so
that it takes at least 30 seconds to fill each one. Look at the
online log to determine how quickly the log files are filling, and
then increase the size of the files proportionately.
08 : 21 : 19 Logical Log 17533 - Backup Started
08 : 21 : 20 Logical Log 17533 Complete, timestamp: 0xa69c37b6.
08 : 21 : 22 Logical Log 17533 - Backup Completed
08 : 21 : 24 Logical Log 17534 Complete, timestamp: 0xa69cd5ba.
08 : 21 : 26 Logical Log 17535 Complete, timestamp: 0xa69d64ba.
08 : 21 : 28 Logical Log 17536 Complete, timestamp: 0xa69e0689.
08 : 21 : 32 Logical Log 17537 Complete, timestamp: 0xa69f03e0.
08 : 21 : 33 WARNING: Buffer pool size is too small for read ahead operation
08 : 21 : 34 Logical Log 17538 Complete, timestamp: 0xa69f7e06.
08 : 21 : 37 Logical Log 17539 Complete, timestamp: 0xa6a038e2.
08 : 21 : 39 Logical Log 17540 Complete, timestamp: 0xa6a0c9f8.
08 : 21 : 41 Logical Log 17541 Complete, timestamp: 0xa6a15aef.
08 : 21 : 44 Logical Log 17542 Complete, timestamp: 0xa6a21bc7.
08 : 21 : 47 Logical Log 17543 Complete, timestamp: 0xa6a2da36.
08 : 21 : 49 Logical Log 17544 Complete, timestamp: 0xa6a35771.
08 : 21 : 52 Logical Log 17545 Complete, timestamp: 0xa6a43912.
08 : 21 : 54 Logical Log 17546 Complete, timestamp: 0xa6a4d55e.
08 : 21 : 56 Logical Log 17547 Complete, timestamp: 0xa6a557c1.
08 : 21 : 58 Logical Log 17548 Complete, timestamp: 0xa6a5f473.
08 : 22 : 02 Logical Log 17549 Complete, timestamp: 0xa6a6c255.
08 : 22 : 04 Logical Log 17550 Complete, timestamp: 0xa6a75c4b.
Подскажите из за чего такое может быть ? |
|
|
