Oracle Timesten Overview and Datasore Refresh

 Overview of Timesten:

Oracle TimesTen In-Memory Database (TimesTen) is a full-featured, memory-optimized, relational database with persistence and recoverability. It provides applications with the instant responsiveness and very high throughput required by database-intensive applications. Deployed in the application tier, TimesTen operates on databases that fit entirely in physical memory (RAM). Applications access the TimesTen database using standard SQL interfaces. For customers with existing application data residing on the Oracle Database, TimesTen is deployed as an in-memory cache database with automatic data synchronization between TimesTen and the Oracle Database.


Timesten Datasource Refresh:


Step 1: Take backup. (Source)

/export/TimesTen/7.0.5_64/bin/ttbackup -dir /var/tmp -fname PROD_DATASTORE_081010_Bkp DSNNAME


Step 2: Scp dumps to Target.


Step 3: Destroy the DSN(Target)


hostname% ./ttdestroy DSNNAME

hostname% ./ttstatus

TimesTen status report as of Mon Oct 11 08:20:16 2010


Daemon pid 10251 port 53388 instance tt1121

TimesTen server pid 10256 started on port 53389

------------------------------------------------------------------------

Accessible by group cheops

End of report


Step 4: Start restore


hostname% ./ttrestore -fname PROD_DATASTORE_081010_Bkp -dir /var/tmp DSNNAME

Restore started ...

ttRestore: SQL Warning: Connected to data store with warning

*** [TimesTen][TimesTen 11.2.1.6.1 ODBC Driver][TimesTen]TT6200: New value for permanent data partition size ignored since smaller than current value of 10240 megabytes -- file "db.c", lineno 10141, procedure "sbDbConnect"

*** ODBC Warning = 01000, TimesTen Warning = 6200  ( HAVE TO CHANGE PERMSIZE VALUE)


Restore complete


Some times we might encounter above warning. It is because the permsize is different from source & target. We have to change the permsize in sys.odbc.ini.


Changing sys.odbc.ini file.


hostname% cd /var/TimesTen/tt11

hostname% cp -p sys.odbc.ini sys.odbc.ini_sep11_2010

hostname% vi sys.odbc.ini


change PermSizeà  10240


We have to do below steps in order to apply the new value.


Step 5: make rampolicy manual.


hostname% ./ttAdmin -rampolicy manual DSNNAME


Step 6:  Ram unload and load it


hostname% ./ttAdmin -ramunload DSNNAME

RAM Residence Policy            : manual


hostname% ./ttAdmin -ramload DSNNAME


hostname% ./ttisql DSNNAME


Copyright (c) 1996-2010, Oracle.  All rights reserved.

Type ? or "help" for help, type "exit" to quit ttIsql.


Step 7: drop replications.

Command> repschemes;


Replication Scheme REPL.PROD:



  Store: PROD_DS on HOSTNAME

    Port: (auto)

    Log Fail Threshold: (none)

    Retry Timeout: 120 seconds

    Compress Traffic: Disabled


1 replication scheme found.

Command> drop replication REPL.PROD;

Command> repschemes;


0 replication schemes found.


Step 8: Delete bookmark.


Command> delete xladeletebookmark


XLA Bookmark: PROD_bookmark

  Read Log File:  1286099029

  Read Offset:    1705274

  Purge Log File: 1310

  Purge Offset:   55749560

  PID:            1868

  In Use:         No


1 bookmark found.

Command> xladeletebookmark PROD_bookmark;

Command> xladeletebookmark;


0 bookmarks found.

Command>

Command>


Step 9: Create the users which are requested by user.

Command> create user USERNAME identified by 'PASSWORD';


Step 10: Make Rampolicy to always.


hostname% ./ttAdmin -rampolicy always DSNNAME

Comments

Post a Comment

Popular posts from this blog

How to Solve - "WAIT FOR EMON PROCESS NTFNS"

Event Monitor Process in short called as EMON is generally used by oracle to send notification. Often applications uses Database Change Notification process also called as DBCN to be aware of changes in the database, based on these notifications they take further actions. Often clients subscribe to the database and notifications are send as callback to them. In some cases you will notice database sessions are showing wait event "WAIT FOR EMON PROCESS NTFNS" and it can even make your database un-responsive. One observation can be these processes are taking more CPU (may not in be in all cases). As stated EMON process deals with database notification and it's spawn and gets down itself and Administrators have no control on theses processes. Anyone can go through oracle documents to read more EMON functioning process.  EMON uses oracle advanced queues and database queue notifications into them and EMON process these notifications to clients based on their subscriptions. In s
Read more

Query Regression - "OR" Transformation Oracle 19c

Recently while upgrading Oracle Database from version 12.1 to 19.10 found there were couple of queries which was running slow post upgrade. Usually these type of behavior is seen while upgrading to newer version and oracle provide various ways to fix them. The difference between good and bad plan was an introduction of  "MERGE JOIN CARTESIAN" (aka MJC) and that's in where regressed query in 19c taking most of the time. MJC sometimes works for queries but in this case it was clearly not helping.  We had following options here:     1. Copy the profile from 12c to 19c database and it worked, but the problem was not just to specific query but with many similar query. This means profile option is not very attractive in this case.     2. We also tried running query with OFE 12.1 to use the same optimizer features as previous version and query behaves well. Though this option can't be placed as we need to use 19c OFE and can be placed only for testing purpose.           alte
Read more

ORA - 12537: TNS: connection closed

Often when active clone to be done to create a new environment, we land up into couple of issues. I will discuss about one issues during this process. Action : Create a new database on different machine from a source. Error : ORA - 12537: TNS: connection closed In order to duplicate the environment was using below rman log /tmp/duplicate.log connect target sys/<password>@<source tns alias> connect auxiliary sys/<password>@<target tns alias> run{ allocate channel ch1 device type disk; allocate channel ch2 device type disk; allocate channel ch3 device type disk; allocate channel ch4 device type disk; allocate auxiliary channel ax1 device type disk; allocate auxiliary channel ax2 device type disk; allocate auxiliary channel ax3 device type disk; allocate auxiliary channel ax4 device type disk; DUPLICATE TARGET DATABASE TO <TARGET_DBNAME> FROM ACTIVE DATABASE NOFILENAMECHECK; } While making connection to Auxiliary database received mentioned error ORA - 12537:
Read more