New feature SOCKSPROXY parameter in GoldenGate 12c

Hello everyone!
Does anybody try to use the new parameter SOCKSPROXY in the GoldenGate extract?
I got the following error when I use it:
2015-04-14 12:40:37  ERROR   OGG-00382  Oracle GoldenGate Capture for Oracle, ext2.prm:  Invalid option for RMTHOST.
2015-04-14 12:40:37  ERROR   OGG-01668  Oracle GoldenGate Capture for Oracle, ext2.prm:  PROCESS ABENDING.
Settings:
RMTHOST dc0a5db00.ps, MGRPORT 7809, SOCKSPROXY 10.70.133.10:17809
or
ADD EXTRACT test1 desc "test extract" RMTHOST dc0a5db00.ps MGRPORT 7809 RMTNAME test1 SOCKSPROXY 10.70.133.10:17809
Could you please help me in it?
Thank you beforehand,
Sergey Kushnarev.

Hi Nishar,
Thank you for our quick answer! You are just right! I have the privious version
Oracle GoldenGate 12.1.2
As I understand there is no such version 12.1.2.1.0 for Solaris SPARC 64bit? Only Linux and et cetera...?

Similar Messages

  • A potential bug on the new feature (12c) of Identity Column?

    Hi,
    I am testing a newly introduced feature of Identity Column in Oracle 12c. I used EclipseLink (JPA) to access the database.
    I may have found a potential bug with this feature. I am getting "ORA-30667: cannot drop NOT NULL constraint on a DEFAULT ON NULL column" when I try to insert a row. My code doesn't explicitly drop "NOT NULL" constraint.
    When I delete all the tables under the user and re-define the user and the tables, the error disappear.
    Here are the details:
    Error:
    DatabaseException Internal Exception: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 ORA-30667: cannot drop NOT NULL constraint on a DEFAULT ON NULL column Error Code: 604 Call: INSERT INTO MyTable (ID, SOMEID, SOMEDATE) VALUES (?, ?, ?) bind => [null, 100100147, 2013-11-29 Query: InsertObjectQuery(cus.entity.MyTable@1a9ea5b)
    Table definition:
    CREATE TABLE MyTable (id NUMBER GENERATED BY DEFAULT ON NULL AS IDENTITY PRIMARY KEY,
          someId INT NOT NULL,
          someDate DATE NOT NULL,
          PARTITION BY range(someDate)
          interval(numtodsinterval(1,'year'))
          SUBPARTITION BY HASH ( someId)
          SUBPARTITIONS 20
           PARTITION p0 VALUES LESS THAN (TO_DATE('01-12-2013', 'DD-MM-YYYY'))
    Could anyone tell me if there might be a bug associated with the new feature or if there was something wrong with my code?
    I would be appreciated if anyone can help.

    "here is a reproducible test case in the SCOTT schema - if it reproduces for you open an SR with Oracle"
    Yes. I have just followed the instruction you posted and managed to re-produce the same error I reported earlier. Here are the details of the script output following your posted instruction:
    table MYTABLE dropped.
    purge recyclebin
    table MYTABLE created.
    1 rows inserted.
    table MYTABLE dropped.
    OBJECT_NAME                                                                                                                      ORIGINAL_NAME                                                                                                                    OPERATION TYPE                      TS_NAME                        CREATETIME          DROPTIME               DROPSCN PARTITION_NAME                                                                                                                   CAN_UNDROP CAN_PURGE    RELATED BASE_OBJECT PURGE_OBJECT      SPACE
    BIN$6NCDTxmXTb2QBpUWF0kGqw==$0                                                                                                   SYS_C0010655                                                                                                                     DROP      INDEX                     USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030808                                                                                                                                  NO         YES            98789       98789        98812          8
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:30:56 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98790       98789        98789          0
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:31:37 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98833       98789        98789       1024
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:31:37 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98833       98789        98789       1024
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:31:37 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98833       98789        98789       1024
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:31:37 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98833       98789        98789       1024
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:31:37 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98833       98789        98789       1024
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:31:37 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98833       98789        98789       1024
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:31:37 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98833       98789        98789       1024
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:31:37 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98833       98789        98789       1024
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:31:37 2013-12-01:10:32:17    4030812                                                                                                                                  NO         NO             98833       98789        98789       1024
    BIN$Ka0sgN7XRBeCsjyXTQ76cA==$0                                                                                                   MYTABLE                                                                                                                          DROP      Table Composite Partition USERS                          2013-12-01:10:31:37 2013-12-01:10:32:17    4030812                                                                                                                          &

  • Crvs2010 beta - parameter panel - new feature

    Hello,
    I read the list of  new features for crvs2010. One of the new features listed in the message is the Parameter Panel. The runtime engine supports a parameter panel on the left-hand side. You can optionally place parameters on the panel.
    I did not see the feature in the beta that I have installed. Is it in the beta yet, or is there really something wrong with my installation?
    I would greatly appreciate it if someone would let me know if they have this feature?
    Thank you
    Tracy

    No problem David.
    I know that you have a lot on your plate and I have been known to be a handful, as they say.
    I can understand not updating the vs viewer, when there are other, more up to date options available. For the most post Visual Studio and Crystal are for what us old timers would have called "hard core" programmers, not end users. Today, though, that is changing, more end-users are sometimes very involved in creating what they need.
    When I can catch my breath, I am going to search for a beginners tutorial that covers setting up the .net winform viewer.
    As usual, thank you for all of your help. I really appreciate it.

  • Where can i find best course material for Oracle 12c New features for admin

    Dear Good wishes.
    Im oracle 10g ocp certified.  Looking to upgrade to OCP 12c new features for admin.
    I want to get a best course material for this. Please guide me to find the downloadable link.
    Thank you.

    http://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=1Z0-060
    or https://www.selftestsoftware.com/certtestprep/practice-test/oracle/1z0-060.kap
    or https://www.transcender.com/practice-exam/oracle/1z0-060.kap
    or https://www.transcender.com/e-learning/oracle/1z0-060.kap
    or  http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=609&get_params=dc:D77758,clang:EN
    Hemant K Chitale

  • Register in integrated capture in GoldenGate 12c

    register extract <name process > database
    register in integrated capture in GoldenGate 12c.
    detail workflow in register?
    Thanks,
    T N

    Hi T N,
    Integrated Capture is one of the New features of Oracle GoldenGate  11g. In Integrated Capture mode, the Extract process does not directly reads the Redo Logs. Instead, it directly interacts with the database log mining server.
    The log mining server reads the database redo logfiles and captures the changes in the form of Logical Change Records. These records are then written to the Oracle GoldenGate trail files by the Extract Process.
    Earlier in Classic Capture Mode, the Extract directly reads the Redo Logfiles, captures the changes and writes it to the GoldenGate Trail Files. But here it is totally different. The Oracle has binded the GoldenGate process with the Oracle Log Mining Server to capture the changes and hence it is has been named as Integrated Capture.
    To Integrate the Extract with the Database Log miner server, we need to first Register the extract with the database.
    REGISTER EXTRACT <EXTRACT_NAME> DATABASE
    This registers the Extract with the database to make the Extract process integrate with the Oracle Database Log miner server. Once you Register your Primary Extract to the database, automatically dedicated Log Miner Server will be assigned to that Primary Extract Group. So that Log Miner Server will capture the changes from the Redo Logs and gives it to the Extract process which in turn is written to the GoldenGate Trail files.
    Only Primary Extract can be registered with the Database. I mean if you are using a Datapump extract, you cannot register it to the Database.
    Regards,
    Veera

  • Oracle 10G New Feature........Part 1

    Dear all,
    from last couple of days i was very busy with my oracle 10g box,so i think this is right time to
    share some intresting feature on 10g and some internal stuff with all of you.
    Have a look :-
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Oracle 10g Memory and Storage Feature.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    1.Automatic Memory Management.
    2.Online Segment Shrink
    3.Redolog Advisor, checkpointing
    4.Multiple Temporary tablespace.
    5.Automatic Workload Repository
    6.Active Session History
    7.Misc
    a)Rename Tablespace
    b)Bigfile tablespace
    c)flushing buffer cache
    8.ORACLE INTERNAL
    a)undocumented parameter (_log_blocks_during_backup)
    b)X$ view (x$messages view)
    c)Internal Structure of Controlfile
    1.Automatic memory management
    ================================
    This feature reduce the overhead of oracle DBA.previously mostly time we need to set diff oracle SGA parameter for
    better performance with the help of own experience,advice views and by monitoring the behaviour
    of oracle database.
    this was just time consuming activity.........
    Now this feature makes easy life for oracle DBA.
    Just set SGA_TARGET parameter and it automatically allocate memory to different SGA parameter.
    it focus on DB_CACHE_SIZE
    SHARED_POOL_SIZE
    LARGE_POOL
    JAVA_POOL
    and automatically set it as
    __db_cache_size
    __shared_pool_size
    __large_pool_size
    __java_pool_size
    check it in alert_log
    MMAN(memory manager) process is new in 10g and this is responsible for sga tuning task.
    it automatically increase and decrease the SGA parameters value as per the requirement.
    Benefit:- Maximum utlization of available SGA memory.
    2.Online Segment Shrink.
    ==========================
    hmmmmm again a new feature by oracle to reduce the downtime.Now oracle mainly focus on availablity
    thats why its always try to reduce the downtime by intrducing new feature.
    in previous version ,reducing High water mark of table was possible by
    Exp/imp
    or
    alter table move....cmd. but on these method tables was not available for normal use for long hrs if it has more data.
    but in 10g with just few command we can reduce the HWmark of table.
    this feature is available for ASSM tablespaces.
    1.alter table emp enable row movement.
    2.alter table emp shrink space.
    the second cmd have two phases
    first phase is to compact the segment and in this phase DML operations are allowed.
    second phase(shrink phase)oracle shrink the HWM of table, DML operation will be blocked at that time for short duration.
    So if want to shrink the HWM of table then we should use it with two diff command
    first compact the segment and then shrink it on non-peak hrs.
    alter table emp shrink space compact. (This cmd doesn't block the DML operation.)
    and alter table emp shrink space. (This cmd should be on non-peak hrs.)
    Benefit:- better full table scan.
    3.Redolog Advisor and checkpointing
    ================================================================
    now oracle will suggest the size of redo log file by V$INSTANCE_RECOVERY
    SELECT OPTIMAL_LOGFILE_SIZE
    FROM V$INSTANCE_RECOVERY
    this value is influence with the value of FAST_START_MTTR_TARGET .
    Checkpointing
    Automatic checkpointing will be enable after setting FAST_START_MTTR_TARGET to non-zero value.
    4.Multiple Temporary tablespace.
    ==================================
    Now we can manage multiple temp tablespace under one group.
    we can create a tablespace group implicitly when we include the TABLESPACE GROUP clause in the CREATE TEMPORARY TABLESPACE or ALTER TABLESPACE statement and the specified tablespace group does not currently exist.
    For example, if group1 is not exists,then the following statements create this groups with new tablespace
    CREATE TEMPORARY TABLESPACE temp1 TEMPFILE '/u02/oracle/data/temp01.dbf'
    SIZE 50M
    TABLESPACE GROUP group1;
    --Add Existing temp tablespace into group by
    alter tablespace temp2 tablespace group group1.
    --we can also assign the temp tablespace group on database level as default temp tablespace.
    ALTER DATABASE <db name> DEFAULT TEMPORARY TABLESPACE group1;
    benefit:- Better I/O
    One sql can use more then one temp tablespace
    5.AWR(Automatic Workload Repository):-
    ================================== AWR is built in Repository and Central point of Oracle 10g.Oracle self managing activities
    is fully dependent on AWR.by default after 1 hr, oracle capure all database uses information and store in AWR with the help of
    MMON process.we called it Memory monitor process.and all these information are kept upto 7 days(default) and after that it automatically purge.
    we can generate a AWR report by
    SQL> @?/rdbms/admin/awrrpt
    Just like statspack report but its a advance and diff version of statspack,it provide more information of Database as well as OS.
    it show report in Html and Text format.
    we can also take manually snapshot for AWR by
    BEGIN
    DBMS_WORKLOAD_REPOSITORY.CREATE_SNAPSHOT ();
    END;
    **The STATISTICS_LEVEL initialization parameter must be set to the TYPICAL or ALL to enable the Automatic Workload Repository.
    [oracle@RMSORA1 oracle]$ sqlplus / as sysdba
    SQL*Plus: Release 10.1.0.2.0 - Production on Fri Mar 17 10:37:22 2006
    Copyright (c) 1982, 2004, Oracle. All rights reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> @?/rdbms/admin/awrrpt
    Current Instance
    ~~~~~~~~~~~~~~~~
    DB Id DB Name Inst Num Instance
    4174002554 RMSORA 1 rmsora
    Specify the Report Type
    ~~~~~~~~~~~~~~~~~~~~~~~
    Would you like an HTML report, or a plain text report?
    Enter 'html' for an HTML report, or 'text' for plain text
    Defaults to 'html'
    Enter value for report_type: text
    Type Specified: text
    Instances in this Workload Repository schema
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DB Id Inst Num DB Name Instance Host
    * 4174002554 1 RMSORA rmsora RMSORA1
    Using 4174002554 for database Id
    Using 1 for instance number
    Specify the number of days of snapshots to choose from
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Entering the number of days (n) will result in the most recent
    (n) days of snapshots being listed. Pressing <return> without
    specifying a number lists all completed snapshots.
    Listing the last 3 days of Completed Snapshots
    Snap
    Instance DB Name Snap Id Snap Started Level
    rmsora RMSORA 16186 16 Mar 2006 17:33 1
    16187 16 Mar 2006 18:00 1
    16206 17 Mar 2006 03:30 1
    16207 17 Mar 2006 04:00 1
    16208 17 Mar 2006 04:30 1
    16209 17 Mar 2006 05:00 1
    16210 17 Mar 2006 05:31 1
    16211 17 Mar 2006 06:00 1
    16212 17 Mar 2006 06:30 1
    16213 17 Mar 2006 07:00 1
    16214 17 Mar 2006 07:30 1
    16215 17 Mar 2006 08:01 1
    16216 17 Mar 2006 08:30 1
    16217 17 Mar 2006 09:00 1
    Specify the Begin and End Snapshot Ids
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Enter value for begin_snap: 16216
    Begin Snapshot Id specified: 16216
    Enter value for end_snap: 16217
    End Snapshot Id specified: 16217
    Specify the Report Name
    ~~~~~~~~~~~~~~~~~~~~~~~
    The default report file name is awrrpt_1_16216_16217.txt. To use this name,
    press <return> to continue, otherwise enter an alternative.
    Benefit:- Now DBA have more free time to play games.....................:-)
    Advance version of statspack
    more DB and OS information with self managing capabilty
    New Automatic alert and database advisor with the help of AWR.
    6.Active Session History:-
    ==========================
    V$active_session_history is view that contain the recent session history.
    the memory for ASH is comes from SGA and it can't more then 5% of Shared pool.
    So we can get latest and active session report from v$active_session_history view and also get histortical data of
    of session from DBA_HIST_ACTIVE_SESS_HISTORY.
    v$active_session_history include some imp column like:-
    ~SQL identifier of SQL statement
    ~Object number, file number, and block number
    ~Wait event identifier and parameters
    ~Session identifier and session serial number
    ~Module and action name
    ~Client identifier of the session
    7.Misc:-
    ========
    Rename Tablespace:-
    =================
    in 10g,we can even rename a tablespace by
    alter tablespace <tb_name> rename to <tb_name_new>;
    This command will update the controlfile,data dictionary and datafile header,but dbf filename will be same.
    **we can't rename system and sysaux tablespace.
    Bigfile tablespace:-
    ====================
    Bigfile tablespace contain only one datafile.
    A bigfile tablespace with 8K blocks can contain a 32 terabyte datafile.
    Bigfile tablespaces are supported only for locally managed tablespaces with automatic segment-space management.
    we can take the advantage of bigfile tablespace when we are using ASM or other logical volume with RAID.
    without ASM or RAID ,it gives poor response.
    syntax:-
    CREATE BIGFILE TABLESPACE bigtbs
    Flushing Buffer Cache:-
    ======================
    This option is same as flushing the shared pool,but only available with 10g.
    but i don't know, whats the use of this command in prod database......
    anyway we can check and try it on test server for tuning n testing some query etc....
    SQL> alter system flush buffer_cache;
    System altered.
    ++++++++++++++++++
    8.Oracle Internal
    ++++++++++++++++++
    Here is some stuff that is not related with 10g but have some intresting things.
    a)undocumented parameter "_log_blocks_during_backup"
    ++++++++++++++++++++++++
    as we know that oracle has generate more redo logs during hotbackup mode because
    oracle has to maintain the a complete copy of block into redolog due to split block.
    we can also change this behaviour by setting this parameter to False.
    If Oracle block size equals the operating system block size.thus reducing the amount of redo generated
    during a hot backup.
    WITHOUT ORACLE SUPPORT DON'T SET IT ON PROD DATABASE.THIS DOCUMENT IS JUST FOR INFORMATIONAL PURPOSE.
    b)some X$ views (X$messages)
    ++++++++++++++++
    if you are intresting in oracle internal architecture then x$ view is right place for getting some intresting things.
    X$messages :-it show all the actions that a background process do.
    select * from x$messages;
    like:-
    lock memory at startup MMAN
    Memory Management MMAN
    Handle sga_target resize MMAN
    Reset advisory pool when advisory turned ON MMAN
    Complete deferred initialization of components MMAN
    lock memory timeout action MMAN
    tune undo retention MMNL
    MMNL Periodic MQL Selector MMNL
    ASH Sampler (KEWA) MMNL
    MMON SWRF Raw Metrics Capture MMNL
    reload failed KSPD callbacks MMON
    SGA memory tuning MMON
    background recovery area alert action MMON
    Flashback Marker MMON
    tablespace alert monitor MMON
    Open/close flashback thread RVWR
    RVWR IO's RVWR
    kfcl instance recovery SMON
    c)Internal Structure of Controlfile
    ++++++++++++++++++++++++++++++++++++
    The contents of the current controlfile can be dumped in text form.
    Dump Level Dump Contains
    1 only the file header
    2 just the file header, the database info record, and checkpoint progress records
    3 all record types, but just the earliest and latest records for circular reuse record types
    4 as above, but includes the 4 most recent records for circular reuse record types
    5+ as above, but the number of circular reuse records included doubles with each level
    the session must be connected AS SYSDBA
    alter session set events 'immediate trace name controlf level 5';
    This dump show lots of intresting information.
    it also show rman recordes if we used this controlfile in rman backup.
    Thanks
    Kuljeet Pal Singh

    You can find each doc in html and pdf format on the Documentation Library<br>
    You can too download all the documentation in html format to have all on your own computer here (445.8MB)<br>
    <br>
    Nicolas.

  • 10 new features to the oracle dataabse 10g

    Hi all.
    Recently, I have been interivewed and I have been asked to list 10 new features of Oracle 10g.
    I told him about:
    1) Here, stats have been collected automatically, in oracle 9i it was manual
    2) AWR
    3) RULE based optimizer is not there only in oracle 9i
    4) ASM
    Anything else which you want to mentioned:

    The Automatic Database Diagnostic Monitor (ADDM) analyzes data in the Automatic Workload Repository (AWR) to identify potential performance bottlenecks. For each of the identified issues it locates the root cause and provides recommendations for correcting the problem. An ADDM analysis task is performed and its findings and recommendations stored in the database every time an AWR snapshot is taken provided the STATISTICS_LEVEL parameter is set to TYPICAL or ALL. The ADDM analysis includes:
    •     CPU load
    •     Memory usage
    •     I/O usage
    •     Resource intensive SQL
    •     Resource intensive PL/SQL and Java
    •     RAC issues
    •     Application issues
    •     Database configuration issues
    •     Concurrency issues
    •     Object contention
    ASM
    Automatic Storage Management (ASM) simplifies administration of Oracle related files by allowing the administrator to reference disk groups rather than individual disks and files, which are managed by ASM
    DBMS_FILE_TRANSFER Package in Oracle Database 10g•     Common Usage Notes
    •     COPY_FILE
    •     GET_FILE
    •     PUT_FILE
    Flashback New Features and Enhancements in Oracle Database 10g•     Flashback Query
    •     Flashback Version Query
    •     Flashback Transaction Query
    •     Flashback Table
    •     Flashback Drop (Recycle Bin)
    •     Flashback Database
    •     Flashback Query Functions
    Oracle Data Pump
    STARTUP UPGRADE
    The is a new startup mode associated with the upgrade procedure in Oracle 10g.
    SQL> STARTUP UPGRADE
    Automatic Shared Memory ManagementAutomatic Shared Memory Management puts Oracle in control of allocating memory within the SGA. The SGA_TARGET parameter sets the amount of memory available to the SGA. This parameter can be altered dynamically up to a maximum of the SGA_MAX_SIZE parameter value. Provided the STATISTICS_LEVEL is set to TYPICAL or ALL and the SGA_TARGET is set to a value other than "0" Oracle will control the memory pools which would otherwise be controlled by the following parameters:
    •     DB_CACHE_SIZE (default block size)
    •     SHARED_POOL_SIZE
    •     LARGE_POOL_SIZE
    •     JAVA_POOL_SIZE
    If these parameters are set to a non-zero value they represent the minimum size for the pool. These minimum values may be necessary if you experience application errors when certain pool sizes drop below a specific threshold.
    The following parameters must be set manually and take memory from the quota allocated by the SGA_TARGET parameter:
    •     DB_KEEP_CACHE_SIZE
    •     DB_RECYCLE_CACHE_SIZE
    •     DB_nK_CACHE_SIZE (non-default block size)
    •     STREAMS_POOL_SIZE
    •     LOG_BUFFER

  • AUTONOMOUS TRANSACTION(8I NEW FEATURE)에 대한 소개

    제품 : ORACLE SERVER
    작성날짜 : 2003-10-14
    AUTONOMOUS TRANSACTION(8I NEW FEATURE)에 대한 소개
    ==================================================
    autonomous transaction은 child transaction이라고도 불리우며 Oracle
    8i부터 제공되는 새로운 기능이며 현재까지는 pl/sql을 통해서만 구현이
    가능하지만 앞으로는 OCI까지 확장될 예정이다.
    pl/sql routine의 declare section 중 어떠한 곳에서라도 아래의 progma
    (compiler directive)를 지시함으로써 autonomous로 구분이 가능하다.
    pragma AUTONOMOUS_TRANSACTION;
    'pragma'는
    1) top-level anonymous blocks
    2) local, standalone or packaged functions and procedures
    3) methods of object types
    4) database triggers의 declare section 어디에서나 나타낼 수 있슴.
    아래의 경우에는 사용이 불가능.
    1) outside of a declase section
    2) nested block의 declare section
    3) package specification
    4) package body 중 procedure나 function definition 외부
    5) type body중 method definition의 외부
    autonomous transaction(tx) 내에서 명시적으로 rollback이나 commit을
    하여야 한다. 만일 이를 위반하였을 경우 main transcation 및 child
    transaction 모두 error 발생과 함께 rollback이 되게 된다.
    main transaction이 수행 중이고 child transaction이 아래의 상태의 경우 :
    1) autonomous transcation으로 선언된 code unit의 declare section에서
    기술된 statement가 수행 중인 동안 parent tx는 active로 남아있게 된다.
    2) "begin" 이후의 첫 executable step을 만나게 되면 parent transaction은
    유보되고 새로운 tx(child tx)가 시작된다.
    3) 이 code unit은 normal하게 수행이 되나 tx context는 새로운 transaction로
    설정된다.
    4) autonomous code unit에서 commit 이나 rollback 이 수행되면 이
    autonomous tx은 종료된다. 이 때까지 parent(main) tx는 계속 유보상태로
    남아 있으며 autonomous unit에서 계속되는 operation이 있다면 새로운 tx이
    시작된다.
    5) autonomous code unit에서 exit를 하게 되면 transaction context는
    parent로 전환이 된다.
    transaction context의 변경은 session parameter에 영향을 주지 않는다.
    따라서 parent transaction 에서 적용된 session parameter는 그대로 child
    tx에서도 영향을 미치게 된다.
    parent tx와 child tx는 서로 독립적이므로 lock 역시 공유하지 못한다.
    만일 parent tx에서 점유된 lock을 child에서 소유하고자 한다면 dead lock
    현상이 발생할 것이다. 이런 경우 ORA-60 이 발생되고 child tx는 자동적으로
    rollback 된다.
    <주의>
    ORACLE 8.1.6 README에서는 분산 transaction에서 autonomous tx 사용 시
    dead lock 발생 시 distributed lock timeout을 정상적으로 하지 못한다는
    주의사항이 소개되고 있슴.
    [예제]
    create table test_lobs (c1 number,c2 clob);
    create table msg (msg varchar2(120));
    create or replace function getlen (p1 in clob,
    p2 in number) return number as
    pragma AUTONOMOUS_TRANSACTION;
    len number;
    buf varchar2(120);
    tlen number;
    begin
    len := dbms_lob.getlength(p1);
    if len != 0 then
    dbms_lob.read(p1,len,1,buf);
    dbms_output.put_line('Value: '||buf);
    insert into msg values (buf);
    commit;
    end if;
    select dbms_lob.getlength(c2) into tlen
    from test_lobs where c1=p2;
    dbms_output.put_line('Length selected from table is '||tlen);
    return len;
    end;
    insert into test_lobs values (1,'Hello');
    insert into test_lobs values (2,'The quick brown fox');
    commit;
    declare
    cl1 clob;
    cl2 clob;
    ret number;
    begin
    select c2 into cl1 from test_lobs where c1 = 1 for update;
    select c2 into cl2 from test_lobs where c1 = 2;
    ret := getlen(cl1,1);
    dbms_output.put_line('Length of first row is '||ret);
    ret := getlen(cl2,2);
    dbms_output.put_line('Length of second row is '||ret);
    dbms_lob.writeappend(cl1,6,' there');
    ret := getlen(cl1,1);
    dbms_output.put_line('Length of first row is now '||ret);
    end;
    gives:
    Value: Hello
    Length selected from table is 5
    Length of first row is 5
    Value: The quick brown fox
    Length selected from table is 19
    Length of second row is 19
    Value: Hello there
    Length selected from table is 5
    Length of first row is now 11
    Selecting from the msg table gives 3 rows as follows:
    Hello
    The quick brown fox
    Hello there

  • (V9I) ORACLE9I NEW FEATURE : LOGMINER 의 기능과 사용방법

    제품 : ORACLE SERVER
    작성날짜 : 2002-11-13
    (V9I) ORACLE9I NEW FEATURE : LOGMINER 의 기능과 사용방법
    ==========================================
    Purpose
    Oracle 9i LogMiner 의 새로운 기능과 사용방법에 대해 알아보도록 한다.
    (8I LogMiner의 일반적인 개념과 기능은 BUL. 12033 참조)
    Explanation
    LogMiner 는 8I 에서부터 새롭게 제공하는 기능으로 Oracle 8 이상의 Redo
    log file 또는 Archive log file 분석을 위해 이용된다.
    9I 에서는 기존 8I 에서 제공하던 기능을 모두 포함하고 그 외 새로운 점은
    LogMiner 분석을 위해 dictionary 정보를 Flat file(output)로 생성이 가능하
    였으나 9I 에서부터는 Flat file 과 함께 On line redo log 를 이용하여
    dictionary 정보를 저장할 수 있게 되었고, Block corruption이 발생하였을
    경우 해당 부분만 skip할 수 있는 기능이 추가되었다.
    9I 에서의 New feature 를 정리하면 다음과 같다.
    1. 9I New feature
    1) DDL 지원 단, 9I 이상의 Redo/Archive log file만 분석 가능
         : V$LOGMNR_CONTENTS 의 OPERATION column에서 DDL 확인
    2) LogMiner 분석을 위해 생성한 dictioanry 정보를 online redo 에 저장 가능
         : 반드시 Archive log mode 로 운영 중이어야 한다.
         : DBMS_LOGMNR_D.BUILD를 사용하여 dictionary file 생성
         : 기존 Flat file 또는 Redo log 에 생성 가능
         : 예) Flat file
              - SQL> EXECUTE dbms_logmnr_d.build
                   (DICTIONARY_FILENAME => 'dictionary.ora'
                   ,DICTIONARY_LOCATION => '/oracle/database'
                   ,OPTIONS => DBMS_LOGMNR_D.STORE_IN_FLAT_FILE);
         예) Redo log
              - SQL> EXECUTE dbms_logmnr_d.build
                   (OPTIONS => DBMS_LOGMNR_D.STORE_IN_REDO_LOGS);
    3) Redo log block corruption 이 발생하였을 경우 corruption 된 부분을 skip하고 분석
         : 8I 에서 log corruption 발생 시 LogMiner 가 종료되고 분석 위해 다시 시도
         : 9I 에서는 DBMS_LOGMNR.START_LOGMNR 의 SKIP_CORRUPTION option 으로 skip 가능
    4) Commit 된 transaction 에 대해서만 display
         : DBMS_LOGMNR.START_LOGMNR 의 COMMITTED_DATA_ONLY option
    5) Index clustered 와 연관된 DML 지원 (8I 제공 안 됨)
    6) Chained and Migrated rows 분석
    2. 제약 사항(9I LogMiner 에서 지원하지 않는 사항)
    1) LONG and LOB data type
    2) Object types
    3) Nested tables
    4) Object Refs
    5) IOT(Index-Organized Table)
    3. LogMiner Views
    1) V$LOGMNR_CONTENTS - 현재 분석되고 있는 redo log file의 내용
    2) V$LOGMNR_DICTIONARY - 사용 중인 dictionary file
    3) V$LOGMNR_LOGS - 분석되고 있는 redo log file
    4) V$LOGMNR_PARAMETERS - LogMiner에 Setting된 현재의 parameter의 값
    4. LogMiner 를 이용하기 위한 Setup
    1) LogMiner 를 위한 dictionary 생성(flatfile or on line redo log)
    2) Archive log file or Redo log file 등록
    3) Redo log 분석 시작
    4) Redo log 내용 조회
    5) LogMiner 종료
    5. LogMiner Example
    1) flatfile이 생성될 location을 확인
    SQL> show parameter utl
    NAME TYPE VALUE
    utl_file_dir string /home/ora920/product/9.2.0/smlee
    2) dictionary 정보를 저장할 flatfile 정의 -> dictionary.ora 로 지정
    SQL> execute dbms_logmnr_d.build -
    (dictionary_filename => 'dictionary.ora', -
    dictionary_location => '/home/ora920/product/9.2.0/smlee', -
    options => dbms_logmnr_d.store_in_flat_file);PL/SQL procedure successfully completed.
    3) logfile을 switch 하고 current logfile name과 current time을 기억한다.
    SQL> alter system switch logfile;
    System altered.
    SQL> select member from v$logfile, v$log
    2 where v$logfile.group# = v$log.group#
    3 and v$log.status='CURRENT';
    MEMBER
    /home/ora920/oradata/ORA920/redo02.log
    SQL> select current_timestamp from dual;
    CURRENT_TIMESTAMP
    13-NOV-02 10.37.14.887671 AM +09:00
    4) test를 위해 table emp30 을 생성하고 update -> drop 수행
    SQL> create table emp30 as
    2 select employee_id, last_name, salary from hr.employees
    3 where department_id=30;
    Table created.
    SQL> alter table emp30 add (new_salary number(8,2));
    Table altered.
    SQL> update emp30 set new_salary = salary * 1.5;
    6 rows updated.
    SQL> rollback;
    Rollback complete.
    SQL> update emp30 set new_salary = salary * 1.2;
    6 rows updated.
    SQL> commit;
    Commit complete.
    SQL> drop table emp30;
    select
    Table dropped.
    SQL> select current_timestamp from dual;
    CURRENT_TIMESTAMP
    13-NOV-02 10.39.20.390685 AM +09:00
    5) logminer start (다른 session을 열어 작업)
    SQL> connect /as sysdba
    Connected.
    SQL> execute dbms_logmnr.add_logfile ( -
    logfilename => -
    '/home/ora920/oradata/ORA920/redo02.log', -
    options => dbms_logmnr.new)PL/SQL procedure successfully completed.
    SQL> execute dbms_logmnr.start_logmnr( -
    dictfilename => '/home/ora920/product/9.2.0/smlee/dictionary.ora', -
    starttime => to_date('13-NOV-02 10:37:44','DD_MON_RR HH24:MI:SS'), -
    endtime => to_date('13-NOV-02 10:39:20','DD_MON_RR HH24:MI:SS'), -
    options => dbms_logmnr.ddl_dict_tracking + dbms_logmnr.committed_data_only)PL/SQL procedure successfully completed.
    6) v$logmnr_contents view를 조회
    SQL> select timestamp, username, operation, sql_redo
    2 from v$logmnr_contents
    3 where username='HR'
    4 and (seg_name = 'EMP30' or seg_name is null);
    TIMESTAMP                USERNAME           OPERATION           SQL_REDO           
    13-NOV-02 10:38:20          HR               START               set transaction read write;
    13-NOV-02 10:38:20          HR               DDL               CREATE TABLE emp30 AS
                                                      SELECT EMPLOYEE_ID, LAST_NAME,
                                                      SALARY FROM HR.EMPLOYEES
                                                      WHERE DEPARTMENT_ID=30;
    13-NOV-02 10:38:20          HR                COMMIT
    commit;
    13-NOV-02 10:38:50          HR               DDL               ALTER TABLE emp30 ADD
                                                      (new_salary NUMBER(8,2));
    13-NOV-02 10:39:02          HR               UPDATE          UPDATE "HR"."EMP30" set
                                                      "NEW_SALARY" = '16500' WHERE
                                                      "NEW_SALARY" IS NULL AND ROWID
                                                      ='AAABnFAAEAALkUAAA';
    13-NOV-02 10:39:02-10     HR               DDL               DROP TABLE emp30;
    7) logminer 를 종료한다.
    SQL> execute dbms_logmnr.end_logmnr
    PL/SQL procedure successfully completed.
    Reference Documents
    Note. 148616.1

  • Maxdb new features - Page Clustering and Prefetch

    Hi to all,
    2 new features of maxdb are available with new patches: Page Clustering and Prefetch in OLTP-Systems.
    Are there any experiences to this features?
    READAHEAD_TABLE_THRESHOLD
    "This parameter is used to specify, if read operations of tables
    should be optimized, i.e. if during a table access more than the
    specified value in pages is affected, servertasks will be used to
    read ahead pages of this table."
    I activated this parameter in November. The system now starts more quickly and some expensive sql-statements may be faster. But the average db-time didn't change.
    Page Clustering can be activated with parameter: DATA_IO_BLOCK_COUNT
    Then tables can be migrated with SQL-Statement: ALTER TABLE <table name> CLUSTER
    I activated this only for one table. This table now is read much faster.
    My questions.
    Is there a documentation available for this features?
    How can I "uncluster" clustered tables?
    When this features are activated, expensive sql-statements are processed much faster. Because of the high workload on storagesystem, all other transaction may get slower?
    regards
    Franz

    > 2 new features of maxdb are available with new patches: Page Clustering and Prefetch in OLTP-Systems.
    First of all: both features, although technically available, are not yet generally released for OLTP usage.
    The current implementation of page prefetching is explicitely a proof-of-concept implementation which should be used by recommendation from MaxDB support only.
    There are several limitations to the functionality at the moment, e.g. it does only work for table scans.
    It does not work for joins, for index builds neither does it work on clustered tables.
    Prefetching is available to 7.6 release only at the moment, so after an upgrade to 7.7 this feature would be gone...
    > I activated this parameter in November. The system now starts more quickly and some expensive sql-statements may be faster. But the average db-time didn't change.
    Well, nothing surprising here.
    On SAP start there happen a lot of tablescans, mostly attributable to the fully buffered tables for the ABAP internals (security, ddic, etc.)
    These statements will of course benefit if the pages are now read into the buffer in parallel.
    For the avg. db-time: be happy!
    This basically means, that most of the statements running in your system aren't processed by table scans, which is for MaxDB nearly always a very good thing.
    > Page Clustering can be activated with parameter: DATA_IO_BLOCK_COUNT
    > Then tables can be migrated with SQL-Statement: ALTER TABLE <table name> CLUSTER
    Ok, page clustering is not documented yet (just as prefetching is not officially documented) and not released for OLTP.
    > I activated this only for one table. This table now is read much faster.
    >
    > My questions.
    > Is there a documentation available for this features?
    Hmm.. you're using undocumented features - what do you expect?`
    No, currently there is no official documentation.
    There is work going on to provide official documentation but none of it is released yet (and it will take some more time!)
    > How can I "uncluster" clustered tables?
    ALTER TABLE <tablename> NOT CLUSTER
    > When this features are activated, expensive sql-statements are processed much faster. Because of the high workload on storagesystem, all other transaction may get slower?
    It's not that simple.
    Both features address specific issues and are used only in very specific circumstances.
    The clustering feature will not improve performance if the table is not accessed via the cluster key.
    In fact, it may even decrease performance if this is done.
    Also, at the moment clustered tables don't stay clustered on updates/inserts/deletes.
    Therefore it is not necessarily a good idea to cluster tables like REPOLOAD pr REPOSRC on a development system.
    regards,
    Lars

  • New Features WAD of SPS13

    Hi Experts,
      I need use a scroll bar in Analysis webitem in WAD. We show that new feature is avaliable in this SPS13,
    http://help.sap.com/saphelp_nw70/helpdata/en/76/489d39d342de00e10000000a11402f/frameset.htm
      So we upgraded the components :
      SPS to 13
      Saplogon 710 FEP 4
      BI SP2 and patch 1
      But unfortunately the paging new features didnt appears. (USE_SCROLLBARS ....).
    Have we forgot any upgrade ? Does anyone test this new feature ?
      Kind regards,
      Alexandre

    Hi Alexandre,
    Unfortunately, I am not at SP13, however I have something you can test.  It it possible that although the parameter is now valid for processing but not available in the WAD within the Analysis Item properties window.
    Try adding the parameter directly to the Instruction for the Analysis Item.  Something like the following and see how it renders:
      <bi:SET_ITEM_PARAMETERS >
                   <bi:cmd_item_parameters type="ANALYSIS_ITEM" >
                      <bi:USE_SCROLLBARS value="X" />
                   </bi:cmd_item_parameters>
                   <bi:TARGET_ITEM_REF value="ANALYSIS_ITEM_1" />
      </bi:SET_ITEM_PARAMETERS>
    Cheers,
    Dave

  • Follow-up to archived thread "Another Error (I think) In the 12.1 New Features Guide"

    I hoped to be able to add a reply to the most recent reply on March 8 in the "Another Error (I think) In the 12.1 New Features Guide" thread (https://community.oracle.com/thread/3526588), but since that thread has been archived, I am doing what was suggested elsewhere: create a new thread referencing the old one. My reply is:
    Thank you for your explanation about preferring PDF over HTML. That is perfectly fine and understandable. Also, we very much appreciate your documentation feedback in this forum, and encourage you to continue to report any issues here.
    I apologize for not replying much sooner. I either didn't get or overlooked an original notification about "Recent activity" after your reply; otherwise, I would have replied then.

    Thanks for that comment. I have sent a pointer to it to the writer for that book. Note that with the New Features Guide, most of the content is automatically drawn from an internal system that tracks projects and features; so if a change is needed, the writer will notify the owner of that content (typically a developer or a product manager) to investigate and (if necessary) modify the underlying data, after which the changed information will be picked up for a future revision of the book.
    Also, while anyone is welcome to enter documentation comments in this forum, another option that may be more convenient for comments on specific sections is the Reader Comment area at the bottom of each HTML page (such as http://docs.oracle.com/cd/E16655_01/server.121/e17906/chapter1.htm#NEWFT495 for the page containing Section 1.5.9.8). Any comments entered in a Reader Comment area go to someone in our documentation production group, who forwards them to the appropriate writers.
    However, if a comment involves multiple HTML pages or books, or if you want the matter to be in a public forum for visibility and searchability, posting in this forum is a good option.

  • Ios 5 Update New Features says that iCal now has a week view for iPhone but after updating last weekend, I don't see any week view--just List, Day and Month..How do I get the week view?

    ios 5 Update New Features says that calendar now has a week view but after updating my iPhone 4 last weekend, I don't see any week view for iCal--just List, Day and Month as in the past. Is the weekly view available for iCal and if so, how do I access it?

    Rotate your phone to landscape.

  • New Features and Improvements for CS6

    IMPORTANT:
    By default, Photoshop comes with the Proofing Colors (Cmd/Ctrl+Y) activated and set to CMYK. Adobe must warn about that, because I was editing a large amount of pictures for work and I was doing it under that color profile/work space.
    LAYERS PANEL:
    Layer Adjustments:
    Solid Color: visual feedback in real time.
    Gradient: IDEM as above.
    Pattern: IDEM as above.
    Gradient Map: IDEM as above.
    Gradient Editor: IDEM as above.
    Opacity and Fill: IDEM as above.
    Curves and Levels: Ability to load alfa channels. This way, the adjustments made on the alfa channel won't be destructive.
    CHANNELS PANEL:
    Channel Luminosity Selection:
    Ability to add and subtract from the selection.
    Ability to designate an area to be selected.
    For point 1, by using the shortcut Cmd+Alt+[number] the luminosity of a channel is loaded as selection. With Cmd+Alt+Shift+[number], the selection grows. But there is no way to subtract from selection (unless by clicking with the mouse on the channel's thumbnail). I think that can be solved by using Cmd+Alt+Shift+[- or +] in order to subtract or add from selection.
    Point 2 maybe even more important than point 1, because it allows selecting a designated area by the user, instead of the default luminosity selection, which ranges from 50% of the mid tones to the highlights (or shadows, if the selection is inverted). The user should be allowed to select the starting and finishing points of the luminosity selection.
    I thought 2 ways for solving these issues (and making it more intuitive and faster):
    A) By using the Histogram Panel, by dragging and highlighting an area on it, that it should load the selected luminosity pixels as a selection, as shown in figure 1:
      figure 1
    So the result of doing that will be a selection based on the area of the histogram that have been highlighted.
    B) By creating a new Adjustment Layer:
    It can be based in the same structure of the HUE Adjustment Layer, like figure 2 shows:
    Figure 2
    Or it can be this way (much better). Figure 3:
    Figure 3
    The selection can also be controlled by using the Click and Drag as suggested in the figure 1, as shown in the figure 4:
    Figure 4
    The overlaid highlighting over the histogram can be functional or just a mere graphic representation of the Range and Fade Selector. The "Fading" areas should be also be draggable in order to increase smooth the selection. However, the smoothing can be much better done with the Refining Selection tool and it can be ignored from this new tool.
    In any of these cases, the adjustments should give real time feedback when growing or shrinking selection; we must see the selection going bigger or smaller and also, the highlighted area should be draggable as well.
    TOOLS PANEL:
    Brush: detect edges while painting on masks (for manual mask refining. It would work similar to the Replace Color Brush, but only for masks and alfa channels). It also needs a shortcut to set the opacity.
    Dodge & Burn: Protect Tones should be allowed when painting on masks or alfa channels (for manual mask refining). D&B can also use edge detection as well.
    FILTERS:
    Some of them, like the ones involving Blur or the High-Pass and the Unsharp Mask filter, should work in real time (these ones, at the least).
    It can also added a Particle Generator Filter.
    It would be really nice having the ability to create particles such as dust, fog, rain, snow, etc in a more realistic manner than just the scattering function from the Brush Palette, or by mixing different filters with different blends. The Particle Generator should have an slider to control the depth of field, so it will give a feeling of depth and also, a way to load masks, so that way, the particles can exists before the image and also, behind. It would be great for creating a nice feeling of depth (kind of a bokeh effect).
    I've been playing with After Effect few times, and the way to create shapes and forms from nothing is the way of easier than in Photoshop.
    TIME LINE:
    I think it's time give dynamism the filters applied to a movie clip, and also, dynamics to the fade effects, like it happens in After Effects by adding Bezier Curves.
    HISTOGRAM:
    It should be possible to zoom in into the histogram, for a more precise feedback and analysis of the image tonal values.
    ADDITIONAL FEATURES:
    The fade tool should work in real time.
    Loupe/Magnificator View:
    This is very useful when it comes to edit and image in detail, with a lot of zoom, like 3200%. Unfortunately, Photoshop doesn't provide a real time feedback in an additional window, such as the Window/Arrange/New Window For […].
    It would be really useful having a window showing the image at fit on the screen while working on the other window at 100% or 3200% of zoom, but in real time. This way, you can see if you're doing a good job on the pixels or, if you're overdoing it.
    It happens that, when working with big images at 100% of the image size (or more), the brain cannot figure out how is looking the whole image, so having a realtime feedback in the other window would help a lot for detailled work.
    And why not, ading the same real time structure descrived above but to the Navigator, for faster and lighter use of the hardware capabilities. Probably, adding a check box to the navigator that blocks it to a given zoom, so when zooming into the image in the navigator, the image shown in the window isn't magnified too.
    Give me a chance to show you some examples of what I have done by improvising particles and fog about 5 years ago:
    http://mart1980.deviantart.com/gallery/5027033#/d1m119x
    And what I did 7 years ago by manually, selecting different shades of gray and using just Levels for 8 hours (which coule be done faster and easier with another tool I thought, which I will post later):
    I cannot post examples of the other features I'm suggesting because there are not such new features yet (I would have to create an hipothetical enviroment, but I think, you can fiure it out in your mind).
    Unfortunately, I don't know programing, even though, I tried something with Filter Factory, achieving good results, but that pluging consumes too much resources and/or is bad designed/have not the right tools for certain things.
    Hope this post is enough worthy of the Adobe's attention.
    Thanks,
    س

    This is a poorly explained reason about why is so important having a loupe in Photoshop. I've not also, used the best example, but I will. This belongs to the ADDITIONAL FEATURES: Loupe/Magnificator View:. Also, I will try to make my english clrearer, but here it goes:

  • New Features in Logic 8

    Here's a link to the New Features in logic 8 .pdf
    http://manuals.info.apple.com/en/NewFeatures_in_Logic_Pro8.pdf
    {New song length is 12 hours at normal tempo}
    RealDave

    Thanks RealDave.
    I'm still reading through the manual as well...and so far I do not see any mention of an improvement of the SRC (sample rate conversion), which was an issue.
    I hope they have re-done that code in this update. I will probably email Apple, although, they never answer...so...
    Cheers

Maybe you are looking for

  • Open an accordion widget in the closed state?

    I have searched the forums but have yet to find a resolution for this issue. I am using an accordion widget and would like for all of my panels to appear closed when the page initially loads. Only once the user has clicked the tab do I want the panel

  • BADI/User exit for SE09 transaction

    Hi all, We have requirement in such a way that whenever the description of transport request doesn't follow our client policies we need provide a error message saying that you are violating policies. While creating transport request i am using the BA

  • Excel as default...

    I have Excel on my Mac, but Numbers always opens by default when I download spreadsheets.  I'm not really getting on with Numbers and copying data from Numbers to Excel is a real pain.  I love my Mac but I really can't be bothered to learn Numbers wh

  • Creation of child tables

    Hi Is it possible to create five child tables under one parent table? i tried but getting some error regards jintu

  • GUI STATUS MISSING

    Hello All, When i execute cs03 tcode its showing error 'gui status maa0 missing in prog' now i knw pfstatus for the given prog is not set. when i open this prog there are some 1000 lines of code and include in tht, now how to find the pfstatus in tht