Go to primary content

SQL Developer: TimesTen Support

If you connect to an Oracle TimesTen In-Memory Database, you can perform many TimesTen-specific operations within SQL Developer.

This topic adapts selected material from Oracle SQL Developer Oracle TimesTen In-Memory Database Support User's Guide, which is in the SQL Developer documentation library.

Testing Passwordless SSH Configuration

Passwordless SSH (secure shell) is required between all intended hosts for a grid in TimesTen Scaleout, regardless of the type of instance (management instance or data instance) on each host. Passwordless SSH is also required for any host that is used as a scp repository.

SQL developer provides a tool to test that each host in the grid can access one another through passwordless SSH. To test the passwordless SSH configuration of your hosts, ensure that you are on the main SQL Developer page and that you have enabled the TimesTen Grid view.

  1. In the TimesTen Grid view node, right-click the TimesTen Grid folder and select Test Passwordless SSH.
    The Test Passwordless SSH configuration dialog displays. Locate the Instance Administrator Credentials region.
  2. In the Instance Administrator text field, type the username of the instance administrator that will create and manage the grid.
  3. By default, the Use Password option is selected. In the Use Password text field, type the password of the instance administrator.

    Note:

    Alternatively, you can select the Use SSH key file option and use the Browse button to specify an SSH key file. The Use SSH key file option enables you to avoid having to specify the password of the instance administrator. You can generate this SSH key file on any of the hosts of your grid as long as you have successfully setup passwordless SSH between these hosts.


    Locate the Add Hosts button in the Hosts region.
  4. Click Add Hosts once for every host that you want to add to the grid topology.
  5. In the Host Address column of the hosts table, type the host address for every host that will be part of the grid topology.

    Note:

    In case that you are using different internal and external addresses for a host, use the internal host address.

  6. Click Test.
    The test can take several minutes depending on the number of hosts that you selected. In the Result column of the Details table and the Test Result column of the Hosts table, you should see the text "OK" for every host. If any host displays the text "Failed", ensure that the particular host is configured for passwordless SSH. Locate the Close button at the bottom of the dialog.
  7. Click Close
    The Test Passwordless SSH configuration dialog closes.
You have successfully tested the passwordless SSH configuration between all hosts for a grid in TimesTen Scaleout. You are now ready to create a grid.

Configure Your First Management Instance

To configure the first management instance for your grid:
The Simple Grid Wizard enables you to a create a single management instance. It is recommended that you create an additional management instance by creating a second management instance. See "Create a new management instance" for more information.
  1. In the Name text field, type a name for your grid. Select a name that is a meaningful identifier. The default value is grid1.
  2. Select a K-safety level from the K-safety list. It is recommended that you select a K-safety level of 2.
  3. In the Membership Configuration field, specify a ZooKeeper membership configuration file. You can specify the path of the file in the text field or you can use the Browse button to locate a file.
  4. If you want to specify a host name for the management instance that is different from the host name that the operating system assigns, deselect the Use Default check box. In the Host Name field, type a name for your management instance host. Select a name that is a meaningful identifier.
  5. In the Internal Address field, specify the internal address of the management instance.
  6. In the External Address field, specify the external address of the management instance.
  7. In the Instance Name field, type a name for your management instance. Select a name that is a meaningful identifier. The default value is instance1.
  8. In the Instance Location field, specify the directory where you want TimesTen to create the instance. TimesTen creates a directory with the instance name inside of the directory you specify. For example, if you have an instance name of instance1 and an instance location of /TimesTen/instance/, TimesTen creates your instance in the /TimesTen/instance/instance1/ directory.
  9. In the Daemon Port field, specify the port number for the TimesTen daemon. The default value is 6624.
  10. In the Client/Server Port field, specify the port number for the TimesTen client/server. The default value is 6625.
  11. In the Management Port field, specify the management port number. The default value is 3754.
    The management port is the value for the TCP/IP port number of the first management instance replication agent.
  12. In the Software Location field, specify the location of the TimesTen installation file. You can specify the path in the text field or you can use the Browse button to locate the file.
  13. In the Installation Location field, specify the directory where you want TimesTen to copy the install file. TimesTen copies the install file and then extracts the installation files. The installation files are extracted to a directory that is named based on the release number of TimesTen Scaleout. For example, if you are installing TimesTen Scaleout 18.1, the files are extracted to a tt18.1.1.1.0 directory inside of the installation location that you specified.
  14. If you want to specify a user group that will own the TimesTen installation that is different from the primary user group of the instance administrator, deselect the Use Default check box. In the TimesTen Group field, specify the user group that will own the TimesTen installation. All the installations and instances in the grid will be owned by this user group.
  15. In the Instance Administrator field, type the instance administrator of the management instance. Ensure that the instance administrator exists on all intended hosts with a common user ID and numeric UID.
  16. By default, the Use Password option is selected. In the Use Password text field, type the password for the instance administrator.

    Note:

    Alternatively, you can select the Use SSH key file option and use the Browse button to specify an SSH key file. The Use SSH key file option enables you to avoid having to specify the password of the instance administrator. You can generate this SSH key file on any of the hosts of your grid as long as you have successfully setup passwordless SSH between these hosts.


  17. To avoid SQL Developer prompts for the instance administrator password during future operations, select the Save Password check box.
    You are now ready to have SQL Developer validate your input values. Locate the Next button.
  18. Click Next.

SQL Developer validates your input values and displays a progress dialog. The validation can take a few minutes. If SQL Developer displays an error message, troubleshoot the error and click the Next button again to revalidate your input values.

The progress dialog closes and the Simple Grid Wizard dialog refreshes. You are now ready to add data instances.

Add Data Instances

To add data instances to your grid:

Note:

When you add a data instance, SQL Developer actually adds a host, an installation, and then an instance.

  1. Right-click the Data Instances folder and select New.
    You are now ready to add the information for your data instance. Locate the Host Name text field.
  2. If you want to specify a host name for the data instance that is different from the host name that the operating system assigns, deselect the Use Default check box. In the Host Name field, type a name for your data instance host. Select a name that is a meaningful identifier.
  3. In the Internal Address field, specify the internal address of the data instance.
  4. In the External Address field, specify the external address of the data instance.
  5. In the Instance Name field, type a name for your management instance. Select a name that is a meaningful identifier. The default value is instance1.
  6. In the Instance Location field, specify the directory where you want TimesTen to create the instance.
  7. In the Daemon Port field, specify the port number for the TimesTen daemon. The default value is 6624.
  8. In the Client/Server Port field, specify the port number for the TimesTen client/server. The default value is 6625.
  9. In the Installation Location field, specify the directory where you want TimesTen to copy the install file. TimesTen copies the install file and then extracts the installation files. The installation files are extracted to a directory that is named based on the release number of TimesTen Scaleout. For example, if you are installing TimesTen Scaleout 18.1, the files are extracted to a tt18.1.1.1.0 directory inside of the installation location that you specified.
    Locate the Save button.
  10. Click Save to save the configuration of your data instance.
    You have successfully added a data instance. When you add a data instance, SQL Developer actually adds a host, an installation, and then an instance. You are now ready to add additional data instances.

    You can add additional hosts with installations and data instances by:

    • Adding a new data instance.

      Right-click the Data Instances folder and select New. Then, follow the steps described in Add Data Instances.

    • Duplicating the configuration of another data instance.

      Right-click the data instance that you want to duplicate and select Duplicate. SQL Developer adds a new data instance with the same configuration values as the original data instance except for the host name, internal address, and external address. Ensure that you enter the values for the host name, internal address, and external address text fields.

    You can remove a data instance by right-clicking the data instance that you want to remove and select Delete.

  11. Once you have added all of your intended data instances to your grid, click Next.
    SQL Developer validates your input values and displays a progress dialog. The validation can take a few minutes. If SQL Developer displays an error message, troubleshoot the error and click the Next button again to revalidate your input values.

    The progress dialog closes and the Simple Grid Wizard dialog refreshes. You are now ready to assign your hosts to data space groups.

Assign Hosts to Data Space Groups

Organize the hosts that contain one full copy of the data into a single data space group. Since there are k copies of the data, there are an equal number of data space groups, which are numbered from 1 to kk is the value that you set for the K-safety configuration of your grid. The hosts in one data space group should be physically separate from the group of hosts in another data space group. Thus, hosts in one data space group are more likely to fail together; hosts in separate data space groups are less likely to fail simultaneously.

Once you have assigned a host to a data space group and you have applied that change to the grid model, you cannot change the data space group of that host.

To assign hosts to data space groups:

Right-click the host name that you want to assign to a data space group. Then, select the data space group where you want to assign the host.

Your host gets assigned to the data space group that you selected. Repeat this procedure to assign all of your hosts to data space groups. Ensure that you have the same amount of hosts in each data space group.

Once you have assigned all of your hosts to data space groups, click Next.

The Simple Grid Wizard refreshes and shows a summary table with the configuration for your grid.

Verify that the configuration settings for your grid are correct and click Finish.

The Simple Grid Wizard dialog closes and a Create Grid progress dialog displays. Creating a grid can take a few minutes depending on the number of hosts. If SQL Developer displays an error message, troubleshoot the error. In the case that an error file is generated, the Create Grid progress dialog displays the error file as a hyperlink. You can save the error file and troubleshoot any errors that are listed in the file.

Create a Grid with the New Grid Option

To use the new grid option to create a grid, ensure that you are on the main SQL Developer page and that you have enabled the TimesTen Grid view. To create a new grid with the new grid option:
  1. In the TimesTen Grid view node, right-click the TimesTen Grid Folder and select New Grid.

    If you are using the new grid option for the first time, a Passwordless SSH dialog displays. Ensure that you have completed the prerequisites that the dialog specifies. If you do not want to see the Passwordless SSH dialog when you use the Simple Grid Wizard, select the Skip This Message Next Time check box. Then, click the Yes button.

    You are now ready to configure your initial management instance.

  2. In the Name text field, type a name for your grid. Select a name that is a meaningful identifier. The default value is grid1.
  3. Select a K-safety level from the K-safety list. It is recommended that you select a K-safety level of 2.
  4. In the Membership Configuration field, specify a ZooKeeper membership configuration file. You can specify the path of the file in the text field or you can use the Browse button to locate a file.
  5. If you want to specify a host name for the management instance that is different from the host name that the operating system assigns, deselect the Use Default check box. In the Host Name field, type a name for your management instance host. Select a name that is a meaningful identifier.
  6. In the Internal Address field, specify the internal address of the management instance.
  7. In the External Address field, specify the external address of the management instance.
  8. In the Instance Name field, type a name for your management instance. Select a name that is a meaningful identifier. The default value is instance1.
  9. In the Instance Location field, specify the directory where you want TimesTen to create the instance. TimesTen creates a directory with the instance name inside of the directory you specify. For example, if you have an instance name of instance1 and an instance location of /TimesTen/instance/, TimesTen creates your instance in the /TimesTen/instance/instance1/ directory.
  10. In the Daemon Port field, specify the port number for the TimesTen daemon. The default value is 6624.
  11. In the Client/Server Port field, specify the port number for the TimesTen client/server. The default value is 6625.
  12. In the Management Port field, specify the management port number. The default value is 3754.
    The management port is the value for the TCP/IP port number of the first management instance replication agent.
  13. In the Software Location field, specify the location of the TimesTen installation file. You can specify the path in the text field or you can use the Browse button to locate the file.
  14. In the Installation Location field, specify the directory where you want TimesTen to copy the install file. TimesTen copies the install file and then extracts the installation files. The installation files are extracted to a directory that is named based on the release number of TimesTen Scaleout. For example, if you are installing TimesTen Scaleout 18.1, the files are extracted to a tt18.1.1.1.0 directory inside of the installation location that you specified.
  15. If you want to specify a user group that will own the TimesTen installation that is different from the primary user group of the instance administrator, deselect the Use Default check box. In the TimesTen Group field, specify the user group that will own the TimesTen installation. All the installations and instances in the grid will be owned by this user group.
  16. In the Instance Administrator field, type the instance administrator of the management instance. Ensure that the instance administrator exists on all intended hosts with a common user ID and numeric UID.
  17. By default, the Use Password option is selected. In the Use Password text field, type the password for the instance administrator.

    Note:

    Alternatively, you can select the Use SSH key file option and use the Browse button to specify an SSH key file. The Use SSH key file option enables you to avoid having to specify the password of the instance administrator. You can generate this SSH key file on any of the hosts of your grid as long as you have successfully setup passwordless SSH between these hosts.

  18. To avoid SQL Developer prompts for the instance administrator password during future operations, select the Save Password check box.
    You are now ready to have SQL Developer validate your input values. Locate the Create button.
  19. Click Create.

    SQL Developer validates your input values and displays a progress dialog. The validation can take a few minutes. If SQL Developer displays an error message, troubleshoot the error and create your grid with the new grid option again.

    The New TimesTen Grid dialog closes and the a progress dialog displays. Creating a grid can take a few minutes. If SQL Developer displays an error message, troubleshoot the error. In the case that an error file is generated, the Create Grid progress dialog displays the error file as a hyperlink. You can save the error file and troubleshoot any errors that are listed in the file.

You have successfully created a management instance for your grid. You are now ready to add an additional management host or data instances.

Manage an Existing Grid

If you created a grid with the ttGridAdmin utility, you can add the grid to the TimesTen Grid view. After you add your grid to the TimesTen Grid view you can manage and work with your grid in SQL Developer.

To add an existing grid to the TimesTen Grid view, ensure that you are on the main SQL Developer page and that you have enabled the TimesTen Grid view. To manage an existing grid:

  1. In the TimesTen Grid view node, right-click the TimesTen Grid Folder and select Manage an Existing Grid.
    The Manage an Existing Grid dialog displays. Locate the Host Address text field.
  2. In the Host Address field, specify the external address of the active management instance of your grid.
  3. In the Instance Home field, specify the instance home directory of your active management instance.
  4. In the Instance Administrator field, type the instance administrator of the active management instance.
  5. By default, the Use Password option is selected. In the Use Password text field, type the password for the instance administrator.

    Note:

    Alternatively, you can select the Use SSH key file option and use the Browse button to specify an SSH key file. The Use SSH key file option enables you to avoid having to specify the password of the instance administrator. You can generate this SSH key file on any of the hosts of your grid as long as you have successfully setup passwordless SSH between these hosts.

  6. To avoid SQL Developer prompts for the instance administrator password during future operations, select the Save Password check box.
    You are now ready to have SQL Developer validate your input values. Locate the Test button.
  7. Click Test.

    A progress dialog displays. The test process can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Once the test process completes, a Test Grid Existence dialog displays. Locate the OK button.

  8. Click OK.
    The Test Grid Existence dialog closes. You are now ready to save the configuration of your existing grid.

    Locate the OK button.

  9. Click OK.

    SQL Developer validates your input values and displays a progress dialog. The validation can take a few minutes. If SQL Developer displays an error message, troubleshoot the error and fix any invalid input values.

    Once SQL Developer completes validation, a Manage an Existing Grid confirmation dialog displays. Locate the OK button.

  10. Click OK.
    The Manage an Existing Grid dialog closes.
You have successfully added an existing Grid to SQL Developer. You are now ready to manage and work with your grid in SQL Developer.

Shutdown a Grid

SQL Developer enables you to shutdown the components of a grid, such as databases, data instances, and management instances.

To shutdown a grid, ensure that you are on the main SQL Developer page and that you have enabled the TimesTen Grid view.


Note:

If you unload a database, stop a data instance, or stop a management instance and the progress dialog does not progress, you can cancel out of the progress dialog. Then, click Next and SQL Developer displays a warning message that a database is loaded or an instance is started. Click Yes to proceed to the next shutdown step.

  1. Right-click the name of your grid, select Grid Control, then select Shutdown.

    The Shutdown Grid Wizard dialog and Updating databases information progress dialog display.

    The Updating databases information progress dialog closes. If a database has open connections, click the link in the Applications Connection column of the database table to view active connections to a specific database. Ensure that you close all applications that are connected to the database before shutting down a grid.

    Locate the Unload databases button.

  2. Click Unload databases.
    The Updating databases information progress dialog displays. Unloading databases can take a few minutes depending on the number of databases. If SQL Developer displays an error message, troubleshoot the error.

    Note:

    • For databases from a version prior to TimesTen Scaleout 18.1.2, if you are unable to disconnect an application from a database, SQL Developer may be unable to unload that database. If that is the case, you can cancel the unload databases process and go to step 3 to attempt to unload your data instances.
    • For databases from TimesTen Scaleout 18.1.2 or higher, you may use the Force All User Connections to Disconnect check box. SQL Developer will attempt to abort all user connections if it fails to terminate them by using the transactional and immediate modes. Forcing all user connections to disconnect may result in data loss.

    The Updating databases information progress dialog closes. In the output text area, you should see the text "All databases are unloaded."

    Locate the Next button.

  3. Click Next.

    The Shutdown Grid wizard dialog refreshes and the Updating instances information progress dialog displays. The Updating instances information progress dialog closes.

    Locate the Stop instances button.

  4. Click Stop Instances.

    Note:

    Optionally, select the Force action check box of a specific instance to forcefully stop that instance. Forcefully stopping an instance may result in data loss. It is recommended to have a backup of your data before forcefully stopping an instance.

    The Updating instances information progress dialog displays. Stopping instances can take a few minutes depending on the number of instances. If SQL Developer displays an error message, troubleshoot the error.

    The Updating instances information progress dialog closes. In the output text area, you should see the text "All data instances are down."

    Locate the Next button.

  5. Click Next.

    The Shutdown Grid wizard dialog refreshes and the Updating instances information progress dialog displays. The Updating instances information progress dialog closes.

    Locate the Stop instances button.

  6. Click Stop instances.

    The Updating instances information progress dialog displays. If SQL Developer displays an error message, troubleshoot the error.

    The Updating instances information progress dialog closes. In the output text area, you should see the text "All management instances are down."

    Locate the Finish button.

  7. Click Finish.
    The Shutdown Grid Wizard dialog closes.
You have successfully shutdown the components of a grid, such as databases, data instances, and management instances.

Start a Grid

SQL Developer enables you to start the components of a grid, such as management instances, data instances, and databases.

To start a grid, ensure that you are on the main SQL Developer page and that you have enabled the TimesTen Grid view.


Note:

If you load a database, start a data instance, or start a management instance and the progress dialog does not progress, you can cancel out of the progress dialog. Then, click Next and SQL Developer displays a warning message that a database is not loaded or an instance is stopped. Click Yes to proceed to the next startup step.

  1. Right-click the name of your grid, select Grid Control, then select Start.
    The Start Grid Wizard dialog and Updating instances information progress dialog display. The Updating instances information progress dialog closes.

    Locate the Start instances button.

  2. Click Start instances.

    The Updating instances information progress dialog displays. Starting instances can take a few minutes depending on the number of instances. If SQL Developer displays an error message, troubleshoot the error.

    The Updating instances information progress dialog closes. In the output text area, you should see the text "All management instances are up and running."

    Locate the Next button.

  3. Click Next.

    The Start Grid Wizard dialog refreshes and the Updating instances information progress dialog displays. The Updating instances information progress dialog closes.

    Locate the Start instances button.

  4. Click Start instances.

    The Updating instances information progress dialog displays. Starting instances can take a few minutes depending on the number of instances. If SQL Developer displays an error message, troubleshoot the error.

    The Updating instances information progress dialog closes. In the output text area, you should see the text "All data instances are up and running."

    Locate the Next button.

  5. Click Next.

    The Updating databases information progress dialog displays. The Updating databases information progress dialog closes.

    The Start Grid wizard dialog refreshes.

    Locate the Load databases button.

  6. Click Load databases.

    The Updating databases information progress dialog displays. Loading databases can take a few minutes depending on the number of databases. If SQL Developer displays an error message, troubleshoot the error.

    The Updating databases information progress dialog closes. In the output text area, you should see the text "All databases are loaded"

    Locate the Finish button.

  7. Click Finish.
    The Start Grid Wizard dialog closes.
You have successfully started your grid. Ensure that you open your databases before you attempt to connect applications to the database.

Apply Grid Model Changes to the Grid

After you add more objects to a grid model, you need to apply these components to the grid. Changes made to the model do not immediately impact a grid until you explicitly apply these changes. After you apply the changes, TimesTen Scaleout implements the changes made to the latest version of the model into the operational grid. For example, if you add a new installation and data instance to the latest version of the model, applying the changes to the model performs all of the necessary operations to create and initialize both the installation and the data instance in that host.

Applying grid model changes to the grid is a resource intensive operation. If you plan on making multiple changes to the grid model, make all the changes to your grid model before applying the changes to the grid.

To apply grid model changes to the grid, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded:

  1. Right-click the name of your grid, select Grid Model, then select Apply Changes.

    The Comparing current and latest grid dialog model dialog displays. Comparing grid models can take a few minutes.

    If SQL Developer does not find any changes between the current and latest grid model, the Comparing current and latest grid dialog model dialog displays the text "Latest model is up to date with current model". Click Close to close the dialog.

    If SQL Developer finds any changes between the current and latest grid model, a Changes in current grid model dialog displays. Locate the changes table.

  2. Review that the changes listed in the table are grid model changes that you want to apply to the grid.
  3. Click Yes.
    The Changes in current grid model dialog closes and a Apply Changes dialog displays. Applying changes to the grid model can take a few minutes depending on the number of grid model changes. If SQL Developer displays an error message, troubleshoot the error.
  4. Click Close.
    The Apply Changes dialog closes.
You have successfully applied the grid model changes to your grid.

Export the Grid Model

SQL Developer enables you to export the current model of your grid.

To export the current model of your grid, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

  1. Right-click the name of your grid, select Grid Model, then select Export.
    The Export Grid Model dialog displays. Locate the Choose Version to Export region.
  2. From the Choose Version to Export region, select a version of the configuration to export. These are the options:
    • Current - This is the current grid model that is applied to the grid.

    • Latest - This is the latest grid model that is not yet applied to the grid.

    • Version - This is the version of the configuration file that you can select. If you select this option, use the text field to the right of the Version radio button to select the version to export.

    Locate the Browse button.

  3. Click Browse.
    The Export file dialog displays. Specify the location of where you want to export the grid model file.
  4. In the File Name text field, specify a meaningful name for the grid model file and click Save.
    The Export file dialog closes. In the Export dialog, locate the Export button.
  5. Click Export.

    The Verifying File Location progress dialog displays. If SQL Developer displays an error message, troubleshoot the error.

    The Verifying File Location progress dialog and the Export Grid Model dialog close. The Export grid model progress dialog displays. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button.

  6. Click Close.
    The Export grid model progress dialog closes.
You have successfully exported a grid model file.

View the Changes to the Grid Model

SQL Developer enables you to view the changes between your current and latest grid model. These changes are not yet applied to your grid model.

To view the changes to your grid model, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

Right-click your grid node, select Grid Model, then select Show Changes.

The Comparing current and latest grid model progress dialog displays.

If there are no changes between your current and latest grid model, you see the message "Latest model is up to date with current model". Click Close.

If there are changes between your current and latest grid model, the Comparing current and latest grid model progress dialog closes and the Changes in current grid model dialog displays. Review the changes to your grid mode and click Close.

You have successfully viewed the changes between your current and latest grid model.

Define a New Physical Group

To add a physical group to the grid model, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.
  1. Expand the Grid Model option, right-click the Physical Groups option, then select New Physical Group.
    The New Physical Group dialog displays. Locate the Physical Group Name text field. Select a name that is a meaningful identifier.
  2. In the Physical Group name text field, specify the name of the physical group. Select a name that is a meaningful identifier.

    Note:

    Step 3 is only required if you want to assign an existing host to the physical group. If you do not want to assign an existing host to the physical group, skip to step 4. Once you add a new host to the grid model, you are able to assign that host to a specific physical group.

  3. In the Excluded list, locate the row that contains the host name that you want to assign to your new physical group. Double click the host name. If you want to assign multiple hosts, double click the corresponding host name of any additional host.
  4. Click OK.

    The New Physical Group dialog closes and a Creating Physical Group progress dialog displays. Creating a physical group can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    If you are adding or editing a grid model object for the first time, a Apply Changes dialog displays. This dialog shows you a reminder to apply your changes to the grid model. If you do not want to see this dialog when you add or edit a grid model object, select the Skip This Message Next Time check box. Then, click the OK button.

    Locate the Close button in the Creating Physical Group progress dialog.

  5. Click Close.
    The Creating Physical Group progress dialog closes.
You have successfully added a physical group to the grid model. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes.

Assign or Remove hosts from a Physical Group

To edit a physical group, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.
  1. Expand the Grid Model option, expand the Physical Groups option, right-click the name of the physical group, then select Edit.
    The Add Hosts to Physical Group dialog displays. Locate the Excluded and Selected lists. Identify the hosts that you want to assign or remove from the physical group.
  2. In the Excluded list, locate the row that contains the host name that you want to assign to your physical group. Double click the host name. If you want to assign multiple hosts, double click the corresponding host name of any additional host.
  3. In the Selected list, locate the row that contains the host name that you want to remove from your physical group. Double click the host name. If you want to remove multiple hosts, double click the corresponding host name of any additional host.
    Review the Excluded list to ensure that the list contains the hosts that you want to remove from your physical group. Review the Selected list to ensure that the list contains the hosts that you want to assign to your physical group. Locate the OK button.
  4. Click OK.

    The Add Hosts to Physical Group dialog closes and a Assigning Physical Group progress dialog displays. Assigning hosts to physical groups can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button in the Add Hosts to Physical Group progress dialog.

  5. Click Close.
    You have successfully edited a physical group in the grid model. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Add a New Host

To add a new host to the grid model, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.
  1. Expand the Grid Model option, right-click the Hosts option, then select New Host.

    The New Host dialog displays. Locate the Host Name text field.

    In some cases, a Passwordless SSH dialog displays. Ensure that you have completed the prerequisites that the dialog specifies. If you do not want to see the Passwordless SSH dialog again, select the Skip This Message Next Time check box. Then, click the Yes button.

  2. If you want to specify a host name for the host that is different from the host name that the operating system assigns, deselect the Use Default check box. In the Host Name field, type a name for your host. Select a name that is a meaningful identifier.
  3. In the Internal Address field, specify the internal address of the host.
  4. In the External Address field, specify the external address of the host.
  5. From the Data Space Group drop-down list, select the data space group where you want to assign the host.

    Note:

    Steps 6-8 are only required if you are using physical groups. If you do not want to use physical groups, skip to step 9.

  6. To select a physical group for this host, click the Select button to the right of the Physical Group(s) field.
    The Physical Group(s) dialog displays. Locate the Excluded list.
  7. In the Excluded list, locate the row that contains the physical group to which you want to assign to your host. Double click the physical group name. If you want to assign your host to multiple physical groups, double click the corresponding physical group name of any additional physical group.
    Review the Selected list to ensure that the list contains the physical groups to which you want to assign your host. Locate the OK button.
  8. Click OK.
    The Physical Group(s) dialog closes and the New Host dialog refreshes. Locate the OK button in the New Host dialog.
  9. Click OK.

    The New Host dialog closes and a New Host progress dialog displays. Adding a new host can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button in the New Host progress dialog.

  10. Click Close.
    You have successfully added a new host to the grid model. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Clone a Host

Cloning a host enables you to create a host for an instance (management or data) by duplicating the configuration of an existing host, including its associated installations and instances.

To clone a host, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

  1. Expand the Grid Model option, expand the Hosts options, right-click the host that you want to clone, then select Clone.

    In some cases, a Passwordless SSH dialog displays. Ensure that you have completed the prerequisites that the dialog specifies. If you do not want to see the Passwordless SSH dialog again, select the Skip This Message Next Time check box. Then, click the Yes button.

    If you are cloning a management instance for the first time, a Management Instance dialog displays. Ensure that you are sure that you want to clone a management instance. If you do not want to see the Management Instance dialog when you clone a management instance, select the Skip This Message Next Time check box. Then, click the Yes button.

    The Clone Host dialog displays.

  2. If you want to specify a host name for the host that is different from the host name that the operating system assigns, deselect the Use Default check box. In the Host Name field, type a name for your host. Select a name that is a meaningful identifier.
  3. In the Internal Address field, specify the internal address of the host.
  4. In the External Address field, specify the external address of the host.
    You are now ready to clone the host. Locate the OK button.
  5. Click OK.

    The Clone Host dialog closes and a Clone Host progress dialog displays. Cloning a host can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button in the Clone Host progress dialog.

  6. Click Close.

Edit the host to change the physical group or data space group of this host. You can only change the data space group of this new host before applying model changes to the grid. See Edit a Host for more information.

You have successfully cloned a host. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Edit a Host

SQL Developer enables you to edit the data space group and physical group of a host.
To edit a host, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.
  1. Expand the Grid Model option, expand the Hosts options, right-click the host that you want to edit, then select Edit.
    The Edit Host dialog displays.
  2. From the Data Space Group drop-down list, select the data space group where you want to assign the host.
    Once you have assigned a host to a data space group and you have applied that change to the grid model, you cannot change the data space group of that host.
  3. To select a physical group for this host, click the Select button to the right of the Physical Group(s) field.
    The Physical Group(s) dialog displays. Locate the Excluded and Selected lists. Identify the physical group(s) to which you want to assign your host.
  4. In the Excluded list, locate the row that contains the physical group to which you want to assign your host. Double click the host name. If you want to assign your host to multiple physical groups, double click the corresponding physical group name of any additional physical group.
  5. In the Selected list, locate the row that contains the physical group from which you want to withdraw your host. Double click the host name. If you want to withdraw multiple physical groups, double click the corresponding physical group name of any additional physical group.
    Review the Excluded list to ensure that the list contains the physical groups from which you want to withdraw your host. Review the Selected list to ensure that the list contains the physical groups to which you want to assign your host. Locate the OK button.
  6. Click OK.
    The Physical Group(s) dialog closes. Locate the OK button in the Edit Host dialog.
  7. Click OK.

    The Edit Host dialog closes and the Edit Host progress dialog displays. Editing a host can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button in the Edit Host progress dialog.

  8. Click Close.
    You have successfully edited a host. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Assign Hosts to Data Space Groups

SQL Developer enables you to assign hosts to data space groups as long as the host is not already associated with a data space group. Once a host is assigned to a data space group, you cannot reassign that host.

To assign hosts to data space groups, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen grid view, and that your grid node is expanded.

  1. Expand the Grid Model option, right-click the Hosts options, then select Assign to Data Space Groups.
    The Assign Hosts to Data Space Groups dialog displays. Locate the host that you want to assign to a data space group.
  2. Right-click the host name that you want to assign to a data space group. Then, select the data space group where you want to assign the host.

    Note:

    If you have configured physical groups, you can click the Suggest Assignment button to have TimesTen Scaleout suggest data space groups for your hosts. Ensure that you have configured physical groups before using the Suggest Assignment button.

    Your host gets assigned to the data space group that you selected. Repeat this procedure to assign all of your hosts to data space groups. Ensure that you have the same amount of hosts in each data space group.

  3. Once you have assigned all of your hosts to data space groups, click OK.

    The Assign Hosts to Data Space Groups progress dialog displays. Assigning hosts to a data space group can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    The Assign Hosts to Data Space Groups progress dialog and the Assign Hosts to Data Space Groups dialog close.

You have successfully assigned hosts to data space groups. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Execute a Command on a Host

SQL Developer enables you to execute commands on hosts that are part of your grid. To execute a command on a host, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

Note:

This procedure opens the Execute command dialog which enables you to select any host on which you want to execute commands. The Execute command dialog also enables you to execute a command on multiple hosts simultaneously.

  1. Expand the Grid Model option, expand the Hosts options, right-click the host on which you want to execute a command, then select Execute Command.
    The Execute Command dialog displays. Locate the Excluded folder in the right part of the Execute Command dialog.

    Note:

    If you want to see the data space group of each host, check the Show Data Space Group check box that is located at the bottom of the Execute Command dialog. This option separates the hosts in the Included and Excluded folders based on the data space group of each host.

  2. In the Excluded folder, locate the host on which you want to execute a command. Right-click the host name and select Move. If you want to execute a command on additional hosts, right-click the corresponding host name and select Move for any additional hosts.
    Review the Included folder to ensure that the list contains the hosts on which you want to execute a command. Review the Excluded folder to ensure that the list contains the hosts on which you do not want to execute a command. Locate the Run Command text field.
  3. In the Run command text field, type the command that you want to execute on the hosts that you selected.
    Locate the Execute button.
  4. Click Execute.

    TimesTen Scaleout executes the command on all of the hosts that you selected. SQL Developer displays a tab with the output of every host. You can click on a host tab to view the output of the command for that specific host. You can save the output of a host by clicking the Save button. You can also save the output of every host by clicking the Save All button.

    You have successfully executed a command on a host from your grid. You can execute additional commands by typing the new command in the Execute command text field and then clicking the Execute button. Once you have finished executing commands on your hosts, locate the Close button.

  5. Click Close.
    The Execute command dialog closes.

Create a New Installation

SQL Developer enables you to create a new installation on a host that is part of your grid.
To create a new installation on a host, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.
  1. Expand the Grid Model option, expand the Hosts options, expand the host on which you want to create an installation, right-click the Installations option, then select New Installation.
    The New Installation dialog displays. Locate the Installation Name text field.
  2. In the Installation Name field, type a name for your installation. Select a name that is a meaningful identifier. The default value is installationn, where n is the next sequential number based on your highest numbered installation name. For example, if you have an installation named installation1, the default value is installation2.
    Locate the Select Source region of the New Installation dialog.
  3. In the Location field, specify the directory on your selected host where the TimesTen installation file can be copied.
  4. Select an installation source from the Select Source radio buttons. These installation sources are available:

Use Existing Source

The Use Existing Source option enables you to copy an existing TimesTen installation from a host that is part of your grid. Before selecting the Use Existing Source option, ensure that you have completed the steps up to step 3 from Create a New Installation.
  1. From the Host drop-down list, select the host that contains the existing installation that you want to copy.
    The Installation drop-down list refreshes with the available installations of the selected host. If the host that you selected does not contain any TimesTen installation, SQL Developer switches your source to New Source.
  2. From the Installation drop-down list, select the installation that you want to copy.
  3. Click OK.

    The New Installation dialog closes and the Creating Installation in grid model progress dialog displays. Creating a new installation can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button in the Creating Installation in grid model progress dialog.

  4. Click Close.
    You have successfully created a new TimesTen installation. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

New Source

The New Source option enables you to use new installation files from a host that is part of your grid. Before selecting the New Source option, ensure that you have completed the steps up to step 3 from Create a New Installation.
  1. From the Host drop-down list, select the host that contains the new installation files that you want to copy.
  2. In the Location field, specify the directory on your specified host where the TimesTen installation file are located.
  3. Click OK.

    The New Installation dialog closes and the Creating Installation in grid model progress dialog displays. Creating a new installation can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button in the Creating Installation in grid model progress dialog.

  4. Click Close.
    You have successfully created a new TimesTen installation. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Create a New Management Instance

To create a new management instance, ensure that you are on the main SQL Developer page and that you have enabled the TimesTen Grid view.
  1. Right-click the name of your grid, select Grid Management, then select New Management Instance.
    The New Management Instance dialog displays. Locate the Select Host region.
  2. From the Select Host drop-down list, select the host where you want to create the management instance.
    If you want to add a new host, click the New button next to the Select Host drop-down list.
  3. From the Select Installation drop-down list, select the installation that you want to use for the management instance. If you selected a host without an existing TimesTen installation, you need to create an installation on your selected host.
    If you want to create a new installation, click the New button next to the Select Installation drop-down list. See Create a New Installation for more information on the New Installation dialog.
  4. In the Instance Name field, type a name for your management instance. Select a name that is a meaningful identifier. The default value is instance1.
  5. In the Instance Location field, specify the directory where you want TimesTen to create the instance. TimesTen creates a directory with the instance name inside of the directory you specify. For example, if you have an instance name of instance1 and an instance location of /TimesTen/instance/, TimesTen creates your instance in the /TimesTen/instance/instance1/ directory.
  6. In the Daemon Port field, specify the port number for the TimesTen daemon.

    If you selected a host without a TimesTen instance, the default value for the TimesTen daemon port is 6624.

    If you selected a host with a TimesTen instance, the default value is the daemon port of your original instance plus 100. For example, if your original instance has a daemon port of 6624, the default value is 6724.

  7. In the Client/Server Port field, specify the port number for the TimesTen client/server.

    If you selected a host without a TimesTen instance, the default value for the TimesTen client/server port is 6625.

    If you selected a host with a TimesTen instance, the default value is the client/server port of your original instance plus 100. For example, if your original instance has a client/server port of 6625, the default value is 6725.

  8. In the Management Port field, specify the management port number.

    The management port is the value for the TCP/IP port number of the first management instance replication agent.

    If you selected a host without a TimesTen instance, the default value for the management port is 3754.

    If you selected a host with a TimesTen instance, the default value is the management port of your original instance plus 100. For example, if your original instance has a management port of 3754, the default value is 3854.

  9. Click OK.

    The Creating grid object(s) progress dialog displays. If your selected instance directory does not exist, a confirmation dialog displays to ensure that you want to create the new directory. If this warning dialog displays, click Yes.

    Creating a management instance can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    The Management Instance dialog closes.

    Locate the Close button.

  10. Click Close.
    You have successfully created a TimesTen management instance. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Replace a Management Instance

SQL Developer enables you to replace a management instance with a new instance. This is useful if you want to retire the host of an existing management instance and replace it with a new host.

You can only replace a management instance when your grid has an active and standby management instance.

If you replace the active management instance, TimesTen Scaleout promotes the standby management instance to the active management instance. Then, TimesTen Scaleout deletes your original active management instance and adds your new management instance as the standby management instance.

If you replace the standby management instance, TimesTen Scaleout deletes your current standby management instance and adds your new management instance as the standby management instance.

To replace an instance, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.
  1. Expand the Management Instances option, right-click the management instance, then select Replace.
    The Replace Management Instance dialog displays.
  2. From the Select Installation drop-down list, select the installation that you want to use for the management instance. If you selected a host without an existing TimesTen installation, you need to create an installation on your selected host.
    If you want to create a new installation, click the New button next to the Select Installation drop-down list. See Create a New Installation for more information on the New Installation dialog.
  3. In the Instance Name field, type a name for your management instance. Select a name that is a meaningful identifier. The default value is instance1.
  4. In the Instance Location field, specify the directory where you want TimesTen to create the instance. TimesTen creates a directory with the instance name inside of the directory you specify. For example, if you have an instance name of instance1 and an instance location of /TimesTen/instance/, TimesTen creates your instance in the /TimesTen/instance/instance1/ directory.
  5. In the Daemon Port field, specify the port number for the TimesTen daemon.

    If you selected a host without a TimesTen instance, the default value for the TimesTen daemon port is 6624.

    If you selected a host with a TimesTen instance, the default value is the daemon port of your original instance plus 100. For example, if your original instance has a daemon port of 6624, the default value is 6724.

  6. In the Client/Server Port field, specify the port number for the TimesTen client/server.

    If you selected a host without a TimesTen instance, the default value for the TimesTen client/server port is 6625.

    If you selected a host with a TimesTen instance, the default value is the client/server port of your original instance plus 100. For example, if your original instance has a client/server port of 6625, the default value is 6725.

  7. In the Management Port field, specify the management port number.

    The management port is the value for the TCP/IP port number of the first management instance replication agent.

    If you selected a host without a TimesTen instance, the default value for the management port is 3754.

    If you selected a host with a TimesTen instance, the default value is the management port of your original instance plus 100. For example, if your original instance has a management port of 3754, the default value is 3854.

  8. Click OK.

    The Replace Management Instance progress dialog displays. If your selected instance directory does not exist, a confirmation dialog displays to ensure that you want to create the new directory. If this warning dialog displays, click Yes.

    Replacing a management instance can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    The Replace Management Instance dialog closes.

    Locate the Close button.

  9. Click Close.
    You have successfully created a new management instance, deleted an old management instance, and set the new management instance as your standby management instance. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Create a New Data Instance

SQL Developer enables you to create a new data instance with a data instance wizard or directly on a specific host.

Consider the following before creating a new data instance:

  • Ensure that the hosts on which you create data instances for database distribution are assigned to a data space group. If you attempt to create a data instance on a host that is not assigned to a data space group, TimesTen Scaleout does not create that data instance. See Assign Hosts to Data Space Groups for more information on assigning a host to a data space group.

Use one of these options to create a data instance:

New Data Instance Wizard

To create a new data instance, ensure that you are on the main SQL Developer page and that you have enabled the TimesTen Grid view.

Right-click the name of your grid, then select New Data Instance.

Then follow the steps, starting on step 2, as described in Create a New Management Instance. You do need to specify a management port for a data instance.

New Data Instance on a Specific Host

SQL Developer enables you to create a new data instance on a host that is part of your grid.

To create a new data instance on a host, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

  1. Expand the Grid Model option, expand the Hosts options, expand the host on which you want to create an instance, right-click the Instances option, then select New Instance.
    The New Instance dialog displays. Locate the Instance Name text field.
  2. In the Instance Name field, type a name for your instance. Select a name that is a meaningful identifier. The default value is instancen, where n is the next sequential number based on your highest numbered instance name. For example, if you have an instance named instance1, the default value is instance2.
  3. In the Instance Location field, specify the directory where you want TimesTen to create the instance. TimesTen creates a directory with the instance name inside of the directory you specify. For example, if you have an instance name of instance1 and an instance location of /TimesTen/instance/, TimesTen creates your instance in the /TimesTen/instance/instance1/ directory.
  4. In the Daemon Port field, specify the port number for the TimesTen daemon. By default, the default value is the daemon port of your original instance plus 100. For example, if your original instance has a daemon port of 6624, the default value is 6724.
  5. In the Client/Server Port field, specify the port number for the TimesTen client/server. By default, the default value is the client/server port of your original instance plus 100. For example, if your original instance has a client/server port of 6625, the default value is 6725.
  6. From the Installation drop-down list, select the installation that you want TimesTen to use to create the instance. This drop-down list only shows available installations on the host on which you are creating the new instance.
    To use an installation that is located on a different host or use a new installation source, click the New button that is located next to the Installation drop-down list. See Create a New Installation for more information about the New Installation dialog.
  7. Click OK.

    The New Instance dialog closes and the New Instance progress dialog displays. If your selected instance directory does not exist, a confirmation dialog displays to ensure that you want to create the new directory. If this warning dialog displays, click Yes.

    Creating an instance can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button.

  8. Click Close.
    You have successfully created a TimesTen instance. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Start or Stop the Instance and Server

SQL Developer enables you to start or stop the TimesTen instance and the TimesTen server.
To start or stop the TimesTen instance or the TimesTen server, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.
  1. Expand the Grid Model option, expand the Hosts options, expand the host on which your instance is located, expand the Instances option, then right-click the instance and select one of these options:
    • Start - This option starts the TimesTen instance.

    • Start Server - This option starts the TimesTen server.

    • Stop - This option stops the TimesTen instance.

    • Stop Server - This option stops the TimesTen server.

    A confirmation dialog displays. Locate the OK button.


    Note:

    If you want to immediately start or stop a service and ignore warnings, select the Force Action check box.

  2. Click OK.
    The confirmation dialog closes. Starting or stopping a TimesTen instance or TimesTen server can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

Edit a Data Instance

SQL Developer enables you to edit the installation of a data instance.

Note:

You can only edit a TimesTen data instance. You cannot edit a management instance.

To edit a data instance, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.
  1. Expand the Grid Model option, expand the Hosts options, expand the host on which your instance is located, expand the Instances option, then right-click the instance and select Edit.
    The Edit Instance dialog displays.
  2. From the Installation drop-down list, select the new installation that you want to use for your instance.
  3. Click OK.

    The Edit Instance dialog closes and the Edit Instance progress dialog displays. Editing an instance can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button in the Edit Instance progress dialog.

  4. Click Close.
    The Edit Instance progress dialog closes.
You have successfully edited an instance. However, you need to apply your changes to the grid and restart your instance. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid and Start or Stop the Instance and Server for more information on applying model changes to a grid and restarting an instance, respectively.

Import a Configuration File

SQL Developer enables you to import multiple types of configuration files.

To import a configuration file, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

  1. Expand the Grid Model option, then right-click the configuration file name and select Import.
    The Import dialog displays. Locate the Browse button.
  2. Click Browse.
    The Import file dialog displays. Browse for your configuration file.
  3. Select your configuration file and click Open.
    The Import file dialog closes. In the Import dialog, locate the Import button.
  4. Click Import.

    The Verifying File Location progress dialog displays. SQL Developer verifies that the configuration file that you specified is a valid file. If SQL Developer displays an error message, troubleshoot the error.

    The Verifying File Location progress dialog and the Import Configuration dialog close. The Importing Configuration progress dialog displays. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button.

  5. Click Close.
    The Import Configuration progress dialog closes.
You have successfully imported a configuration file in the grid model. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Export a Configuration File

SQL Developer enables you to export multiple types of configuration files.

To export a configuration file, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

  1. Expand the Grid Model option, then right-click the configuration file name and select Export.
    The Export dialog displays. Locate the Choose Version to Export region.
  2. From the Choose Version to Export region, select a version of the configuration to export. These are the options:
    • Current - This is the current configuration file that is applied to the grid.

    • Latest - This is the latest configuration file that is not yet applied to the grid.

    • Version - This is the version of the configuration file that you can select. If you select this option, use the text field to the right of the Version radio button to select the version to export.

    Locate the Browse button.

  3. Click Browse.
    The Export file dialog displays. Specify the location of where you want to export the configuration file.
  4. In the File Name text field, specify a meaningful name for the configuration file and click Save.
    The Export file dialog closes. In the Export dialog, locate the Export button.
  5. Click Export.

    The Verifying File Location progress dialog displays. If SQL Developer displays an error message, troubleshoot the error.

    The Verifying File Location progress dialog and the Export Configuration dialog close. The Export Configuration progress dialog displays. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button.

  6. Click Close.
    The Export Configuration progress dialog closes.
You have successfully exported a configuration file from the grid model.

Create a Database with the Database Wizard

SQL Developer enables you to create a database in your grid with the database wizard. You can also create a database from a database definition.

Before you create a database:

  • Ensure that you have a functional grid.

  • Ensure that your grid has at least an equal amount of data instances to the K-safety level of your grid. For example if you have a K-safety level of 2, you need to have at least two data instances.

  • Ensure that each of your data space groups are associated with an equal amount of data instances. Hosts, not data instances, are assigned to data space groups. It is recommended that you have a single data instance on each host. See Assign Hosts to Data Space Groups for more information on assigning a host to a data space group.

To create a database, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

  1. Right-click the Databases option and then select New Database.

    The TimesTen Grid Database Wizard dialog and Comparing current and latest grid model progress dialog displays.

    If you have made changes to your grid model and have not applied the model changes, the Comparing current and latest grid model progress dialog closes and a Changes in current grid model dialog displays. This dialog displays objects that have been added, changed, or removed from the grid model. Creating a database involves applying the grid model changes, so ensure that you want these grid model changes to be applied. Locate the OK button of the Changes in current grid model dialog.

    See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

    If you have not made changed to your grid model, locate the Close button of the Comparing current and latest grid model progress dialog.

  2. Depending on the dialog that displays, either click OK or Close.

    Depending on the dialog that displayed, the Changes in current grid model dialog or the Comparing current and latest grid model progress dialog closes. The TimesTen Grid Database Wizard displays.

    Locate the Database Name field.

  3. In the Database Name text field, type a name for your database. Select a name that is a meaningful identifier. The default value is database1.

    Note:

    Optionally, you can import a database definition file to load attribute values for your database definition. The database definition file must use .dbdef as the file name extension.

    To import a database definition file, click the Import Definition button. Then, select your database definition file and click Open. If an attribute value was set in the wizard before you imported the database definition file, the attribute value changes to the value that is defined in the database definition file.

    Once you have imported the database definition file, you can still edit the database definition within the wizard. If you do not want to keep editing the database definition, skip to step 5.


    If your grid already contains a database, the default value of the database name of your original database plus 1. For example, if your original database name is database1, the default value is database2.

  4. Set the connection attributes for your database. You can set these connection attributes:
    • Data Store Attribute - Attributes that are set at database creation time.


      Note:

      Ensure that you set a valid path for the DataStore attribute. This path must be valid on every host for every data instance.

      It is best practice to specify LogDir and have it be a different location from DataStore.


    • First Connection Attribute - Attributes that are set when a database is loaded into memory.

    • General Connection Attribute - Attributes that are set by each connection and persist for the duration of the connection. These attributes are added to a connectable and not are part of a database definition.

    To set any attribute that is part of the type of connection attributes listed above, select the relevant tab. Each tab of connection attributes contains a list of attributes with default values. You can edit the value of an attribute by double clicking the value from the value column of an attribute. Depending on the connection attribute, you can edit the value with a text field or a drop-down list of valid values.

    You can add additional connection attributes by selecting a connection attribute from the drop-down list located below the connection attribute tabs and then clicking Add. If a connection attribute is not listed in the drop-down list, you can select the New Attribute option and enter the connection attribute name in the Attribute column of the connection attribute table.

    You can remove a connection attribute by selecting a connection attribute from the connection attribute table and then clicking Delete.

  5. Once you have set your connection attributes, click Next.

    SQL Developer validates your connection attribute values. If SQL Developer displays an error message, troubleshoot the error and click the Next button again to revalidate your input values.

    The Checking Directory Attributes dialog displays. Checking for a directory can take a few minutes. If your selected database directory does not exist on the host of a data instance, a confirmation dialog displays to ensure that you want to create the new directory on that host. If this warning dialog displays, click Yes.


    Note:

    SQL Developer creates the selected database directory on all hosts of available data instances.

    The Checking Directory Attributes dialog closes and the TimesTen Grid Database Wizard dialog refreshes. Locate the Database Distribution map.

  6. By default, the default value is the maximum number of data instances based on their data space group without leaving a replica set incomplete. Review the SQL Developer suggestion for data instances and perform any necessary modifications.

    Note:

    If you do not want to configure the distribution map in this wizard, check the Skip database distribution check box and click Next. See Define the Distribution Map of a Database for more information on defining a distribution map for a database.


    Note:

    Ensure that each data space group contains the same number of data instances to create complete replica sets. If your data space groups do not contain the same number of data instances, an error dialog displays after you click the Apply button.

    If you want to remove a suggested data instance, right-click the instance name and select Remove.

    If you want to add a data instance from the Available column, right-click the instance name and select Add.

  7. Once you have selected all of your data instances for data distribution, click Next.
    The TimesTen Grid Database Wizard refreshes and shows a summary table with the configuration for your database.
  8. Verify that the configuration settings for your database are correct and click Finish.

    Note:

    Optionally, click the Export Definition button to save the database definition as a .dbdef file.

    The TimesTen Grid Database Wizard dialog closes and a Creating Database progress dialog displays. Creating a database can take a few minutes depending on the number of data instances included in the distribution map. If SQL Developer displays an error message, troubleshoot the error. In the case that an error file is generated, the Creating Database progress dialog displays the error file as a hyperlink. You can save the error file and troubleshoot any errors that are listed in the file.


    Note:

    If SQL Developer displays an error or if you cancel the database creation process, review the grid navigator to see if the database and definition file were created. In case that a database or database definition was created, delete the database and database definition. Then, create a new database. See Destroy a Database for more information on deleting a database.


  9. Click Close.
    The Creating Database progress dialog closes.

You have successfully created a database in your grid.

Before you attempt to connect an application to the database, ensure that you open the database and create a user with the appropriate privileges to connect to the database. To create a user for your database with SQL Developer, use the ttIsql utility through the Execute command on a host dialog. You can execute this utility on any of the data instances of your database.

This command creates a user, terry, with a password of terry for the database, database1. Then, terry is granted admin privileges.

ttisql -e 'CREATE USER terry IDENTIFIED BY terry;

GRANT ADMIN TO terry; ' DSN=database1

See Execute a Command on a Host for more information executing a command on a host, respectively.

Create a Database Definition

SQL Developer enables you to create a database definition. To create a database definition, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

Note:

When you create a new database definition, TimesTen also creates a direct connectable for this new database definition.

  1. Expand the Grid Model option, right-click the Database Definitions option, then select New Database Definition.
    The New Database Definition dialog displays. Locate the Database Name field.
  2. In the Database Name text field, type a name for your database. Select a name that is a meaningful identifier. The default value is database1.

    Note:

    Optionally, you can import a database definition file to load attribute values for your database definition. The database definition file must use .dbdef as the file name extension. To import a database definition file, click the Import Definition button. Then, select your database definition file and click Open. If an attribute value was set in the wizard before you imported the database definition file, the attribute value changes to the value that is defined in the database definition file. Once you have imported the database definition file, you can still edit the database definition within the wizard. If you do not want to keep editing the database definition, skip to step 4.

    If your grid already contains a database, the default value is the database name of your original database plus 1. For example, if your original database name is database1, the default value is database2.

  3. Set the connection attributes for your database definition. You can set these connection attributes:
    • Data Store Attribute - Attributes that are set at database creation time.


      Note:

      Ensure that you set a valid path for the DataStore attribute. This path must be valid on every host for every data instance.It is best practice to specify LogDir and have it be a different location from DataStore.

    • First Connection Attribute - Attributes that are set when a database is loaded into memory.

    • General Connection Attribute - Attributes that are set by each connection and persist for the duration of the connection.

    To set any attribute that is part of the type of connection attributes listed above, select the relevant tab. Each tab of connection attributes contains a list of attributes with default values. You can edit the value of an attribute by double clicking the value from the value column of an attribute. Depending on the connection attribute, you can edit the value with a text field or a drop-down list of valid values.

    You can add additional connection attributes by selecting a connection attribute from the drop-down list located below the connection attribute tabs and then clicking Add. If a connection attribute is not listed in the drop-down list, you can select the New Attribute option and enter the connection attribute name in the Attribute column of the connection attribute table.

    You can remove a connection attribute by selecting a connection attribute from the connection attribute table and then clicking Delete.

  4. Once you have set your connection attributes, click OK.

    SQL Developer validates your connection attribute values. If SQL Developer displays an error message, troubleshoot the error and click the OK button again to revalidate your input values.

    The Checking Directory Attributes dialog displays. Checking for a directory can take a few minutes. If your selected database directory does not exist on the host of a data instance, a confirmation dialog displays to ensure that you want to create the new directory on that host. If this warning dialog displays, click Yes.


    Note:

    SQL Developer creates the selected database directory on all hosts of available data instances.

    The Checking Directory Attributes dialog closes and the Creating Database Definition progress dialog displays. Creating a database definition can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button.

  5. Click Close.
    The Creating Database Definition progress dialog closes.

You have successfully created a database definition and a direct connectable. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.


Note:

After creating a database definition, a database icon from your database definition displays under the Databases node of your grid node in SQL Developer. However, you are unable to perform database operation with this database until you create the database from your database definition.

Edit a Database Definition

SQL Developer enables you to edit an existing database definition.

Before you edit an existing database definition:

  • If you want to edit a database attribute and there is a database that was created from the database definition you are editing, you must stop the database, destroy it, and recreate it with the new database attributes. Since you are destroying the database, this causes you to lose all data in that database.

  • If you want to edit a general connection attribute, edit the respective connectable because general connection attributes are associated with a connectable. See Edit a Connectable for more information.

  • If you edit a first connection attribute of a database definition of an open database, these changes are not applied until you unload and reload the database. SQL Developer displays a warning message if your database is currently open when you edit the database definition.

To edit a database definition, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

Expand the Grid Model option, expand the Database Definitions option, right-click the name of your database definition, then select Edit.

The Edit Database Definition dialog and the Checking if database exists progress dialog display.

If there is an open database that was created from the database definition you are editing, the Checking if database exists progress dialog closes and a Editing open database warning dialog displays. If you do not want to see the Editing open database warning for future operations, select the Skip This Message Next Time check box. Then, click the OK button.

If there is no open database that was created from the database definition you are editing, the Checking if database exists progress dialog closes.

Follow the steps, starting on step 3, as described in Create a Database Definition.

Define the Distribution Map of a Database

SQL Developers enables you to define the distribution map of a new database from a database definition. You can also redefine the distribution map of an existing database. You cannot access a database that is in the process of defining or redefining its distribution map. To define the distribution map of a database, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

Note:

Redefining the distribution map of an existing database can take up to a few hours. Ensure that you do not need to access this database before redefining the distribution map.

  1. Expand the Databases option, right-click the name of your database, then select Redistribute.
    The Distribution for database dialog displays. Locate the Database Distribution map.
  2. If you want to add a data instance from the Available column, right-click the instance name and select Add.

    If you want to remove a suggested data instance, right-click the instance name and select Remove. If you want to replace the data instance that you are removing, select Remove and replace with and select the new data instance.

    If you want to evict a data instance, right-click the instance name and select Evict. Only evict a data instance if you are unable to fix that data instance and you have a backup of the data from that data instance. Evicting a data instance can result in data loss. If you want to replace the data instance that you are evicting, Select Evict and replace with and select the new data instance.


    Note:

    Ensure that each data space group contains the same number of data instances to create complete replica sets. If your data space groups do not contain the same number of data instances, an error dialog displays after you click the Apply button.

  3. Once you have selected all of your data instances for data distribution, click Apply.

    The Performing operations progress dialog displays. Defining the distribution map of a new database can take a few minutes. If you are redistributing the data of an existing database, the redistribution can take up to a few hours. If SQL Developer displays an error message, troubleshoot the error.

    Once the distribution map of your database is applied, the Performing operations progress dialog closes and the Distribution for database dialog refreshes. The distribution map shows how your data instances are distributed in replica sets and data space group.

    Locate the Close button.

  4. Click Close.
    The Distribution for database dialog closes.
You have successfully defined the distribution map of a database.

Perform Database Operations

SQL Developer enables you to start, load, open, stop, close, and unload the TimesTen database.

To start, load, open, stop, close, or unload the TimesTen database, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

Expand the Databases option, then right-click the name of your database and select one of these options:


Note:

Depending on the current state of your database, you may be unable to perform a certain operation. If SQL Developer is unable to perform a specific operation, an error or warning message displays. For example, you cannot open a database that is already open.

  • Start - Loads every element of the database into memory of their respective hosts and enables the database for user connections. This option does the same thing as if you perform a load and open operation of the database.
  • Load - Loads every element of the database into memory of their respective hosts.
  • Open - Enables the database for user connections.
  • Stop - Disables new user connections to a database and unloads every element of the database from the memory of their respective hosts. This option does the same thing as if you perform a close and unload operation of the database.
  • Close - Disables new user connections to a database.
  • Unload - Unloads every element of the database from the memory of their respective hosts

SQL Developer performs the operation that you selected. The operation can take a few minutes.


Note:

If you select the stop, close, or unload option, a warning dialog displays asking you to confirm that you want to continue with the operation.
  • For databases from a version prior to TimesTen Scaleout 18.1.2, the dialog contains a number hyperlink that you can click to view the current connections to your database.
  • For databases from TimesTen Scaleout 18.1.2 or higher, the dialog contains a Force All User Connections to Disconnect check box for the stop or unload options. If checked, SQL Developer will attempt to abort all user connections if it fails to terminate them by using the transactional and immediate modes. Forcing all users connections to disconnect may result in data loss.

A progress dialog displays in the lower right corner of the main SQL Developer window. If SQL Developer displays an error message, troubleshoot the error.

You can review the status of your database by double clicking the name of your database from the TimesTen Grid view region. If your database status is already open, you can click the refresh button that is located in the top left corner of the database status window to refresh your database status.

You have successfully performed an operation on the database.

Create a Connectable

SQL Developer enables you to create client/server and direct connectables.

To create a client/server or direct connectable, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

  1. Expand the Databases option, expand the name of your database, then either right-click the Client/Server Connectables or Direct Connectables option and select New Connectable.
    The New Connectable dialog displays. Locate the Connectable Name text field.
  2. In the Connectable Name text field, type a name for your connectable. Select a name that is a meaningful identifier.
  3. From the Connect to instance drop-down list, select a specific instance that applications connect to through the client/server DSN. The default value is Any Instance which lets your application connect to your database through any available data instance.

    Note:

    Optionally, you can import a connectable file to load connection attribute values for your connectable. The connectable file must use .connect as the file name extension.

    To import a connectable file, click the Import Definition button. Then, select your connectable file and click Open. If a connection attribute value was set in the wizard before you imported the connectable file, the connection attribute value changes to the value that is defined in the connectable file.

    Once you have imported the connectable file, you can still edit the connectable definition within the wizard. If you do not want to keep editing the connectable definition, skip to step 5.


  4. Set the connection attributes for your connectable.

    You can add additional connection attributes by selecting a connection attribute from the drop-down list located below the Connect to instance drop-down list and then clicking Add. If a connection attribute is not listed in the drop-down list, you can select the New Attribute option and enter the connection attribute name in the Attribute column of the connection attribute table. Depending on the connection attribute, you can edit the value with a text field or a drop-down list of valid values.

    You can remove a connection attribute by selecting a connection attribute from the connection attribute table and then clicking Delete.

  5. Once you have set your connection attributes, click OK.

    The New Connectable dialog closes and the Creating connectable progress dialog displays. Creating a connectable can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button.

  6. Click Close.
    The Creating connectable progress dialog closes.
You have successfully created a connectable for your database. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Edit a Connectable

SQL Developer enables you to edit an existing connectable.

To edit a connectable, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

Expand the Grid Model option, expand the Database Definitions option, expand the name of your database, then either expand the Client/Server Connectables or Direct Connectables option, right-click the name of the connectable and select Edit.

The Edit Connectable dialog displays.

Follow the steps, starting on step 3, as described in Create a Connectable.

View Active Connections to the Database

SQL Developer enables you to view all active connections to a database. This is useful to determine if it is safe to perform certain database operations like destroying a database or closing a database.

To view active connections to a database, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

Expand the Databases option and select the name of your database.

The database status displays or refreshes if it is already displayed. Locate the connections link that is next to the Number of applications connected to the database_name label.

Click the connections link that is next to the Number of applications connected to the database_name label.

The Updating information for database progress dialog displays. Once the database information has been loaded, the Updating information for database progress dialog closes and the Connection Details dialog displays.

The Connection Details dialog enables you to view all connections to your database data instances or specific data instances. Use the Instance drop-down list to select an instance for which you want to see its connection. In case that you want to see system connections, select the Include System Connections check box. You can also use the Connection Name text field to create a filter for all available connections to your selected instance.


Note:

For databases from TimesTen Scaleout 18.1.1.3 or higher, selecting a row from the connections table provides below additional information on the element, host, instance, connection id, connection name, process id, and type of connection. For proxy connections, it also provides information on the host, instance, connection id, and process id of the proxy. For client/server connections, it also provides information on the host, address, and connection id of the client.

Click the OK button to close the Connection Details dialog.

Destroy a Database

SQL Developer enables you to destroy a database.

Before you create a grid:

  • Ensure that you have migrated or backed up all data from the database.

  • Ensure that the database is unloaded from memory.

To destroy a database, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.

  1. Expand the Databases option, then right-click the name of your database and select Destroy.

    The Destroy database dialog displays.

    Ensure that there are no active connections to your database before proceeding. Click the number hyperlink near the top of the dialog to view the connection details of your database. Ensure that there are no critical connections to your database or properly close any active connections.

    If there are 0 active connections to the database, you are ready to proceed.

  2. In the text field, enter the instance administrator name.
  3. If you want to delete the database definition of your database, click in the check box to the left of the text Delete database definition.
  4. Click OK.

    The Destroying database dialog displays. Deleting a database can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    The Locate the Close button.

  5. Click Close.
    The Destroying database progress and Destroy database dialogs close.
You have successfully deleted a database. However, you need to apply your changes to the grid. Changes made to the grid model do not immediately impact a grid until you explicitly apply these changes. See Apply Grid Model Changes to the Grid for more information on applying model changes to a grid.

Create a Repository

To create a new grid repository, ensure that you are on the main SQL Developer page, that you have enabled the TimesTen Grid view, and that your grid node is expanded.
  1. Expand the Grid Model option, right-click Repositories and select Create Repository.
    The Create Repository dialog displays. Locate the Repository Name field.
  2. In the Repository Name field, specify the name for the repository.
  3. In the Location field, specify a location that is mounted using NFS on each host or as a directory path that is accessible on each host with SSH or SCP.
  4. From the Method drop-down list, select a mounting option:
    • Mount - Creates a repository as a directory path mounted using NFS on each host of your grid.

    • SCP - Creates a repository as a directory path that is not directly mounted on each host of your grid.

  5. If you selected the SCP method, specify the fully qualified domain name of the host on which the repository exists in the Address field.
  6. Click OK.

    The Create Repository dialog closes and the Create Repository progress dialog displays. Creating the repository can take a few minutes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button in the Create Repository progress dialog.

  7. Click Close.
    The Create Repository progress dialog closes.
You have successfully created a repository. This repository is now available in the repositories folder of your grid model.

Inspecting Logs

SQL Developer enables you to review the support and user log of a TimesTen Scaleout. These logs may be useful in troubleshooting errors with your grid. For each instance that is part of your grid, you can view these logs:

  • Support Log

  • User Error Log

To view logs, ensure that you are on the main SQL Developer page and that you have enabled the TimesTen Grid view.

  1. Right-click your grid node, select Inspect Logs, then select Support Log or User Error Log.
    Depending on the option that you select, the Inspect Support Log or Inspect User Error log dialog displays.
  2. In the Available instance folder, locate the instance for which you want to view a log. Right-click the instance name and select Load/Unload. If you want to view a log of additional instances, right-click the corresponding instance name and select Load/Unload for any additional instances.

    Note:

    In case the log panel expands and hides the instance panel of the dialog, place your cursor at the left edge of the log panel and use the resize arrow to resize the log panel.

    If you want to close a log of an instance, locate the instance in the Showing Logs folder for which you want to close a log. Then, right-click the instance name and select Load/Unload.

    If you want to create filters, save the filtered logs, refresh logs, or perform various other operations with the logs, click the Logs menu button. The Logs menu button is located in the top left corner of the Inspect Support Log or Inspect User Error log dialog.

  3. After you finish reviewing the log, click Cancel.
    Depending on the option that you select, the Inspect Support Log or Inspect User Error log dialog closes.
You have successfully reviewed the support log or user error log of the instances of your grid.

Create a Table

You can create a table for the TimesTen database or TimesTen Grid database with SQL Developer.

To create a table, ensure that you are on the main SQL Developer page and that your TimesTen or TimesTen Grid connection is expanded.

  1. Right-click the Tables option and select New Table.
    The Create Table dialog displays. Locate the Schema drop-down list.
  2. From the Schema drop-down list, select the owner of the table.
  3. In the Name text field, type a name for the table.
    You are now ready to define the columns for your table. Locate the Columns region.

Create an Index for Your Table

To define an index for your table, you need to have defined a primary key for your table. To define an index on your table:

Select an index type from the Index Type options.

If you selected a hash index, type a RowPages parameter in the Page size(Rows) text field.

Compute this value by dividing the number of expected rows in your table by 256. For example, if your table has 256,000 rows, specify 1000 for the value of RowPages (256000/256=1000)

You have successfully defined an index on your table. You are now ready to define constraints for your table.

Create a Sequence

You can create a sequence for the TimesTen database or TimesTen Scaleout database with SQL Developer.

To create a sequence, ensure that you are on the main SQL Developer page and that your TimesTen or TimesTen Grid connection is expanded.

  1. Right-click the Sequences option and select New Sequence.
    The Create Sequence dialog displays. Locate the Schema drop-down list.
  2. From the Schema drop-down list, select the owner of the sequence.
  3. In the Name text field, type a name for the sequence.
  4. In the Start With text field, specify the first sequence number to be generated.
    Use this field to start an ascending sequence at a value that is greater than the minimum value or to start a descending sequence at a value less than the maximum.
  5. In the Increment text field, specify the incremental value between consecutive numbers.
    This value can be either a positive or negative integer. It cannot be 0. If the value is positive, it is an ascending sequence. If the value is negative, it is descending. The default value is 1.
  6. In the Min Value text field, specify the minimum value for an ascending sequence, or the final value for a descending sequence.
    This value must be less than or equal to the value that you specified in the Start With field. The default minimum value is 1.
  7. In the Max Value text field, specify the largest possible value for an ascending sequence, or the starting value for a descending sequence.
    This value must be greater than or equal to the value that you specified in the Start With field. The default maximum value is (263) -1, which is the maximum value of the BIGINT data type.
  8. If you want to cache the numbers from this sequence, select the Cache option from the Cache drop-down list. If not, select the No Cache option.
  9. If you selected the Cache option from the Cache drop-down list, in the Cache Value text field, specify the range of numbers that are cached.
    When a restart occurs, unused cached numbers are lost. If you specify a cache value of 1, then each use of the sequence results in an update to the database. Larger cache values result in fewer changes to the database and less overhead. The default value is 20.
  10. From the Cycle drop-down list, select one of these options:
    • Cycle - The sequence number generator continues to generate numbers after it reaches the maximum or minimum value.

    • No Cycle - The sequence number generator stops generating numbers when the maximum or minimum value is reached.

    By default, sequences do not cycle. Once the number reaches the maximum value in the ascending sequence, the sequence wraps around and generates numbers from its minimum value. For a descending sequence, when the minimum value is reached, the sequence number wraps around, beginning from the maximum value.
  11. In the Batch value text field, define the range of unique sequence values that are stored at each element of the grid. The default value is 10 million. This option is only available for TimesTen Scaleout databases.
    Locate the OK button.

    Note:

    If you want to review the DDL statement that TimesTen or TimesTen Scaleout uses to create your sequence, click the DDL tab.

  12. Click OK.
    The Create Sequence dialog closes and TimesTen or TimesTen Scaleout creates your sequence.
You have successfully created a sequence.

Compile All of Your PL/SQL Packages

To compile all of your saved PL/SQL packages, ensure that you are on the main SQL Developer page and that your TimesTen connection is expanded.
  1. Right-click the Packages option and select Compile All.
    The Compile All dialog displays. Locate the Apply button.
  2. Click Apply.
    TimesTen compiles all of your saved PL/SQL packages. A confirmation dialog displays with the compilation results and any errors that TimesTen encountered.
  3. Click OK.
    Review the Messages - Log area to see the compilation results. If you see any compilation errors, troubleshoot and fix the compilation errors. Then, recompile and save your PL/SQL packages.
You have successfully compiled all of your saved PL/SQL packages.

Compile Invalid PL/SQL Packages

To compile all of your invalid PL/SQL packages, ensure that you are on the main SQL Developer page and that your TimesTen connection is expanded.
  1. Right-click the Packages option and select Compile Invalid.
    The Compile Invalid dialog displays. Locate the Apply button.
  2. Click Apply.
    TimesTen compiles all of your invalid PL/SQL packages. A confirmation dialog displays with the compilation results and any errors that TimesTen encountered.
  3. Click OK.
    Review the Messages - Log area to see the compilation results. If you see any compilation errors, troubleshoot and fix the compilation errors. Then, recompile and save your PL/SQL packages.
You have successfully compiled all of your invalid PL/SQL packages.

Loading Data from Oracle Database Tables

Before attempting to load data from an Oracle database into a TimesTen database:

  • Ensure that you are using Oracle TimesTen In-Memory Database Release 11.2.2.4 (or later).

  • Ensure that you have specified the Oracle database connection information (Oracle Database Password and Oracle Net Service Name) for your TimesTen SQL developer connection.

To load data from an Oracle database into a TimesTen database, ensure that you are on the main SQL Developer page and that your TimesTen connection is expanded.

  1. Right-click the Tables option and select Load from Oracle Database Tables.
    The Load from Oracle Database Tables dialog displays. Locate your Oracle database schema name from the navigation tree on the left of the Load from Oracle Database Tables dialog.
  2. Select a mode:
    • Simple - This option enables you to load data from an Oracle database.

    • Advanced - This option enables you to load data from an Oracle database and specify the mapping of Oracle database data types to TimesTen database data types. You can also specify additional load options.

  3. Once you have selected a mode, click Next>.
    Depending on the mode that you selected, follow the instructions from Advanced or Simple.

Advanced

The advanced mode enables you to select the mapping of Oracle database data types to TimesTen data types and get data compression recommendations through compression analysis.
Before using the advanced mode, ensure that you have completed all the steps from Loading Data from Oracle Database Tables.

Note:

The data type mapping and compression settings set in this section are applied to all the tables that you load from the Oracle database.


Note:

You can click the Reset Factory Defaults button to set all configuration values to factory defaults.

  1. In the Type Mapping section of the Type Mapping & Compression tab, choose the data type mapping for the following data types:
    • NUMBER: Data type mapping for the NUMBER data type. You can select the following data type mappings:

      • No Mapping: Columns of data type NUMBER are not analyzed and are imported with the same data type as in the Oracle database table.

      • Standard Mapping: Columns of data type NUMBER with precision zero are mapped to a suitable TimesTen native integer data type.

      • Aggressive Mapping: All columns of data type NUMBER are mapped in the TimesTen database as columns of data type NUMBER with the maximum precision and scale used in the Oracle database table.

    • VARCHAR2: Data type mapping for the VARCHAR2 and NVARCHAR2 data type. You can select the following data type mappings:

      • No Mapping: Columns of data type VARCHAR2 and NVARCHAR2 are not analyzed and are imported with the same data type as in the Oracle database table.

      • Aggressive Mapping: All columns of data type VARCHAR2 and NVARCHAR2 are mapped in the TimesTen database as columns with the maximum precision and scale used in the Oracle database table.

    • TIMESTAMP with TIME ZONE: Data type mapping for the TIMESTAMP WITH TIMEZONE data type. You can select the following data mapping types:

      • Treat as unsupported type: Columns of data type TIMESTAMP WITH TIMEZONE are treated as an unsupported data type. If you select Stop on Any Bad Type as the Analysis Parameter, the data type mapping analysis stops when it encounters a TIMESTAMP WITH TIMEZONE data type column. If you select any other option for the Analysis Parameter, the data type mapping analysis continues and TIMESTAMP WITH TIMEZONE data type columns are ignored during table loading.

      • Map to TIMESTAMP: Columns of data type TIMESTAMP WITH TIMEZONE are mapped in the TimesTen database as TIMESTAMP data type columns. However, all the timezone information is lost because the TIMESTAMP data type does not support timezone information.

    • LOB data types: Data type mapping for any LOB data type. You can select the following data mapping types:

      • Map to VAR*: This maps columns of LOB data types from the Oracle database to VAR data types in the TimesTen database:

        BLOB as VARBINARY(4194304)

        CLOB as VARCHAR2(4194304)

        NCLOB as NVARCHAR2(2097152)

    • RAW data types: Data type mapping for any LOB data type. You can select the following data mapping types:

      • Treat as unsupported type: Columns of any RAW data type are treated as an unsupported data type. If you select Stop on Any Bad Type as the Analysis Parameter, the data type mapping analysis stops when it encounters any RAW data type column. If you select any other option for the Analysis Parameter, the data type mapping analysis continues and RAW data type columns are ignored during table loading.

      • Map to VAR*: This maps columns of LOB data types from the Oracle database to VAR data types in the TimesTen database:

        RAW(n) as VARBINARY(n) where n can have a maximum value of 4194304.

        LONG as VARCHAR2(4194304)

        LONG RAW as VARCHAR2(4194304)

    • Inline Column Size Limit: The maximum size limit for inline columns. This is an integer value with valid values between 0 and 32768.

    • Padding Factor: The percentage increase of the determined maximum value for precision and length as determined by analysis when Aggressive Mapping is selected for the NUMBER and VARCHAR2 data type mapping. This is an integer value with valid values between 0 and 1000. A padding factor of 50 indicates an increase of 50%.

    Locate the Compression section.

  2. In the Compression section, set the following compression parameters:
    • Type of Compression: You can select the following types of compression:

      • No Compression: The source Oracle database table is not analyzed for compression. If you select this option, all of the compression parameters are disabled.

      • Use Maximum Number of Distinct Values: The source Oracle database table is analyzed for compression using the maximum dictionary pointer size for every column.

      • Use Optimal Number of Distinct Values: The source Oracle database table is analyzed for compression using a dictionary pointer size that is adjusted based on the actual number of distinct values in the column.

    • Padding Factor: The percentage increase of the determined maximum value for distinct values in a table as determined by analysis. This is an integer value with valid values between 0 and 1000. A padding factor of 50 indicates an increase of 50% for the MAXVALUES parameter of the COMPRESS statement.

    • Minimum Compression Ratio: The minimum compression factor that must be achieved for a column or table to be considered for compression. The value is the percentage ratio between the compressed and uncompressed size of the column or table. Smaller values represent higher compression. This is an integer value with valid values between 1 and 100.

    • Minium Number of Rows: The minimum number of rows for table to be considered for compression. This is an integer value with valid values greater than 0.

    Locate the Analysis Parameters section.
  3. Choose the values for the Analysis Parameters:
    • Select the action to take when an unsupported data type is encountered for a table column. There are two options:

      • Stop on Any Bad Type: The data type mapping analysis stops when it encounters a bad data type. If a bad data type is encountered, you can view the error message in analysis results.

      • Skip Columns with Bad Types: The data type mapping analysis skips columns with bad data types, but the analysis does not stop.

    Once you have set all the parameters of the Type Mapping & Compression tab, locate the Load Options tab.

  4. Click the Load Options tab.
    The Load Options tab displays. Locate the Complex Data Mapping section.
  5. In the Load Options Configuration section of the Load Options tab, specify these options:

    Note:

    These options are only supported in TimesTen 18.1 or higher.

    • Inserter Threads: Number of threads that insert data in the TimesTen table.

    • Fetcher Threads: Number of threads that retrieve data from the Oracle database table.

    • Error Threshold: Threshold for the maximum number of allowed errors.

    • Resume from SCN: The load queries the Oracle database from this SCN. This value is optional and if it is not specified it will use the latest SCN.

    • Ignore Duplicates: This option ignores any duplicate data. It only works if the TimesTen table has a uniqueness constraint on it. All uniqueness constraint violations are ignored.

    • Direct Load: This option loads data directly into the table during commit points, whereas not using direct load loads data with standard INSERT SQL statements. The direct load has better performance and scalability for large amounts of data.

    Locate the Other Parameters section in the Advanced tab.
  6. In the Index Creation section, specify index creation policies:
    • Policy: Specify one of these index creation policies:

      • Copy all indexes from peer Oracle database table

      • Only copy unique indexes from peer Oracle database table

      • Do not copy indexes from peer Oracle database table

    • Only create indexes when tables are loaded with no errors: This option determines if the indexes are created after tables are loaded without errors.

    Locate the Next> button.

  7. Click Next>.
    The Load from Oracle Database Tables: Load Selected Tables dialog displays. You can now follow the steps from Simple as from this step forward, the steps are the same for the advanced and simple modes.

Simple

The simple mode enables you to load data from the Oracle database without selecting the mapping of Oracle database data types to TimesTen. However, if you are using advanced mode, you can follow these instructions after specifying the mapping of your data types and compression. If you are using advanced mode, ensure that you have completed all the steps from Advanced.

Select Tables to Load

To select the tables that you want to load from the Oracle database into the Timesten database.
  1. Click the + located next to your Oracle database schema name to expand the Oracle database tables list.
    Your Oracle database schema expands showing a list of available Oracle database tables. Locate the Oracle database tables you want to load into the TimesTen database.
  2. Right-click the name of the Oracle database table that you want to load into the TimesTen database and select Load. You can repeat this step, including for the same Oracle database table, to load multiple Oracle database tables.
    If you want to load all of the Oracle database tables, right-click the Oracle database schema name and select Load All. The TimesTen Username dialog displays. Enter the TimesTen user for which you want to create the tables and click OK.

    Your selected tables are added to the right pane and are displayed in a table format.

  3. Review the selected Oracle database tables and edit any necessary fields. You can edit a field by double clicking it. A description of each column follows:
    • TimesTen Username

      The owner of the TimesTen table that you are creating. By default, this is the TimesTen connection user. You can edit this column. An error message is displayed if the specified table owner does not exist or the TimesTen connection user does not have privileges to access the specified table owner.

    • TimesTen Table Name

      The name of the TimesTen table that you are creating. By default, this is the same table name as the Oracle database table. You can edit this column.

    • Query to Run on Oracle database

      The SQL query executed on the Oracle database to generate the desired result set. By default, this is a SELECT * FROM oracledb_tbl query, where oracledb_tbl is the Oracle database table from which you are loading data. You can edit this column. For more information on valid Oracle Database SQL queries, see Oracle Database SQL Language Reference.

    • Oracle Table Row Count

      The number of rows that TimesTen loads from the Oracle database table. This is the row count of the result set from the "Query to Run on the Oracle database" field. By default, this value is not counted.

      To populate the Row Count field for a specific Oracle database table, right-click on the Row Count field for your table, then select Count.

      To populate the Row Count fields for all the selected Oracle database tables, right-click on a Row Count field of any table, then select Count All. A confirmation dialog displays. Click Yes to continue with the row count of all of your previously selected Oracle database tables.

    • Only Create Table

      This option enables you to choose if you want to only create a table and not load it with any data.

    • Create Table Statement

      The SQL statement that TimesTen uses to create the table to load your Oracle database data. You cannot edit this column. Review the CREATE TABLE statement by double clicking on the Create Table Statement field.

      If a TimesTen table with the same name already exists in the TimesTen database, the data from the Oracle database table is appended to the existing TimesTen table. TimesTen does not load table constraints from the Oracle database table. An error dialog displays if a TimesTen table with the same name but different table structure already exists in the TimesTen database.

    • Distribution Scheme

      This column is only displayed if you are using a TimesTen Scaleout database.

      Click the View/Edit button in this column to select a distribution scheme for this table.

      From the Distribution method drop-down list, select a distribution method for your table:

      Distribute by Hash - Distribution scheme that distributes data based on the hash of the primary key or a set of user-specified columns.

      If you select Distribute by Hash, select columns to be part of your distribution column:

      To select columns to be part of your distribution column, double click the column name in the Available Columns list.

      To remove columns from your distribution column, double click the column name in the Selected Columns list.

      Distribute by Reference - Distribution scheme that distributes the data of a child table based on the location of the corresponding parent row of a foreign key constraint. Your table needs at least one foreign key to be able to use this distribution scheme.

      If you select Distribute by Reference, from the Foreign Key drop-down list, select the foreign key to distribute the data of your table.

      Duplicate - Distribution scheme that distributes full identical copies of the table's data to all the elements of a database.

      If you select Duplicate, you do not need to specify any additional fields in the Distribution tab of the Create Table dialog.

    Once you have edited all of the fields, locate the Next> button at the bottom of the dialog.

  4. Click Next>.
    A Load From Oracle Database Tables progress dialog displays. Once TimesTen finishes loading your tables, the progress dialog closes and the Load Summary results displays. If there are any errors, troubleshoot the errors. Locate the Finish button.
  5. Click Finish.

    If your load operation had any errors, SQL Developer asks if you want to save the load profile. This load profile for resuming the load operation once you have fixed any errors that might have come up. See Resume Loading Data from Oracle database tables for more information on how to resume the load operation.

    The Load Summary dialog closes.

You have successfully loaded data from an Oracle database into a TimesTen database.

Resume Loading Data from Oracle database tables

In some cases when you attempt to load data from Oracle database tables, you may run into some errors that prevent all data from being loaded from the Oracle database tables. If you saved the load profile after your load operation failed, you can resume the load operation using the load profile.

To resume loading data from an Oracle database table, ensure that you saved the load profile, that you are on the main SQL Developer page, and that your TimesTen connection is expanded.

  1. Right-click the Table option and select the Resume Loads from Oracle Database Tablesoption.
    The Resume Loads from Oracle Database Tables dialog displays. Locate the Browse button.
  2. Click Browse.
    The Open dialog displays. Locate your load profile file.
  3. Once you have located your load profile file, click Open.
    The Open dialog closes.

    Note:

    SQL Developer displays a warning message if you are using a different database connection than the one that was used when the load profile was saved.

  4. Review the information that is loaded in the Resume Loads and Load Options tabs.

    The Resume Loads tab displays information related to which tables can be loaded from the Oracle database tables into TimesTen tables.

    The Load Options tab displays information related to the load options that will be used to load the Oracle database tables into TimesTen tables. These options cannot be edited.

  5. Once you have reviewed the load information, click Resume Loads.

    A progress dialog displays. Once all tables have been loaded, the progress dialog closes. If SQL Developer displays an error message, troubleshoot the error.

    Locate the Close button.

  6. Click Close.
    The Resume Loads from Oracle Database Tables dialog closes.
You have successfully resumed loading data from Oracle Database tables.

Load Data from an Oracle Database Table into an Existing TimesTen Table

To load data from an Oracle database table into an existing TimesTen table, follow these steps. Make sure you are on the main SQL Developer page and that your TimesTen connection is expanded.

  1. Click the + located next to Tables to expand the TimesTen tables list.

    The TimesTen tables list expands.

  2. Right-click the name of the table and select the Table option, then select the Load from Oracle Database Table option.

    The Load from Oracle Database Tables dialog displays. The Schema name, TimesTen Username, and TimesTen Table Name are auto-filled and you cannot edit these fields. Prepare to enter the SQL query and the Parallel Thread Count.

  3. In the Select Query field, enter the SQL query to execute on the Oracle database. The result of the SQL query is loaded into your TimesTen table.

  4. In the Load Options section, specify these options:


    Note:

    These options are only supported in TimesTen 18.1 or higher.

    • Inserter Threads: Number of threads that insert data in the TimesTen table.

    • Fetcher Threads: Number of threads that retrieve data from the Oracle database table.

    • Error Threshold: Threshold for the maximum number of allowed errors.

    • Resume from SCN: The load queries the Oracle database from this SCN. This value is optional and if it is not specified it will use the latest SCN.

    • Ignore Duplicates: This option ignores any duplicate data. It only works if the TimesTen table has a uniqueness constraint on it. All uniqueness constraint violations are ignored.

    • Direct Load: This option loads data directly into the table during commit points, whereas not using direct load loads data with standard INSERT SQL statements. The direct load has better performance and scalability for large amounts of data.

    Locate the Load button.

  5. Click Load.

    A progress dialog displays. Once TimesTen loads the data from the Oracle database table, the progress dialog closes. If there are any errors, troubleshoot the errors. If you execute the query on a small Oracle database table, the progress dialog may close almost immediately.

Create a New TimesTen Connection

To create a named connection to a TimesTen database, make sure you are on the main SQL Developer page.

  1. Right-click the Connections node and select New Connection.

    The New/Select Database Connection dialog appears.

  2. Select the TimesTen tab.

    You are ready to enter information for the connection.

  3. In the Connection Name field, enter the connection name.

  4. In the Username field, enter the TimesTen user. If you use the TimesTen database to cache data from an Oracle database, enter the TimesTen cache manager user name. If you use the TimesTen database to load data from an Oracle database, enter the TimesTen user name that has SELECT privileges on the Oracle database tables that you want to load.

  5. In the Password field, enter the password for the TimesTen user.

    To save the password, choose Save Password. If you save the password, you will not be prompted for the password on subsequent connections to the TimesTen database.

  6. To allow TimesTen to issue an implicit commit after DML statements, select the Autocommit check box. By default, the Autocommit check box is selected.

  7. Select a connection type from the Connection Type drop-down list. The following types of connections are available:

    • DSN

    • Easy Client/Server

    • Advanced

    You are now ready to define your new connection.

DSN

The DSN connection type allows you to connect to databases by specifying a DSN. The DSN must exist in your .ODBC.INI on UNIX and the ODBC Data Source Administrator on Windows.

  1. Select a predefined DSN that references the TimesTen database from the DSN drop-down list. You can select either a Data Manager DSN to establish a direct connection or a client DSN to establish a client/server connection.

  2. In the Connection Attributes field, enter the attributes for the DSN. The Connection Attributes field is not required. Each attribute setting must be separated by a semicolon. If you do not specify any connection attributes, TimesTen uses the connection attributes specified in the DSN.

  3. To cache data from an Oracle database or load data from an Oracle database into a TimesTen database, select the Enable Cache/Load tables from Oracle database check box.

  4. In the Oracle Database Password field, enter the Oracle database password for the Oracle database user. The Oracle database user must be the same user as the TimesTen user you specified in the Username field. This text field is only available if you selected the Enable Cache/Load tables from Oracle database check box.

  5. Click Save to save the connection name under the Connections node.

    Your connection is saved. You can establish connections to the database using the settings in the named connection without having to specify the values in the fields of the New/Select Database Connection dialog box again.

  6. Click Connect.

    SQL Developer is connected to your TimesTen database.

Easy Client/Server

The easy client/server connection type allows you to connect to local and remote databases without having to define a DSN.

  1. In the Server Host Name field, enter the name or the IP address of the TimesTen server host.

  2. In the Server DSN field, enter the DSN of the TimesTen server.

  3. In the Server Port field, enter the TCP port of the TimesTen server. You can use the ttStatus utility to find the TCP port of your TimesTen server.

    In the following example, the server port number is 53396. This example is part of a sample output from the ttStatus utility.

    TimesTen server pid 24379 started on port 53396
    

    For more information about the ttStatus utility, see "ttStatus" in the Oracle TimesTen In-Memory Database Reference.

  4. To cache data from an Oracle database or load data from an Oracle database into a TimesTen database, select the Enable Cache/Load tables from Oracle database check box.

  5. In the Oracle Database Password field, enter the Oracle database password for the Oracle database user. The Oracle database user must be the same user as the TimesTen user you specified in the Username field. This text field is only available if you selected the Enable Cache/Load tables from Oracle database check box.

  6. In the Oracle Net Service Name field, enter the Oracle database net service name for the Oracle database. This text field is only available if you selected the Enable Cache/Load tables from Oracle database check box.

  7. Click Save to save the connection name under the Connections node.

    Your connection is saved. You can establish connections to the database using the settings in the named connection without having to specify the values in the fields of the New/Select Database Connection dialog box again.

  8. Click Connect.

    SQL Developer is connected to your TimesTen database.

Related Topics

Advanced

The advanced connection type allows you to define a connection string to connect to your TimesTen database.

  1. Select a driver type for the TimesTen database from the Driver Type option. Select either Client/server to establish a client/server connection or Direct to establish a direct connection.

  2. In the Connection string field, enter a connection string to define the DSN and set attributes for the DSN. If you choose Client/Server as the Driver Type specify the server host, server port, and DSN. Each attribute setting must be separated by a semicolon. Do not delimit the connection string with a pair of double quotation marks.

  3. To cache data from an Oracle database or load data from an Oracle database into a TimesTen database, select the Enable Cache/Load tables from Oracle database check box.

  4. In the Oracle Database Password field, enter the Oracle database password for the Oracle database user. The Oracle database user must be the same user as the TimesTen user you specified in the Username field. This text field is only available if you selected the Enable Cache/Load tables from Oracle database check box.

  5. Click Save to save the connection name under the Connections node.

    Your connection is saved. You can establish connections to the database using the settings in the named connection without having to specify the values in the fields of the New/Select Database Connection dialog box again.

  6. Click Connect.

    SQL Developer is connected to your TimesTen database.

Set the Cache Administrator User Name and Password

You must create a cache administration user in the Oracle database. This user creates, owns and maintains Oracle objects that store information used to manage cache. This user also enforces predefined behaviors of cache groups.

After you create the cache administration user in the Oracle database, you must set the name and password for the user in the TimesTen database.

To set the cache administration user name and password, right-click the node of the connection name for the TimesTen database and select Set Cache Administration User.

The Setting the cache administration user dialog appears. For the Prompts tab, in the Cache administration user ID field, type the cache administration user name. In the Cache administration user password field, type the Oracle password for the cache administration user.

Click Apply.

You must set the cache administration user name and password for each TimesTen database that caches Oracle. If you drop and re-create the TimesTen database or drop and re-create the cache administration user in the Oracle database, then the cache administration user name and password must be reset in the TimesTen database.

Start and Stop the Cache Agent

After you set the cache administration user name and password, create a cache grid and associate the TimesTen database with the cache grid, you must start the TimesTen cache agent process. The cache agent processes cache operations such as loading a cache group and automatic refresh.

To start the cache agent, right-click the node of the connection name for the TimesTen database and select Start/Stop Cache Agent.

In the Starting/stopping the cache agent dialog box, select Start agent within the Prompts tab. Then click Apply to start the cache agent.

To stop a running cache agent process, right-click the node of the connection name for the TimesTen database and select Start/Stop Cache Agent in an identical fashion as was done when starting the cache agent.

In the Starting/stopping the cache agent dialog box, select Stop agent within the Prompts tab. Then click Apply to stop the cache agent.

Related Topics

Create a Cache Group

A cache group defines the set of Oracle data to cache in the TimesTen database. When you create a cache group, cache tables are created in the TimesTen database that correspond to the Oracle tables being cached.

To create a cache group, right-click the Cache Groups node under the node of the connection name for the TimesTen database and select New Cache Group.

In the Create cache group dialog, specify a name for the cache group in the Name field within the Cache Group Attributes tab. For Type, choose the desired cache group type (read-only, asynchronous writethrough, synchronous writethrough or user managed).

Cache groups are categorized as either explicitly loaded or dynamic. If you are creating a dynamic cache group, then choose Dynamic in the Type section.

In an explicitly loaded cache group, data is loaded manually into its cache tables from the corresponding Oracle tables using a load or refresh operation, or automatically using an automatic refresh operation. In a dynamic cache group, data is loaded into its cache tables on demand from the corresponding Oracle tables using a dynamic load operation, or manually using a load operation.

A read-only, asynchronous writethrough (AWT) or synchronous writethrough (SWT) cache group can be defined as a dynamic cache group. A user managed cache group can be defined as a dynamic cache group if it does not contain all of the following characteristics:

  • Automatic refresh is defined

  • At least one of its cache tables are updatable

  • Committed updates on one or more of its updatable cache tables are propagated to the corresponding Oracle tables

Cache groups are classified as either local or global. If you are creating a global cache group, then select the Global in the Type section.

In a local cache group, data in its cache tables are not shared across TimesTen databases. In a global cache group, data in its cache tables are shared across TimesTen databases.

Only an AWT cache group can be defined as global cache group.

Defining a cache group and cache table attributes

Within the Cache Group Attributes tab of the Create cache group dialog, if you are creating a user managed cache group and you select Autorefresh within the Table Attributes section to enable automatic refresh when either All tables readonly or Propagate all tables is selected, or you are creating a read-only cache group, then for the following automatic refresh characteristics:

  • Set the automatic refresh mode in the Mode field by choosing either Full or Incremental. The default automatic refresh mode is Incremental.

  • Set the automatic refresh interval in the Refresh Interval field by specifying a numeric value followed by a unit of time in minutes, seconds or milliseconds. The default automatic refresh interval is 5 minutes.

  • Set the automatic refresh state in the Refresh State field by choosing either Paused, On or Off. The default automatic refresh state is Paused.

If you are creating a user managed cache group, then from the Table Attributes section in the Cache Group Attributes tab within the Create cache group dialog, choose one:

  • All tables readonly: All cache tables are read-only

  • Propagate all tables: All cache tables are updatable and committed updates on the cache tables are propagated to the corresponding Oracle tables

  • Varies from table to table: Some cache tables are read-only and other cache tables are updatable where committed updates on the cache tables may or may not be propagated to the corresponding Oracle tables

Defining the root table

Click the Tables tab in the Create cache group dialog. Right-click in the Tables panel and select Add root table.

The Select the root table dialog appears. The list of Oracle tables and Oracle synonyms that you can choose to designate as the root table for your cache group is displayed. Oracle tables that have primary keys and Oracle tables that have unique non-null indexes are available for selection.

Select the table and click OK.

To show only Oracle tables owned by the current connection user, choose Show only my tables.

Related Topics

Selecting the columns to cache

In the Columns tab within the Tables tab of the Create cache group dialog, select the check boxes under the Inline field to specify the INLINE attribute for the column. You can specify the INLINE attribute for columns of type VARCHAR2, NVARCHAR2, and VARBINARY.

Select the check boxes under the Allow null values field for each cached column to accept null values. By default, the nullability of a cache table's column is identical to the nullability of the corresponding Oracle table's column.

Select the check boxes under the Cached field for each column to cache. By default, all columns of the table are selected and are cached. The Oracle table's unique identifying columns (primary key, unique index or unique constraint) must be included in the TimesTen cache table and constitutes the cache table's primary key.

To select all columns or deselect all columns, except for the Oracle table's unique identifying columns, to accept null values or to cache, select or deselect the check boxes that appear to the left of the Allow null values and Cached fields, respectively.

Some Oracle data types have multiple compatible TimesTen data types. For columns in the Oracle table whose data type can map multiple TimesTen data types, a menu appears under the Data type in TimesTen field for those columns. Select the desired data type for the column in the cache table. The default compatible TimesTen data type for the Oracle data type appears in italics.

For updatable cache tables, you can specify a default column value under the Default Value field for each cached column to define a default value. By default, the default value of a cache table's column is identical to the default value of the corresponding Oracle table's column.

Specifying the table attributes

By default, TimesTen creates a range index on the cache table's primary key columns. To create a hash index instead of a range index on the primary key columns, in the Primary Key section of the Table Attributes tab within the Tables tab of Create cache group, choose Use hash. You must size the hash index by specifying either the maximum number of rows the underlying cache table is anticipated to have or the number of pages to allocate to the index in the Hash sizing policy menu and the adjacent field after the colon (:) which requires a numeric value. The default selection is Current table row count.

For more information about the index that is automatically created on a cache table's primary key columns, see "CREATE CACHE GROUP" in the Oracle TimesTen In-Memory Database SQL Reference.

For more information about properly sizing a hash index, see "CREATE TABLE" in the Oracle TimesTen In-Memory Database SQL Reference.

By default, the primary key columns of a cache table are identical to the primary key columns of the corresponding Oracle database table. You can define a different column or set of columns as the primary key for the cache table.

In the Manual table management section of the Table Attributes tab within the Tables tab of the Create cache group dialog, click Redefine primary key.

In the Define Primary Key(s) dialog, the non-nullable unique columns of the corresponding Oracle table is shown in the Non-null unique columns list. Select the columns for the primary key of the cache table and then choose >> to move those columns into the Primary key(s) list. The order of the columns in a composite primary key is significant if a range index is to be created on the columns. Click OK to define the alternate primary key for the cache table.

If the primary key of the cache table consists of a different set of columns than the primary key of the corresponding Oracle table, then the tables may become unsynchronized when committed updates are made on the cache table or the corresponding Oracle table. Unique constraint violations can occur when:

  • Committed updates on the cache table are propagated to the corresponding Oracle table

  • Committed updates on the Oracle table are refreshed to the corresponding cache table

You can specify an optional WHERE clause for the cache table in the WHERE clause field of the Table Attributes tab within the Tables tab of Create cache group. A WHERE clause is only allowed for table definitions in a read-only cache group or a user managed cache group that has automatic refresh defined.

If the cache table is in a user managed cache group that has selected the Varies from table to table in the Table attributes section within the Cache Group Attributes tab of the Create cache group dialog, then you must specify the table attribute for the cache table.

In the Propagation Type section of the Table Attributes tab within the Tables tab of Create cache group, choose:

  • Readonly to define the cache table as read-only

  • Propagate to define the cache table as updatable with updates on the table to be propagated to the corresponding Oracle table

  • Neither to define the cache table as updatable with updates on the table not propagated to the corresponding Oracle table

By default, cache tables in a user managed cache group are updatable with updates on the table not propagated to the corresponding Oracle table.

Related Topics

Specifying an aging policy

You can specify an aging policy for the cache table in the Aging tab of the Create cache group dialog. An aging policy is explicitly defined on the root table of a cache group and it implicitly applies to all the child tables.

Choose:

  • Usage-based to define a least recently used (LRU) aging policy

  • Time-based to define a time-based aging policy

  • No aging to not define an aging policy

An LRU aging policy can be defined for tables in an explicitly loaded AWT, SWT or user managed cache group that does not have automatic refresh defined. The default aging state is set to off for global explicitly loaded cache groups. For dynamic cache groups that do not have automatic refresh defined, the default aging state is set to on and the type of aging is set to usage-based.

The TimesTen database memory usage thresholds that determine when data starts and stops being deleted from tables that are subject to LRU aging are shown when the Usage-based is selected. The default usage threshold that determines when data starts being deleted from the tables is 90%. The default usage threshold that determines when data stops being deleted from the tables is 80%. The default LRU aging cycle is 1 minute.

A time-based aging policy can be defined on a cache table that contains a non-nullable DATE or TIMESTAMP column. Columns in the table of these data types appear in the Column within the Aging tab of the Create cache group dialog when Time-based is selected. Select the column to store the timestamp value indicating when each row was inserted or most recently updated.

In the Life-time field, indicate the length of time in which data that has not been updated is to be kept in the table by specifying a numeric value followed by a unit of time in minutes, hours or days from the drop-down menu list.

In the Cycle field, indicate the frequency in which data is to be aged out of the table by specifying a numeric value followed by a unit of time in minutes, hours or days in the drop-down menu list. The default time-based aging cycle is 5 minutes.

Specify an aging state by choosing on or off.

Verifying the root table definition

After you have defined the tables and columns to cache, the type of index to create on the primary key columns, the table attributes including an optional WHERE clause, and an optional aging policy for the root table, you can view the CREATE CACHE GROUP statement used to create the cache group and its cache table in the DDL tab of the Create cache group dialog.

Click Apply to create the cache group and its cache table if you are not going to add any child tables to the cache group.

Related Topics

Defining the child tables

Within the Tables tab of the Create cache group dialog, right-click in the Tables panel and select Add child tables.

The Select one or more child tables dialog appears. This dialog displays the list of Oracle tables and Oracle synonyms that you can choose to designate as the child table(s) for your cache group. Oracle tables that have primary keys and Oracle tables that have unique non-null indexes are available for selection.

Select the tables to designate as the child tables for your cache group and click OK.

To select multiple child tables, press and hold the CTRL key, and click the desired tables. The child tables appear under their appropriate parent table. You can also drag and drop a particular child table so that it appears under the desired parent table.

To show only Oracle tables owned by the current connection user, choose Show only my tables.

Related Topics

Selecting the columns to cache

Click a child table and in the Columns tab within the Tables tab of the Create cache group dialog, select the check boxes under the Allow null values field for each cached column to accept null values. By default, the nullability of a cache table's column is identical to the nullability of the corresponding Oracle table's column.

Select the check boxes under the Cached field for each column to cache. By default, all columns of the table are selected and are cached. The Oracle table's unique identifying columns must be included in the TimesTen cache table and constitute the cache table's primary key. The Oracle table's foreign key columns that reference its parent table must also be included in the cache table.

To select all columns or deselect all columns, except for the Oracle table's unique identifying columns and the foreign key columns that reference its parent table, to accept null values or to cache, select or deselect the check boxes that appear to the left of the Allow null values and Cache fields.

For columns in the Oracle table whose data type can map to multiple TimesTen data types, a drop-down select list appears under the Data type in TimesTen field for those columns. Select the desired data type for the column in the child cache table.

For updatable cache tables, you can specify a default column value under the Default Value field for each cached column in the child cache table that defines a default value.

Specifying the table attributes

In the Table Attributes tab within the Tables tab of the Create cache group dialog, select whether to create a range index or a hash index on the child cache table's primary key columns in a similar fashion as was specified for the root table. You can define a different column or set of columns as the primary key for the cache table than the columns of the corresponding Oracle table in a similar fashion as was specified for the root table. You can also specify an optional WHERE clause for the cache table in a similar fashion as was specified for the root table. A WHERE clause is only allowed for table definitions in a read-only cache group or a user managed cache group that has automatic refresh defined.

If you would like the foreign key columns of a child table to have cascade delete enabled such that when rows containing referenced key values are deleted from its parent table, rows in the child table with dependent foreign key values are automatically deleted, then select Cascade delete foreign key.

By default, the foreign key columns of a child cache table are identical to the foreign key columns of the corresponding Oracle table. You can define a different column or set of columns as the foreign key for the cache table.

In the Manual table management section of the Table Attributes tab within the Tables tab of the Create cache group dialog, select Redefine foreign key.

In the Define Foreign Key(s) dialog, the columns in the child table whose data types are compatible with the primary key columns of the parent table are shown in the Foreign Key(s) drop-down select list. Select the columns for the foreign key of the cache table. Click OK to define the alternate foreign key for the cache table.

If the child cache table is in a user managed cache group that has selected Varies from table to table in the Table attributes section within the Cache Group Attributes tab of the Create cache group dialog, then you must specify the table attribute for the cache table in a similar fashion as was specified for the root table. If the cache table is updatable, then specify whether updates on the table are to be propagated or not propagated to the corresponding Oracle table.

Completing the definitions of the child tables

Define the columns to cache, the type of index to create on the primary key columns, the cascade delete setting for the foreign key columns, and the table attributes including an optional WHERE clause for any remaining child tables.

Verifying the cache group definition

In the DDL tab of the Create cache group dialog, you can view the CREATE CACHE GROUP statement used to create the cache group and its cache tables.

Click Apply to create the cache group and its cache tables.

If you created an AWT cache group, then you must start the replication agent for committed updates on its cache tables to be asynchronously propagated to the corresponding Oracle tables.

This task must be performed either outside of SQL Developer using a command-line interface such as the ttIsql utility, or within SQL Developer using SQL Worksheet.

Drop a Cache Group

When you drop a cache group, its cache tables are also dropped.

Under the Cache Groups node within the node of the connection name for the TimesTen database, right-click the name of the cache group to drop and select Drop.

Click Apply to drop the cache group.

Related Topics

Load or Refresh a Cache Group

Click the + to the left of the Cache Groups node to view the list of cache groups. Next right-click the name of the cache group to load or refresh. Select Load to load the cache group or Refresh to refresh the cache group.

The cache agent must be running to load or refresh a cache group. .

For a read-only cache group or a user managed cache group that has automatic refresh defined, you must set the automatic refresh state to Paused before you can load or refresh the cache group.

In the Prompts tab of the Load or Refresh dialog, specify a numeric value in the Commit every n rows field to indicate the frequency, based on the number of rows that are loaded or refreshed into the cache group, at which a commit is issued during the load or refresh operation. By default, a transaction is committed after every 256 rows are loaded or refreshed into the cache group.

In the Number of threads to run in parallel field within the Prompts tab of the Load or Refresh dialog box, specify the number of cache agent process threads to spawn and use for the load or refresh operation. Parallel processing of the load or refresh operation can potentially improve the operation's throughput. The numeric value specified in this field cannot exceed 10 and should not exceed the number of CPUs on the system that can be dedicated to the parallel load or refresh operation. The default value of 1 indicates that the load or refresh operation is processed serially.

You can specify an optional WHERE clause for the load or refresh operation in the Where clause field within the Prompts tab of the Load or Refresh dialog. You can use a WHERE clause for a load or refresh operation on an AWT, SWT or user managed cache group that does not have automatic refresh defined.

Click Apply to load or refresh the cache group.

Flush a Cache Group

Only user managed cache groups containing cache tables that are not all read-only, or not all updatable where updates on the tables are propagated to the corresponding Oracle tables can be flushed.

Click the + to the left of the Cache Groups node to view the list of cache groups. Next right-click the name of the cache group that you to flush. Select Flush to flush the cache group.

In the Where clause field within the Prompts tab of the Flush dialog, specify an optional WHERE clause for the flush operation.

Click Apply to flush the cache group.

Unload a Cache Group

Click the + to the left of the Cache Groups node to view the list of cache groups. Next right-click the name of the cache group to unload. Select Unload to unload the cache group.

In the Where clause field within the Prompts tab of the Unload dialog, specify an optional WHERE clause for the unload operation. You can use a WHERE clause for an unload operation on an AWT, SWT or user managed cache group that does not have automatic refresh defined.

Click Apply to unload the cache group.

Related Topics

Alter the Automatic Refresh Attributes of a Cache Group

You can alter the automatic refresh attributes of a read-only cache group or a user managed cache group that has automatic refresh defined.

Under the Cache Groups node, right-click the name of the cache group and select Autorefresh.

In the Prompts tab of the Autorefresh dialog, you can change any of the following automatic refresh attributes:

  • To change the automatic refresh mode, in the Mode field, choose either Incremental or Full.

  • To change the automatic refresh interval, in the Refresh Interval field, specify a numeric interval and units of time in minutes, seconds or milliseconds.

  • To change the automatic refresh state, in the Refresh State field, choose Paused, On or Off.

Click Apply.

Specify and Display LOB Data Types

If you are using TimesTen release 11.2.2.2.0 or greater, then you can specify and display LOB data types in your table definitions.

If you want to create a table with a LOB data type, then in the Create Table dialog, expand the Type column header. You see CLOB, NCLOB, and BLOB as valid data types.

To view the data type for your columns, select the table and then choose the Columns tab. You see the LOB data type for your column.

If you want to add a column and specify a LOB data type, in the Add Column dialog, expand Data Type. You see CLOB, NCLOB, and BLOB among the possible choices.

For PL/SQL objects, you can specify LOB data types as IN, OUT, and IN OUT parameters. In the PL/SQL edit dialogs, for parameter types, choose CLOB, NCLOB, or BLOB.

Specify the INLINE Attribute for Columns

You can specify the INLINE attribute for columns of type VARCHAR2, NVARCHAR2, and VARBINARY.

In the Create Table dialog, locate the column header named Inline. Click in the checkbox to define the column with the INLINE attribute.

You can also specify the INLINE attribute when adding a column to a table. Right-click on the table, select Column, then select Add. The Add Column dialog appears. For columns of type VARCHAR2, NVARCHAR2, and VARBINARY, click in the Inline checkbox to add the column with the INLINE attribute.

Compute Table Size

If you are using TimesTen Release 11.2.2.0 or greater, you can compute table size information.

To view table size information, you must first compute the table size:

  1. Choose + to the left of the Tables node to view the list of tables.

  2. Right-click the name of the table to compute table size information.

  3. Select Table, then select Compute Size.

    The Compute Size dialog appears. The owner and name of the table are displayed.

  4. Click in the checkbox if you want to compute out-of-line sizes.

  5. Choose Apply.

    A Confirmation dialog appears.

  6. Choose OK.

    The table size statistics for the table are computed.

To view the SQL for computing the table size, choose the SQL tab in the Compute Size dialog. You see that a TimesTen built-in procedure called ttComputeTabSizes is executed. After this built-in is executed, you can review the table size information for your table. Note that this table size information is on a per table basis.

To compute table sizes for all tables in your database including materialized views, system tables, and tables that are part of cache groups, use the SQL Worksheet and execute the command: Call ttComputeTabSizes (NULL,0); or to include out-of-line data: Call ttComputeTabSizes (NULL,1);.

After you compute the table size for one or more tables, you can view the table size information:

  1. Choose + to the left of the Tables node to view the list of tables.

  2. Choose the table you want to review table size information.

  3. Choose the Sizes tab located among the tabs that display the attributes of the table.

    Table size information is displayed. Specifically, values for INLINE BYTES, OUT OF LINE BYTES, and METADATA BYTES are shown.

You can choose the Actions menu to generate or regenerate the table size. If you choose the Actions menu, then Table, then select Compute Size. The Compute Size dialog appears allowing you to compute the table size information.

Choose Refresh to refresh the displayed table size data.

You can view table size information for all tables that you have computed table sizes. To view such information, select TimesTen Reports, then Table, then select Table Sizes.

For more information on the ttComputeTabSizes built-in procedure, see "ttComputeTabSizes" in Oracle TimesTen In-Memory Database Reference.

Use a REF CURSOR as an OUTPUT Parameter

You can test a PL/SQL function, procedure, or package by defining a REF CURSOR as an OUTPUT parameter in your PL/SQL function, procedure, or package. After you define a REF CURSOR, compile and run your PL/SQL function, procedure, or package. The Run dialog appears. Choose OK.

After you choose OK in the Run PL/SQL dialog, you can view the details of the run in the two tabs:

  1. IdeConnections: Displays the status of your run including any errors encountered.

  2. Output Variables: Shows the output from the execution of the function, procedure, or package.

Create a Primary Key Constraint

You can create a primary key constraint on a table that does not have a primary key defined. Follow these steps:

  1. Click the + to the left of the Tables node to view the list of tables. Then right-click the name of the table to create a primary key constraint.

  2. Select Constraint, then select Add Primary Key.

    The Add primary key dialog appears.

  3. In the key index type field choose either Use range to create a primary key using a range index or Use hash to create a primary key using a hash index.

    If you choose Use hash, you see the text with number of followed by a drop-down list of either row or pages. Select either row or pages and in the box after the colon (:), enter the number of rows or pages. The default selection is row.

  4. In the Constraint Name field, enter the constraint name. The name cannot exceed 30 characters in length.

  5. In the Column field(s), you see a drop-down list of column names. Choose the column name(s) to use for the primary key.

  6. Click Apply.

    The Confirm dialog box appears indicating that the primary key constraint has been added.

  7. Click OK.

    The primary key constraint has been added successfully.

To view the SQL statement used to create the primary key constraint, choose the SQL tab of the Add primary key dialog box.


See Also:

  • For information on hash index sizing, see "Column Definition" in the Oracle TimesTen In-Memory Database SQL Reference

  • For information about creating a primary key constraint, see "CREATE TABLE" or "ALTER TABLE" in the Oracle TimesTen In-Memory Database SQL Reference


Change the Attributes of Primary Key

You can change the attributes of a primary key constraint after you have defined a primary key on a table. Follow these steps:

  1. Click the + to the left of the Tables node to view the list of tables. Then right-click the name of the table on which to change the primary key attributes.

  2. Select Constraint, then select Change Primary Key Parameters.

    The Change parameters of a primary key dialog appears.

  3. In the key index type field choose either Use range to change the primary key constraint from using a hash index to using a range index or Use hash to change the primary key constraint from using a range index to using a hash index.

    If you choose Use hash, you see the text with number of followed by a drop-down list of either row or pages. Select either row or pages and in the box after the colon (:), enter the number of rows or pages. The default selection is row.

  4. Click Apply.

    The Confirm dialog appears indicating that the index(es) for the primary key constraint has been changed.

  5. Click OK.

    The index(es) for the primary key constraint has been changed successfully.

To view the SQL statement used to change the attributes of the primary key constraint, choose the SQL tab of the Change parameters of a primary key dialog.


See Also:

  • For information on hash index sizing, see "Column Definition" in Oracle TimesTen In-Memory Database SQL Reference

  • For information about changing the attributes of a primary key constraint, see "ALTER TABLE" in the Oracle TimesTen In-Memory Database SQL Reference


Create a Foreign Key Constraint

You can create a foreign key constraint on a table. Make sure you are on the main SQL Developer page and that your TimesTen connection is expanded.

  1. Click the + to the left of the Tables node to expand the list of tables.

  2. Right-click the name of the table and select Constraint, then select Add Foreign Key.

    The Add Foreign Key dialog displays. The Owner and Name fields are auto-filled and you cannot edit these fields. Prepare to enter the Constraint Name.

  3. To enable the ON DELETE CASCADE referential action, select the Cascade delete foreign key checkbox. If specified, when rows containing referenced key values are deleted from a parent table, rows in child tables with dependent foreign key values are also deleted.

  4. In the Constraint Name field, enter the name of the foreign key.

  5. Select the column on which to apply the foreign key constraint from the Column Name drop-down list.

  6. Select the table name that the foreign key references from the Referenced Table Name drop-down list.

  7. Select the column that the foreign key references from the Referenced Column drop-down list.

    To view the SQL statement that will be used to create the foreign key constraint, choose the SQL tab of the Add Foreign Key dialog box.

  8. Click Apply.

    The Confirmation dialog box displays indicating that the foreign key constraint has been added.

  9. Click OK.

    The foreign key constraint has been added successfully.


See Also:

For information about creating a foreign key constraint, see "CREATE TABLE" or "ALTER TABLE" in the Oracle TimesTen In-Memory Database SQL Reference


Drop a Constraint

You can drop a constraint from a TimesTen table. Make sure you are on the main SQL Developer page and that your TimesTen connection is expanded.

  1. Click the + to the left of the Tables node to expand the list of tables.

  2. Right-click the name of the table and select Constraint, then select Drop.

    The Drop dialog displays. The Owner and Name fields are auto-filled and you cannot edit these fields. Prepare to select the Constraint.

  3. Select the constraint that you want to drop from the Constraint drop-down list.

    To view the SQL statement that will be used to drop the constraint, choose the SQL tab of the Drop dialog box.

  4. Click Apply.

    The Confirmation dialog box displays indicating that the constrain has been dropped.

  5. Click OK.

    The constraint has been successfully dropped.

Add an Aging Policy to a Table

To add an aging policy to a regular table or a cache table, under the Tables node, right-click the name of the table to add an aging policy to and select Aging, then select Add Usage-based to add an LRU aging policy. To add a time-based aging policy select Aging, then select Add Time-based. An aging policy can be added to a cache table only if it is the root table of a cache group.

To add an LRU aging policy to the table, in the Prompts tab of the Add Usage-based dialog box, specify an aging state by choosing either On or Off in the Usage-based aging field. The default aging state is on. Click Apply to add the LRU aging policy to the table.

The TimesTen database memory usage thresholds determine when data starts and stops being deleted from the table. The default memory usage threshold that determines when data starts being deleted from the table is 90%. The default memory usage threshold that determines when data stops being deleted from the table is 80%. The default LRU aging cycle is 1 minute.

An LRU aging policy can be added to any regular table, and only to cache tables in an AWT, SWT or user managed cache group that does not have automatic refresh defined.

To add a time-based aging policy to the table, in the Prompts tab of the Add time-based dialog box, select the column name from Column to store the timestamp value indicating when each row was added or most recently updated.

In the Life-time field, indicate the length of time in which data that has not been updated is to be kept in the table by specifying a numeric value followed by a unit of minutes, hours or days in the drop-down menu.

In the Cycle field, indicate the frequency at which data is to be aged out of the table by specifying a numeric value followed by a unit of minutes, hours or days. The default time-based aging cycle is 5 minutes.

Specify an aging state by choosing either On or Off in the Time-based aging field. The default aging state is on. Then click Apply to add the time-based aging policy to the table.

A time-based aging policy can only be added to a table that contains a non-nullable DATE or TIMESTAMP column.

Drop an Aging Policy from a Table

To drop an existing aging policy from a regular table or a cache table, under the Tables node, right-click the name of the table to drop an aging policy from and then select Aging, then select Drop.

Click Apply to drop the aging policy from the table.

Change the Aging State for the Aging Policy of a Table

To change the aging state of a regular table's or cache table's existing aging policy, under the Tables node, right-click the name of the table to change the aging state of and then select Aging, then select Change State On/Off.

In the Prompts tab of the Change state on/off dialog, change the aging state by selecting either On or Off in the Change aging state field. Click Apply to change the aging state of the table.

Change the Memory Usage Thresholds and LRU Aging Cycle

To change the memory usage thresholds and the LRU aging cycle, right-click the node of the connection name for the TimesTen database and choose Change Usage-based Aging Attributes.

In the Prompts tab of the Changing the usage-based thresholds dialog box, specify the threshold that determines when data starts being deleted from the tables in the High usage threshold field. Specify the threshold that determines when data stops being deleted from the tables in the Low usage threshold field. Specify the LRU aging cycle in the Update Frequency field. Then click Apply to change the memory usage thresholds and the LRU aging cycle.

The new settings apply to all tables that have an LRU aging policy defined.

Change the Lifetime and Cycle for the Time-Based Aging Policy of a Table

To change the lifetime and cycle of a regular table's or cache table's existing time-based aging policy, under the Tables node, right-click the name of the table to change the lifetime and cycle of and select Aging, then select Change Lifetime and Cycle.

In the Life-time field within the Prompts tab of the Change Lifetime and Cycle dialog box, change the length of time in which data that has not been updated is to be kept in the table by specifying a numeric value followed by a unit of minutes, hours or days.

In the Cycle field, change the frequency at which data is to be aged out of the table by specifying a numeric value followed by a unit of minutes, hours or days.

Then click Apply to change the lifetime and cycle for the table.

Grant Object Privileges to a TimesTen Database Element

You can grant privileges to and revoke privileges from the following database objects:

  • Regular and cache tables

  • Regular and materialized views

  • Sequences

  • PL/SQL packages, procedures and functions

To grant privileges on an object, right-click the name of the object and select Privileges, then select Grant.

In the Users drop-down menu of the Grant dialog box, select the user to grant object privileges to the object. In the Privileges section, select the All check box or click >> to grant all available object privileges on the object to the selected user. Otherwise, select the individual privileges from the Available Privileges list for the privileges to grant to the selected user and then click > to move those privileges into the Selected Privileges list. To select multiple privileges, press and hold the CTRL key, and click the desired privileges. Click Apply to grant the selected object privileges on the object to the selected user.

For a particular object type, only the available object privileges are shown. For example, DELETE, INDEX, INSERT, REFERENCES, SELECT and UPDATE privileges can be granted on a table. However, only INDEX, REFERENCES and SELECT privileges can be granted on a materialized view.

Only users with the ADMIN system privilege or the owner of an object can grant object privileges on the object.

Related Topics

Revoke Object Privileges from a TimesTen Database Element

To revoke privileges from an object, right-click the name of the object and select Privileges, then select Revoke.

In the Users drop-down menu of the Revoke dialog box, select the user to revoke object privileges from the object. In the Privileges section, select the All check box or click >> to revoke all granted object privileges on the object from the selected user. Otherwise, select the individual privileges from the Available Privileges list for the privileges to revoke from the selected user and then click > to move those privileges into the Selected Privileges list. To select multiple privileges, press and hold the CTRL key, and click the desired privileges. Click Apply to revoke the selected object privileges on the object from the selected user.

The Users drop-down menu shows only users who have been granted object privileges on the object. For a particular user, only the object privileges that they have been granted are shown.

Only users with the ADMIN system privilege or the owner of an object can revoke object privileges from the object.

Load Data into a Table

You can load data into your table using Import Data. Before you can load your data, you must export the data into a file. To export the data, right-click on the name of the table and choose Export. After successfully exporting your data, you can import the data.

  1. Choose + to the left of the Tables node to view the list of tables.

  2. Right-click on the table name.

  3. Select Table, then select Import Data.

    An Open dialog appears. Locate the data file to import. This file is the file you previously exported.

  4. Choose Open.

    The data is loaded into the table.

Start and Stop the TimesTen Replication Agent

The replication agent process transmits committed updates on replicated tables in a master TimesTen database to the corresponding replicated tables in a subscriber TimesTen database. The replication agent is also responsible for asynchronously propagating committed updates on cache tables in AWT cache groups to the corresponding Oracle tables. After you create a replication scheme or an AWT cache group, you must start the replication agent if it is not running.

To start the replication agent, right-click the node of the connection name for the TimesTen database and select Start/Stop Replication Agent.

The Starting/stopping the replication agent dialog appears. In the Prompts tab, select Start agent. Click Apply.

If there are no replication schemes or AWT cache groups in your TimesTen connection, the replication agent is not started.

To stop a running replication agent process, right-click the node of the connection name for the TimesTen database and select Start/Stop Replication Agent.

The Starting/stopping the replication agent dialog appears. In the Prompts tab, select Stop agent. Click Apply.

Update the Table and Column Statistics Used By the TimesTen Query Optimizer

The query optimizer uses statistics stored in TimesTen database system tables to determine the optimal execution plan for a statement. TimesTen stores table level statistics in the SYS.TBL_STATS table. Column level statistics, such as the minimum and maximum value and the number of unique values in a column, are stored in the SYS.COL_STATS table.

TimesTen does not compute table and column statistics as updates occur on regular and cache tables. Instead, TimesTen updates statistics when an explicit request is made.

You can update statistics for all tables owned by a user or for a specific table owned by an user.

To update statistics for all tables, right-click the Tables node and select Statistics, then select Update.

To update statistics for a specific table, click the + to the left of the Tables node. Right-click the name of the table and select Statistics, then select Update.

In the Prompts tab of the Update statistics dialog, choose Invalidate referenced commands to invalidate the execution plans of statements that reference the table for which statistics are updated. When you invalidate the execution plan of a statement, TimesTen recompiles or reprepares that statement upon its next execution.

For Interval type for table statistics, choose Complete interval to divide the rows of the table into two or more intervals and compute statistics on each interval, or Single interval to compute statistics on the entire set of rows as a single interval. You must define a range index on the table to compute complete interval statistics.

Click Apply.

To view the optimizer statistics of a table, click the name of the table.

In the Statistics tab of the table pane, the top section shows the table statistics such as:

  • The number of rows in the table

  • A timestamp indicating when statistics were most recently updated for the table

The bottom section shows the column statistics. For each column, the following information is displayed:

  • The name of the column

  • The number of intervals the data is divided into to compute statistics

  • Total number of NULL values

  • Total number of non-NULL unique values

  • Total number of rows in each interval

For each interval of each column, SQL Developer displays the following:

  • The number of unique values other than the most frequently occurring value

  • The number of rows that contain a value other than the most frequently occurring value

  • The number of rows that contain the most frequently occurring value

  • The minimum value

  • The maximum value

  • The most frequently occurring value

Export the Table Statistics Used By the TimesTen Query Optimizer

You can generate a set of SQL statements that allow you to restore the table statistics to the current state. You can generate SQL statements for a single table or for user tables that the connection user has permission to access. After you export your table statistics to a .sql file, you can import your table statistics by opening the .sql file in SQL Developer and running the script file.

To export the current TimesTen table statistics, make sure you are on the main SQL Developer page.

  1. To save table statistics for a single table, right-click the name of the table and select Statistics, then select Export. To save table statistics for all user tables, right-click Tables and select Statistics, then select Export.

    The Export Optimizer Statistics dialog displays. Locate the Save button at the bottom right of the dialog.

  2. Click Save.

    The Save Optimizer Statistics Export Commands dialog displays.

  3. Select the directory where you want to save the current TimesTen table statistics.

  4. In the File Name field, define the name of your current TimesTen table statistics.

    The default filename of the current TimesTen table statistics is connection_name-exportstatistics-YYYYMMDDMISS.sql, where connection_name is the name of the connection. YYYYMMDDHHMISS is a timestamp of when the recommendations were made, where YYYY is the year, MM the month, DD the day, HH the hour, MI the minutes, and SS the seconds.

  5. Click Save.

    TimesTen saves your current TimesTen table statistics.

Create a TimesTen Performance Metrics Snapshot

A snapshot is a collection of performance metrics from a database. You can create a report comparing two snapshots to analyze the performance of your database.

To create a new snapshot of a database, make sure you are on the main SQL Developer page and that you have expanded the TimesTen connection in the connections navigator.

  1. Right-click the name of the database and select TimesTen Performance Metrics, then select Create Snapshot.

    The New TimesTen Metrics Snapshot dialog displays.

  2. In the Prompts tab of the New TimesTen Metrics Snapshot dialog, select the desired capture level from the Capture Level drop-down list:

    • TYPICAL: For a typical set of metrics. This level is appropriate for most purposes. This is the default capture level.

    • NONE: For metrics outside of SYS.SYSTEMSTATS only.

    • BASIC: For a minimal basic set of metrics.

    • ALL: For all available metrics.

    Make sure to use the same capture level for any two snapshots to be used in a report. An error dialog displays if you attempt to generate a report that compares two snapshots with different capture levels.

    You are now ready to create a new snapshot.

  3. Click Apply to create the snapshot.

    A confirmation dialog shows the ID number of the snapshot. TimesTen generates the snapshot ID.

  4. Click OK.

    TimesTen creates the snapshot with the specified snapshot ID. The snapshot ID is useful for creating TimesTen metrics reports.

Drop a TimesTen Performance Metrics Snapshot

Consider dropping unneeded snapshots to free up permanent space. If you need to save more snapshots of your database, consider editing the TimesTen performance metrics configuration. See "Editing the TimesTen performance metrics configuration" in the Oracle SQL Developer Oracle TimesTen In-Memory Database Support User's Guide.

To drop a new snapshot from a database, make sure you are on the main SQL Developer page.

  1. Right-click the name of the database and select TimesTen Performance Metrics, then select Drop Snapshot.

  2. By default, the Prompts tab of the Drop TimesTen Metrics Snapshot(s) dialog is selected. In the Selector column, select the snapshots you want to drop.

    You can also click on the column header to sort the table based on the column. A description of each column follows:

    • Selector

      The check box you select to determine the snapshots that you want to drop.

    • Snapshot

      The snapshot ID of the snapshot.

    • Timestamp

      The timestamp of when the snapshot was captured.

    • Capture Level

      The capture level of the snapshot. This value can be TYPICAL, NONE, BASIC, or ALL.

    To select all snapshots, click the Select all check box.

  3. Once you have selected the snapshots that you want to drop, click the Apply button.

    A Confirm dialog displays asking you if you want to proceed with dropping the selected snapshots.

  4. Click Yes.

    A confirmation dialog displays a message indicating that one or more TimesTen Metrics snapshots were dropped.

  5. Click OK.

    You successfully dropped the TimesTen metrics snapshots.

Edit the TimesTen Performance Metrics Configuration

TimesTen performance metrics configuration allows you to modify the maximum snapshot count and the maximum snapshot retention size. These configuration settings are useful both in preventing your database from running out of permanent space and in allowing you to save more snapshots.

Once the maximum snapshot count or the maximum snapshot retention size is reached, TimesTen removes the oldest snapshots to free up permanent space. By default, the maximum snapshot count is 256 and the maximum snapshot retention size is 256 MB.

To edit the TimesTen performance metrics configuration for a database, make sure you are on the main SQL Developer page.

  1. Right-click the name of the database and select TimesTen Performance Metrics, then select Edit Configuration.

    The TimesTen Metrics Configuration dialog displays and you see the current configuration for the TimesTen metrics.

  2. The Prompts tab of the TimesTen Metrics Configuration dialog is selected. In the Maximum Snapshot Count field, specify a numeric value to indicate the maximum number of snapshots. By default, the maximum number of snapshots is 256.

  3. In the Maximum Snapshot Retention Size (MB) field, specify the maximum total size of all stored snapshots, in megabytes. By default, the maximum snapshot retention size is 256 MB.

  4. Click Apply.

    You have applied the new TimesTen Metrics configuration settings.

Create a TimesTen Performance Metrics Report

TimesTen performance metrics reports use the data from two specified snapshots of TimesTen metrics to produce a report in HTML format. TimesTen metrics reports include information for each metric. For more information about the various metrics displayed in the report, see "Report examples" in the Oracle TimesTen In-Memory Database Reference.

To generate a new report for a database, make sure you are on the main SQL Developer page.

  1. Right-click the name of the database and select TimesTen Performance Metrics, then select Report.

    The Create TimesTen Metrics Report dialog displays.

  2. By default, the Report generator tab of the Create TimesTen Metrics Report dialog is selected. In the Selector column, select two snapshots to compare.

    You can also click on the column header to sort the table based on the column. A description of each column follows:

    • Selector

      The check box that determines the snapshots that are compared in the metrics report. Make sure to only select two snapshots with the same capture level. An error dialog displays if you attempt to generate a report that compares more than two snapshots.

    • Snapshot

      The snapshot ID of the snapshot.

    • Timestamp

      The timestamp of when the snapshot was captured.

    • Capture Level

      The capture level of the snapshot. This value can be TYPICAL, NONE, BASIC, or ALL.

  3. Once you have selected two snapshots with the same capture level, click the Generate report button. An error dialog displays if you attempt to generate a report that compares snapshots with different capture levels.

    TimesTen generates your TimesTen metrics report. You can view the generated TimesTen metrics report in the pane located below the Generate report button.

    If you do not want to save the report, click Close. If you want to save the report, see Save a report.

Save a report

If you want to save the report for future reference, follow these steps:

  1. Click Save.

    The Save dialog displays.

  2. Select the directory where you want to save the TimesTen metrics report.

  3. In the File Name field, define the name of your TimesTen metrics report.

    The default filename of the TimesTen metrics report is ttstats-snapshot_id_1-snapshot_id_2-YYYYMMDDHHMISS.html, where snapshot_id_1 and snapshot_id_2 are the snapshot IDs of the two snapshots you are comparing in your report. YYYYMMDDHHMISS is a timestamp of when the report was generated, where YYYY is the year, MM the month, DD the day, HH the hour, MI the minutes, and SS the seconds.

  4. Click Save.

    SQL Developer saves your report.

Capture Data for the TimesTen Index Advisor at the Connection Level

Before attempting to capture data for the TimesTen Index Advisor, make sure your table statistics have been updated in the past 24 hours. Up-to-date table statistics provide the most up-to-date statistics for data collection and allow statements to be prepared with the optimized query plan.

You have the following options:

Capture data from a SQL worksheet

You can capture data for the TimesTen Index Advisor at the connection level from the SQL Developer SQL worksheet. Make sure your SQL workload is in the SQL Developer SQL worksheet.

  1. Click the TimesTen Index Advisor button from the SQL worksheet menu bar.

    • If your table statistics are outdated, an information dialog displays information about the outdated tables. TimesTen recommends that you update your table statistics.

    • If your table statistics are up to date, the Index Advisor Configuration dialog displays.

  2. To update your table statistics, click Cancel and follow the steps in "Updating the table and column statistics used by the query optimizer" in the Oracle SQL Developer Oracle TimesTen In-Memory Database Support User's Guide. To proceed without updating your table statistics, click OK.

    The Index Advisor Configuration dialog displays.

  3. Select the desired capture mode from the Capture mode drop-down list:

    • Prepare SQL: TimesTen prepares but does not execute the SQL commands from the SQL worksheet. The TimesTen Index Advisor makes recommendations using computed statistics and query plan analysis. This is the default capture mode.

    • Execute SQL: TimesTen executes the SQL commands from the SQL worksheet. The TimesTen Index Advisor makes recommendations using the actual execution of the SQL commands. This capture mode may take longer than the Prepare SQL mode because TimesTen has to complete SQL execution.

    You are ready to choose if you want to use optimizer hints.

  4. The Include optimizer hints for Oracle BI server checkbox allows you to use optimizer hints that direct the TimesTen query optimizer to generate a specific execution plan. These optimizer hints are recommended queries generated by the Oracle BI server. If you do not want to use optimizer hints, click Start.

    The Index Advisor Configuration dialog closes. A TimesTen index advisor pane displays at the bottom of the SQL worksheet.

  5. In the Selector column, select the index recommendations you want to create.

    You can also click on the column header to sort the table based on the column. A description of each column follows:

    • Selector

      The check box you select to determine the index recommendations that you want to create.

    • Index Recommendation

      The CREATE INDEX statement that the TimesTen index advisor recommends.

    • Affected Statement Count

      The number of statements that benefit from the recommendation.

    • Created

      Shows if you have already created the index recommendation. This value can be Yes or No.

    If you want to select all index recommendations, click the Select all check box.

    If you want to review the SQL commands that are being evaluated by the TimesTen index advisor, click the SQL tab. The SQL tab is located at the top right of the TimesTen index advisor pane.

  6. Once you select the index recommendations that you want to create, click the Create Selected Indexes button.

    The Create Selected Indexes dialog displays. Locate the Details >> button.

  7. Click Details >>.

    A details pane expands that shows progress information about creating the selected indexes. Locate the Close button at the bottom of the dialog.

  8. Click Close.

    The Create Selected Indexes dialog closes. TimesTen creates the indexes.

Saving index recommendations from a SQL worksheet

To save index recommendations for future reference, follow these steps:

  1. Click Save Indexes. TimesTen saves all index recommendations. TimesTen does not save individual index recommendations.

    The Save Indexes dialog displays.

  2. Select the directory where you want to save the TimesTen index advisor recommendations.

  3. In the File Name field, define the file name of your TimesTen index advisor recommendations.

    The default filename of the TimesTen index advisor recommendations is connection_name-indexadvice-YYYYMMDDMISS.sql, where connection_name is the name of the connection. YYYYMMDDHHMISS is a timestamp of when the recommendations were made, where YYYY is the year, MM the month, DD the day, HH the hour, MI the minutes, and SS the seconds.

  4. Click Save.

    TimesTen saves the index recommendations.

    The saved file header contains the following information:

    • The timestamp of when TimesTen generated the report.

    • The version of SQL Developer.

    • The version of the TimesTen database.

    • The name of the TimesTen connection.

    For example:

    -- This file was generated by SQL Developer at 2013-04-29 11:08:45
    -- SQL Developer version 4.0.0.11.51
    -- Database version: 11.02.02.0005 Oracle TimesTen IMDB version 11.2.2.5.0
    -- Connection name: sampledb_1122

Capture data from a SQL workload script

You can capture data for the TimesTen Index Advisor at the connection level using the SQL queries from a SQL workload script file. Make sure you are on the main SQL Developer page and that your TimesTen connection is expanded.

  1. Right-click the name of the database and select Index Advisor, then select Connection Level Capture.

    • If your table statistics are outdated, an information dialog displays information about the outdated tables. TimesTen recommends that you update your table statistics.

    • If your table statistics are up to date, the Index Advisor Configuration dialog displays.

  2. To update your table statistics, click Cancel and follow the steps in "Updating the table and column statistics used by the query optimizer" in the Oracle SQL Developer Oracle TimesTen In-Memory Database Support User's Guide. To proceed without updating your table statistics, click OK.

    The Index Advisor - Connection Level Capture dialog displays.

  3. In the Configuration tab of the Index Advisor - Connect Level Capture dialog, select the desired capture mode from the Capture mode drop-down list:

    • Prepare SQL: TimesTen prepares but does not execute the SQL commands from the workload script. The TimesTen Index Advisor makes recommendations using computed statistics and query plan analysis. This is the default capture mode.

    • Execute SQL: TimesTen executes SQL commands from the workload script. The TimesTen Index Advisor makes recommendations using the actual execution of the workload script. This capture mode may take longer than the Prepare SQL mode because TimesTen has to complete SQL execution.

    You are ready to specify your SQL workload script. Locate the Browse button that is to the right of the Workload script field.

  4. Click Browse.

    The Open dialog displays.

  5. Select the directory where you saved your SQL workload script.

  6. Select the SQL workload script for which you want to generate index recommendations.

  7. Click Open.

    The TimesTen index advisor is now ready to collect data for your SQL workload. Locate the Start button.

    To review the SQL commands that are being evaluated by the TimesTen index advisor, click the SQL tab. The SQL tab is located at the top of the Index Advisor - Connection Level Capture dialog.

  8. The Include optimizer hints for Oracle BI server checkbox allows you to use optimizer hints that direct the TimesTen query optimizer to generate a specific execution plan. These optimizer hints are recommended queries generated by the Oracle BI server. If you do not want to use optimizer hints, click Start.

    The Index advisor assistant progress dialog displays. Locate the Details >> button.

    If the TimesTen index advisor does not have any recommendations, the Index Recommendation Feedback dialog displays. Close this dialog to return to the main SQL developer page.

  9. Click Details >>.

    A details pane expands that shows progress information about the index advisor connection level capture. Locate the Close button at the bottom of the dialog.

  10. Click Close.

    The Index advisor assistant progress dialog closes. Locate the Index Recommendations tab.

  11. Click the Index Recommendations tab.

    The Index Recommendations tab of the Index Advisor - Connection Level Capture dialog displays.

  12. In the Selector column, select the index recommendations that you want to create.

    You can also click on the column header to sort the table based on the column. A description of each column follows:

    • Selector

      The check box you select to determine the index recommendations that you want to create.

    • Index Recommendation

      The CREATE INDEX statement that the TimesTen index advisor recommends.

    • Affected Statement Count

      The number of statements that benefit from the recommendation.

    • Created

      Shows if you have already created the index recommendation. This value can be Yes or No.

    If you want to select all index recommendations, click the Select all check box.

  13. Once you have selected the index recommendations that you want to apply, click the Create Selected Indexes button.

    The Creating Selected Indexes dialog displays. Locate the Details >> button.

  14. Click Details >>.

    A details pane expands that shows progress information about creating the selected indexes. Locate the Close button at the bottom of the dialog.

  15. Click Close.

    The Creating Selected Indexes dialog closes. TimesTen created the indexes. If you want to save the index recommendations, see "Saving index recommendations" in the Oracle SQL Developer Oracle TimesTen In-Memory Database Support User's Guide.

Capture Data for the TimesTen Index Advisor at the Database Level

Before attempting to capture data for the TimesTen Index Advisor, make sure your table statistics have been updated in the past 24 hours. Up-to-date table statistics provide the most up-to-date statistics for data collection and allow statements to be prepared with the optimized query plan.

To collect data for the TimesTen index advisor at the database level, make sure you are on the main SQL Developer page and that your TimesTen connection is expanded.

  1. Right-click the name of the database and select Index Advisor, then select Database Level Capture.

    • If your table statistics are outdated, an information dialog displays information about the outdated tables. It is recommended that your table statistics are up to date.

    • If your table statistics are up to date, the Index Advisor - Database Level Capture dialog displays.

  2. To update your table statistics, click Cancel and follow the steps in "Updating the table and column statistics used by the query optimizer" in the Oracle SQL Developer Oracle TimesTen In-Memory Database Support User's Guide. If you want to proceed without updating your table statistics, click OK.

    The Index Advisor - Database Capture dialog displays. Locate the Start button at the bottom of the dialog.

  3. In the Control tab of the Index Advisor - Connect Level Capture dialog, click Start.

    The Index Advisor Database Capture In Progress dialog displays. Locate the Details >> button.

  4. Click Details >>.

    A details pane expands that shows progress information about the index advisor database level capture. Locate the Close button at the bottom of the dialog.

  5. Click Close.

    The Index Advisor Database Capture In Progress dialog closes.

  6. Once you have captured your desired SQL workload, click Stop.

    If the TimesTen index advisor has recommendations, the Index Advisor Database Capture In Progress dialog displays.

    If the TimesTen index advisor does not have any recommendations, the Index Recommendation Feedback dialog displays. You may close this dialog to return to the main SQL developer page.

  7. If the TimesTen index advisor has recommendations, click Details >>.

    A details pane expands that shows progress information about the index advisor database capture. Locate the Close button at the bottom of the dialog.

  8. Click Close.

    The Index Advisor Database Capture In Progress dialog closes. The Index Advisor Database Capture dialog shows information about the completed database capture. Locate the Index Recommendations tab at the top of the dialog.

  9. Click the Index Recommendations tab.

    The Index Recommendations tab of the Index Advisor - Database Capture dialog displays.

  10. In the Selector column, select the index recommendations that you want to create.

    You can also click on the column header to sort the table based on the column. A description of each column follows:

    • Selector

      The check box you select to determine the index recommendations that you want to create.

    • Index Recommendation

      The CREATE INDEX statement that the TimesTen index advisor recommends.

    • Affected Statement Count

      The number of statements that benefit from the recommendation.

    • Created

      Shows if you have already created the index recommendation. This value can be Yes or No.

    If you want to select all index recommendations, click the Select all check box.

  11. Once you have selected the index recommendations that you want to apply, click the Create Selected Indexes button.

    The Creating Selected Indexes dialog displays. Locate the Details >> button.

  12. Click Details >>.

    A details pane expands that shows progress information about creating the selected indexes. Locate the Close button at the bottom of the dialog.

  13. Click Close.

    The Creating Selected Indexes dialog closes. The indexes are created. If you want to save the index recommendations, see "Saving index recommendations" in the Oracle SQL Developer Oracle TimesTen In-Memory Database Support User's Guide.

View the TimesTen Index Advisor Capture State

The TimesTen index advisor capture state allows you to view the status of connection and database level captures. To view the TimesTen index advisor capture state for a database, make sure you are on the main SQL Developer page.

  1. Right-click the name of the database and select Index Advisor, then select Index Advisor Capture State.

    The Index Advisor Capture State dialog displays and you see the current status of connection and database level captures.

    You can also click on the column header to sort the table based on the column. A description of each column follows:

    • Connection ID

      The connection ID of the connection that initiated the TimesTen index advisor capture.

    • Capture Level

      The capture level of the TimesTen index advisor capture. This value can be Connection or Database.

    • Capture Mode

      The capture mode of the TimesTen index advisor capture. This value can be Execute SQL or Prepare SQL.

    • Capture State

      The capture state of the TimesTen index advisor capture. This value can be In Progress or Completed.

    • Prepared Count

      The number of prepared SQL statements during the capture period.

    • Execute Count

      The number of executed SQL statements during the capture period.

    • Start Time

      The timestamp of when the index advisor capture began. The timestamp format is YYYY-MM-DD HH:MI:SS.FF, where YYYY is the year, MM the month, DD the day, HH the hour, MI the minutes, SS the seconds, and FF the milliseconds.

    • End Time

      The timestamp of when the index advisor capture ended. The timestamp format is YYYY-MM-DD HH:MI:SS.FF, where YYYY is the year, MM the month, DD the day, HH the hour, MI the minutes, SS the seconds, and FF the milliseconds. This value is empty if the Capture State is in In Progress.

  2. Click Refresh to update the table with the most current information of the TimesTen index advisor captures.

    The Index Advisor Capture State dialog is refreshed with the most recent capture state information.