Document Type | Troubleshooting
Category | Installation
Applicable Product Versions | 6FS01, 6FS02, 6FS03, 6FS04, 6FS05, 6FS06, 6FS07, 6FS07PS, 7FS01, 7FS02, 7FS02PS
Document Number | TINTI012
Issue
When configuring TAC-TSC, if the standby is a file system rather than raw configuration, running tbrmgr fails.
Cause
When using tbrmgr, if the configuration is not composed of the same raw, recognition errors continuously occur.
Solutions
Resolve by installing using dd copy.
1. Create files using dd copy command
Create files using the same names as the raw names.
dd if=/dev/raw/ps1/r1g29vg01 of=/idiska/pub1/tactsc1/backup/r1g29vg01 bs=40M
dd if=/dev/raw/ps1/r1g32vg01 of=/idiska/pub1/tactsc1/backup/r1g32vg01 bs=1M count=256 โ For redo files, if the allocated raw size and the actual created raw size differ, the count option must be used to match the size
dd if=/dev/raw/ps1/r1g33vg01 of=/idiska/pub1/tactsc1/backup/r1g33vg01 bs=1M count=256
dd if=/dev/raw/ps1/r1g34vg01 of=/idiska/pub1/tactsc1/backup/r1g34vg01 bs=40M
dd if=/dev/raw/ps1/r1g35vg01 of=/idiska/pub1/tactsc1/backup/r1g35vg01 bs=40M
dd if=/dev/raw/ps1/r1g36vg01 of=/idiska/pub1/tactsc1/backup/r1g36vg01 bs=40M
dd if=/dev/raw/ps1/r1g37vg01 of=/idiska/pub1/tactsc1/backup/r1g37vg01 bs=40M
dd if=/dev/raw/ps1/r1g38vg01 of=/idiska/pub1/tactsc1/backup/r1g38vg01 bs=40M
dd if=/dev/raw/ps1/r1g39vg01 of=/idiska/pub1/tactsc1/backup/r1g39vg01 bs=40M
dd if=/dev/raw/ps1/r1g40vg01 of=/idiska/pub1/tactsc1/backup/r1g40vg01 bs=1M count=256
dd if=/dev/raw/ps1/r1g41vg01 of=/idiska/pub1/tactsc1/backup/r1g41vg01 bs=1M count=256
dd if=/dev/raw/ps1/r1g42vg01 of=/idiska/pub1/tactsc1/backup/r1g42vg01 bs=40M
dd if=/dev/raw/ps1/r1g43vg01 of=/idiska/pub1/tactsc1/backup/r1g43vg01 bs=40M
dd if=/dev/raw/ps1/r1g28vg01 of=/idiska/pub1/tactsc1/backup/r1g28vg01 bs=40M
2. Add the STANDBY_FILE_NAME_CONVERT parameter to the tip file
STANDBY_FILE_NAME_CONVERT="/dev/raw/ps1/,/sdiske/ps1/tactas/standby/tbdata/"
3. Transfer the dd copy files to the location specified in the STANDBY_FILE_NAME_CONVERT parameter
4. Start standby mount
5. Perform alter database standby controlfile
6. Perform tbboot recovery