Clifford Fernandez
asked on
SYBASE ASE 15.7 Cluster Edition on HP-UNIX raw-disk setup?
Hi Experts,
Please excuse the lenght of this mail. It contains many required details.
I am Installing a 3 node Sybase cluster on Sybase ASE Cluster Edition 15.7 SP122 on HP-UX B.11.31
I need help please, How do i configure and present the raw disks to Sybase?
* Although qrmutil says that the devices are fence capable.
eg: qrmutil --fence-capable=/dev/rdisk
Executing command 'test fence capability', argument '/dev/rdisk/disk39'...
Device '/dev/rdisk/disk39' is fence capable.
Command 'test fence capability', argument '/dev/rdisk/disk39' succeeded.
qrmutil execution completed.
* I am receiving the below msgs while trying to build the cluster through sybcluster
Would you like to check whether this device supports IO fencing capability (Y/N)? [ Y ] Y
Validating the device /dev/rdisk/disk90 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
Validating the device /dev/rdisk/disk107 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
Validating the device /dev/rdisk/disk183 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
* Raw-disk Configuration on each node:
Assigned the below permissions to each database and quorum disk.
(since this is a Test intall I am using the root id)
chown root disk174
chgrp root disk174
chmod 666 disk174
I am unable to set:( As per SAP® Adaptive Server® Enterprise Cluster Edition
Document Version: 15.7 SP130 (Installation Guide for HP-UX Page 80))
Permanent SYS_DEVICES privileges can be granted to the current user’s shell process. For example:
usermod -K defaultpriv=basic,sys_devi
*Sybcluster log:( Sybase only gets installed on one node, Then shuts down. Interface files get created on all nodes)
# sybcluster -U uafadmin -P Test123$ -F
Please help. Please let me know if any other details are required? i will post them.
Thank you.
Please excuse the lenght of this mail. It contains many required details.
I am Installing a 3 node Sybase cluster on Sybase ASE Cluster Edition 15.7 SP122 on HP-UX B.11.31
I need help please, How do i configure and present the raw disks to Sybase?
* Although qrmutil says that the devices are fence capable.
eg: qrmutil --fence-capable=/dev/rdisk
Executing command 'test fence capability', argument '/dev/rdisk/disk39'...
Device '/dev/rdisk/disk39' is fence capable.
Command 'test fence capability', argument '/dev/rdisk/disk39' succeeded.
qrmutil execution completed.
* I am receiving the below msgs while trying to build the cluster through sybcluster
Would you like to check whether this device supports IO fencing capability (Y/N)? [ Y ] Y
Validating the device /dev/rdisk/disk90 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
Validating the device /dev/rdisk/disk107 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
Validating the device /dev/rdisk/disk183 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
* Raw-disk Configuration on each node:
Assigned the below permissions to each database and quorum disk.
(since this is a Test intall I am using the root id)
chown root disk174
chgrp root disk174
chmod 666 disk174
I am unable to set:( As per SAP® Adaptive Server® Enterprise Cluster Edition
Document Version: 15.7 SP130 (Installation Guide for HP-UX Page 80))
Permanent SYS_DEVICES privileges can be granted to the current user’s shell process. For example:
usermod -K defaultpriv=basic,sys_devi
# usermod -K defaultpriv=basic,sys_devices root
Unrecognized Option 'K'
Usage: usermod [-F] [-p <encrypted-password>] [-u <uid> [-o]] [-g <group>] [-G <group>[,<group...>]] [-d <dir> [-m] [-i]] [-s <shell>] [-c <comment>] [-f <inactive>]
[-e <expire>] [-l <new logname>] [-P -S <alternate password file>] <login>
Node 1
hostname
testdb01.example.inDevice File Name Size [MB] Tgt Lun LUN WWN VV Name Code Rev Serial#
===============================================================================================================================================================
/dev/rdisk/disk39 1024 00 02 60002ac0000000002500072600003f84 Quorum 3.1.2 GA 1416260
/dev/rdisk/disk56 10240 00 07 60002ac0000000002500072700003f84 firstlstdevice 3.1.2 GA 1416260
/dev/rdisk/disk73 10240 01 0a 60002ac0000000002500072800003f84 secondlstdevice 3.1.2 GA 1416260
/dev/rdisk/disk90 2048 00 03 60002ac0000000002500072900003f84 master 3.1.2 GA 1416260
/dev/rdisk/disk107 2048 00 04 60002ac0000000002500072a00003f84 sysproc 3.1.2 GA 1416260
/dev/rdisk/disk124 2048 00 06 60002ac0000000002500073f00003f84 sysdb 3.1.2 GA 1416260
/dev/rdisk/disk141 1048576 01 08 60002ac0000000002500074000003f84 database_device 3.1.2 GA 1416260
/dev/rdisk/disk142 10240 00 01 60002ac000000000da000d5b00003f84 thirdlstdevice 3.1.2 GA 1416260
/dev/rdisk/disk183 2048 01 0b 60002ac0000000004800116e00003f84 systemdb 3.1.2 GA 1416260total 32
crw-r----- 1 bin sys 13 0x000005 Jan 24 2014 disk1_p2
crw-r----- 1 bin sys 13 0x000001 Jan 24 2014 disk1
crw-r----- 1 bin sys 13 0x000004 Jan 24 2014 disk1_p1
crw-r----- 1 bin sys 13 0x000006 Jan 24 2014 disk1_p3
crw-r----- 1 bin sys 13 0x000003 Jan 25 2014 disk3
crw-r----- 1 bin sys 13 0x000007 Jan 25 2014 disk3_p1
crw-r----- 1 bin sys 13 0x000008 Jan 25 2014 disk3_p2
crw-r----- 1 bin sys 13 0x000009 Jan 25 2014 disk3_p3
crw-r----- 1 bin sys 13 0x000021 Mar 19 2014 disk124
crw-rw-rw- 1 root root 13 0x000022 Mar 19 2014 disk141
crw-rw-rw- 1 root root 13 0x000024 Oct 22 14:17 disk175
drwxr-xr-x 2 bin bin 8192 Jan 17 16:07 .
dr-xr-xr-x 21 bin bin 8192 Jan 28 16:22 ..
crw-rw-rw- 1 root root 13 0x00001f Feb 10 12:25 disk90
crw-rw-rw- 1 root root 13 0x000020 Feb 10 12:26 disk107
crw-rw-rw- 1 root root 13 0x000025 Feb 10 12:26 disk183
crw-rw-rw- 1 root root 13 0x00001d Feb 10 12:27 disk56
crw-rw-rw- 1 root root 13 0x00001e Feb 10 12:27 disk73
crw-rw-rw- 1 root root 13 0x000023 Feb 10 12:27 disk142
crw-rw-rw- 1 root root 13 0x00001c Feb 10 12:28 disk39
Node 2
hostname
testdb02.example.inDevice File Name Size [MB] Tgt Lun LUN WWN VV Name Code Rev Serial#
===============================================================================================================================================================
/dev/rdisk/disk5 10240 00 00 60002ac000000000da000d5b00003f84 thirdlstdevice 3.1.2 GA 1416260
/dev/rdisk/disk62 1024 00 00 60002ac0000000002500072600003f84 Quorum 3.1.2 GA 1416260
/dev/rdisk/disk63 2048 00 00 60002ac0000000002500072900003f84 master 3.1.2 GA 1416260
/dev/rdisk/disk64 2048 00 00 60002ac0000000002500072a00003f84 sysproc 3.1.2 GA 1416260
/dev/rdisk/disk65 2048 00 00 60002ac0000000002500073f00003f84 sysdb 3.1.2 GA 1416260
/dev/rdisk/disk66 10240 00 00 60002ac0000000002500072700003f84 firstlstdevice 3.1.2 GA 1416260
/dev/rdisk/disk67 10240 01 00 60002ac0000000002500072800003f84 secondlstdevice 3.1.2 GA 1416260
/dev/rdisk/disk157 2048 01 00 60002ac0000000004800116e00003f84 systemdb 3.1.2 GA 1416260
/dev/rdisk/disk174 1048576 01 00 60002ac0000000002500074000003f84 database_device 3.1.2 GA 1416260total 32
crw-r----- 1 bin sys 13 0x000001 Jan 24 2014 disk1
crw-r----- 1 bin sys 13 0x000004 Jan 24 2014 disk1_p1
crw-r----- 1 bin sys 13 0x000005 Jan 24 2014 disk1_p2
crw-r----- 1 bin sys 13 0x000006 Jan 24 2014 disk1_p3
crw-r----- 1 bin sys 13 0x000003 Jan 25 2014 disk3
crw-r----- 1 bin sys 13 0x000007 Jan 25 2014 disk3_p1
crw-r----- 1 bin sys 13 0x000008 Jan 25 2014 disk3_p2
crw-r----- 1 bin sys 13 0x000009 Jan 25 2014 disk3_p3
crw-rw-rw- 1 root root 13 0x000014 Oct 22 14:02 disk63
crw-rw-rw- 1 root root 13 0x000018 Oct 22 14:02 disk67
crw-rw-rw- 1 root root 13 0x000012 Oct 22 14:02 disk5
crw-rw-rw- 1 root root 13 0x000013 Oct 22 14:02 disk62
crw-rw-rw- 1 root root 13 0x000017 Oct 22 14:02 disk66
crw-rw-rw- 1 root root 13 0x000015 Oct 22 14:02 disk64
crw-rw-rw- 1 root root 13 0x000016 Oct 22 14:02 disk65
crw-rw-rw- 1 root root 13 0x000019 Oct 22 14:16 disk76
crw-rw-rw- 1 root root 13 0x000022 Jan 17 16:07 disk157
dr-xr-xr-x 19 bin bin 8192 Jan 28 16:23 ..
drwxr-xr-x 2 bin bin 8192 Jan 30 12:48 .
crw-rw-rw- 1 root root 13 0x000023 Jan 30 12:48 disk174
Node 3
hostname
testdb03.example.inDevice File Name Size [MB] Tgt Lun LUN WWN VV Name Code Rev Serial#
===============================================================================================================================================================
/dev/rdisk/disk5 1024 00 02 60002ac0000000002500072600003f84 Quorum 3.1.2 GA 1416260
/dev/rdisk/disk15 10240 00 07 60002ac0000000002500072700003f84 firstlstdevice 3.1.2 GA 1416260
/dev/rdisk/disk20 10240 01 0a 60002ac0000000002500072800003f84 secondlstdevice 3.1.2 GA 1416260
/dev/rdisk/disk25 2048 00 03 60002ac0000000002500072900003f84 master 3.1.2 GA 1416260
/dev/rdisk/disk30 2048 00 04 60002ac0000000002500072a00003f84 sysproc 3.1.2 GA 1416260
/dev/rdisk/disk35 2048 00 06 60002ac0000000002500073f00003f84 sysdb 3.1.2 GA 1416260
/dev/rdisk/disk40 1048576 01 08 60002ac0000000002500074000003f84 database_device 3.1.2 GA 1416260
/dev/rdisk/disk49 10240 00 01 60002ac000000000da000d5b00003f84 thirdlstdevice 3.1.2 GA 1416260
/dev/rdisk/disk55 2048 01 0b 60002ac0000000004800116e00003f84 systemdb 3.1.2 GA 1416260total 949520
crw-r----- 1 bin sys 13 0x000006 Jan 24 2014 disk1_p3
crw-r----- 1 bin sys 13 0x000001 Jan 24 2014 disk1
crw-r----- 1 bin sys 13 0x000004 Jan 24 2014 disk1_p1
crw-r----- 1 bin sys 13 0x000005 Jan 24 2014 disk1_p2
crw-r----- 1 bin sys 13 0x000003 Jan 25 2014 disk3
crw-r----- 1 bin sys 13 0x000007 Jan 25 2014 disk3_p1
crw-r----- 1 bin sys 13 0x000008 Jan 25 2014 disk3_p2
crw-r----- 1 bin sys 13 0x000009 Jan 25 2014 disk3_p3
crw-r----- 1 bin sys 13 0x00000b Jan 25 2014 disk6
crw-r----- 1 bin sys 13 0x00000c Jan 25 2014 disk6_p1
crw-r----- 1 bin sys 13 0x00000e Jan 25 2014 disk6_p3
crw-r----- 1 bin sys 13 0x00000d Jan 25 2014 disk6_p2
crw-rw-rw- 1 root root 13 0x000012 Mar 19 2014 disk5
crw-rw-rw- 1 root root 13 0x000013 Mar 19 2014 disk15
crw-rw-rw- 1 root root 13 0x000014 Mar 19 2014 disk20
crw-rw-rw- 1 root root 13 0x000015 Mar 19 2014 disk25
crw-rw-rw- 1 root root 13 0x000016 Mar 19 2014 disk30
crw-rw-rw- 1 root root 13 0x000017 Mar 19 2014 disk35
crw-rw-rw- 1 root root 13 0x000018 Mar 19 2014 disk40
-rw-r----- 1 root sys 50331648 Mar 25 2014 disk124
-rw-r----- 1 root sys 251658240 Apr 24 2014 disk90
-rw-r----- 1 root sys 180355072 Apr 24 2014 disk107
-rw------- 1 root sys 3763712 Apr 24 2014 disk39
crw-rw-rw- 1 root root 13 0x000019 Oct 22 14:02 disk49
crw-rw-rw- 1 root root 13 0x00001a Oct 22 14:12 disk50
drwxr-xr-x 2 bin bin 8192 Jan 17 16:08 .
crw-rw-rw- 1 root root 13 0x00001b Jan 17 16:08 disk55
dr-xr-xr-x 19 bin bin 8192 Jan 28 16:24 ..
#
*SCC configuration:
Node 1
---- System Info ----
Agent Home: /databaseinstance/instance_01/SCC-3_2
Agent Version: SCC Framework Server 3.2.7.4837
Node: testdb01.example.in(10.0.16.37)
RMI Address: testdb01.example.in(10.0.16.37)
RMI Port: 9999
OS Name: HP-UX
OS Version: B.11.31
OS Architecture: ia64
Platform: hpita
Bitwidth: 64
Available Processors: 64
Total Physical Memory: 720717 MB
Free Physical Memory: 624678 MB
java.library.path: /databaseinstance/instance_01/SCC-3_2/rtlib:
Java Home: /databaseinstance/instance_01/shared/SAPJRE-7_1_011_64BIT
Java Version: 1.7.0_25
Java VM Version: 7.1.011 23.5-b02
VM Process ID 3283@testdb01.example.in
VM Arguments: -Xms128m, -XX:MaxPermSize=128m, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=/databaseinstance/instance_01/SCC-3_2/log, -
Dcom.sybase.home=/databaseinstance/instance_01, -Dcom.sybase.ua.toplevel=/databaseinstance/instance_01/SCC-3_2, -
Dcom.sybase.ua.home=/databaseinstance/instance_01/SCC-3_2, -Dcom.sybase.platform=hpita, -Djava.library.path=/databaseinstance/instance_01/SCC-3_2/rtlib:, -
Djava.security.policy=/databaseinstance/instance_01/SCC-3_2/conf/java.policy, -Djava.util.logging.manager=com.sybase.ua.util.logging.bridge.JavaToLog4jLogManager, -
Dcom.sybase.security.BootstrapConfigurationURL=file:////databaseinstance/instance_01/SCC-3_2/conf/csibootstrap.properties
Message level: WARN
scc-console> status
Agent Home: /databaseinstance/instance_01/SCC-3_2
Connection URL: service:jmx:rmi:///jndi/rmi://testdb01.example.in:9999/agent
Status: RUNNING
----- Services -----
Service Id Service Name Is Running
---------- ------------ ----------
Agent Agent Service true
BootstrapService BootstrapService true
ConfigService Configuration Service true
DeploymentService Deployment Service true
EnvironmentDiscoveryService Environment Service true
FileTransferService File Transfer Service true
PluginRegisterService Plugin Registration Service true
RMIService RMI Service true
RemoteShellService Remote Shell Service true
SecurityService Security Service true
SelfDiscoveryService Self Discovery Service true
ServiceRegistrationService Service Registration Service true
SessionService Session Service true
SnmpService SNMP Service true
SybaseHomeService Sybase Home Service true
TaskExecutionService TaskExecution Service true
TdsService TDS Service true
----- Plugins -----
Plugin ID Plugin Name Version Is Loaded
--------- ----------- ------- ---------
com.sybase.ase.cluster ASE Cluster Agent Plugin 15.0.1 true
com.sybase.ase.snmp ASE SNMP Agent Plugin 2.0.0 true
scc-console>
Node 2:
---- System Info ----
Agent Home: /databaseinstance/instance_02/SCC-3_2
Agent Version: SCC Framework Server 3.2.7.4837
Node: testdb02.example.in(10.0.16.38)
RMI Address: testdb02.example.in(10.0.16.38)
RMI Port: 9999
OS Name: HP-UX
OS Version: B.11.31
OS Architecture: ia64
Platform: hpita
Bitwidth: 64
Available Processors: 64
Total Physical Memory: 720717 MB
Free Physical Memory: 624316 MB
java.library.path: /databaseinstance/instance_02/SCC-3_2/rtlib:
Java Home: /databaseinstance/instance_02/shared/SAPJRE-7_1_011_64BIT
Java Version: 1.7.0_25
Java VM Version: 7.1.011 23.5-b02
VM Process ID 27348@testdb02.example.in
VM Arguments: -Xms128m, -XX:MaxPermSize=128m, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=/databaseinstance/instance_02/SCC-3_2/log, -
Dcom.sybase.home=/databaseinstance/instance_02, -Dcom.sybase.ua.toplevel=/databaseinstance/instance_02/SCC-3_2, -
Dcom.sybase.ua.home=/databaseinstance/instance_02/SCC-3_2, -Dcom.sybase.platform=hpita, -Djava.library.path=/databaseinstance/instance_02/SCC-3_2/rtlib:, -
Djava.security.policy=/databaseinstance/instance_02/SCC-3_2/conf/java.policy, -Djava.util.logging.manager=com.sybase.ua.util.logging.bridge.JavaToLog4jLogManager, -
Dcom.sybase.security.BootstrapConfigurationURL=file:////databaseinstance/instance_02/SCC-3_2/conf/csibootstrap.properties
Message level: WARN
scc-console> status
Agent Home: /databaseinstance/instance_02/SCC-3_2
Connection URL: service:jmx:rmi:///jndi/rmi://testdb02.example.in:9999/agent
Status: RUNNING
----- Services -----
Service Id Service Name Is Running
---------- ------------ ----------
Agent Agent Service true
BootstrapService BootstrapService true
ConfigService Configuration Service true
DeploymentService Deployment Service true
EnvironmentDiscoveryService Environment Service true
FileTransferService File Transfer Service true
PluginRegisterService Plugin Registration Service true
RMIService RMI Service true
RemoteShellService Remote Shell Service true
SecurityService Security Service true
SelfDiscoveryService Self Discovery Service true
ServiceRegistrationService Service Registration Service true
SessionService Session Service true
SnmpService SNMP Service true
SybaseHomeService Sybase Home Service true
TaskExecutionService TaskExecution Service true
TdsService TDS Service true
----- Plugins -----
Plugin ID Plugin Name Version Is Loaded
--------- ----------- ------- ---------
com.sybase.ase.cluster ASE Cluster Agent Plugin 15.0.1 true
com.sybase.ase.snmp ASE SNMP Agent Plugin 2.0.0 true
scc-console>
Node 3:
---- System Info ----
Agent Home: /databaseinstance/instance_03/SCC-3_2
Agent Version: SCC Framework Server 3.2.7.4837
Node: testdb03.example.in(10.0.16.39)
RMI Address: testdb03.example.in(10.0.16.39)
RMI Port: 9999
OS Name: HP-UX
OS Version: B.11.31
OS Architecture: ia64
Platform: hpita
Bitwidth: 64
Available Processors: 64
Total Physical Memory: 720717 MB
Free Physical Memory: 625309 MB
java.library.path: /databaseinstance/instance_03/SCC-3_2/rtlib:
Java Home: /databaseinstance/instance_03/shared/SAPJRE-7_1_011_64BIT
Java Version: 1.7.0_25
Java VM Version: 7.1.011 23.5-b02
VM Process ID 20486@testdb03.example.in
VM Arguments: -Xms128m, -XX:MaxPermSize=128m, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=/databaseinstance/instance_03/SCC-3_2/log, -
Dcom.sybase.home=/databaseinstance/instance_03, -Dcom.sybase.ua.toplevel=/databaseinstance/instance_03/SCC-3_2, -
Dcom.sybase.ua.home=/databaseinstance/instance_03/SCC-3_2, -Dcom.sybase.platform=hpita, -Djava.library.path=/databaseinstance/instance_03/SCC-3_2/rtlib:, -
Djava.security.policy=/databaseinstance/instance_03/SCC-3_2/conf/java.policy, -Djava.util.logging.manager=com.sybase.ua.util.logging.bridge.JavaToLog4jLogManager, -
Dcom.sybase.security.BootstrapConfigurationURL=file:////databaseinstance/instance_03/SCC-3_2/conf/csibootstrap.properties
Message level: WARN
scc-console> status
Agent Home: /databaseinstance/instance_03/SCC-3_2
Connection URL: service:jmx:rmi:///jndi/rmi://testdb03.example.in:9999/agent
Status: RUNNING
----- Services -----
Service Id Service Name Is Running
---------- ------------ ----------
Agent Agent Service true
BootstrapService BootstrapService true
ConfigService Configuration Service true
DeploymentService Deployment Service true
EnvironmentDiscoveryService Environment Service true
FileTransferService File Transfer Service true
PluginRegisterService Plugin Registration Service true
RMIService RMI Service true
RemoteShellService Remote Shell Service true
SecurityService Security Service true
SelfDiscoveryService Self Discovery Service true
ServiceRegistrationService Service Registration Service true
SessionService Session Service true
SnmpService SNMP Service true
SybaseHomeService Sybase Home Service true
TaskExecutionService TaskExecution Service true
TdsService TDS Service true
----- Plugins -----
Plugin ID Plugin Name Version Is Loaded
--------- ----------- ------- ---------
com.sybase.ase.cluster ASE Cluster Agent Plugin 15.0.1 true
com.sybase.ase.snmp ASE SNMP Agent Plugin 2.0.0 true*Sybcluster log:( Sybase only gets installed on one node, Then shuts down. Interface files get created on all nodes)
# sybcluster -U uafadmin -P Test123$ -F
"testdb01.example.in:9999,testdb02.example.in:9999,testdb03.example.in:9999"
> show agents
Verifying the supplied agent specifications...
Agent Information: service:jmx:rmi:///jndi/rmi://testdb01.example.in:9999/agent
-----------------------------------------------------
Node Name: testdb01.example.in
Agent Port: 9999
Agent Version: 3.2.7
Agent Build: 4837
OS Name: HP-UX
OS Version: B.11.31
OS Architecture: ia64
Agent Service Info:
Agent Service (Agent) Build: 4837 Status: running
BootstrapService (BootstrapService) Build: 4837 Status: running
Configuration Service (ConfigService) Build: 4837 Status: running
Deployment Service (DeploymentService) Build: 20 Status: running
Environment Service (EnvironmentDiscoveryService) Build: 4837 Status: running
File Transfer Service (FileTransferService) Build: 4837 Status: running
Plugin Registration Service (PluginRegisterService) Build: 4837 Status: running
RMI Service (RMIService) Build: 4837 Status: running
Remote Shell Service (RemoteShellService) Build: 4837 Status: running
Security Service (SecurityService) Build: 4837 Status: running
Self Discovery Service (SelfDiscoveryService) Build: 4837 Status: running
Service Registration Service (ServiceRegistrationService) Build: 4837 Status: running
Session Service (SessionService) Build: 4837 Status: running
SNMP Service (SnmpService) Build: 10 Status: running
Sybase Home Service (SybaseHomeService) Build: 14 Status: running
TaskExecution Service (TaskExecutionService) Build: 4837 Status: running
TDS Service (TdsService) Build: 10 Status: running
Agent Plugin Info:
ASE SNMP Agent Plugin (com.sybase.ase.snmp) Version: 2.0.0 Build: 8 Instance: 1 Status: running
Agent Information: service:jmx:rmi:///jndi/rmi://testdb02.example.in:9999/agent
-----------------------------------------------------
Node Name: testdb02.example.in
Agent Port: 9999
Agent Version: 3.2.7
Agent Build: 4837
OS Name: HP-UX
OS Version: B.11.31
OS Architecture: ia64
Agent Service Info:
Agent Service (Agent) Build: 4837 Status: running
BootstrapService (BootstrapService) Build: 4837 Status: running
Configuration Service (ConfigService) Build: 4837 Status: running
Deployment Service (DeploymentService) Build: 20 Status: running
Environment Service (EnvironmentDiscoveryService) Build: 4837 Status: running
File Transfer Service (FileTransferService) Build: 4837 Status: running
Plugin Registration Service (PluginRegisterService) Build: 4837 Status: running
RMI Service (RMIService) Build: 4837 Status: running
Remote Shell Service (RemoteShellService) Build: 4837 Status: running
Security Service (SecurityService) Build: 4837 Status: running
Self Discovery Service (SelfDiscoveryService) Build: 4837 Status: running
Service Registration Service (ServiceRegistrationService) Build: 4837 Status: running
Session Service (SessionService) Build: 4837 Status: running
SNMP Service (SnmpService) Build: 10 Status: running
Sybase Home Service (SybaseHomeService) Build: 14 Status: running
TaskExecution Service (TaskExecutionService) Build: 4837 Status: running
TDS Service (TdsService) Build: 10 Status: running
Agent Plugin Info:
ASE SNMP Agent Plugin (com.sybase.ase.snmp) Version: 2.0.0 Build: 8 Instance: 1 Status: running
Agent Information: service:jmx:rmi:///jndi/rmi://testdb03.example.in:9999/agent
-----------------------------------------------------
Node Name: testdb03.example.in
Agent Port: 9999
Agent Version: 3.2.7
Agent Build: 4837
OS Name: HP-UX
OS Version: B.11.31
OS Architecture: ia64
Agent Service Info:
Agent Service (Agent) Build: 4837 Status: running
BootstrapService (BootstrapService) Build: 4837 Status: running
Configuration Service (ConfigService) Build: 4837 Status: running
Deployment Service (DeploymentService) Build: 20 Status: running
Environment Service (EnvironmentDiscoveryService) Build: 4837 Status: running
File Transfer Service (FileTransferService) Build: 4837 Status: running
Plugin Registration Service (PluginRegisterService) Build: 4837 Status: running
RMI Service (RMIService) Build: 4837 Status: running
Remote Shell Service (RemoteShellService) Build: 4837 Status: running
Security Service (SecurityService) Build: 4837 Status: running
Self Discovery Service (SelfDiscoveryService) Build: 4837 Status: running
Service Registration Service (ServiceRegistrationService) Build: 4837 Status: running
Session Service (SessionService) Build: 4837 Status: running
SNMP Service (SnmpService) Build: 10 Status: running
Sybase Home Service (SybaseHomeService) Build: 14 Status: running
TaskExecution Service (TaskExecutionService) Build: 4837 Status: running
TDS Service (TdsService) Build: 10 Status: running
Agent Plugin Info:
ASE SNMP Agent Plugin (com.sybase.ase.snmp) Version: 2.0.0 Build: 8 Instance: 1 Status: running
> create cluster databasecluster
Enter the ASE sa user password:
Re-enter the ASE sa user password:
Cluster databasecluster - Enter the maximum number of instances: [ 4 ] 3
How many agents will participate in this cluster: [ 4 ] 3
Verifying the supplied agent specifications...
1) testdb01.example.in 9999 3.2.7 HP-UX
2) testdb02.example.in 9999 3.2.7 HP-UX
3) testdb03.example.in 9999 3.2.7 HP-UX
Enter the number corresponding to the cluster node in the above list : [ 3 ] 1
2) testdb02.example.in 9999 3.2.7 HP-UX
3) testdb03.example.in 9999 3.2.7 HP-UX
Enter the number corresponding to the cluster node in the above list : [ 3 ] 2
3) testdb03.example.in 9999 3.2.7 HP-UX
Enter the number corresponding to the cluster node in the above list : [ 3 ] 3
Will this cluster be configured using private SYBASE installations? (Y/N) : [ N ] Y
------------------ Quorum Device ---------------------
The quorum device is used to manage a cluster. It contains information shared between instances and nodes.
Enter the full path to the quorum disk: /dev/rdisk/disk39
Enter any traceflags:
-------------------- Page Size --------------------
Enter the page size in kilobytes: [ 2 ] 16
--------------- Master Database Device ----------------
The master database device controls the operation of the Adaptive Server and stores information about all user databases and their associated database devices.
Enter the full path to the master device: /dev/rdisk/disk90
Enter the size the Master Device (MB): [ 240 ] 600
Enter the size the Master Database (MB): [ 104 ] 400
------------ Sybase System Procedure Device --------
Sybase system procedures (sybsystemprocs) are stored on a device.
Enter the System Procedure Device path: /dev/rdisk/disk107
Enter System Procedure Device size (MB): [ 172 ] 400
Enter the System Procedure Database size (MB): [ 172 ] 240
-------------- System Database Device ------------------
The system database (sybsystemdb) stores information about distributed transactions.
Enter the System Database Device path: /dev/rdisk/disk183
Enter the System Database Device size (MB): [ 24 ] 240
Enter the System Database size (MB): [ 24 ] 64
--------------- PCI Device ----------------
Pluggable Component Interface (PCI) provides support for Java in database by loading off-the-shelf JVMs from any vendor. If you want to use JVM, create a device for
it.
Enable PCI in Adaptive Servier (Y/N): [ N ] N
--------------- Secondary Network and Starting Port ----------------
A secondary network is for backup in case the primary network is down.
Does this cluster have a secondary network: [ Y ] N
The clustered instances require several ports to communicate with the other instances.
The starting port entered will be used to determine the range of ports allocated on all nodes on all network.
Enter the starting port: [ 15100 ]
--------------------------------------------------------
--------------------------------------------------------
You will now be asked for the instance information on a node by node basis.
-- Cluster: databasecluster - Node: testdb01.example.in - Agent: testdb01.example.in:9999 --
Enter the name of the cluster instance: asce01
Enter any traceflags:
Enter the Sybase installation directory on databasecluster: [ /databaseinstance/instance_01 ]
Enter the environment shell script path on databasecluster: [ /databaseinstance/instance_01/SYBASE.sh ]
Enter the ASE home directory on databasecluster: [ /databaseinstance/instance_01/ASE-15_0 ]
Enter path to the dataserver config file: [ /databaseinstance/instance_01/databasecluster.cfg ]
Enter the interface file query port number for instance asce01: 19786
Enter the primary protocol address for asce01: [ testdb01.example.in ]
--------------- Local System Temporary Database ---------
The Local System Temporary Database Device contains a database for each instance in the cluster.
Enter the LST device name: firstlstdevice
Enter the LST device path: /dev/rdisk/disk56
Enter LST device size (MB): 10000
Enter the LST database name: [ databasecluster_tdb_1 ]
Enter the LST database size (MB): [ 10000 ] 9000
-- Cluster: databasecluster - Node: testdb02.example.in - Agent: testdb02.example.in:9999 --
Enter the name of the cluster instance: asce02
Enter any traceflags:
Enter the Sybase installation directory on databasecluster: [ /databaseinstance/instance_02 ]
Enter the environment shell script path on databasecluster: [ /databaseinstance/instance_02/SYBASE.sh ]
Enter the ASE home directory on databasecluster: [ /databaseinstance/instance_02/ASE-15_0 ]
Enter path to the dataserver config file: [ /databaseinstance/instance_02/databasecluster.cfg ]
Enter the interface file query port number for instance asce02: 19786
Enter the primary protocol address for asce02: [ testdb02.example.in ]
--------------- Local System Temporary Database ---------
The Local System Temporary Database Device contains a database for each instance in the cluster.
Enter the LST device name: [ firstlstdevice ] secondlstdevice
Enter the LST device path: /dev/rdisk/disk73
Enter LST device size (MB): 10000
Enter the LST database name: [ databasecluster_tdb_2 ]
Enter the LST database size (MB): [ 10000 ] 9000
-- Cluster: databasecluster - Node: testdb03.example.in - Agent: testdb03.example.in:9999 --
Enter the name of the cluster instance: asce03
Enter any traceflags:
Enter the Sybase installation directory on databasecluster: [ /databaseinstance/instance_03 ]
Enter the environment shell script path on databasecluster: [ /databaseinstance/instance_03/SYBASE.sh ]
Enter the ASE home directory on databasecluster: [ /databaseinstance/instance_03/ASE-15_0 ]
Enter path to the dataserver config file: [ /databaseinstance/instance_03/databasecluster.cfg ]
Enter the interface file query port number for instance asce03: 19786
Enter the primary protocol address for asce03: [ testdb03.example.in ]
--------------- Local System Temporary Database ---------
The Local System Temporary Database Device contains a database for each instance in the cluster.
Enter the LST device name: [ secondlstdevice ] thirdlstdevice
Enter the LST device path: /dev/rdisk/disk142
Enter LST device size (MB): 10000
Enter the LST database name: [ databasecluster_tdb_3 ]
Enter the LST database size (MB): [ 10000 ] 9000
Would you like to save this configuration information in a file? [ Y ] Y
Enter the name of the file to save the cluster creation information: [ /databaseinstance/instance_01/ASE-15_0/bin/databasecluster.xml ] Y
--------------------------------------------------------
Create the cluster now? [ Y ] Y
INFO - Creating the Cluster Agent plugin on host address testdb01.example.in using agent: testdb01.example.in:9999
INFO - Creating the Cluster Agent plugin on host address testdb02.example.in using agent: testdb02.example.in:9999
INFO - Creating the Cluster Agent plugin on host address testdb03.example.in using agent: testdb03.example.in:9999
For instance asce01, enter the path to the Interfaces file on testdb01.example.in: [ /databaseinstance/instance_01 ]
For instance asce02, enter the path to the Interfaces file on testdb02.example.in: [ /databaseinstance/instance_02 ]
For instance asce03, enter the path to the Interfaces file on testdb03.example.in: [ /databaseinstance/instance_03 ]
Would you like to check whether this device supports IO fencing capability (Y/N)? [ Y ]
Validating the device /dev/rdisk/disk90 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ]
Enter the device path [databasecluster] : [ /dev/rdisk/disk90 ]
Validating the device /dev/rdisk/disk90 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ]
Enter the device path [databasecluster] : [ /dev/rdisk/disk90 ]
Validating the device /dev/rdisk/disk90 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
Validating the device /dev/rdisk/disk107 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
Validating the device /dev/rdisk/disk183 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
INFO - Cluster "databasecluster" creation in progress.
INFO - Choosing the first instance to be created using the connected agent...
INFO - The Sybase home directory is /databaseinstance/instance_01.
INFO - The ASE home directory is /databaseinstance/instance_01/ASE-15_0.
INFO - Retrieving environment variables from /databaseinstance/instance_01/SYBASE.sh.
INFO - The first instance created will be asce01.
INFO - Warning: You have selected '16k' as the logical page size for the Adaptive
INFO - Server. If you plan to load dump from another database, make sure this logical
INFO - page size matches the size of the source database. The default logical page
INFO - size in previous Adaptive Server versions was 2KB.
INFO - Building Adaptive Server 'asce01':
INFO -
INFO - Writing entry into directory services...
INFO - Directory services entry complete.
INFO - Building master device...
INFO - Master device complete.
INFO - Writing RUN_asce01 file...
INFO - RUN_asce01 file complete.
INFO - Starting server...
INFO - Server started.
INFO - Set SA password...
INFO - SA password is set.
INFO - Building sysprocs device and sybsystemprocs database...
INFO - sysprocs device and sybsystemprocs database created.
INFO - Running installmaster script to install system stored procedures...
INFO - installmaster: 10% complete.
INFO - installmaster: 20% complete.
INFO - installmaster: 30% complete.
INFO - installmaster: 40% complete.
INFO - installmaster: 50% complete.
INFO - installmaster: 60% complete.
INFO - installmaster: 70% complete.
INFO - installmaster: 80% complete.
INFO - installmaster: 90% complete.
INFO - installmaster: 100% complete.
INFO - installmaster script complete.
INFO - Creating two-phase commit database...
INFO - Two phase commit database complete.
INFO - Installing common character sets (Code Page 437, Code Page 850, ISO Latin-1,
INFO - Macintosh and HP Roman-8)...
INFO - Character sets installed.
INFO - Setting optimization goal...
INFO - Setting optimization goal complete.
INFO - Server 'asce01' was successfully created.
INFO - Connecting to the dataserver using the host and query port testdb01.example.in:19786.
INFO - Creating the Local System Temporary device firstlstdevice at /dev/rdisk/disk56 of size 10000M.
INFO - Creating the Local System Temporary device secondlstdevice at /dev/rdisk/disk73 of size 10000M.
INFO - Creating the Local System Temporary device thirdlstdevice at /dev/rdisk/disk142 of size 10000M.
INFO - The cluster is now configured. Shutting down this first instance.
The cluster databasecluster was successfully created.
> connect to databasecluster
databasecluster> start cluster
ERROR - Can not get cluster configuration infomation through agent testdb03.example.in:9999. The cluster databasecluster quorum device could not be loaded:
/dev/rdisk/disk39. Cause: The server asece01 did not define a host and port. com.sybase.ua.plugin.AgentPluginException: The server asece01 did not define a host and
port. com.sybase.ua.plugin.AgentPluginException: The cluster databasecluster quorum device could not be loaded: /dev/rdisk/disk39. Cause: The server asece01 did not
define a host and port. com.sybase.ua.plugin.AgentPluginException: The server asece01 did not define a host and port.; nested exception is:
com.sybase.ua.plugin.AgentPluginException: The cluster databasecluster quorum device could not be loaded: /dev/rdisk/disk39. Cause: The server asece01 did not
define a host and port. com.sybase.ua.plugin.AgentPluginException: The server asece01 did not define a host and port.
databasecluster> show cluster config
** Cluster configuration for "databasecluster" **
Installation Mode "private"
Configuration file ""
Trace Flags:
There are no trace flags.
Maximum Instances "3"
Quorum "/dev/rdisk/disk39"
Master Device "/dev/rdisk/disk90"
Primary protocol: "udp"
Secondary protocol: ""
Additional run parameters: ""
Displaying instance 'asce01':
Instance id: "1"
Instance name: "asce01"
Host node: "testdb01.example.in"
Primary address: "testdb01.example.in"
Primary port start: "15100"
Primary port end: "15114"
Secondary address: ""
Secondary port start: ""
Errorlog: "/databaseinstance/instance_01/ASE-15_0/install/asce01.log"
Config file: "/databaseinstance/instance_01/databasecluster.cfg"
Interfaces path: "/databaseinstance/instance_01"
Traceflags: ""
Additional run parameters: ""
Displaying instance 'asce02':
Instance id: "2"
Instance name: "asce02"
Host node: "testdb02.example.in"
Primary address: "testdb02.example.in"
Primary port start: "15115"
Primary port end: "15129"
Secondary address: ""
Secondary port start: ""
Errorlog: "/databaseinstance/instance_02/ASE-15_0/install/asce02.log"
Config file: "/databaseinstance/instance_02/databasecluster.cfg"
Interfaces path: "/databaseinstance/instance_02"
Traceflags: ""
Additional run parameters: ""
Displaying instance 'asce03':
Instance id: "3"
Instance name: "asce03"
Host node: "testdb03.example.in"
Primary address: "testdb03.example.in"
Primary port start: "15130"
Primary port end: "15144"
Secondary address: ""
Secondary port start: ""
Errorlog: "/databaseinstance/instance_03/ASE-15_0/install/asce03.log"
Config file: "/databaseinstance/instance_03/databasecluster.cfg"
Interfaces path: "/databaseinstance/instance_03"
Traceflags: ""
Additional run parameters: ""
databasecluster> show cluster status
ERROR - Can not get cluster configuration infomation through agent testdb03.example.in:9999. The cluster databasecluster quorum device could not be loaded:
/dev/rdisk/disk39. Cause: The server asece01 did not define a host and port. com.sybase.ua.plugin.AgentPluginException: The server asece01 did not define a host and
port. com.sybase.ua.plugin.AgentPluginException: The cluster databasecluster quorum device could not be loaded: /dev/rdisk/disk39. Cause: The server asece01 did not
define a host and port. com.sybase.ua.plugin.AgentPluginException: The server asece01 did not define a host and port.; nested exception is:
com.sybase.ua.plugin.AgentPluginException: The cluster databasecluster quorum device could not be loaded: /dev/rdisk/disk39. Cause: The server asece01 did not
define a host and port. com.sybase.ua.plugin.AgentPluginException: The server asece01 did not define a host and port.
INFO - Listening for the cluster heartbeat. This may take a minute. Please wait... (databasecluster::AseProbe:434)
ERROR - java.lang.NullPointerException: while trying to invoke the method com.sybase.ase.sdcadmin.config.ICluster.getServer(java.lang.Integer) of a null object loaded
from a local variable at slot 9Please help. Please let me know if any other details are required? i will post them.
Thank you.
ASKER
Thank you for your reply Joe.
Yes it is pretty specialized, unable to find much help on-line. And have tried it a dozen or more times unsuccessfully :(
I am performing the Sybase Cluster build with root since this is a Test System. Hence have changed the the ownership to root for all disks.
# chown sybase /dev/rdisk/disk32
# chgrp sybase /dev/rdisk/disk32
# chmod 666 /dev/rdisk/disk32
I will try it with a Sybase account asap.
Thank you Joe.
Yes it is pretty specialized, unable to find much help on-line. And have tried it a dozen or more times unsuccessfully :(
I am performing the Sybase Cluster build with root since this is a Test System. Hence have changed the the ownership to root for all disks.
# chown sybase /dev/rdisk/disk32
# chgrp sybase /dev/rdisk/disk32
# chmod 666 /dev/rdisk/disk32
I will try it with a Sybase account asap.
Thank you Joe.
I'm also thinking if you contact SAP Tech support that's the first thing they're going to zero in on. "Ah you haven't installed as instructed"... even if it fixes nothing it's an important step for ruling things out.
ASKER
Yes I agree. You are correct switching to the sybase user id will help ruling out ownership and permission issues. Will post details as soon as I do a re-run.
Thank you Joe.
Thank you Joe.
ASKER
Hi Joe,
Good day to you. I re-did the installation with the sybase id and changed the device ownership to Sybase as well, Still getting the same error while building the sybase database cluster. Will keep checking.
Thank you Joe.
Good day to you. I re-did the installation with the sybase id and changed the device ownership to Sybase as well, Still getting the same error while building the sybase database cluster. Will keep checking.
Thank you Joe.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Joe
Thank you for your reply. You are correct one area of uncertainty has been eliminated.
The patch level seems to be met. some of the patches come bundled with the OS or are under different names as per the UNIX guys.
***** MLOCK permissions to the Sybase login: ( No mention of MLOCK in "SAP® Adaptive Server® Enterprise Cluster Edition
Document Version: 15.7 SP130 - 2014-08-26" Installation Guide for HP-UX)
OS version: HP-UX B.11.31 ia64
# /etc/privgrp add mlock sybase
sh: /etc/privgrp: not found. ( This privgrp file does not exist)
#
As per http://www.dba-sybase.com/case_study_28.php
I have created /etc/privgroup file on all 3 nodes as it was not existing earlier(It wasn't there earlier)r:
# pwd
/etc
# ls *priv*
privgroup setprivgrp
# cat privgroup
sybase MLOCK
# pwd
/etc
/usr/sbin/setprivgrp -f /etc/privgroup (I haves set MLOCK privilege on all 3 nodes)
*****
I have checked all the disks on the 3 nodes. They are fence capable.
eg
# iofenceutil --device=/dev/rdisk/disk39
/dev/rdisk/disk39 is fence capable.
iofenceutil provides similar functionality to qrmutil --fence_capable
eg: qrmutil --fence-capable=/dev/rdisk
I have tried it with both utilities, all devices seem to be fence capable.
******
Still throwing the below error when I try to start the cluster:
Would you like to check whether this device supports IO fencing capability (Y/N)? [ Y ] Y
Validating the device /dev/rdisk/disk90 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
Validating the device /dev/rdisk/disk183 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
Validating the device /dev/rdisk/disk107 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
INFO - Cluster "billingcluster" creation in progress.
INFO - Choosing the first instance to be created using the connected agent...
INFO - The Sybase home directory is /billinginstance/instance_
INFO - The ASE home directory is /billinginstance/instance_
INFO - Retrieving environment variables from /billinginstance/instance_
INFO - The first instance created will be asce01.
INFO - Warning: You have selected '16k' as the logical page size for the Adaptive
INFO - Server. If you plan to load dump from another database, make sure this logical
INFO - Building Adaptive Server 'asce01':
INFO - page size matches the size of the source database. The default logical page
INFO - Writing entry into directory services...
INFO - size in previous Adaptive Server versions was 2KB.
INFO - Directory services entry complete.
INFO -
INFO - Building master device...
INFO - Master device complete.
INFO - Writing RUN_asce01 file...
INFO - RUN_asce01 file complete.
INFO - Starting server...
INFO - Server started.
INFO - Set SA password...
INFO - SA password is set.
INFO - Building sysprocs device and sybsystemprocs database...
INFO - sysprocs device and sybsystemprocs database created.
INFO - Running installmaster script to install system stored procedures...
INFO - installmaster: 10% complete.
INFO - installmaster: 20% complete.
INFO - installmaster: 30% complete.
INFO - installmaster: 40% complete.
INFO - installmaster: 50% complete.
INFO - installmaster: 60% complete.
INFO - installmaster: 70% complete.
INFO - installmaster: 80% complete.
INFO - installmaster: 90% complete.
INFO - installmaster: 100% complete.
INFO - installmaster script complete.
INFO - Creating two-phase commit database...
INFO - Two phase commit database complete.
INFO - Installing common character sets (Code Page 437, Code Page 850, ISO Latin-1,
INFO - Macintosh and HP Roman-8)...
INFO - Character sets installed.
INFO - Setting optimization goal...
INFO - Setting optimization goal complete.
INFO - Server 'asce01' was successfully created.
INFO - Connecting to the dataserver using the host and query port testdb01.example.in:19786.
INFO - Creating the Local System Temporary device firstlstdevice at /dev/rdisk/disk56 of size 10000M.
INFO - Creating the Local System Temporary device secondlstdevice at /dev/rdisk/disk73 of size 10000M.
INFO - Creating the Local System Temporary device thirdlstdevice at /dev/rdisk/disk142 of size 10000M.
INFO - The cluster is now configured. Shutting down this first instance.
The cluster billingcluster was successfully created.
> connect to billingcluster
billingcluster> start cluster
ERROR - Can not get cluster configuration infomation through agent testdb03.example.in:9999. The cluster billingcluster quorum device could not be loaded: /dev/rdisk/disk39. Cause: quorum device does not exist or cannot read.
com.sybase.ua.plugin.Agent
com.sybase.ua.plugin.Agent
com.sybase.ua.plugin.Agent
; nested exception is:
com.sybase.ua.plugin.Agent
com.sybase.ua.plugin.Agent
billingcluster>
The below commands show that the quorum device exists:
# qrmutil --quorum-dev=/dev/rdisk/di
Using DSQUORUM device '/dev/rdisk/disk39'
Executing command 'view / set ASE config file version', argument 'null'...
Acquiring the quorum file system lock...
ASE config file version 20 is stored on the quorum device.
Command 'view / set ASE config file version', argument 'null' succeeded.
Releasing the quorum file system lock...
qrmutil execution completed.
# qrmutil --quorum-dev=/dev/rdisk/di
Using DSQUORUM device '/dev/rdisk/disk39'
Executing command 'display', argument 'config'...
Beginning display of cluster configuration:
Cluster configuration id: edbcd0e8-2d3e-4666-baef-57
Cluster name: 'databasecluster'
Max instances: 3
Master devices: '/dev/rdisk/disk90'
Config file: ''
Interfaces path: '/databaseinstance/instanc
Traceflags: ''
Primary protocol: 'udp'
Secondary protocol: ''
Additional run parameters: ''
Installation mode: 'private'
Membership mode: ''
Displaying instance 'asce01' (1)
Instance id: 1
Instance name: 'asce01'
Host node: 'testdb01.example.in'
Primary address: 'testdb01.example.in'
Primary port start: '15100'
Secondary address: ''
Secondary port start: ''
Errorlog: '/databaseinstance/instanc
Config file: '/databaseinstance/instanc
Interfaces path: '/databaseinstance/instanc
Traceflags: ''
Additional run parameters: ''
Displaying instance 'asce02' (2)
Instance id: 2
Instance name: 'asce02'
Host node: 'testdb02.example.in'
Primary address: 'testdb02.example.in'
Primary port start: '15115'
Secondary address: ''
Secondary port start: ''
Errorlog: '/databaseinstance/instanc
Config file: '/databaseinstance/instanc
Interfaces path: '/databaseinstance/instanc
Traceflags: ''
Additional run parameters: ''
Displaying instance 'asce03' (3)
Instance id: 3
Instance name: 'asce03'
Host node: 'testdb03.example.in'
Primary address: 'testdb03.example.in'
Primary port start: '15130'
Secondary address: ''
Secondary port start: ''
Errorlog: '/databaseinstance/instanc
Config file: '/databaseinstance/instanc
Interfaces path: '/databaseinstance/instanc
Traceflags: ''
Additional run parameters: ''
Command 'display', argument 'config' succeeded.
qrmutil execution completed.
# qrmutil --quorum-dev=/dev/rdisk/di
Using DSQUORUM device '/dev/rdisk/disk39'
Executing command 'display', argument 'nodes'...
Beginning display of registered nodes:
testdb01.example.in
testdb02.example.in
testdb03.example.in
Command 'display', argument 'nodes' succeeded.
qrmutil execution completed.
#
I am suspecting shared disk configuration issues.
Thank you Joe
Thank you for your reply. You are correct one area of uncertainty has been eliminated.
The patch level seems to be met. some of the patches come bundled with the OS or are under different names as per the UNIX guys.
***** MLOCK permissions to the Sybase login: ( No mention of MLOCK in "SAP® Adaptive Server® Enterprise Cluster Edition
Document Version: 15.7 SP130 - 2014-08-26" Installation Guide for HP-UX)
OS version: HP-UX B.11.31 ia64
# /etc/privgrp add mlock sybase
sh: /etc/privgrp: not found. ( This privgrp file does not exist)
#
As per http://www.dba-sybase.com/case_study_28.php
I have created /etc/privgroup file on all 3 nodes as it was not existing earlier(It wasn't there earlier)r:
# pwd
/etc
# ls *priv*
privgroup setprivgrp
# cat privgroup
sybase MLOCK
# pwd
/etc
/usr/sbin/setprivgrp -f /etc/privgroup (I haves set MLOCK privilege on all 3 nodes)
*****
I have checked all the disks on the 3 nodes. They are fence capable.
eg
# iofenceutil --device=/dev/rdisk/disk39
/dev/rdisk/disk39 is fence capable.
iofenceutil provides similar functionality to qrmutil --fence_capable
eg: qrmutil --fence-capable=/dev/rdisk
I have tried it with both utilities, all devices seem to be fence capable.
******
Still throwing the below error when I try to start the cluster:
Would you like to check whether this device supports IO fencing capability (Y/N)? [ Y ] Y
Validating the device /dev/rdisk/disk90 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
Validating the device /dev/rdisk/disk183 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
Validating the device /dev/rdisk/disk107 for IO Fencing Capabilities.
This device does not have SCSI-3 PGR capability. It does not support I/O fencing
Do you want to continue (Y/N)? [ N ] Y
INFO - Cluster "billingcluster" creation in progress.
INFO - Choosing the first instance to be created using the connected agent...
INFO - The Sybase home directory is /billinginstance/instance_
INFO - The ASE home directory is /billinginstance/instance_
INFO - Retrieving environment variables from /billinginstance/instance_
INFO - The first instance created will be asce01.
INFO - Warning: You have selected '16k' as the logical page size for the Adaptive
INFO - Server. If you plan to load dump from another database, make sure this logical
INFO - Building Adaptive Server 'asce01':
INFO - page size matches the size of the source database. The default logical page
INFO - Writing entry into directory services...
INFO - size in previous Adaptive Server versions was 2KB.
INFO - Directory services entry complete.
INFO -
INFO - Building master device...
INFO - Master device complete.
INFO - Writing RUN_asce01 file...
INFO - RUN_asce01 file complete.
INFO - Starting server...
INFO - Server started.
INFO - Set SA password...
INFO - SA password is set.
INFO - Building sysprocs device and sybsystemprocs database...
INFO - sysprocs device and sybsystemprocs database created.
INFO - Running installmaster script to install system stored procedures...
INFO - installmaster: 10% complete.
INFO - installmaster: 20% complete.
INFO - installmaster: 30% complete.
INFO - installmaster: 40% complete.
INFO - installmaster: 50% complete.
INFO - installmaster: 60% complete.
INFO - installmaster: 70% complete.
INFO - installmaster: 80% complete.
INFO - installmaster: 90% complete.
INFO - installmaster: 100% complete.
INFO - installmaster script complete.
INFO - Creating two-phase commit database...
INFO - Two phase commit database complete.
INFO - Installing common character sets (Code Page 437, Code Page 850, ISO Latin-1,
INFO - Macintosh and HP Roman-8)...
INFO - Character sets installed.
INFO - Setting optimization goal...
INFO - Setting optimization goal complete.
INFO - Server 'asce01' was successfully created.
INFO - Connecting to the dataserver using the host and query port testdb01.example.in:19786.
INFO - Creating the Local System Temporary device firstlstdevice at /dev/rdisk/disk56 of size 10000M.
INFO - Creating the Local System Temporary device secondlstdevice at /dev/rdisk/disk73 of size 10000M.
INFO - Creating the Local System Temporary device thirdlstdevice at /dev/rdisk/disk142 of size 10000M.
INFO - The cluster is now configured. Shutting down this first instance.
The cluster billingcluster was successfully created.
> connect to billingcluster
billingcluster> start cluster
ERROR - Can not get cluster configuration infomation through agent testdb03.example.in:9999. The cluster billingcluster quorum device could not be loaded: /dev/rdisk/disk39. Cause: quorum device does not exist or cannot read.
com.sybase.ua.plugin.Agent
com.sybase.ua.plugin.Agent
com.sybase.ua.plugin.Agent
; nested exception is:
com.sybase.ua.plugin.Agent
com.sybase.ua.plugin.Agent
billingcluster>
The below commands show that the quorum device exists:
# qrmutil --quorum-dev=/dev/rdisk/di
Using DSQUORUM device '/dev/rdisk/disk39'
Executing command 'view / set ASE config file version', argument 'null'...
Acquiring the quorum file system lock...
ASE config file version 20 is stored on the quorum device.
Command 'view / set ASE config file version', argument 'null' succeeded.
Releasing the quorum file system lock...
qrmutil execution completed.
# qrmutil --quorum-dev=/dev/rdisk/di
Using DSQUORUM device '/dev/rdisk/disk39'
Executing command 'display', argument 'config'...
Beginning display of cluster configuration:
Cluster configuration id: edbcd0e8-2d3e-4666-baef-57
Cluster name: 'databasecluster'
Max instances: 3
Master devices: '/dev/rdisk/disk90'
Config file: ''
Interfaces path: '/databaseinstance/instanc
Traceflags: ''
Primary protocol: 'udp'
Secondary protocol: ''
Additional run parameters: ''
Installation mode: 'private'
Membership mode: ''
Displaying instance 'asce01' (1)
Instance id: 1
Instance name: 'asce01'
Host node: 'testdb01.example.in'
Primary address: 'testdb01.example.in'
Primary port start: '15100'
Secondary address: ''
Secondary port start: ''
Errorlog: '/databaseinstance/instanc
Config file: '/databaseinstance/instanc
Interfaces path: '/databaseinstance/instanc
Traceflags: ''
Additional run parameters: ''
Displaying instance 'asce02' (2)
Instance id: 2
Instance name: 'asce02'
Host node: 'testdb02.example.in'
Primary address: 'testdb02.example.in'
Primary port start: '15115'
Secondary address: ''
Secondary port start: ''
Errorlog: '/databaseinstance/instanc
Config file: '/databaseinstance/instanc
Interfaces path: '/databaseinstance/instanc
Traceflags: ''
Additional run parameters: ''
Displaying instance 'asce03' (3)
Instance id: 3
Instance name: 'asce03'
Host node: 'testdb03.example.in'
Primary address: 'testdb03.example.in'
Primary port start: '15130'
Secondary address: ''
Secondary port start: ''
Errorlog: '/databaseinstance/instanc
Config file: '/databaseinstance/instanc
Interfaces path: '/databaseinstance/instanc
Traceflags: ''
Additional run parameters: ''
Command 'display', argument 'config' succeeded.
qrmutil execution completed.
# qrmutil --quorum-dev=/dev/rdisk/di
Using DSQUORUM device '/dev/rdisk/disk39'
Executing command 'display', argument 'nodes'...
Beginning display of registered nodes:
testdb01.example.in
testdb02.example.in
testdb03.example.in
Command 'display', argument 'nodes' succeeded.
qrmutil execution completed.
#
I am suspecting shared disk configuration issues.
Thank you Joe
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Aha! Good job! Good to know the next time I run into this. I hope I at least narrowed down the issues for you.
ASKER
Answer provided by own research resolves the issue completely.
I always suspect environment first. The fact that raw disks are still owned by root makes me suspicious. Try it by the book, with a sybase account owning what it's supposed to own?