Document Type | Troubleshooting
Category | Installation
Applicable Product Versions | 6FS01, 6FS02, 6FS03, 6FS04, 6FS05, 6FS06, 6FS07, 6FS07PS, 7FS01, 7FS02, 7FS02PS
Document Number | TINTI004
Issue
- First TAS setup completed
- TAS rebuild: 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
- When performed in nomount mode: new diskspace creation
- When performed in mount or above mode: add diskspace
Solutions
Case 1. When patch 203789a is applied
dd if=/dev/zero of=/data/tastac_new/tbdata/disk0 bs=1M count=10240
Case 2. When patch 203789b or later is applied
Add _AS_CREATE_DISKSPACE_FORCE parameter
If set to _AS_CREATE_DISKSPACE_FORCE=Y, when create diskspace is executed in nomount mode, the disk header check is skipped, so diskspace will be created without error messages even if the disk has previously been used by TAS. (default = N)
Add the force keyword to the create diskspace statement
When creating diskspace, if you add the force keyword after the DS name as in the example below, the disk header will not be checked and diskspace will 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.