If a tablespace is added on a raw I/O device or shared file system after the SAP MaxDB hierarchy has been created in SPS, you must manually create a resource hierarchy for the raw device or file system via the LifeKeeper GUI. The newly created resource hierarchy must then be made a dependent (child) of the SAP MaxDB resource hierarchy. The updated parameter files must be redistributed if necessary to all servers that protect the database instance (this is not required if the IndepDataPath is located on a shared disk).


Thanks for your feedback.

Post your comment on this topic.

Post Comment