DataGuard - init parameters

We copy the day before primary init files db, all initialization parameters are identical to that of the primary database

Usually is the change of settings in the standby mode different

I'll give a slightly different answer to @bpeasland.  And that's a typical response of DBA.

It depends on.

Which plan you use your DG waiting for?  for example, a database, a switch, a backup...?

If you plan to use for backups or reports, then it is not a problem to have a lower specced ensures that primary.  As long as you are fully aware of the consequences.

If you want to use as a failover, so it's more of a problem, but again, this depends on what your needs are.  Is your organization willing to accept that a failover situation, your DB can perform the same as it normally does?  How long for?  What is your RTO for the primary?

It depends on.

BTW if you look at the Hardware reqs (https://docs.oracle.com/cd/E11882_01/server.112/e41134/standby.htm#SBYDB4715) there is no mention of a primary/secondary or this production that makes them different, other than architecture and OS.

Tags: Database

Similar Questions

  • A query is very convenient which lists all the important associated DG init parameters

    Version: 11.2/10.2

    Did you guys a very practical query that I could run in the primary and Standby sites that will be all important lists
    Data Guard related init parameters.

    Something like below but a query that lists important Dataguard bound init.ora parameters
    col name format a35
    col display_value forma a20
    set pages 25
    
    SELECT name, display_value FROM v$parameter WHERE name IN ('db_name', 
    'db_block_size','undo_retention',
    'shared_servers', 
    'memory_target','sessions',
    'processes', 
    'session_cached_cursors', 
    'sga_target', 
    'pga_aggregate_target', 
    'compatible', 
    'open_cursors',
    'nls_date_format',
    'db_file_multiblock_read_count',
    'cpu_count',
    'cursor_sharing')ORDER BY name;

    Hello

    You must include standby settings, check below to see if it is useful for you or not?

    sys@ORCL> set line 500
    sys@ORCL> column name for a30
    sys@ORCL> column display_value for a30
    sys@ORCL> SELECT name, display_value FROM v$parameter WHERE name IN ('db_name','db_unique_name','log_archive_config','log_archive_dest_2','log_archive_dest_state_2','fal_client','fal_server','standby_
    file_management') order by name;
    
    NAME                           DISPLAY_VALUE
    ------------------------------ ------------------------------
    db_name                        orcl
    db_unique_name                 orcl
    fal_client
    fal_server
    log_archive_config
    log_archive_dest_2
    log_archive_dest_state_2       enable
    standby_file_management        MANUAL
    
    8 rows selected.
    
    sys@ORCL>
    

    My environment is not in sleep mode, so some of the values are NULL.

    Thank you.

  • Compare the INIT parameters

    Hello gurus,

    I was invited to "' * compare the INIT parameters among 3 bodies *"; " 2 on a particular server and 1 on another server. The oracle DB versions I have for all instances of 3 are:

    Instance 1: 10.2.0.4.0
    Instance 2: 11.2.0.1.0
    3 instance: 11.2.0.1.0

    Please let me know what should I do in matter of compare parameters these instances installed on my servers init. The only thing I know is ' SQL > create pfile from spfile;

    It depends on you are looking for.

    One way is to compare the parameter $ v or v$ spparameter between instances using the links in the database. Version 10 and 11 have a different number of parameters.

    HTH
    Antonio NAVARRO

  • DataGuard init.ora

    Hi all

    9i

    RHEL5

    Can help you identify what are the critical important parameters that will be inside the primary and standby init.ora?

    My point is, because there is a passage such as the role of the two database are inverted or exchanged.

    Then, I conclude that all of the settings contained in the primary and standby must me the same or equal?

    1. for example: standby mode parameter > lock_name_space = STBY

    I can also put it in the primary as > lock_name_space = PROD?

    2. What is the difference between the parameter:

    LOG_ARCHIVE_DEST_1='LOCATION=/U02/oradev/devdb/9.2.0/dbs/arch'

    and

    STANDBY_ARCHIVE_DEST = /u02/oradev/devdb/9.2.0/dbs/arch

    3. is it possible to place these 2 settings on standby and primary?

    LOG_ARCHIVE_DEST_STATE_1 = enable

    LOG_ARCHIVE_DEST_STATE_2 = enable

    Thank you all,

    JC

    Take a look at the documentation. This is for your release (9i)

    Chapter 3 - creating a database of physical sleep.

    Oracle Data Guard Concepts and Administration - content

    Concerning

    AJ

  • Dynamically change the Init parameters

    Hello

    We will improve our database 10.1.0.5 to 10.2.0.5.

    The database is running on pfile.

    SQL > show the pfile parameter

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    chain of SPFile

    After you run the tool preupgrade, got the warnings below.
    **********************************************************************
    Update settings: [update of the Oracle 10.2 database init.ora or spfile]
    **********************************************************************
    ATTENTION: - > "streams_pool_size" must be increased at least 50331648
    ATTENTION: - > "session_max_open_files" must be worn at least 20


    I don't find these settings in the pfile file. Is it possible to dynamically change these settings?

    Can I add these parameters to the pfile file before the upgrade of the database?

    SQL > show parameter of flow

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    STREAMS_POOL_SIZE big integer 0

    SQL > show parameter session_max_open_files

    VALUE OF TYPE NAME
    ------------------------------------ ----------- ------------------------------
    session_max_open_files integer 10

    Thank you
    Pradeep

    As noted, if the values are not explicitly defined, they assume default values - see the documentation

    http://docs.Oracle.com/CD/B14117_01/server.101/b10755/initparams209.htm#REFRN10243
    http://docs.Oracle.com/CD/B14117_01/server.101/b10755/initparams187.htm#REFRN10196

    HTH
    Srini

  • RAC init parameters

    Hello

    We have 2 node rac database version 11.2.0.4 on Linux platform.

    There is a different opinion between our system dba and application dba on init parameter of the cars.

    System dba definied *.processes = 2000 in rac db init file.

    This means that processes 2000 can connect to instance 1 and 2000 process can connect to instance 2 at the same time?

    Or does this mean that 2000 process can connect to all DB?

    We (application dba) says 2000 process can connect to instance 1 and 2000 process can connect to instance 2 at the same time.

    then sysdba said dba 2000 process can connect to all DB IE 1500 to 1 and 500 (max) to the instance 2, but total will not be more than 2000.

    Help, please.

    Thank you

    Ashish

    We (application dba) says 2000 process can connect to instance 1 and 2000 process can connect to instance 2 at the same time.

    then sysdba said dba 2000 process can connect to all DB IE 1500 to 1 and 500 (max) to the instance 2, but total will not be more than 2000.

    This DBA application is correct. 2000 process can connect to instance 1 and 2000 process can connect to instance 2 at the same time. Also... Here is the link to the documentation on this setting: http://docs.oracle.com/database/121/REFRN/refrn10175.htm#REFRN10175

    Note that it says that "several instances can have different values.

    Finally, ask your SYSDBA check RESOURCE_LIMIT $ GV in an Oracle RAC database. Note that each instance has a limit. Here's my setting for the setting PROCESS of my database to RAC 3-blink of eye:

    SQL > show parameter processes

    VALUE OF TYPE NAME

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

    aq_tm_processes integer 1

    db_writer_processes integer 1

    gcs_server_processes integer 2

    global_txn_processes integer 1

    JOB_QUEUE_PROCESSES integer 20

    log_archive_max_processes integer 5

    whole process 1500

    So, I can have up to 1500 process. Fortunately, his instance the because here is what my current use looks like:

    SQL > select INST_ID, resource_name, current_utilization, limit_value

    2 from resource_limit $ SGS where resource_name = '' process. ''

    INST_ID SELECT RESOURCE_NAME CURRENT_UTILIZATION LIMIT_VALU

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

    1 724 1500 process

    2 709 1500 process

    3 720 1500 processes

    I have more than 2000 process total in all instances, higher than my setting. This should prove that the application DBA statement is correct.

    HTH,
    Brian

  • Init parameters

    Background: ColdFusion programmer, trying to learn Flex

    Problem
    How can I pass arguments to initialize / variables in a Flex application at launch? I have searched around the livedocs, but haven't found anything.

    More details
    Each language has a way to pass variables to initialize / arguments / information in the launch ColdFusion app using a URL and form variables. C++ uses the array Args. Some languages use init files. Flex does something? Can I use < param > tags when the page using the < object > tag to call the swf file? Or can I include variables URLS on the page that starts the Flex application and have Flex back on these variables URLS somehow?

    Thank you

    -Neil

    First of all, it is not a matter of Flex Builder, so it should go in the forum Discussion General Flex, not here.

    Second, here's a hint for the documentation search: for some reason any Adobe encapsulates google quotes search terms, which makes it an exact phrase match. Then, when I search here: http://livedocs.macromedia.com/flex/2/docs/wwhelp/wwhimpl/js/html/wwhelp.htm?href=Part2_De vApps.html
    using the words: transfer data to Flex
    I get without success. Remove the quotes from the search terms on the results page google returns several good hits, prominent is this one:
    http://livedocs.Macromedia.com/Flex/2/docs/00001003.html

    Tracy

  • After you have patched init parameters

    Version of the database: 10.2.0.4 Patch 45 on Windows 2003
    1. documentation says to resolve the value '_first_spare_parameter' 6904068 bug. What should be the value if we actually see this bug occurring after you apply the hotfix. How can we determine that we need this setting to be turned on?

    2. How can we determine that we must define "_third_spare_parameter"? How can we check if there is a regression on the log files?

    No, the mentioned parameter '_first_spare_parameter' just NOT and NOT lone operative. It will work as expected only when the Patch 6904068 is applied.

    Description of the main problem:
    Excessive CPU consumption when the mutex for slider axis has been activated. Testicles made on this matter, consisting of the repeated execution of a
    and and the same SQL statement by multiple sessions simultaneously. They will all support for the mutex of mode S child cursor. If the mutex cannot be obtained
    After a few times of spinning, kgx calls a customer provided wait function. For the slider S mutex, the wait function (kksLockWait) was actually yield the CPU
    rather than wait for a fixed time. For this particular unit test, given the number of processors available and the fact that the process had little to others
    that run this SQL, call performance apparently does not provide enough time and the end result is that the processes were constantly spinning and
    the consumption of CPU, trying to get the mutex. This problem is the result of combined factors - the repeated execution of the same simplistic SQL top
    number of simultaneous sessions that running SQL and do not do anything else, large number of processors on the computer and perhaps other factors as well. This
    the combination is probably unlikely to happen in any real life application scenario, although this client insisted that their unit test was representative of their
    real-world application.

    Description of the fix: in kksLockWait(), now wait for a period fixed instead of give up trying to get the mutex in S mode and there is no holder of X.
    By forcing a period much more long wait between attempts to get mutex (compared to "yield"), the unit test has been found to consume much less CPU and
    delivered at rates higher than the old latch implementation

    The time-out period is controlled by a parameter. The parameter as it comes in unique pieces is called "_first_spare_parameter" and takes an integer
    a value that represents the time-out in CENTIseconds (1cs = 10ms). The default value of 0 will retain the current behavior (ie the cPU performance). The value can be
    dynamically adjusted to the level of the SYSTEM, but not at the level of the SESSION.

  • There the init.ora parameters cannot be changed at all?

    DB version: 11 GR 2

    We have the following two types of initialization parameters

    Dynamic - which can be changed without a rebound in DB (example CURSOR_SHARING)
    Static - which can be changed with a rebound in DB (example MEMORY_MAX_TARGET)

    The two types of init parameters listed above can be changed with or without a rebound in the DB. There are initialization parameters that cannot be changed at all with or without a rebound in DB?

    Max wrote:

    Documentation is Oracle that describes the init.ora parameters ' Oracle database reference 11gRelease 2'. It is not answered my question

    Maybe it does.

    of DB_BLOCK_SIZE

    The value of DB_BLOCK_SIZE in effect at the time you create the database determines the size of the blocks. The value must be set to its initial value.


  • Necessary init.ora parameters

    Hi all


    I want to start the database using the nomount using init .ora file
    What, then, are the only init parameters that must be present in the init file so that db is started

    his authorization as a folder number all owned by root! This file should be owned by oracle or user from which you installed oracle.

  • ORA - 16698:LOG_ARCHIVE_DEST_n when you configure dataguard

    Hello

    Im trying to configure a Dataguard under oracle 12 c

    DB01 is primary, DB02 is standby

    On DB01

    ALTER system set log_archive_dest_1 =' LOCATION = / DATA01/DB/DB01/flash/archiv/VALID_FOR =(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME = DB01';

    ALTER system set log_archive_dest_2 is 'SERVICE = DB02 ASYNC VALID_FOR =(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME = DB02';.

    On DB02

    Set log_archive_dest_1 =' LOCATION = / DATA01/DB/DB02/flash/archiv/VALID_FOR =(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME = DB02'

    Set log_archive_dest_2 = 'SERVICE = DGN01 ASYNC VALID_FOR =(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME = DGN01'

    I have issue_

    Create the "DG" configuration as database primary is "DB01" connect identifier is DB01;

    ORA - 16698:LOG_ARCHIVE_DEST_n parameter defined for the object to add

    I discovered that the destination must not be into siege mode.

    Notes on the Oracle:

    To clear the LOG_ARCHIVE_DEST_n parameter, use the ALTER SYSTEM SET LOG_ARCHIVE_DEST_n =""

    However, when configuring physical Standby I read:

    This destination transmits redo data to the remote physical expectations

    Can someone give me a hand

    Christian

    Log_archive_dest_n manual management (and other DG Associates init parameters) and using Data Guard Broker to manage automatically these settings is not the right way (it may cause inconsistency between the spfile and broker configuration files).
    You must clear the log_archive_dest_n parameters defined with the attribute of SERVICE and without NOREGISTER attribute, and then try to create the broker configuration (it will automatically set the log_archive_dest_n when you add a database to the configuration).

    When you use data guard broker always make your changes through DGMGRL for consistency purposes.

    Kind regards

    Ivica Arsov

  • FAL_SERVER and FAL_CLIENT

    Hi all,

    I am going through the Concepts of Dataguard and Docs of the Administration.

    I have a doubt.
    For Eg: My primary db is referred to as: PRD
    Standby DB is the name only: PRDSTBY

    Now regarding the init parameters, I mention

    FAL_CLIENT = PRDSTBY (in the init PRD file)
    FAL_SERVER = PRD (in prd but it works when switch right?)

    FAL_CLIENT = PRDSTBY (in prdstby but it works when switch right?)
    FAL_SERVER = PRD (in PRDSTBY)

    Is my interpretation correct?


    Kind regards
    Delphine K

    Yes it's true. FAL_CLIENT should be your entry of Eve tnsnames. FAL_SERVER must be your tnsnames prod entry
    MSK

    Published by: MSK on November 16, 2009 05:16

  • clean clean

    I use the 1.1 plugin eclipse and the 8520 with the api 5.0 Simulator.

    My application saves a file called DATA.txt and I'm trying to get rid of it.

    I tried clean.bat - it's still there.

    I tried the own eclipse - it's still there.

    I know that this is because the I have open in my application and read the init parameters, which are

    worse - so I want to re - initialize this file. But I can't because I can't delete it.

    Where is the file on the pc?

    What happens here?

    Thank you!

    lucidbee

    I cut and pasted this example of the documentation of the API for the class FileConnection.  It tells you how to create (and remove) a file.

    ... the following code can be used to create a new file on a file system, where CFCard is a valid root name existing file system for a given application:

     try {     FileConnection fconn = (FileConnection)Connector.open("file:///CFCard/newfile.txt");     // If no exception is thrown, then the URI is valid, but the file may or may not exist.     if (!fconn.exists())         fconn.create();  // create the file if it doesn't exist
    
         fconn.close(); } catch (IOException ioe) { }
    

    Developers should always check for existence of file or folder once a connection is established to determine if the file or directory actually exists. Similarly, directories or files can be deleted using the FileConnection.delete () method, and developers should close the connection immediately after deletion to avoid exceptions to access a connection to a non-existent file or directory.

  • test DB has no AMM, the request takes 5 seconds, the prod DB has AMM query takes 5 minutes

    I created a copy of test of production for a long time, when I was creating the test I have not activated AMM.

    A developer created a new report and told me that it took seconds to run on the Pb test, as he was taking up to 10 minutes on the Pb of the production. I got it to extract the SQL code for the report and he ran from a command line, and on the Pb test, it took 5 seconds and more than 5 minutes on the Pb of the production.

    I then checked the AMM with the show memory_target parameter to see if AMM was activated and on the Pb of the prod is 1 GB on the DB test is 0

    memory allocation requests show this for prod:

    NAME                                     VALUE

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

    PGA maximum allowed 578929664

    pga_aggregate_target 0

    SGA_TARGET 0

    MEMORY_TARGET

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

    578929664

    for the BP to test:

    NAME                                       VALUE

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

    PGA maximum allowed 214604800

    pga_aggregate_target 101711872

    SGA_TARGET 624951296

    MEMORY_TARGET

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

    839556096

    I have not dbcontrol currently enabled on the Pb test, so I could not watch the advisors of the memory, but it is enabled on the Pb of the prod, that tells me it should be to the 1 GB is currently at.

    Two of these db are on the same server.

    Now I wonder if I should disable the AMM on the prod server and allocate manually to match the test, or should I change the AMM if possible so that it can perform as good as the Pb of test?

    Thanks in advance.

    I tried the suggestion of Geert earlier but I forgot to mention that it made no difference.

    However, I managed to find out what it is, starting at the beginning by looking at all the init parameters. It was then that I noticed the Prod OPTIMIZER_FEATURES_ENABLE was set to 9.2.0.8, while the test was 11.2.0.3, a quick alter system set optimizer_features_enable = '11.2.0.3' scope = both and the query ran<5 seconds,="" just="" like="" the="" test.="" it="" also="" got="" rid="" of="" the="" note="" that="" the="" cpu="" costing="" was="" not="">

    I thought a bit more wording accurate in the order note explain plan could be useful - but in any case, it makes sense, I guess...

    However, this has been a useful exercise for me, I have a better idea how they use the remote database for retrieving information and will make suggestions, it may be easier to create views of the side remote (SQL Server), rather than on the side of the Oracle.

    Still do not know how the test done with the right parameter and the prod has not, I used to create the init.ora file to create the test instance by getting a carbon copy of the production spfile, but I missed this setting this time.

    In any case, it's a good thing I had the right parameter under test - otherwise the Developer & users may have accepted, he was going to be a slow and left...

    Thanks again for all your help

    PS. Now here is the plan explain of production:

    SQL> SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY_CURSOR(NULL,NULL,'ALLSTATS LAST'));
    SQL_ID  bqh1aq71rshpp, child number 1
    -------------------------------------
    SELECT /*+ GATHER_PLAN_STATISTICS */
    DOMCUST.CUSTOMER,DOMHEADER.WOODTYPE,DOMHEADER.ISSUEDATE ISSUEDATE,
    vw_testlots.TLOT_PREV PREV_LOT, VW_TESTLOTS.TLOT_NEXT NEXT_LOT,
    DOMLOTS.lotno ship_lot,       VW_PTMS_LOTS.AIRDRY
    AIRDRY,VW_PTMS_LOTS.BRIGHTNESS BRIGHT,VW_PTMS_LOTS.DIRT
    DIRT,VW_PTMS_LOTS.VISCOSITY VISCOSITY,
    (A.CCSF_0+B.CCSF_0)/2 CCSF_0,
    (A.TEAR1_0+B.TEAR1_0)/2 TEAR1_0,
    (A.BL_0+B.BL_0)/2 BL_0,
    (A.BURST_0+B.BURST_0)/2 BURST_0,
    (A.BULK_0+B.BULK_0)/2 BULK_0,
    (A.POROSITY_0+B.POROSITY_0)/2 POROSITY_0,
      (A.BOND_0+B.BOND_0)/2 BOND_0,
    (A.OPACITY_0+B.OPACITY_0)/2 OPACITY_0,
    (A.CCSF_1+B.CCSF_1)/2 CCSF_400,
    (A.TEAR1_1+B.TEAR1_1)/2 TEAR1_400,                                 (
    
    Plan hash value: 2207188603
    
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    | Id  | Operation                              | Name         | Starts | E-Rows | A-Rows |   A-Time   | Buffers | Reads  | Writes |  OMem |  1Mem | Used-Mem | Used-Tmp|
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    |   0 | SELECT STATEMENT                       |              |      1 |        |    255 |00:00:05.90 |    1091K|     45 |     45 |       |       |          |         |
    |   1 |  SORT AGGREGATE                        |              |    255 |      1 |    255 |00:00:00.91 |     385K|      0 |      0 |       |       |          |         |
    |*  2 |   FILTER                               |              |    255 |        |  57880 |00:00:01.11 |     385K|      0 |      0 |       |       |          |         |
    |*  3 |    TABLE ACCESS BY INDEX ROWID         | LOTTEST      |    255 |      1 |  57880 |00:00:00.99 |     385K|      0 |      0 |       |       |          |         |
    |*  4 |     INDEX RANGE SCAN                   | UK_LOTNO     |    255 |     45 |    767K|00:00:00.85 |    5015 |      0 |      0 |       |       |          |         |
    |   5 |  SORT AGGREGATE                        |              |    255 |      1 |    255 |00:00:00.52 |     158K|      0 |      0 |       |       |          |         |
    |*  6 |   FILTER                               |              |    255 |        |  55792 |00:00:00.47 |     158K|      0 |      0 |       |       |          |         |
    |*  7 |    TABLE ACCESS BY INDEX ROWID         | LOTTEST      |    255 |      1 |  55792 |00:00:00.36 |     158K|      0 |      0 |       |       |          |         |
    |*  8 |     INDEX RANGE SCAN                   | UK_LOTNO     |    255 |     45 |    516K|00:00:00.55 |    1372 |      0 |      0 |       |       |          |         |
    |   9 |  SORT ORDER BY                         |              |      1 |      1 |    255 |00:00:05.90 |    1091K|     45 |     45 | 70656 | 70656 |63488  (0)|         |
    |  10 |   NESTED LOOPS                         |              |      1 |        |    255 |00:00:04.47 |     547K|     45 |     45 |       |       |          |         |
    |  11 |    NESTED LOOPS                        |              |      1 |      1 |    255 |00:00:04.47 |     546K|     45 |     45 |       |       |          |         |
    |  12 |     NESTED LOOPS                       |              |      1 |      1 |    255 |00:00:03.88 |     383K|     45 |     45 |       |       |          |         |
    |  13 |      NESTED LOOPS                      |              |      1 |      1 |    255 |00:00:03.02 |     979 |     45 |     45 |       |       |          |         |
    |  14 |       NESTED LOOPS                     |              |      1 |      1 |    255 |00:00:03.01 |     712 |     45 |     45 |       |       |          |         |
    |* 15 |        HASH JOIN                       |              |      1 |      1 |    255 |00:00:03.01 |     527 |     45 |     45 |   858K|   858K| 1283K (0)|         |
    |  16 |         NESTED LOOPS                   |              |      1 |     19 |    255 |00:00:00.01 |      28 |      0 |      0 |       |       |          |         |
    |  17 |          NESTED LOOPS                  |              |      1 |      1 |      9 |00:00:00.01 |      17 |      0 |      0 |       |       |          |         |
    |  18 |           TABLE ACCESS BY INDEX ROWID  | DOMCUST      |      1 |      1 |      1 |00:00:00.01 |       2 |      0 |      0 |       |       |          |         |
    |* 19 |            INDEX UNIQUE SCAN           | PK_DOMCUST   |      1 |      1 |      1 |00:00:00.01 |       1 |      0 |      0 |       |       |          |         |
    |* 20 |           TABLE ACCESS FULL            | DOMHEADER    |      1 |      1 |      9 |00:00:00.01 |      15 |      0 |      0 |       |       |          |         |
    |* 21 |          INDEX RANGE SCAN              | PK_DOMLOTS   |      9 |     21 |    255 |00:00:00.01 |      11 |      0 |      0 |       |       |          |         |
    |  22 |         VIEW                           | VW_PTMS_LOTS |      1 |    101 |  15101 |00:00:03.05 |     499 |     45 |     45 |       |       |          |         |
    |  23 |          SORT UNIQUE                   |              |      1 |    101 |  15101 |00:00:03.02 |     499 |     45 |     45 |  1328K|   587K| 1180K (0)|         |
    |  24 |           UNION-ALL                    |              |      1 |        |  15101 |00:00:03.06 |     499 |     45 |     45 |       |       |          |         |
    |  25 |            HASH GROUP BY               |              |      1 |    100 |  15101 |00:00:02.98 |       0 |     45 |     45 |  3004K|   982K| 3262K (1)|    1024 |
    |* 26 |             FILTER                     |              |      1 |    100 |  15842 |00:00:02.99 |       0 |      0 |      0 |       |       |          |         |
    |  27 |              REMOTE                    |              |      1 |        |  16563 |00:00:02.95 |       0 |      0 |      0 |       |       |          |         |
    |* 28 |            TABLE ACCESS FULL           | PTMSLOTS     |      1 |      1 |      0 |00:00:00.01 |     499 |      0 |      0 |       |       |          |         |
    |* 29 |        INDEX UNIQUE SCAN               | PK_DOMLOTS   |    255 |      1 |    255 |00:00:00.01 |     185 |      0 |      0 |       |       |          |         |
    |  30 |       TABLE ACCESS BY INDEX ROWID      | DOMHEADER    |    255 |      1 |    255 |00:00:00.01 |     267 |      0 |      0 |       |       |          |         |
    |* 31 |        INDEX UNIQUE SCAN               | PK_DOMHEADER |    255 |      1 |    255 |00:00:00.01 |      12 |      0 |      0 |       |       |          |         |
    |  32 |      TABLE ACCESS BY INDEX ROWID       | LOTTEST      |    255 |      1 |    255 |00:00:00.91 |     383K|      0 |      0 |       |       |          |         |
    |* 33 |       INDEX UNIQUE SCAN                | PK_LOTTEST   |    255 |      1 |    255 |00:00:00.91 |     382K|      0 |      0 |       |       |          |         |
    |  34 |        SORT AGGREGATE                  |              |    255 |      1 |    255 |00:00:00.91 |     382K|      0 |      0 |       |       |          |         |
    |  35 |         TABLE ACCESS BY INDEX ROWID    | LOTTEST      |    255 |      1 |    261 |00:00:00.90 |     382K|      0 |      0 |       |       |          |         |
    |* 36 |          INDEX RANGE SCAN              | UK_LOTNO     |    255 |      1 |    261 |00:00:00.90 |     382K|      0 |      0 |       |       |          |         |
    |  37 |           SORT AGGREGATE               |              |    255 |      1 |    255 |00:00:00.90 |     382K|      0 |      0 |       |       |          |         |
    |* 38 |            FILTER                      |              |    255 |        |  57880 |00:00:01.09 |     382K|      0 |      0 |       |       |          |         |
    |* 39 |             TABLE ACCESS BY INDEX ROWID| LOTTEST      |    255 |      1 |  57880 |00:00:00.97 |     382K|      0 |      0 |       |       |          |         |
    |* 40 |              INDEX RANGE SCAN          | UK_LOTNO     |    255 |     45 |    767K|00:00:00.85 |    1798 |      0 |      0 |       |       |          |         |
    |* 41 |     INDEX UNIQUE SCAN                  | PK_LOTTEST   |    255 |      1 |    255 |00:00:00.53 |     162K|      0 |      0 |       |       |          |         |
    |  42 |      SORT AGGREGATE                    |              |    255 |      1 |    255 |00:00:00.53 |     162K|      0 |      0 |       |       |          |         |
    |  43 |       TABLE ACCESS BY INDEX ROWID      | LOTTEST      |    255 |      1 |    264 |00:00:00.52 |     162K|      0 |      0 |       |       |          |         |
    |* 44 |        INDEX RANGE SCAN                | UK_LOTNO     |    255 |      1 |    264 |00:00:00.52 |     162K|      0 |      0 |       |       |          |         |
    |  45 |         SORT AGGREGATE                 |              |    255 |      1 |    255 |00:00:00.52 |     162K|      0 |      0 |       |       |          |         |
    |* 46 |          FILTER                        |              |    255 |        |  55792 |00:00:00.46 |     162K|      0 |      0 |       |       |          |         |
    |* 47 |           TABLE ACCESS BY INDEX ROWID  | LOTTEST      |    255 |      1 |  55792 |00:00:00.35 |     162K|      0 |      0 |       |       |          |         |
    |* 48 |            INDEX RANGE SCAN            | UK_LOTNO     |    255 |     45 |    516K|00:00:00.57 |    5282 |      0 |      0 |       |       |          |         |
    |  49 |    TABLE ACCESS BY INDEX ROWID         | LOTTEST      |    255 |      1 |    255 |00:00:00.01 |     255 |      0 |      0 |       |       |          |         |
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    
    Predicate Information (identified by operation id):
    ---------------------------------------------------
    
       2 - filter(:B1-365<=:B2+365)
       3 - filter(("WOODTYPE"=:B1 AND "PRODDATE">=:B2-365 AND "PRODDATE"<=:B3+365))
       4 - access("LOTNO"<:B1)
       6 - filter(:B1-365<=:B2+365)
       7 - filter(("WOODTYPE"=:B1 AND "PRODDATE">=:B2-365 AND "PRODDATE"<=:B3+365))
       8 - access("LOTNO">=:B1)
      15 - access("DOMLOTS"."LOTNO"="VW_PTMS_LOTS"."LOTID")
      19 - access("DOMCUST"."DOMCUSTID"=1)
      20 - filter(("DOMHEADER"."DOMCUSTID"=1 AND "DOMHEADER"."ISSUEDATE">=TO_DATE(' 2014-05-30 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "DOMHEADER"."WOODTYPE"='H'
                  AND TRUNC(INTERNAL_FUNCTION("DOMHEADER"."ISSUEDATE"))<=TO_DATE(' 2015-05-30 00:00:00', 'syyyy-mm-dd hh24:mi:ss')))
      21 - access("DOMHEADER"."DOMID"="DOMLOTS"."DOMID")
      26 - filter("A"."StartTime">GREATEST(SYSDATE@!-730,TO_DATE(' 2013-04-16 13:00:00', 'syyyy-mm-dd hh24:mi:ss')))
      28 - filter("PRODTIME">SYSDATE@!-730)
      29 - access("DOMHEADER"."DOMID"="DOMLOTS"."DOMID" AND "DOMLOTS"."LOTNO"="DOMLOTS"."LOTNO")
      31 - access("DOMLOTS"."DOMID"="DOMHEADER"."DOMID")
      33 - access("A"."LOTID"=)
      36 - access("LOTTEST"."LOTNO"=)
      38 - filter(:B1-365<=:B2+365)
      39 - filter(("WOODTYPE"=:B1 AND "PRODDATE">=:B2-365 AND "PRODDATE"<=:B3+365))
      40 - access("LOTNO"<:B1)
      41 - access("B"."LOTID"=)
      44 - access("LOTTEST"."LOTNO"=)
      46 - filter(:B1-365<=:B2+365)
      47 - filter(("WOODTYPE"=:B1 AND "PRODDATE">=:B2-365 AND "PRODDATE"<=:B3+365))
      48 - access("LOTNO">=:B1)
    
    105 rows selected.
    
    Elapsed: 00:00:00.12
    
  • ODBC connection between oracle db and db US7ASCII mysql UTF8

    We are trying to convert our Oracle US7ASCII databases to Unicode (AL32UTF8). We have Connector/ODBC 5.3.4 for Solaris (mysql-connector-odbc-commercial-5.3.4-solaris11-sparc-64bit). Everything works when the two databases are US7ASCII. We have used MISP to convert the Oracle in AL32UTF8 database, changed nothing else, and the connection stops working.

    /usr/local/etc/ODBC.ini table of contents:

    [Default]

    Driver = /usr/local/myodbc/lib/libmyodbc5.so

    Description = MySQL ODBC Driver

    SERVER = alex

    PORT = 3312

    USER = schzoneoffice

    Password =

    Database = SCHZONE

    OPTION = 3

    SOCKET =

    $ORACLE_HOME/hs/admin/initmysql.ora table of contents:


    #

    # HS init parameters

    #

    HS_FDS_CONNECT_INFO = mysql

    HS_FDS_TRACE_LEVEL = we

    HS_FDS_TRACE_FILE = mysql.log

    HS_FDS_SHAREABLE_NAME = /usr/local/lib/libodbc.so

    #

    # ODBC specific environment variables

    #

    Set ODBCINI=/usr/local/etc/odbc.ini

    Can someone suggest the parameters we can try to get this working? I tried to play with the settings HS_LANGUAGE and HS_NLS_NCHAR my initmysql.ora file, under $ORACLE_HOME/hs/admin, nothing helps.

    Right after that I posted this, I answered my own question:

    I was an invalid test, while playing with the parameter HS_LANGUAGE the other day. (lsnrctl reload does not work properly - need to stop and start the receiver, also disconnect and reconnect your oracle session, given that the mysql connection is persistent)

    Today, I added HS_LANGUAGE = american_america. US7ASCII to my initmysql.ora file and it works.

Maybe you are looking for