Options for TESM command

cleandemolicense

The cleandemolicense command cleans the demo license from the DB before applying the permanent license.

tesm cleandemolicense

Example

This command cleans the demo license:

Example: tesm cleandemolicense.

cleanlicense

The cleanlicense command cleans the permanent license from the DB, before applying the new permanent license.

tesm cleanlicense

Example

This command cleans the permanent license:

Example: tesm cleanlicense.

cm

cm setcmpwd pluginname oldpassword newpassword

Operation

The command sets the plugin name and password for the Client Manager.

Example

This command sets the plugin name and password for the Client Manager.

Example: cm setcmpwd tes-6.5.dsp tidal123 tidalabc.

dbbackup

Note: Always enclose arguments containing spaces in quotes, or the command will not execute successfully.

Example: If the Program Files folder is included in a path statement as an argument, the entire path must be enclosed by quotes. The dbbackup command checks the Master status. If the Master is running, this command asks the user to stop the Master manually. After the Master is stopped, it exports the database associated with the Master.

tesm dbbackup <path for dbexport>

Example: tesm dbbackup c:\\temp_dir\\file.dmp (windows) tesm dbbackup etc/temp_dir/file.dmp (UNIX)

These points need to be considered before executing the command:

  • The user associated with the DB must be granted access to CREATE ANY DIRECTORY on oracle DB before starting the export operation.

    Example: GRANT CREATE ANY DIRECTORY TO tidal.

  • To execute the command from Windows box:

    If the database is in the Windows machine, provide the windows path. If the path has any directory, create the path before executing the command. 

    C:\\dmpdir\\file.dmp.

    If the database is in the UNIX machine, provide the windows path. If the path has any directory, create the path before executing the command. 

    \home\dmpdir\file.dmp.

  • To execute the command from Linux box:

    If the database is in the Windows machine, provide the windows path. If the path has any directory, create the path before executing the command. 

    C:/dmpdir/file.dmp.

    If the database is in the UNIX machine, provide the windows path. If the path has any directory, create the path before executing the command. 

    /home/dmpdir/file.dmp.

dbcheck

The dbcheck command checks these:

  • User permission of the database – Checks whether the requiredpermissions are available for the database user (e.g., tidal). If not available, the command displays the error message with details of the permissions that are not available.

  • Indexes of the database – Checks for irrelevant indexes available that are not created through TA by default, and also if any required database indexes are missing from the database which are created through TA.

  • Primary keys and constraints of the database – Checks whether the database tables contain primary key fields and constraints created by TA. If not, then the command will list those details.

  • Database corruption validation – Checks the database for any corrupted data from past scenarios. If yes, then the output displays the corruption details.

  • Table count validation – Validates each object table's max object id against the database table named "tablecnt" which contains all TA object counts.

tesm dbcheck [user][password]

dbcheck -options

Option

Description

user password

Dbcheck properties validated from the specified user and password.

Operation

  • If user and password options are specified, the dbcheck command validates the database based on the given user.

  • If no option denoting a user and password is used, the dbcheck command validates the database based on the 'tidal' user.

Examples

  • This example validates the database based on the 'tidal' user.

    Example: tesm dbcheck.

  • This example validates the database based on the given user.

    Example: tesm dbcheck user pwd.

dbupgrade

Note: Always enclose arguments containing spaces in quotes, or the command will not execute successfully.

Example: If the Program Files folder is included in a path statement as an argument, the entire path must be enclosed by quotes.

The dbupgrade command checks the master status. If the Master is running, this command asks the user to stop the Master manually. After the Master is stopped, it upgrades the database associated with the Master.

tesm dbupgrade [path][silent]

dbupgrade -options

Option

Description

path

Database backup stored in the specified path.

silent

Upgrade the database in silent mode (if the master is running, then this option won't prompt the user to stop the master and exits the command).

Example

tesm dbupgrade c:\\temp_dir\\file.dmp (windows) tesm dbupgrade etc/temp_dir/file.dmp (UNIX)
tesm dbupgrade c:\\temp_dir\\file.dmp silent (windows) tesm dbupgrade etc/temp_dir/file.dmp silent (UNIX)
enableJmx/disableJmx
tesm enableJmx/tesm disableJmx

Operation

This command either enables or disables JMX on the master without the master running.

Examples

This command enables JMX on the master:

Example: tesm enableJmx

This command disables JMX on the master:

Example: tesm disableJmx

ft

tesm ft on/off

Operation

Configures fault tolerance to either on or off by updating the Sysval table in the database. If the flag is set to on, then it checks to verify if the backup master and fault monitor exists.

Examples

This command turns fault tolerance on:

Example: tesm ft on

keystoremgr

tesm keystoremgr -svc <service> -reload

Operation

This command carries out management tasks on the keystore(s) maintained by TA.

Examples

  • -svc <service> specifies service name to target the command to a particular Adapter service. This is the base name of Adapter service package.

    Example: For "webservice.pkg", the base name is "webservice".

  • Use the value ALL in place of <service> to broadcast the command to all active adapters.

    Example: -svc ALL. -reload instructs the recipient(s) to reload keystore.

listnode

tesm listnode [-f Comma-separated-field-names] [-d Delimiter] [-c Comma-separated-filter-conditions]

  • -f Comma-separated-field-names

    Only these field names can be specified in the option: name, machine, port, description, joblimit, active.

  • -d Delimiter

    Delimiter can be any single character used to delimit fields in the output. By default, space is used as a delimiter.

  • -c Comma-separated-filter-conditions

    These conditions can be specified to filter the list of agents or adapter connections:

    active=y, active=n, enabled=y, enabled=n, type=agent, type=adapter.

Operation

Lists the information on Agents or Adapter Connections. This command is available only when the master is running.

Example

Example: tesm listnode -f name,machine -d : -c type=adapter,active=n,enabled=.

Lists the name and hostname of Adapter Connections that are inactive and disabled.

logvalue

tesm loglevel –D logvalu

Operation

Updates the log level in the database for user to debug the master. This command will work even when the master is not running.

Examples

The command updates the log level in the database for debugging purposes to Severe.

These levels are available:

  • SEVERE

  • WARNING

  • INFO

  • LOW

  • MEDIUM

  • HIGH

pause

tesm pause

Operation

Pauses the production schedule. No waiting jobs will run; even if their dependencies are met. The flag in the database is also updated

Examples

The command pauses the production schedule:

Example: tesm pause.

resume

tesm resume

Operation

Resumes the production schedule after being paused. The flag in the database table sysval will be updated to reflect this status.

Examples

The command resumes the production schedule after being paused:

Example: tesm resume.

setpwd

tesm setpwd old password new password or test setpwd

Operation

Allows you to change the database password, even if the master is not running. This command updates the database directly when the master is not running to change the database password.

Examples

  • The command changes the old password (tidal123) to the new password (tidalabc):

    Example: tesm setpwd tidal123 tidalabc.

  • The command tests a password:

    Example: test setpwd.

superuseradd

tesm superuseradd userid domainname

Operation

This command adds a superuser and domain to the master.

Examples

The command adds the superuser, tidaluser, and the domain, tidalsoft, to the master.

Example: tesm superuseradd tidaluser tidalsoft

systemvalue

tesm systemvalue [-i ID] [-string value] [-integer value]

where:

  • -i ID – The ID of the sysval. Specify ALL to display values for all sysvals.

  • -string value – The string to use for sysval_string.

  • -integer value – The integer value to use for sysval_integer.

Operation

The systemvalue command lists or sets system values while the master is running. Only certain supported system values can be set this way. To get a list of system values that can be updated with this command, execute the command without any arguments. If you only specify an ID without any new values, then the current values for that sysval will be returned. If you specify an ID of ALL without any new values, then the current values for all defined sysvals will be returned, including sysvals that cannot be udpated with this command.

validatepurge

The validatepurge command validates log data for jobs based on a specified period of time. This data can range from data logged about audits, errors and alerts pertaining to jobs, to data directly related to past job instances.

tesm validatepurge [date]

validatepurge -options

Option

Description

date

Logs and Job history from the specified date and older are validated.

Operation

Use this format when specifying the date option: YYYYMMDD

  • If date option is specified, then the logs data and the job history are validated.

  • If no option denoting a date is used, then the log data and job history is validated starting from the current date.

Example

  • This example validates the log data and job history is validated starting from the current date:

    Example: tesm validatepurge

  • This example validates the log data and job history for all the jobs that ran on February 1, 2018 and earlier:

    Example: tesm validatepurge 20180101.