Bookshelf 8.0,
Siebel System Administration Guide > Siebel Server Infrastructure Administration > Administering the Siebel File System >
Partitioning the Siebel File System
is using wrong parameters - Change Request 12-1LMZIFJ
has been logged to correct this, but was closed without implementing changes in bookshelf, as it focussed on functionality issues.
Change Request 12-1UIAFCF was logged 8/19/2009 to explicitly request changes to bookshelf 8.0 and 8.1, but often change requests are only implemented in further major versions, so please accept our apologies if bookshelf is still wrong.
A) In bookshelf, supported parameters are documented as /u, /p, /c, /d, /f, /o, /l.
But these are not the supported parameters. sfspartition fails if we use these parameters.
invoking sfspartition (without parameters) from the command prompt shows the following supported parameters:
/O Current Siebel File System paths (Seperate by comma) (Required) /F New Siebel File System paths (Seperate by comma) (Required)
/L Current Hash Level (Default: -1)
/N New Hash Level (Default: -1)
/H Don't append att folder to the file system path (Default: N)
Please find below (section B) a working set of instructions how to use sfspartition on AIX - note this only works from Siebel version 8.0, not before.
Before you change anything,
0. Please backup your current siebns.dat
(srvmrgr command
backup nameserver) - this will allow you to revert to the current state by copying the resulting siebns.dat_<date>_<time> to siebns.dat if needed later
B) Steps followed to test sfspartition are as below:
1) Suppose you want to move the files into /export/home/qa1/21112/fs1, /export/home/qa1/21112/fs2 directories from the current /export/home/qa1/21112/fs directories then:
Create 2 folders: fs1, fs2 under /export/home/qa1/21112. Create the same subfolders that are present under fs, in fs1 and fs2 also.
eg: Under fs1 and fs2,
mkdir att cms Marketing Profile Reports userpref atttmp eim packages red ssp
Give full permissions to fs2, fs3 and its subfolders and share them.
chmod -R 777 fs1 fs2
2) At enterprise level execute:
srvrmgr> Change ent param FileSystem="/export/home/qa1/21112/fs1,/export/home/qa1/21112/fs2"
Bounce the siebel servers
3) Go to siebsrvr/bin directory and execute the following cmd:
sfspartition /O "/export/home/qa1/21112/fs" /F "/export/home/qa1/21112/fs1,/export/home/qa1/21112/fs2" /H Y
The files will be moved from fs to fs1 and fs2 and the attachments added in the UI prior running sfspartition are still accessible. Also .SAF files for newly created attachments in UI move into either fs1 or fs2.
4) Also importantly, the FileSystem needs to be changed for all components that have it set explicitly in the siebns.dat - for example, but not limited to: txnproc, txnroute, txnmerge components (otherwise after synchronization the attachments wont be accessible and it throws an errormsg)
change param filesystem="/export/home/qa6/21032/fs1,/export/home/qa6/21032/fs2" for comp txnproc
change param filesystem="/export/home/qa6/21032/fs1,/export/home/qa6/21032/fs2" for comp txnmerge
change param filesystem="/export/home/qa6/21032/fs1,/export/home/qa6/21032/fs2" for comp txnroute
C) Before you change any component parameters, open a COPY of your siebns.dat file (from <Gateway Root>
with a text editor and check all occurrences of
FileSystem
Only the components that have this parameter set already need to have the parameter changed - all others will inherit it from the Enterprise parameter setting.
D) As a final check, when you have finished setting the component parameters with srvrmgr per C),
you should no longer have the name of your initial filesystem (before the split up)
in your siebns.dat.