NAME

oscp − copy an ObjectStore database

SYNOPSIS

oscp source-pathname destination-pathname

DESCRIPTION

oscp copies the ObjectStore database source-pathname to destination-pathname.  If the destination database exists, it is deleted before the copy is performed. 

Note that oscp takes only non-wildcard pathnames, neither of which may be a directory. 

oscp contacts the Server to ensure that the database being copied is transaction-consistent and fully up to date, but cp does not.  Therefore, you should use cp on a file database only if the Server handling access to the database has been shut down with ossvrshtd.  Otherwise, use oscp. 

Using cp can sometimes produce a database in an inconsistent state (if the database was copied during propagation of data from the log), or in a consistent but out-of-date state (if the effects of some transactions have not yet been propagated from the log to the database). Attempting to operate on an inconsistent copy will fail, signaling err_inconsistent_db. 

Using cp also results in a copy with same database ID as the original, while oscp gives a new, unique ID to the copy. This is important only if you have applica tions that rely on the uniqueness of these IDs. If you use cp, you can give the copy a new, unique ID with os_database::set_new_id(). 

oscp accepts a combination of Directory Manager pathnames and file pathnames. To move a database from a file to a Directory Manager or vice versa, you must use oscp; cp will not work correctly. 

FILES

$OS_ROOTDIR/bin/oscp

SEE ALSO

cp(1)
 

ObjectStore 2.0  —  Last change: October 1992