If you use symbolic links, you may unknowingly cause dbspaces to be created in a different directory from where you may want them to be. For example, suppose you have created dbspaces in the following files:
-rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.db -rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.iq1 -rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.iq2 -rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.iq3 -rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.iqtmp -rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.iqmsg
If you create the following links beforehand, then the dbspaces, when they are created, are actually created in the directories (or on the raw partitions) pointed to by the links:
lrwxrwxrwx 1 dkusner sybase 14 Feb 26 17:48 asiqdemo.iq1 -> LINKS/asiqdemo.iq1
lrwxrwxrwx 1 dkusner sybase 14 Feb 26 17:48 asiqdemo.iq2 -> LINKS/asiqdemo.iq2
lrwxrwxrwx 1 dkusner sybase 18 Feb 26 17:48 asiqdemo.iq3 -> /dev/rdsk/c2t6d0s0
When you back up the files and restore them with the CATALOG ONLY option, you don't see anything telling you that these files were links; in fact, this information is not saved.
Sybase IQ saves these files as though they were actually present in the directory where the symbolic links reside. When you do the restore, the files are recreated in the directories or on the raw partitions named by the database name. Whether or not the links exist at restore time, they are never used again. The database is restored to its original location.
