1,126
edits
Difference between revisions of "arsdb"
Jump to navigation
Jump to search
m
Removed code tags.
m (Moved TOC to be right-justified.) |
m (Removed code tags.) |
||
| Line 9: | Line 9: | ||
arsdb is used during the installation process to create the database, plus OnDemand's internal tables for metadata, and indexes inside those tables. | arsdb is used during the installation process to create the database, plus OnDemand's internal tables for metadata, and indexes inside those tables. | ||
arsdb -I ARCHIVE -ctrv | |||
After the installation is complete, you must build the [[System Log]], [[System Load]], and [[System Migration]] Application Groups separately using the [[arssyscr]] command. | After the installation is complete, you must build the [[System Log]], [[System Load]], and [[System Migration]] Application Groups separately using the [[arssyscr]] command. | ||
| Line 19: | Line 19: | ||
The IBM Content Manager OnDemand database needs routine maintenance to ensure performance and reliability. Depending on the volume and age of your system, you may want to run these options more or less frequently. | The IBM Content Manager OnDemand database needs routine maintenance to ensure performance and reliability. Depending on the volume and age of your system, you may want to run these options more or less frequently. | ||
arsdb -I ARCHIVE -msv | |||
Regular backups are a wise part of any maintenance window. For online backups, use: | Regular backups are a wise part of any maintenance window. For online backups, use: | ||
arsdb -I ARCHIVE -zv | |||
And for offline backups, use: | And for offline backups, use: | ||
arsdb -I ARCHIVE -yv | |||
=== Special Note about Database Backups === | === Special Note about Database Backups === | ||
| Line 37: | Line 37: | ||
In Content Manager OnDemand v7.1 and v7.1.1, upgrades to OnDemand that required database changes required you to export, drop, create, then import your CMOD metadata tables: | In Content Manager OnDemand v7.1 and v7.1.1, upgrades to OnDemand that required database changes required you to export, drop, create, then import your CMOD metadata tables: | ||
arsdb -I ARCHIVE -xlvf | |||
arsdb -I ARCHIVE -xlvf | arsdb -I ARCHIVE -dev | ||
arsdb -I ARCHIVE -trv | |||
arsdb -I ARCHIVE -dev | arsdb -I ARCHIVE -ilvf | ||
arsdb -I ARCHIVE -trv | |||
arsdb -I ARCHIVE -ilvf | |||
In CMOD 7.1.2.x, 8.x and 9.x, IBM has added the -u option to arsdb, allowing you to update the definitions inside the OnDemand database. | In CMOD 7.1.2.x, 8.x and 9.x, IBM has added the -u option to arsdb, allowing you to update the definitions inside the OnDemand database. | ||
arsdb -I ARCHIVE -uv | |||
arsdb -I ARCHIVE -uv | |||
== Usage == | == Usage == | ||
| Line 87: | Line 79: | ||
(MSSQL) Differential OnDemand database backup to the device | (MSSQL) Differential OnDemand database backup to the device | ||
-Z <device> (DB2) Backup the OnDemand database tablespace(s) online to the device | -Z <device> (DB2) Backup the OnDemand database tablespace(s) online to the device | ||