Octopus Administrator's Guide
Octopus Operations

Octopus 24x7 Operations

The OctoRefresh Program

The OctoRefresh program refreshes the database versions used by Octopus after updates have been made to the database outside the Octopus system. Octopus clients are not required to disconnect while the refresh operation is accomplished; clients currently executing queries will "see" the new database version (the current database Snapshot) when they issue their next query. It is also possible to specify a Snapshot other than the current one with which to refresh user's views of the database. For more information about database Snapshots, consult the Persistent Mode Operations (Time Travel) section of the SAND CDBMS Administration Guide.

When the database has been updated using the SET UPDATE KEEP CHANGE command, users' views of the database are automatically refreshed, and it is not necessary to execute the OctoRefresh program.

DBA privileges are required to execute the octorefresh command. Note that a user name (along with password, if applicable) must be included in the program invocation, unless privilege checking has been disabled by including the SecurityLevel=0 parameter in the relevant [OCTOPUS instance-name] section of the nucleus.ini file. When privilege checking is disabled, all users are connected as the user DBA.

Syntax

octorefresh [-v snapshot-number] connection-name database-name user-name[/password]

where connection-name corresponds to the value of the Connection parameter in the relevant OCTOPUS section of the nucleus.ini file, database-name is the name of the database instance running under Octopus (as specified by the DatabaseName parameter). To have OctoRefresh use a database version other than that represented by the current snapshot, include the -v snapshot-number option flag, specifying the desired snapshot.

Resetting the Log and Stat Files with the OctoRollLog Program

Octopus log files, STAT files and CSTAT files can be reset by executing the OctoRollLog program locally or remotely. DBA privileges are required to execute the octorolllog command. Note that as of release 3.2 a user name (along with password, if applicable) must be included in the program invocation, unless privilege checking has been disabled by including the SecurityLevel=0 parameter in the relevant [OCTOPUS instance-name] section of the nucleus.ini file. When privilege checking is disabled, all users are connected as the user DBA.

Syntax

octorolllog [ -r <file types> ] connection-name database-name user-name[/password]

where:

• connection-name corresponds to the value of the Connection parameter in the relevant OCTOPUS section of the nucleus.ini file
• database-name is the name of the database instance running under Octopus (as specified by the DatabaseName parameter)
• The optional -r flag specifies one or more types of file to be reset:

  l	Log file
  d	Detailed statistics (STAT) file
  c	Cumulative statistics (CSTAT) file

  The -r flag should be separated from its parameters by a space. If multiple parameters are included, they should not be separated by white space. If the -r flag is omitted, all types of file are reset.

Executing this command renames the current file(s) by adding the date and time of command execution to the original filename (for example, file-name.otl.yyyy-mm-dd-hh-mm-ss), and then starts a new file.

Example:

octorolllog -r ld cn1 dbtest DBA

 

Previous Topic: Octopus On-Demand Database (ODDB)

Chapter Index

Next Topic: Dynamically Reconfiguring Subclasses