V. LAS REPRESENTACIONES DEL PROFESORADO SOBRE SU PRÁCTICA
V.4. NECESIDADES Y PROPUESTAS DE MEJORA
V.4.3. Con respecto al aprendizaje de los alumnos y alumnas
If this is a new installation of Teradata TARA, configure logging only after you have completed the first four steps described in “Configure the TARA Server” on page 53. If this is not a new installation of Teradata TARA, there is no required order of configuration.
To configure logging
1 [Optional] Check Enable Audit Log to track TARA Server configuration changes. See “TARA Server Audit Log” on page 151 for more information.
2 [Optional] Clear the Override Global Log Level box to change the log level. The Global Log level is pre-set to 32, which is the minimum, or normal, log level. The maximum level is 63. Increasing the Global Log level adds verbosity to the log for each TARA server component.
3 [Optional] Change other logging levels in the dialog box. Logging levels of the individual components of the TARA server are pre-set and cannot be changed unless the Override
Global Log Level check box is selected.
Note: Do not customize log settings unless Teradata Customer Support recommends it.
Configure the Log File
The default size of the Linux TARA server's logfile is 2GB. When this limit is reached, the TARA server saves the existing log as logfile.prev, then creates a new logfile before writing more
log entries. Do not set the value greater than 2GB. Doing so can cause the TARA server to become unresponsive.
Adjust the logfile maximum length to a value less than 2GB by adding an entry within the [Defaults] stanza of the:
• /etc/opt/teradata/tara/defaults file (Linux)
• <install_path>/teradata/tara/server/config/defaults file (Windows)
Example
Specify the file size in bytes:
filesize=numofbytes
For example, to set the log file size to exactly 500MB (500 * 1024), type:
After completing installation and configuration, you can start Teradata backup and restore operations through the Teradata TARA GUI.
This chapter includes the following topics:
• Starting the Teradata TARA GUI
• Archiving a Database Object
• Selecting Individual Objects to Archive or Restore
• Restoring a Database Object
• Restoring a Multistream Archive Using Fewer Streams
• Manually Restoring Multistream Archive Using Fewer Streams
• Restoring the DBC Database Backup Job
• Valid Keywords
• Validating Edited Job Scripts
• CopyScript Options
• Viewing Job History
• Deleting Failed Jobs in Job History
• Aborting Jobs
• Searching for Strings in Job Logs
• Extensions for Job Files
• Deleting Temporary Files in baruser Directory
Starting the Teradata TARA GUI
To start the Teradata TARA GUI
1 To check the status of the TARA server service, type:
/etc/init.d/tdtaraserver status
2 To start the TARA server service, type:
3 To start the Teradata TARA GUI:
• For Linux, type one of the following:
• /opt/teradata/tara/gui/bin/taragui &
• cd /opt/teradata/tara/gui/bin./taragui &
• For Windows, do one of the following:
• Double-click on if you installed the TARA GUI icon on your desktop.
• Click Start>All Programs>Teradata Client>TARA GUI. The Logon to TARA Server dialog box appears.
4 Enter the previously configured password.
The Teradata Tiered Archive/Restore Architecture dialog box appears.
Displaying Help
• There are problems displaying numbered lists when viewing help with Internet Explorer V8.0. To remedy this problem, enable the browser setting to be compatible with Internet Explorer V7.0.
• When using a Linux operating system, the icon to expand a database tree is displayed as .
• When using a Windows operating system, the icon to expand a database tree is displayed as .
Archiving a Database Object
You must log on to Teradata Database before you can select objects to archive or use Auto Generate to automatically archive databases.
• “To log on to Teradata Database” on page 67
• “To archive a database object” on page 67
• “To use Auto Generate to archive databases” on page 73
To log on to Teradata Database
1 Click Teradata Tiered Archive/Restore Architecture>Task>Archive. The Log on to Teradata
DBS dialog box appears.
2 To log on to a Teradata Database, select it from the TDPID list.
3 Type a user account name for the Teradata Database in the UserID box.
4 Type the password for the user account in the Password box, then click Connect. The
ARCHIVE object selection dialog box appears.
To archive a database object
1 In the left and right panes of the ARCHIVE object selection dialog box are database objects that are available for archival. To archive a database, highlight or select the box next to the
database in the left pane. The tables of the database to be archived appear in the right pane, as shown in the next screen capture.
2 Right-click on a table in the right pane, then click Options. A dialog box for Partitioned Primary Index (PPI) options appears for that table.
3 Under Partition selection, click on one of the radio buttons:
• Full table, which is the default, archives the entire table
• All Partitions option is not valid for archive operations
• Selected Partitions archives the specified partitions
Other PPI Options is not valid for archive operations.
4 From the ARCHIVE object selection File menu, click Build ARC script or click . After the database objects are selected, the Selection dialog box appears.
5 Click OK. The Script Options dialog box appears.
Option Description
Job Name Entries in Job Name are case-sensitive. A job name must not contain any spaces, or these characters:
< > ~ " * , ? . \ /
The maximum length of the job name for Archive and Restore scripts is 220 characters. If this limit is exceeded, an error message requests that the job name be re-entered.
Description
TDPID The entry in this box reflects the TDPID with which you logged on. It is not possible to change the TDPID.
User Name The user name with which you logged on appears. To create another job for the specified database, type a new user name.
Password The password with which you logged on appears. To create another job for the specified database using another user name and password, type the new password.
Single stream or Multi stream
Click Single stream or Multi stream. For Multi stream, type the number of streams in the Multi stream box. The number of streams is essentially the number of BAR server tape drives that are configured. For example, if there are four BAR servers, each having two tape drives, enter eight streams. Default Group The list defaults to all clients, which are assigned to streams in a round-robin
manner. For example, if there are six streams and four clients, the stream assignment is:
• Client1 is assigned to Stream1 • Client2 is assigned to Stream2 • Client3 is assigned to Stream3 • Client4 is assigned to Stream4 • Client1 is assigned to Stream5 • Client2 is assigned to Stream6
If there are many clients, select a name from the list of available client groups. Using a client group reduces the amount of selections needed when building a new archive or restore job.
Assign Clients Each stream is defaulted to All clients. Click Assign Clients to assign a specific client (or a specific client group) to each stream.
Configure Protegrity Encryption
This option is no longer valid. The Crypto Key Management System (KMS) replaces Protegrity encryption.
QueryBanding [Optional] Select QueryBanding. In the QueryBanding box, specify one or more pairs of names with associated values to identify the source of a query. This allows setting different priorities for different requests, and the ability to make better use of system resources.
For example, enter a name and value pair, ending with a semi-colon:
aaa=bbb;ccc=ddd;
Online Backup [Optional]
1 Select Online Backup to archive rows from a table at the same time update, insert, or delete operations on the table are taking place. When an online archive is initiated on a table or a database, a log is created for the specified table or separate logs are created for each table in the specified database. The log, which contains all changes to the table, is saved as a part of the archive process. When the table is restored or copied, the changes recorded in the log are used to roll back those changes in the table. The table is rolled back to the point that was established when online archive logging was started on that table. 2 In the drop-down list, select Default or NoSync.
With the NoSync option, no read or access lock is placed on the database and the tables are not synchronized. The tables do not have a shared consistency point. Instead, each table has its own consistency point for restore jobs. The primary purpose of NoSync is to minimize the effect of transactions writing to the database.
See Teradata Archive/Recovery Utility Reference for more information on online archive.
Sessions (per stream)
The default for the selected database is set in the Teradata tab of the TARA
Server Configuration dialog box. A general rule is to have one session per amp being archived in the stream. An adequate number of parallel ARC sessions per stream are necessary to keep data moving. Too few sessions cause ARCMAIN to be the bottleneck during archival. Too many sessions waste resources because some of the sessions remain idle. Refer to Teradata Archive/Recovery Utility Reference for more detail.
Extra Options [Optional] Enter any ARCMAIN command line options that are not part of the GUI ARC build flow. IOTRACE=5, a debug parameter that ARCMAIN uses to enable a level of tracing, is the default.
Backup Application
The default is Tivoli.
Full Backup or Dictionary Only
[Optional] Select Dictionary Only from the drop-down list to archive only the dictionary, or allow the Full Backup selection to archive the dictionary and data.
If you choose Dictionary Only, specify only one stream per job.
Use Catalog [Optional] Select Use Catalog to specify positioning data, so that when an object is restored, Tivoli can locate it without searching the entire tape. Verify
Checksum
[Optional] Verify Checksum verifies that the data being archived is valid. The checkbox is selected by default. However, the overhead of error checking slows the archive process. To improve performance, clear the checkbox.
Note: Job scripts created prior to clearing the Verify Checksum box have the verify checksum feature enabled by default.
Force online logging off
[Optional] To stop online logging: 1 Check the Online Backup box.
2 Check the Force online logging off box.
Normally, Teradata ARC allows online logging to continue even when a job fails or is aborted. Log files can become so large that subsequent attempts to archive the same database result in job failure.
Turning online logging off avoids the problem of log files becoming too large if a job fails or is aborted.
An ONLINE LOGOFF job is created and runs immediately after the parent job completes, except when the TARA server aborts the parent job because no connection could be made to stream 1 within 10 minutes. The ONLINE LOGOFF job is also aborted for connection failure after 10 minutes.
Note: The ONLINE LOGOFF job can be aborted from the GUI, regardless of its state.
Character set The default is UTF-8. Select another character set if appropriate. Management
Class
Click to display the Management Class Selection dialog box. Select one of the following:
• A group from Use Configuration from Group
• A management class for a stream after selecting Manual Selection Other Buttons
Save Click Save to accept the current script. Launch Click Launch to launch the job.
Preview [Optional] Click Preview to open the Script Editor dialog box and display the job script. The job script can be edited, then saved. Click Launch to launch the job.
Close Click Close to close the Script Options dialog box.
7 Click Save, then Launch.
The Teradata Tiered Archive/Restore Architecture dialog box displays the launched job. Under the jobname, each of the job's streams appears. To view the ARC progress for the streams, double-click on one of the streams. In the next example, the State column indicates that Stream 1 has table data. The state conditions are:
• (B): Build phase (only for restore operations)
• (D): Dictionary (for archive and restore operations)
• (T): Table Data (for archive and restore operations)
To use Auto Generate to archive databases
The Auto Generate feature automatically generates the scripts required for archiving only the DBC database or all databases except the DBC database.
1 From the ARCHIVE object selection dialog box, click File>Auto Generate. The Auto Generate dialog box appears.
2 Select one of the following:
• Archive DBC database only
• Archive all databases except DBC database
An ARC script is automatically generated for the selected archive job.
3 [Optional] Edit the ARC script.
4 Click OK.
The Auto Generate dialog box closes and the Script Options dialog box appears.
5 Enter a job name in Job name.
6 [Optional] Enter or change other options in the Script Options dialog box.
7 Click Save.
8 Click Launch.
Job status can be tracked in the State column of the Teradata Tiered Archive/Restore
Architecture dialog box.
Dictionary Only Archive
To create a Dictionary Only archive job
1 In the Script Options dialog box, select Dictionary Only from the Full Backup and Dictionary Only drop-down list.
TSM Parameters Overwrite at Runtime
TARA archive and restore jobs allow you to use Tivoli Storage Manager (TSM) options such as node name and password at runtime. They overwrite the node name and password options provided globally in the TARA Server Configuration - Tivoli panel. If the node name and password are provided for the Archive Script during runtime, ensure they are provided when the Restore Script is created.
To use TSM options
1 [Optional] For an archive job, access the parameters from the Script Options dialog box by clicking ManagementClass.
2 [Optional] For a restore job, access the parameters from the Script Options dialog box by clicking Options.
Selecting Individual Objects to Archive or
Restore
Beginning with Teradata Database 13.0, selecting an individual view, macro, procedure, or other Teradata object to archive or restore is valid. Prior to Teradata TARA 13.0, archiving and restoring was limited to databases and tables.
The prerequisites for this feature are version 13.0 or higher of:
• TARA
• Teradata ARC
• Teradata Database
In the next screen example, the DiskEvents macro in the guest database is the only object selected for archive.
Table 11 lists the icons that represent the objects.
Table 11: Object Icons
Icon Object Database Function Index Join Index Journal Macro
Restoring a Database Object
To restore a database
Use the next procedure to run a restore operation. Procedure
SQL-H
Table
Trigger
User Installed File
View
Table 11: Object Icons (continued)
1 Click Teradata Tiered Archive/Restore Architecture>Task>Restore. The RESTORE object
selection dialog box appears.
In the left pane are datasets (jobs). The names underneath the Datasets icon are backup images and are listed in chronological order (earliest image to latest image). Click to the left of the dataset name to expand the tree further.
2 To restore a job, select the box next to it. The name of the specified object appears in the upper right pane, and the Backup Application name in the lower right pane under Details. The screen capture shows a database example without a hierarchical view.
• If the database has a hierarchical view, go to step 3.
Double-click on the icon to the left of the object name to expand the tree and show the specific tables to be restored.
3 This screen capture shows a database with a hierarchical view. Double-click to navigate to a level in the left pane. The job and its tables appear in the right pane.
4 Right-click on the database icon or table in the right pane. A dialog box for copy and Partitioned Primary Index (PPI) options appears.
5 The options for the COPY options tab are:
Checking any of the boxes on this tab automatically selects the COPY script option of the
Script Options dialog box for restore operations.
6 On the PPI options tab, under Partition selection, click on the radio button for one of these three options:
Option Description
Rename Object Gives the object in the archive a different name from the target object.
Disable fallback on table (NO FALLBACK)
Copies fallback tables into non-fallback tables. If the archived table is already non-fallback, this option has no effect.
Disable journaling on table (NO JOURNAL)
Copies all tables with journaling disabled, whether journaled in the archive or not.
Replace table creator value (REPLACE CREATOR)
Replaces the LastAlterUID, creator name, and Creator ID of the tables in the target database with the user ID and the current user name, that is, the user name specified in the LOGON command. Specify different journal
table
Specifies that a copied database has journaling for the specified database and journal table.
APPLY TO list Identifies the tables in the target system where the change images apply.
• Full table, which is the default, restores the entire table
• All Partitions restores all partitions
• Selected Partitions restores the specified partitions
Under the Other PPI Options portion of the dialog box, select the LOG WHERE box to specify rows to be logged to an error table for manual insertion and deletion. Select the
Error table name box to enter a table name other than the default name that is shown.
Note: All PPI options are valid when restoring a table. Only the All Partitions option is valid when restoring a database.
7 Click RESTORE object selection>File>Build ARC script.
After the database objects are selected, the Selection dialog box appears.
8 Click OK. The Script Options dialog box appears.
Note: If you are restoring a job that backed up only the DBC database or all of the DBC database, the Restore DBC dialog box appears instead of the Script Options dialog box.
Option Description
Job Name Entries in the Job Name box are case-sensitive. A job name must not contain any spaces, or these characters:
< > ~ " * , ? . \ /
Note: Scripts that are created or modified manually are not checked to see if the name contains spaces or the characters listed above.
The maximum length of the job name for Archive and Restore scripts is 220 characters. If this limit is exceeded, an error message requests that the job name be re-entered.
Always restore latest [Optional] Check the Always restore latest box to automatically restore the last image that was backed up successfully.