Document Type | Troubleshooting
Field | Installation
Applicable Product Versions | 6FS01, 6FS02, 6FS03, 6FS04, 6FS05, 6FS06, 6FS07, 6FS07PS, 7FS01, 7FS02, 7FS02PS
Document Number | TINTS002
Issue
When recreating Tibero Active Cluster (hereinafter TAS), if you perform create diskspace in nomount mode, a TBR-31009 error occurs indicating that the disk is already mounted, and diskspace recreation is not possible.
- First TAS setup completed
- TAS reconstruction: create diskspace performed in nomount mode
SQL> CREATE DISKSPACE DS0 external redundancy 2 failgroup ds0_fg0 DISK '/data/tastac_new/tbdata/disk0' SIZE 8g, 3 '/data/tastac_new/tbdata/disk1' SIZE 8g; TBR-31009: The disk, '/data/tastac_new/tbdata/disk0', has already been mounted.
Cause
The mode in which TAS diskspace creation or addition is performed differs, although the syntax of the statement is the same.
- When performed in nomount mode: new diskspace creation
- When performed in mount or higher mode: diskspace addition
There was an issue where users mistakenly added diskspace in nomount mode, causing existing diskspace to be initialized, so a separate patch was created and applied to prevent this. (Applied patch: 203789)
After applying the patch, if create diskspace is performed in nomount mode and the space to be created is not completely empty, an error is output.
Solutions
Case 1. When patch 203789a is applied
Initialize the disk using the โddcopyโ command.
dd if=/dev/zero of=/data/tastac_new/tbdata/disk0 bs=1M count=10240
Case 2. When patch 203789b or later is applied
You can selectively use one of the following two methods.
Add _AS_CREATE_DISKSPACE_FORCE parameter
If set to _AS_CREATE_DISKSPACE_FORCE=Y, when create diskspace is performed in nomount mode, the disk header check is skipped, so even if the disk has been previously used in TAS, diskspace is created without an error message. (default = N)
Add force keyword to create diskspace statement
When creating diskspace, if you add the force keyword after the DS name as in the example below, the disk header check is skipped and diskspace can be created.
SQL> create diskspace DS0 force normal redundancy failgroup FG0 disk '/dev/disk0' name DISK0 failgroup FG1 disk '/dev/disk1' name DISK1 attribute 'AU_SIZE' = '1M'; Diskspace 'DS0' created.