Chinaunix

标题: 请教初始化库的一些问题，谢谢 [打印本页]

作者: 突破瓶颈 时间: 2008-07-25 11:09
标题: 请教初始化库的一些问题，谢谢
现状：1、在solaris上基于文件系统新装了一个informix数据库，库可以起起来 on_line 模式（自己测试学习用的）
   2、我需要逻辑日志已经物理日子从rootdbs中移出来，把系统从on_line模式转换到Quiescent模式，然后利用onspaces分配了一个逻辑日的dbspace以及大小
问题：然后在用onspaces命令时长时间没反应，用onmode -ky也没反应。onmode -m也没反应。不知到哪里出问题了。自己也是刚学功底太薄，请xdjm多多帮忙谢谢！
onstat -

Informix Dynamic Server 2000 Version 9.21.UC5    -- Quiescent -- Up 1 days 18:32:04 -- 19456 Kbytes

onstat -m

Informix Dynamic Server 2000 Version 9.21.UC5    -- Quiescent -- Up 1 days 18:32:37 -- 19456 Kbytes

Message Log File: /opt/informix/online.log.npm
18:12:22  Checkpoint Completed:  duration was 0 seconds.
18:12:22  Checkpoint loguniq 4, logpos 0x12a2a8

18:12:22  Space 'llogdbs' added.
11:55:12  Informix Dynamic Server 2000 Started.
11:55:12  shmget: [EEXIST][17]: key 52ba4801: shared memory already exists
11:55:12  mt_shm_init: can't create resident segment

16:59:52  Informix Dynamic Server 2000 Started.
16:59:52  shmget: [EEXIST][17]: key 52ba4801: shared memory already exists
16:59:52  mt_shm_init: can't create resident segment

17:03:54  Informix Dynamic Server 2000 Started.
17:03:54  shmget: [EEXIST][17]: key 52ba4801: shared memory already exists
17:03:54  mt_shm_init: can't create resident segment

10:41:12  Informix Dynamic Server 2000 Started.
10:41:12  shmget: [EEXIST][17]: key 52ba4801: shared memory already exists
10:41:12  mt_shm_init: can't create resident segment
onconfig：配置

opt/informix/etc> more onconfig.xxx
#**************************************************************************
#
#                         INFORMIX SOFTWARE, INC.
#
#  Title:    onconfig.std
#  Description: Informix Dynamic Server 2000 Configuration Parameters
#
#**************************************************************************

# Root Dbspace Configuration

ROOTNAME       rootdbs       # Root dbspace name
ROOTPATH       /opt/informix/test/rootchunk # Path for device containing root dbspace
ROOTOFFSET    0             # Offset of root dbspace into device (Kbytes)
ROOTSIZE       30000          # 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       rootdbs       # Location (dbspace) of physical log
PHYSFILE       30000          # Physical log file size (Kbytes)

# Logical Log Configuration

LOGFILES       6             # Number of logical log files
LOGSIZE       1500          # Logical log size (Kbytes)

# Diagnostics

MSGPATH       /opt/informix/online.log.xxx # System message log file path
CONSOLE       /dev/console # System console message path
ALARMPROGRAM /opt/informix/etc/log_full.sh
TBLSPACE_STATS  1             # Maintain tblspace statistics
# System Archive Tape Device

TAPEDEV       /dev/tapedev # Tape device path
TAPEBLK       16             # Tape block size (Kbytes)
TAPESIZE       10240          # Maximum amount of data to put on tape (Kbytes)

# Log Archive Tape Device

#LTAPEDEV    /dev/tapedev # Log tape device path
#LTAPEBLK    16             # Log tape block size (Kbytes)
#LTAPESIZE    10240          # Max amount of data to put on log tape (Kbytes)

# Optical

STAGEBLOB                      # Informix Dynamic Server 2000 staging area

# System Configuration
SERVERNUM    100             # Unique id corresponding to a OnLine instance
DBSERVERNAME back                   # Name of default database server
DBSERVERALIASES back1                   # List of alternate dbservernames
NETTYPE       ipcshm,1,100,CPU
NETTYPE       tlitcp,1,100,NET
DEADLOCK_TIMEOUT       60    # Max time to wait of lock in distributed env.
RESIDENT       0             # Forced residency flag (Yes = 1, No = 0)

MULTIPROCESSOR  1             # 0 for single-processor, 1 for multi-processor
NUMCPUVPS    3             # 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          2000          # Maximum number of locks
BUFFERS       1000          # Maximum number of shared buffers
NUMAIOVPS    2                      # Number of IO vps
PHYSBUFF       32             # Physical log buffer size (Kbytes)
LOGBUFF       32             # Logical log buffer size (Kbytes)
LOGSMAX       6             # Maximum number of logical log files
CLEANERS       1             # Number of buffer cleaner processes
SHMBASE       0x0A000000L    # Shared memory base address
SHMVIRTSIZE    8000          # initial virtual shared memory segment size
SHMADD       8192          # Size of new shared memory segments (Kbytes)
SHMTOTAL       0             # Total shared memory (Kbytes). 0=>unlimited
CKPTINTVL    300          # Check point interval (in sec)
LRUS          64             # Number of LRU queues
LRU_MAX_DIRTY 5             # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 2             # LRU percent dirty end cleaning limit
LTXHWM       70             # Long transaction high water mark percentage
LTXEHWM       80             # Long transaction high water mark (exclusive)
STACKSIZE    128          # Stack size (Kbytes)
DYNAMIC_LOGS 2

# 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
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

# 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_LOGDELTA 30    # % of log space allowed in queue memory
CDR_NUMCONNECT  16    # Expected connections per server
CDR_NIFRETRY 300    # Connection retry (seconds)
CDR_NIFCOMPRESS 0    # Link level compression (-1 never, 0 none, 9 max)

# Backup/Restore variables
BAR_ACT_LOG /opt/informix/npm_bar_act.log  # ON-Bar Log file - not in /tmp please
BAR_DEBUG_LOG /opt/informix/bar_dbug.log # ON-Bar Debug Log - not in /tmp please
BAR_MAX_BACKUP  0
BAR_RETRY    1
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 31
RESTARTABLE_RESTORE    ON
BAR_PROGRESS_FREQ    0
BAR_BSALIB_PATH       /opt/informix/lib/ibsad001.so
# 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 opt/informix/test/tmpchunk                      # 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    1             # 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
DATASKIP             # List of dbspaces to skip

# 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
LBU_PRESERVE 0    # Preserve last log for log backup
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)

#
# 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    /opt/informix/extend/krakatoa/jre/    # JRE installation root directory
JVPHOME       /opt/informix/extend/krakatoa # Krakatoa installation directory

JVPPROPFILE    /opt/informix/extend/krakatoa/.jvpprops # JVP property file
JVPLOGFILE    /opt/informix/jvp.log # JVP log file.

JDKVERSION 1.2             # JDK version supported by this server
JVMTHREAD    native          # Java VM thread type (green or native)

# The path to the JRE libraries relative to JVPJAVAHOME
JVPJAVALIB /lib/sparc/

# The JRE libraries to use for the Java VM

JVPJAVAVM    hpi:jvm:java:net:math:zip:jpeg

# Classpath to use upon Java VM start-up (use _g version for debugging)

# JVPCLASSPATH  /usr/informix/extend/krakatoa/krakatoa.jar:/usr/informix/extend/krakatoa/jdbc.jar
JVPCLASSPATH  /usr/informix/extend/krakatoa/krakatoa_g.jar:/usr/informix/extend/krakatoa/jdbc_g.jar

[ 本帖最后由突破瓶颈于 2008-7-25 11:10 编辑 ]

作者: liaosnet 时间: 2008-07-25 12:11
ps -ef | grep oninit
kill掉PPID为1的PID~~~

作者: liaosnet 时间: 2008-07-25 12:11
如果还不行~~~
ipcs
然后ipcrm 删掉informix在用的内存~~

作者: liaosnet 时间: 2008-07-25 12:12
如果还不行~~偶最后教你个绝的~~~

reboot your system!!

作者: 突破瓶颈 时间: 2008-07-25 13:12
呵呵 o(∩_∩)o... 大师谢谢了，我用ipcrm删掉了共享内存，然后有初始化就好了，过程中还有许多不太明白，反正现在问题解决了。
不过新问题又出来了哈哈问题如下：
1、要把逻辑日子从rootdbs中移出，是不是先删掉rootdbs中的逻辑日志，软后再在新建的llogdbs上指定逻辑日志？
重新建立逻辑日志的时候，逻辑日志最少是3个我是不是要分别建立3次
2、我想把数据库的ontape -s 0 备份到本地硬盘比如/opt/test 下面这样我需要怎么做。

请大师帮忙呀

作者: liaosnet 时间: 2008-07-25 13:16

原帖由 突破瓶颈 于 2008-7-25 13:12 发表
呵呵 o(∩_∩)o... 大师谢谢了，我用ipcrm删掉了共享内存，然后有初始化就好了，过程中还有许多不太明白，反正现在问题解决了。
不过新问题又出来了哈哈问题如下：
1、要把逻辑日子从rootdbs中移出，是不 ...

1,移逻辑日志的话,自己先在逻辑日志dbs上建几个新的逻辑日志~~然后移日志,做checkpoint,然后就可以删除在rootdbs上的逻辑日志...
相关操作onparms -a ;onmode -l ;onmode -c ;onparmas d ;ontape -s -L 0
2,备份到文件上~~~修改$ONCONFIG文件里的TAPEDEV~~~修改/opt/test 这个文件的属性为informix:informix 660..

作者: 突破瓶颈 时间: 2008-07-25 13:50
标题: 回复 #6 liaosnet 的帖子
大师 “~~然后移日志” 移日志怎么移

作者: 突破瓶颈 时间: 2008-07-25 13:56
标题: 回复 #6 liaosnet 的帖子
大师好意思困惑还有好多

我想让备份做到 /opt/informix/test/informixbak 下 informixbak是我建的一个文件夹而且 “文件的属性为informix:informix 660”这些都做了
但运行 ontape -s -L 0  时还是报下面的信息：
opt/informix/test> ;ontape -s -L 0

Please mount tape 1 on /opt/informix/test/informixbak and press Return to continue ...
could not write archive tape.
Please mount tape 1 on /opt/informix/test/informixbak and press Return to continue ...
could not write archive tape.

onconfig里面我已经改过来了如下：
# System Archive Tape Device

TAPEDEV       /opt/informix/test/informixbak # Tape device path
TAPEBLK       16             # Tape block size (Kbytes)
TAPESIZE       10240          # Maximum amount of data to put on tape (Kbytes)

请大师赐教

作者: qdice007 时间: 2008-07-25 14:09

原帖由 突破瓶颈 于 2008-7-25 13:56 发表
大师好意思困惑还有好多

我想让备份做到 /opt/informix/test/informixbak 下 informixbak是我建的一个文件夹而且 “文件的属性为informix:informix 660”这些都做了
但运行 ontape -s -L 0 时还是报下面 ...

"informixbak是我建的一个文件夹"，确定是文件夹还是文件？应该是一个文件。

作者: liaosnet 时间: 2008-07-25 14:11

原帖由 突破瓶颈 于 2008-7-25 13:50 发表
大师 “~~然后移日志” 移日志怎么移

所谓移日志就是先在逻辑日志上新建日志,然后删除在rootdbs上的那几个....就是
onparams -a ;onparams -d;这两个操作~~

作者: liaosnet 时间: 2008-07-25 14:12

原帖由 突破瓶颈 于 2008-7-25 13:56 发表
大师好意思困惑还有好多

我想让备份做到 /opt/informix/test/informixbak 下 informixbak是我建的一个文件夹而且 “文件的属性为informix:informix 660”这些都做了
但运行 ontape -s -L 0 时还是报下面 ...

informixbak 不是文件夹,而是文件...

作者: 突破瓶颈 时间: 2008-07-25 14:24
标题: 回复 #10 liaosnet 的帖子
谢谢大师! 已经可以进行了呵呵又有新问题了
我把rootdbs中初始化的3个逻辑日志删掉然后自己用重新建立了3个逻辑日志。
address  number flags uniqid begin       size    used %used
a07ce80  1       F------  0       500035    5000       0    0.00
a07ce9c  2       F------  0       5013bd    5000       0    0.00
a07cef0  5       U---C-L  5       102047       750       9    1.20
a07cf0c  6       F------  0       502745    5000       0    0.00
这里面的size为5000的是我新建的原来rootdbs中的3个逻辑日志已经删掉了2个剩下的这个flags的状态好像时当前正在用的它不让删除。是不是等它用满之后才让删除呀？

作者: liaosnet 时间: 2008-07-25 15:11
不能少于3个逻辑日志~~~~~~

作者: 突破瓶颈 时间: 2008-07-28 10:17
标题: 回复 #13 liaosnet 的帖子
aaaa1-/opt/informix> onstat -l

Informix Dynamic Server 2000 Version 9.21.UC5    -- Quiescent -- Up 2 days 20:54:43 -- 19456 Kbytes

Physical Logging
Buffer bufused  bufsize  numpages numwrits pages/io
  P-1  0       16    24    15    1.60
   phybegin physize  phypos phyused  %used
   200035 4500    24    0       0.00

Logical Logging
Buffer bufused  bufsize  numrecs  numpages numwrits recs/pages pages/io
  L-1  0       16    113    30    30    3.8       1.0
      Subsystem numrecs  Log Space used
      OLDRSAM    113    7612

address  number flags uniqid begin       size    used %used
a07ce80  1       F------  0       500035    5000       0    0.00
a07ce9c  2       F------  0       5013bd    5000       0    0.00
a07ceb8  3       F------  0       503acd    2500       0    0.00
a07cef0  5       U---C-L  5       102047       750    16    2.13
a07cf0c  6       F------  0       502745    5000       0    0.00

aaaa1-/opt/informix> onparams -d -l 5
WARNING: Dropping a logical log file.
Do you really want to continue? (y/n)y
Can only drop an unused logical log.

我又加了一个逻辑日志可是现在 rootdbs中的那个逻辑日志还是删不掉呀？不知是什么原因，是不是因为

rootdbs中的那个逻辑日志是当前正在使用的，就没有办法删除了么？？

[ 本帖最后由突破瓶颈于 2008-7-28 10:19 编辑 ]

作者: liaosnet 时间: 2008-07-28 11:30
做次逻辑日志备份先~~

欢迎光临 Chinaunix (http://bbs.chinaunix.net/)