In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-19 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
Under aix, migrating all sybase libraries from one storage to another, or from one vg to another vg, or moving all sybase libraries to a new location can be achieved by copying the relevant lv under aix. Due to the hardware of the company's ibm minicomputer, give a simple example of migrating sybase devices from rootvg to datavg. The process is as follows:
I. basic information
1 the current equipment of the database is as follows
Name phyname
-
Master / dev/rlv_master
Sysprocsdev / dev/rlv_proc
2 lv information of rootvg
# lsvg-l rootvg
Rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
Hd5 boot 1 1 1 closed/syncd N/A
Hd6 paging 64 64 1 open/syncd N/A
Hd8 jfs2log 1 1 1 open/syncd N/A
Hd4 jfs2 48 48 1 open/syncd /
Hd2 jfs2 64 64 1 open/syncd / usr
Hd9var jfs2 48 48 1 open/syncd / var
Hd3 jfs2 48 48 1 open/syncd / tmp
Hd1 jfs2 1 1 1 open/syncd / home
Hd10opt jfs2 48 48 1 open/syncd / opt
Lg_dumplv sysdump 16 16 1 open/syncd N/A
Lv_master raw 5 5 1 open/syncd N/A
Lv_proc raw 5 5 1 open/syncd N/A
Lv_data1 raw 16 16 1 closed/syncd N/A
3. The contents of the sybase RUN_CRM file are as follows
$cat RUN_CRM
#! / bin/sh
#
# Adaptive Server name: CRM
# ASE page size (KB): 2k
# Master device path: / dev/rlv_master
# Error log path: / sybase/ASE-12_5/install/CRM.log
# Configuration file path: / sybase/ASE-12_5/CRM.cfg
# Directory for shared memory files: / sybase/ASE-12_5
#
/ sybase/ASE-12_5/bin/dataserver\
-sCRM\
-d/dev/rlv_master\
-e/sybase/ASE-12_5/install/CRM.log\
-c/sybase/ASE-12_5/CRM.cfg\
-M/sybase/ASE-12_5\
4. The contents of the API file for sybase are as follows:
# cat interfaces
CRM
Master tcp ether 192.168.85.9 5000
Query tcp ether 192.168.85.9 5000
CRM_back
Master tcp ether 192.168.85.9 5001
Query tcp ether 192.168.85.9 5001
2. Copy all the relevant lv of sybase. In this example, sybase has only two lv of lv_master lv_proc (note that because it is a simple simulation experiment, there are only two lv of sybase)
1 the copy process is as follows:
The cplv command is explained as follows:
-y New lv name
-v destination volume group name
# cplv-y newlv_master-v datavg lv_master
Cplv: Logical volume lv_master successfully copied to newlv_master.
# cplv-y newlv_proc-v datavg lv_proc
Cplv: Logical volume lv_proc successfully copied to newlv_proc.
2 the lv information of datavg after copying lv is as follows:
# lsvg-l datavg
Datavg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
Lv_backup jfs2 320 320 1 open/syncd / backup
Loglv00 jfs2log 1 1 1 open/syncd N/A
Newlv_master raw 10 10 1 closed/syncd N/A
Newlv_proc raw 10 10 1 closed/syncd N/A
Change the name of lv
1 change the name of sybaselv on the original rootvg
The chlv command parameters are explained as follows:
-n is the new lv name
# chlv-n oldlv_master lv_master
# chlv-n oldlv_proc lv_proc
2 change the name of lv on datavg (from newlv_master-- > lv_master | newlv_proc-- > lv_proc)
# chlv-n lv_master newlv_master
# chlv-n lv_proc newlv_proc
IV. The test results after starting the service are as follows
1 start the main service and backup service
$startserver-f RUN_CRM
$startserver-f RUN_CRM_back
2 Verification
You can see below that the sybase master / slave service has been started successfully
$showserver
USER PID CPU MEM SZ RSS TTY STAT STIME TIME COMMAND
Sybase 319558 2.0 25564 17188 pts/1 A 11:42:25 0:03 / sybase/ASE-12_5/bin/dataserver-sCRM-d/dev/rlv_master-e/sybase/ASE-12_5/install/CRM.log-c/sybase/ASE-12_5/CRM.cfg-M/sybase/ASE-12_5
Sybase 286878 0.01.0 7016 7440 pts/1 A 11:43:14 0:00 / sybase/ASE-12_5/bin/backupserver-SCRM_back-e/sybase/ASE-12_5/install/CRM_back.log-Ldefault-Jcp850-N25-C20-M/sybase/ASE-12_5/bin/sybmultbuf
Verify whether the master library can be backed up, as follows:
$isql-Usa-P-SCRM
1 > dump database master to'/ backup/master2.dat'
2 > go
WARNING: In order to LOAD the master database, the SQL Server must run in
Single-user mode. If the master database dump uses multiple volumes, you must
Execute sp_volchanged on another SQL Server at LOAD time in order to signal
Volume changes.
Backup Server session id is: 5. Use this value when executing the
'sp_volchanged' system stored procedure after fulfilling any volume change
Request from the Backup Server.
Backup Server: 4.41.1.1: Creating new disk file / backup/master2.dat.
Backup Server: 6.28.1.1: Dumpfile name 'master132960A524' section number 1
Mounted on disk file'/ backup/master2.dat'
Backup Server: 4.58.1.1: Database master: 4546 kilobytes DUMPED.
Backup Server: 4.58.1.1: Database master: 4716 kilobytes DUMPED.
Backup Server: 4.58.1.1: Database master: 4888 kilobytes DUMPED.
Backup Server: 4.58.1.1: Database master: 5058 kilobytes DUMPED.
Backup Server: 4.58.1.1: Database master: 5230 kilobytes DUMPED.
Backup Server: 4.58.1.1: Database master: 5400 kilobytes DUMPED.
Backup Server: 4.58.1.1: Database master: 5572 kilobytes DUMPED.
Backup Server: 4.58.1.1: Database master: 5710 kilobytes DUMPED.
Backup Server: 3.43.1.1: Dump phase number 1 completed.
Backup Server: 3.43.1.1: Dump phase number 2 completed.
Backup Server: 3.43.1.1: Dump phase number 3 completed.
Backup Server: 4.58.1.1: Database master: 5718 kilobytes DUMPED.
Backup Server: 3.42.1.1: DUMP is complete (database master).
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 219
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.