Huge size scheme export in standard edition

Hi,
Source:-
Oracle 10.2.0.3 standard edition on Linux.
Destination:-
Oracle 11gR2 - enterprise edition.
I have to export a scheme of size 250+ gb, it taking long time to export as we do not have parallelism too in STD edition.
Is there any way? Where I can perform export & import faster?
Constraint is expdp of schema taking 30+ hours, so If transportable tablespaces, then is there any compatibility problem with source and destination versions and editions?
An what is the procedure?
Thanks.

Hemant K Chitale wrote:
Can i use 11gR2 binaries to perform TTS of 10g Std edition database?
You could concurrently run multiple export sessions with table lists --- but you wouldn't get data consistency if the tables are being updated.Thanks for your information.
This question is now out of TTS, talking in general expdp/impdp.
I have posted this question in Export/import division of Database, But no quick responses so i moved my question to Database-General.
Solomon Yakobson mentioned we can use 11gR2 binaries to perform export schema of 10g database, from below link.
Huge size scheme export in standard edition
Hope this will work. any more suggestions on this?
Any suggestions
Edited by: Autoconfig on Oct 17, 2011 6:32 AM

Similar Messages

  • What is limit of database size in oracle 10g standard edition/edition one

    Hai All,
    What is the limit of database size in oracle 10g standard edition and standard edition one.. I see the white paper of oracle says that the limitation is 500 GB. This limitation is correct.? if correct then what happened after the limit..?
    Please help?
    Shiju

    What white paper would that be? I can't see any limit in the Oracle Database 10g Editions comparisons.
    C.

  • Sector size problem when create a "Standby" in Standard Edition

    Hi,
    I've a primary database 11.2.0.4 Standard Edition with Grid Infrastructure with ASM.
    DiskGroup in ASM uses sector size ok 4k.
    I've also a "Standby" the uses filesystem with logical and physical sector size of 512.
    When duplicate from primary I get this warning:
    ORACLE error from auxiliary database: ORA-01378: The logical block size (4096) of file /u03/oradata/ORCL/onlinelog/group_1.268.874153703 is not compatible with the disk sector size (media sector size is 512 and host sector size is 512)
    RMAN-05535: WARNING: All redo log files were not defined properly.
    ORACLE error from auxiliary database: ORA-01378: The logical block size (4096) of file /u03/oradata/ORCL/onlinelog/group_2.265.874153719 is not compatible with the disk sector size (media sector size is 512 and host sector size is 512)
    RMAN-05535: WARNING: All redo log files were not defined properly.
    ORACLE error from auxiliary database: ORA-01378: The logical block size (4096) of file /u03/oradata/ORCL/onlinelog/group_3.263.874153759 is not compatible with the disk sector size (media sector size is 512 and host sector size is 512)
    RMAN-05535: WARNING: All redo log files were not defined properly.
    ORACLE error from auxiliary database: ORA-01378: The logical block size (4096) of file /u03/oradata/ORCL/onlinelog/group_4.261.874153735 is not compatible with the disk sector size (media sector size is 512 and host sector size is 512)
    RMAN-05535: WARNING: All redo log files were not defined properly.
    Finished Duplicate Db at 2015-04-21 23:37:10
    released channel: CH1
    I can recreate 3 redologs with correct sector size, but I unable to drop current log file:
    ERROR at line 1:
    ORA-01623: log 4 is current log for instance ORCL (thread 1) - cannot drop
    ORA-00312: online log 4 thread 1:
    '/u03/oradata/ORCL/onlinelog/group_4.261.874153735'
    So how can I solve this problem?

    yasinyazici wrote:
    Hi
    Oracle Data Guard is available only as a feature of Oracle Database Enterprise Edition. It is not available with Oracle Database Standard Edition.
    Please look  2.3.2 Oracle Software Requirements section  of the  following document
    http://docs.oracle.com/cd/E11882_01/server.112/e41134/standby.htm#SBYDB4716
    Yasin
    It's possible:
    Data Guard and Oracle Standard Edition (Doc ID 305360.1)
    Alternative for standby database in standard edition (Doc ID 333749.1)

  • Standard Edition automated export

    I currently have a SQL Azure database using the old Web edition and have configured automated export. This is very useful for keeping long term daily backups. I am just trying out the new Standard edition and have found the automated export is disabled with
    the message "Automated export is not supported for this database".
    Please tell me this won't be a Premium only feature as it is the only current way to do an automated backup without the use of a third party tool.

    Hello,
    The Automated Export (Preview) feature is not support in the new Basic and Standard tiers currently. For disaster recovery solution in Standard edition, you can try to use Database Copy and Manual Export.
    Reference:
    Azure SQL Database Business Continuity
    Azure SQL Database Service Tiers (Editions)
    Regards,
    Fanny Liu
    If you have any feedback on our support, please click here. 
    Fanny Liu
    TechNet Community Support

  • Export Release Build/Standard Edition

    Hi-
    Is the Export Release Build feature available in Flash Builder 4 - Standard Edition?
    Thanks,
    Dave

    Hi Jason
    I see it in the trail. The trial is the Premier edition though.
    I plan to buy the Standard edition and want to make sure that feature is in that version.
    Dave

  • Standby db-EE edition and Standard edition

    Dear friends,
    10g on solaris 10.
    What are the differences in standby db when using a enterprise edition and standard edition ?..
    Any input will be of great help
    Kai

    Niall and team
    I have read your presentation - "You Probably Don't need dataguard" and I tried it out on test database. I setup a manual standby database, archivelog is manually copied to standby db.
    Maybe you have an idea on regarding SCN or archivelog that is not present but Oracle is asking/suggestion during recovery procedure..
    environment:
    2 virtual box - Solaris 10 Virtual Machine host on Windows XP
    Oracle 10.2.0 Standard Edition
    Primary DB host name: SE
    Standby DB host name: SE2
    archive dest = /export/home/oracle/archive (same on both machine)
    db file = /export/home/oracle/oradata/se , /export/home/oracle/oradata/se2 --> so I used db_file convert parameter in init.ora
    Steps:
    On the newly created database, create a test table and insert values.
    SQL> create table test(a number) tablespace users;
    Table created.
    SQL> insert into test values(&a);
    Enter value for a: 1
    old 1: insert into test values(&a)
    new 1: insert into test values(1)
    1 row created.
    SQL> /
    Enter value for a: 21
    old 1: insert into test values(&a)
    new 1: insert into test values(21)
    1 row created.
    SQL> /
    Enter value for a: 31
    old 1: insert into test values(&a)
    new 1: insert into test values(31)
    1 row created.
    SQL> /
    Enter value for a: 41
    old 1: insert into test values(&a)
    new 1: insert into test values(41)
    1 row created.
    SQL> commit;
    Commit complete.
    SQL> alter system archive log current;
    System altered.
    SQL>
    $ ls -lrt
    total 41808
    -rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
    $
    Again, insert some values to test table,
    SQL> insert into test values(&a);
    Enter value for a: 33
    old 1: insert into test values(&a)
    new 1: insert into test values(33)
    1 row created.
    SQL> /
    Enter value for a: 44
    old 1: insert into test values(&a)
    new 1: insert into test values(44)
    1 row created.
    SQL> /
    Enter value for a: 55
    old 1: insert into test values(&a)
    new 1: insert into test values(55)
    1 row created.
    SQL> /
    Enter value for a: 11
    old 1: insert into test values(&a)
    new 1: insert into test values(11)
    1 row created.
    SQL> commit;
    Commit complete.
    SQL> alter system archive log current;
    System altered.
    SQL> select * from test;
    A
    1
    21
    31
    41
    33
    44
    55
    11
    8 rows selected.
    check archivelog dir,
    $ ls -lrt
    total 41816
    -rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
    -rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
    $
    Then,
    1. shutdown immediate (primary)
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL>
    2. copy datafile, redo, archive log to SE2 node.
    $ pwd
    /export/home/oracle/oradata/se
    $ ls
    control01.ctl control03.ctl redo02.log sysaux01.dbf temp01.dbf users01.dbf
    control02.ctl redo01.log redo03.log system01.dbf undotbs01.dbf
    $ scp * [email protected]:/export/home/oracle/oradata/se2
    Password:
    control01.ctl 100% |******************************************************| 6896 KB 00:01
    control02.ctl 100% |******************************************************| 6896 KB 00:01
    control03.ctl 100% |******************************************************| 6896 KB 00:00
    redo01.log 100% |******************************************************| 51200 KB 00:09
    redo02.log 100% |******************************************************| 51200 KB 00:11
    redo03.log 100% |******************************************************| 51200 KB 00:08
    sysaux01.dbf 100% |******************************************************| 240 MB 00:54
    system01.dbf 100% |******************************************************| 480 MB 01:35
    temp01.dbf 100% |******************************************************| 20488 KB 00:04
    undotbs01.dbf 100% |******************************************************| 25608 KB 00:05
    users01.dbf 100% |******************************************************| 5128 KB 00:01
    $
    $ ls -lrt
    total 41816
    -rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
    -rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
    $ scp 1_2_711819574.dbf [email protected]:/export/home/oracle/archive
    Password:
    1_2_711819574.dbf 100% |******************************************************| 20877 KB 00:04
    $
    3. startup (primary)
    4. create standby control file
    SQL> startup
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1279120 bytes
    Variable Size 62917488 bytes
    Database Buffers 100663296 bytes
    Redo Buffers 2912256 bytes
    Database mounted.
    Database opened.
    SQL> alter database create standby controlfile as '/export/home/oracle/standby.ctl';
    Database altered.
    5. copy standby control file to SE2
    $ pwd
    /export/home/oracle
    $ scp standby.ctl [email protected]:/export/home/oracle
    Password:
    standby.ctl 100% |******************************************************| 6896 KB 00:01
    $
    6. edit init.ora, specify location of control file - use standby control file
    *.control_files='/export/home/oracle/standby.ctl'
    7. SE2,
    SQL> startup nomount pfile=/export/home/oracle/product/10.2.0/db_1/dbs/initse.ora
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1279120 bytes
    Variable Size 62917488 bytes
    Database Buffers 100663296 bytes
    Redo Buffers 2912256 bytes
    8. alter database mount standby database;
    SQL> alter database mount standby database;
    Database altered.
    SQL>
    9. we'll try to open as read only without recovery,
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-16004: backup database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/export/home/oracle/oradata/se2/system01.dbf'
    10. then, we recover by - recover standby database;
    SQL> recover standby database;
    ORA-00279: change 540274 generated at 02/24/2010 15:58:26 needed for thread 1
    ORA-00289: suggestion : /export/home/oracle/archive/1_4_711819574.dbf
    ORA-00280: change 540274 for thread 1 is in sequence #4
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00308: cannot open archived log
    '/export/home/oracle/archive/1_4_711819574.dbf'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    ORA-00308: cannot open archived log
    '/export/home/oracle/archive/1_4_711819574.dbf'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/export/home/oracle/oradata/se2/system01.dbf'
    <observation> notice that archive log 4 is not yet present in Primary DB and STBY DB.
    Question: Why Oracle is asking archivelog that does not exist? I noticed in other exercise that you can use the redo log instead of archive log that does not exist. Is this because when we create the standby control file, the SCN is in sync with redo log.
    10. Now, we will copy archive log 3 to STDB,
    $ cd archive
    $ ls
    1_2_711819574.dbf 1_3_711819574.dbf
    $ scp 1_3_*711819574.dbf [email protected]:/export/home/oracle/archive
    Password:
    1_3_711819574.dbf 100% |******************************************************| 4096 00:00
    $
    11. on SE2, recover
    SQL> recover automatic standby database until cancel;
    ORA-00279: change 540274 generated at 02/24/2010 15:58:26 needed for thread 1
    ORA-00289: suggestion : /export/home/oracle/archive/1_4_711819574.dbf
    ORA-00280: change 540274 for thread 1 is in sequence #4
    ORA-00278: log file '/export/home/oracle/archive/1_4_711819574.dbf' no longer
    needed for this recovery
    ORA-00308: cannot open archived log
    '/export/home/oracle/archive/1_4_711819574.dbf'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/export/home/oracle/oradata/se2/system01.dbf'
    ORA-01112: media recovery not started
    12. Now, to generate the archivelog 4 and get the SCN that is indicated above, from one of our redo log. we will go to PRIMARY DB, and insert some rows to TEST TABLE and switch log file.
    SQL>
    SQL> insert into test values(&a);
    Enter value for a: 99
    old 1: insert into test values(&a)
    new 1: insert into test values(99)
    1 row created.
    SQL> /
    Enter value for a: 100
    old 1: insert into test values(&a)
    new 1: insert into test values(100)
    1 row created.
    SQL> /
    Enter value for a: 101
    old 1: insert into test values(&a)
    new 1: insert into test values(101)
    1 row created.
    SQL> commit;
    Commit complete.
    SQL> alter system switch logfile;
    System altered.
    $ ls -lrt
    total 42568
    -rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
    -rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
    -rw-r----- 1 oracle oinstall 376832 Feb 24 16:28 1_4_711819574.dbf
    13. We will again, switch logfile, to generate archive 5, before we copied archive 4 to STBY, we are sure that arch 5 is the active archivelog.
    SQL> alter system switch logfile;
    System altered.
    SQL> exit
    Disconnected from Oracle Database 10g Release 10.2.0.2.0 - Production
    $ ls -lrt
    total 42570
    -rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
    -rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
    -rw-r----- 1 oracle oinstall 376832 Feb 24 16:28 1_4_711819574.dbf
    -rw-r----- 1 oracle oinstall 1024 Feb 24 16:31 1_5_711819574.dbf
    $
    14. copy archive log 4 to STBY (SE2)
    $ scp 1_4_711819574.dbf [email protected]:/export/home/oracle/archive
    Password:
    1_4_711819574.dbf 100% |********************************************| 368 KB 00:00
    $
    15. In SE2, recover
    SQL> recover automatic standby database until cancel;
    ORA-00279: change 540985 generated at 02/24/2010 16:28:36 needed for thread 1
    ORA-00289: suggestion : /export/home/oracle/archive/1_5_711819574.dbf
    ORA-00280: change 540985 for thread 1 is in sequence #5
    ORA-00278: log file '/export/home/oracle/archive/1_5_711819574.dbf' no longer
    needed for this recovery
    ORA-00308: cannot open archived log
    '/export/home/oracle/archive/1_5_711819574.dbf'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    Media recovery cancelled.
    15. Now let's see if we can open as read only and check test table.
    SQL> alter database open read only;
    Database altered.
    SQL> select * from test;
    A
    1
    21
    31
    41
    33
    44
    55
    11
    99
    100
    101
    11 rows selected.
    16. Now shutdown STBY database,
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL>
    17. On SE (PRIMARY), insert some records to TEST table, please take note that current archivelog is no. 5. We want to generate archivelog 6 and archivelog 7. Then only archivelog 5 and 6 will be copied to STBY.
    SQL> insert into test values(&a);
    Enter value for a: 1000
    old 1: insert into test values(&a)
    new 1: insert into test values(1000)
    1 row created.
    SQL> /
    Enter value for a: 1001
    old 1: insert into test values(&a)
    new 1: insert into test values(1001)
    1 row created.
    SQL> /
    Enter value for a: 1002
    old 1: insert into test values(&a)
    new 1: insert into test values(1002)
    1 row created.
    SQL> commit;
    Commit complete.
    SQL> alter system archive log current;
    System altered.
    SQL> exit
    Disconnected from Oracle Database 10g Release 10.2.0.2.0 - Production
    $ ls -lrt
    total 42632
    -rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
    -rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
    -rw-r----- 1 oracle oinstall 376832 Feb 24 16:28 1_4_711819574.dbf
    -rw-r----- 1 oracle oinstall 1024 Feb 24 16:31 1_5_711819574.dbf
    -rw-r----- 1 oracle oinstall 31744 Feb 24 16:41 1_6_711819574.dbf
    we will do, log switch to create archive log 7,
    SQL> alter system switch logfile;
    System altered.
    SQL> exit
    Disconnected from Oracle Database 10g Release 10.2.0.2.0 - Production
    $ ls -lrt
    total 42634
    -rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
    -rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
    -rw-r----- 1 oracle oinstall 376832 Feb 24 16:28 1_4_711819574.dbf
    -rw-r----- 1 oracle oinstall 1024 Feb 24 16:31 1_5_711819574.dbf
    -rw-r----- 1 oracle oinstall 31744 Feb 24 16:41 1_6_711819574.dbf
    -rw-r----- 1 oracle oinstall 1024 Feb 24 16:42 1_7_711819574.dbf
    Then copy, arc 5 and arc 6 to SE2 (STBY)
    $ scp 1_5_711819574.dbf 1_6_711819574.dbf [email protected]:/export/home/oracle/archive
    Password:
    1_5_711819574.dbf 100% |*********************************************************| 1024 00:00
    1_6_711819574.dbf 100% |*********************************************************| 31744 00:00
    $
    17. in SE2, recover
    SQL> startup nomount pfile=/export/home/oracle/product/10.2.0/db_1/dbs/initse.ora
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1279120 bytes
    Variable Size 62917488 bytes
    Database Buffers 100663296 bytes
    Redo Buffers 2912256 bytes
    SQL> alter database mount standby database;
    Database altered.
    SQL> recover automatic standby database until cancel;
    ORA-00279: change 541270 generated at 02/24/2010 16:41:26 needed for thread 1
    ORA-00289: suggestion : /export/home/oracle/archive/1_7_711819574.dbf
    ORA-00280: change 541270 for thread 1 is in sequence #7
    ORA-00278: log file '/export/home/oracle/archive/1_7_711819574.dbf' no longer
    needed for this recovery
    ORA-00308: cannot open archived log
    '/export/home/oracle/archive/1_7_711819574.dbf'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    Media recovery cancelled.
    18. open as read only, to check if the newly inserted records can be view,
    SQL> alter database open read only;
    Database altered.
    SQL> select * from test;
    A
    1
    21
    31
    41
    33
    44
    55
    11
    99
    100
    101
    A
    1000
    1001
    1002
    14 rows selected.
    OK, that means that archive log 5 and archivelog 6 are applied to STBY database.
    Question. Why Oracle is asking the arc 7 , is it correct to say that last SCN is based on arc 5 and arc 6. Or is it Oracle behavior to ask the "next" SCN, after the arc 6. when performing recovery? ... that's why we have CANCEL.
    Appreciate your response on this..
    Thanks..
    19. For the sake of curiosity, lets try if we can use - recover managed standby database; (archivelog is still manually copied)
    on SE2, we will put it on "recovery mode"
    shutdown immediate,
    startup nomount pfile =
    alter database mount standby database
    recover managed standby database; (though the archivelogs are still copied manually )
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup nomount pfile=/export/home/oracle/product/10.2.0/db_1/dbs/initse.ora
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1279120 bytes
    Variable Size 62917488 bytes
    Database Buffers 100663296 bytes
    Redo Buffers 2912256 bytes
    SQL> alter database mount standby database;
    Database altered.
    SQL> recover managed standby database; (it will "hang", if you need to CANCEL open new session and use - recover managed standby database cancel)
    our current arch is 7, we will insert records to test table, and generate arch 8 and arch 9, then we will transfer arch 7 and arch 8 to SE2,
    on SE,
    Connected to:
    Oracle Database 10g Release 10.2.0.2.0 - Production
    SQL> insert into test values(&a);
    Enter value for a: 2000
    old 1: insert into test values(&a)
    new 1: insert into test values(2000)
    1 row created.
    SQL> /
    Enter value for a: 2001
    old 1: insert into test values(&a)
    new 1: insert into test values(2001)
    1 row created.
    SQL> /
    Enter value for a: 2003
    old 1: insert into test values(&a)
    new 1: insert into test values(2003)
    1 row created.
    SQL> commit;
    Commit complete.
    SQL> alter system archive log current;
    System altered.
    SQL> alter system switch logfile;
    System altered.
    SQL> exit
    Disconnected from Oracle Database 10g Release 10.2.0.2.0 - Production
    $ pwd
    /export/home/oracle/archive
    $ ls -lrt
    total 45758
    -rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
    -rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
    -rw-r----- 1 oracle oinstall 376832 Feb 24 16:28 1_4_711819574.dbf
    -rw-r----- 1 oracle oinstall 1024 Feb 24 16:31 1_5_711819574.dbf
    -rw-r----- 1 oracle oinstall 31744 Feb 24 16:41 1_6_711819574.dbf
    -rw-r----- 1 oracle oinstall 1024 Feb 24 16:42 1_7_711819574.dbf
    -rw-r----- 1 oracle oinstall 1584640 Feb 24 17:02 1_8_711819574.dbf
    -rw-r----- 1 oracle oinstall 2048 Feb 24 17:02 1_9_711819574.dbf
    $
    $ scp 1_7_711819574.dbf 1_8_711819574.dbf [email protected]:/export/home/oracle/archive
    Password:
    1_7_711819574.dbf 100% |*********************************************************| 1024 00:00
    1_8_711819574.dbf 100% |*********************************************************| 1547 KB 00:00
    $
    Please take note that in SE2 initse.ora file, we also set standby_control_file = /export/home/oracle/archive parameter.
    19. On SE2, open new session, and cancel recovery,
    session 2,
    SQL> recover managed standby database cancel;
    Media recovery complete.
    SQL>
    session 1,
    SQL> recover managed standby database;
    ORA-16043: managed recovery session canceled
    ORA-16037: user requested cancel of managed recovery operation
    Lets check if archivelog is applied, by checking test table,
    SQL> alter database open read only;
    Database altered.
    SQL> select * from test;
    A
    1
    21
    31
    41
    33
    44
    55
    11
    99
    100
    101
    A
    1000
    1001
    1002
    14 rows selected.
    Notice that 2000, 2001, 2002 are not added in TEST table.
    Lets do manual recovery,
    SQL> startup nomount pfile=/export/home/oracle/product/10.2.0/db_1/dbs/initse.ora
    ORACLE instance started.
    Total System Global Area 167772160 bytes
    Fixed Size 1279120 bytes
    Variable Size 62917488 bytes
    Database Buffers 100663296 bytes
    Redo Buffers 2912256 bytes
    SQL> alter database mount standby database;
    Database altered.
    SQL> recover automatic standby database until cancel;
    ORA-00279: change 541804 generated at 02/24/2010 17:02:34 needed for thread 1
    ORA-00289: suggestion : /export/home/oracle/archive/1_9_711819574.dbf
    ORA-00280: change 541804 for thread 1 is in sequence #9
    ORA-00278: log file '/export/home/oracle/archive/1_9_711819574.dbf' no longer
    needed for this recovery
    ORA-00308: cannot open archived log
    '/export/home/oracle/archive/1_9_711819574.dbf'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    Media recovery cancelled.
    SQL> select * from test;
    select * from test
    ERROR at line 1:
    ORA-01219: database not open: queries allowed on fixed tables/views only
    SQL> alter database open read only;
    Database altered.
    SQL> select * from test;
    A
    1
    21
    31
    41
    33
    44
    55
    11
    99
    100
    101
    A
    1000
    1001
    1002
    2000
    2001
    2003
    17 rows selected.

  • Database Upgrade from 10.2.0.3 standard edition to 10.2.0.4 enterprise

    Hi Guys,
    We are running oracle standard edition 10.2.0.3 in solaris 10 having size of 1TB. We would like to upgrade this database/database server to 10.2.0.4 enterprise edition.
    I am planning as below:-
    1) upgrade 10.2.0.3 standard edition to 10.2.0.3 enterprise edition first.
    2). upgrade it to 10.2.0.4 enterprise edition.
    can anybody suggest me if its a best way ?
    or
    1). uninstall the standard editiont.
    2). install the 10.2.0.4 enterprise edition
    3). create a database in enterprise edition
    4). import the data of standard edition.
    Regards,
    Pradeep

    We are running oracle standard edition 10.2.0.3 in solaris 10 having size of 1TB. We would like to upgrade this database/database server to 10.2.0.4 enterprise edition.
    I am planning as below:-
    1) upgrade 10.2.0.3 standard edition to 10.2.0.3 enterprise edition first.
    2). upgrade it to 10.2.0.4 enterprise edition.
    can anybody suggest me if its a best way ?
    or
    1). uninstall the standard editiont.
    2). install the 10.2.0.4 enterprise edition
    3). create a database in enterprise edition
    4). import the data of standard edition.
    As you are using export/import to migrate database to 10.2.0.4. enterprise edition.
    So there is no need to upgrade 10.2.0.3 standard edition.
    1. So take export from 10.2.0.3 standard edition.
    2. install the 10.2.0.4 enterprise edition and Create new database in 10.2.0.4 enterprise edition
    3. import
    4. Drop old database after taking backup. Uninstall 10.2.0.3 standard edition
    Regards
    Rajesh

  • Upgrade Oracle 9i Standard Edition

    Hi,
    I have a requirement to migrate my Oracle 9i Standard Edition to Oracle 9i Enterprise Edition on Windows 2000 and on Linux
    What is the best way for me to do this?
    1.I was thinking of taking exports of all the user tablespaces.
    2.De-installing oracle standard edition from the machines that have to be migrated.
    3. Install Oracle 9i Enterprise Edition.
    4. Import the user tablespaces again.
    The amount of data that is to be exported and reimported is about 100 MB. very small amount.
    I was wondering if there is a better way to do the migration- perhaps run a migration wizard (but the universal installer did not contain any such thing)
    Would the steps that I have outlined work? Or are there any gotchas that I need to look out for?
    Many thanks for any posts in this regard.

    Hi,
    Hi, Is there any cost involved to upgrade Oracle 9i standard edition to 11g? The license was purchased in 2004.
    As updated by Jim you need pay all these missed years  since 2004.
    I recommend you to take new license for 11g that will save huge amount.
    thanks,
    X A H E E R

  • Sample Response File for Oracle Database 12c Standard Edition on Oracle Linux 6.4 -- working

    oracle@styles-and-artists-development-oracle database]$ cat response/db_install.rsp
    ## Copyright(c) Oracle Corporation 1998,2013. All rights reserved.##
    ## Specify values for the variables listed below to customize     ##
    ## your installation.                                             ##
    ## Each variable is associated with a comment. The comment        ##
    ## can help to populate the variables with the appropriate        ##
    ## values.                                                        ##
    ## IMPORTANT NOTE: This file contains plain text passwords and    ##
    ## should be secured to have read permission only by oracle user  ##
    ## or db administrator who owns this installation.                ##
    # Do not change the following system generated value.
    oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v12.1.0
    # Specify the installation option.
    # It can be one of the following:
    #   - INSTALL_DB_SWONLY
    #   - INSTALL_DB_AND_CONFIG
    #   - UPGRADE_DB
    oracle.install.option=INSTALL_DB_AND_CONFIG
    # Specify the hostname of the system as set during the install. It can be used
    # to force the installation to use an alternative hostname rather than using the
    # first hostname found on the system. (e.g., for systems with multiple hostnames
    # and network interfaces)
    ORACLE_HOSTNAME=styles-and-artists-development-oracle
    # Specify the Unix group to be set for the inventory directory. 
    UNIX_GROUP_NAME=oracle
    # Specify the location which holds the inventory files.
    # This is an optional parameter if installing on
    # Windows based Operating System.
    INVENTORY_LOCATION=/home/oracle/oracleInventory
    # Specify the languages in which the components will be installed.            
    # en   : English                  ja   : Japanese                 
    # fr   : French                   ko   : Korean                   
    # ar   : Arabic                   es   : Latin American Spanish   
    # bn   : Bengali                  lv   : Latvian                  
    # pt_BR: Brazilian Portuguese     lt   : Lithuanian               
    # bg   : Bulgarian                ms   : Malay                    
    # fr_CA: Canadian French          es_MX: Mexican Spanish          
    # ca   : Catalan                  no   : Norwegian                
    # hr   : Croatian                 pl   : Polish                   
    # cs   : Czech                    pt   : Portuguese               
    # da   : Danish                   ro   : Romanian                 
    # nl   : Dutch                    ru   : Russian                  
    # ar_EG: Egyptian                 zh_CN: Simplified Chinese       
    # en_GB: English (Great Britain)  sk   : Slovak                   
    # et   : Estonian                 sl   : Slovenian                
    # fi   : Finnish                  es_ES: Spanish                  
    # de   : German                   sv   : Swedish                  
    # el   : Greek                    th   : Thai                     
    # iw   : Hebrew                   zh_TW: Traditional Chinese      
    # hu   : Hungarian                tr   : Turkish                  
    # is   : Icelandic                uk   : Ukrainian                
    # in   : Indonesian               vi   : Vietnamese               
    # it   : Italian                                                  
    # all_langs   : All languages
    # Specify value as the following to select any of the languages.
    # Example : SELECTED_LANGUAGES=en,fr,ja
    # Specify value as the following to select all the languages.
    # Example : SELECTED_LANGUAGES=all_langs 
    SELECTED_LANGUAGES=en
    # Specify the complete path of the Oracle Home.
    ORACLE_HOME=/extended2/oracleBase/db12c1
    # Specify the complete path of the Oracle Base.
    ORACLE_BASE=/extended2/oracleBase
    # Specify the installation edition of the component.                    
    # The value should contain only one of these choices.       
    #   - EE     : Enterprise Edition                               
    #   - SE     : Standard Edition                                 
    #   - SEONE  : Standard Edition One
    #   - PE     : Personal Edition (WINDOWS ONLY)
    oracle.install.db.InstallEdition=SE
    # PRIVILEGED OPERATING SYSTEM GROUPS                                          #
    # Provide values for the OS groups to which OSDBA and OSOPER privileges       #
    # needs to be granted. If the install is being performed as a member of the   #
    # group "dba", then that will be used unless specified otherwise below.       #
    # The value to be specified for OSDBA and OSOPER group is only for UNIX based #
    # Operating System.                                                           #
    # The DBA_GROUP is the OS group which is to be granted OSDBA privileges.
    oracle.install.db.DBA_GROUP=osdba
    # The OPER_GROUP is the OS group which is to be granted OSOPER privileges.
    # The value to be specified for OSOPER group is optional.
    oracle.install.db.OPER_GROUP=osoper
    # The BACKUPDBA_GROUP is the OS group which is to be granted OSBACKUPDBA privileges.
    oracle.install.db.BACKUPDBA_GROUP=bckdba
    # The DGDBA_GROUP is the OS group which is to be granted OSDGDBA privileges.
    oracle.install.db.DGDBA_GROUP=dbdba
    # The KMDBA_GROUP is the OS group which is to be granted OSKMDBA privileges.
    oracle.install.db.KMDBA_GROUP=kmdba
    #                               Grid Options                                  #
    # Specify the type of Real Application Cluster Database
    #   - ADMIN_MANAGED: Admin-Managed
    #   - POLICY_MANAGED: Policy-Managed
    # If left unspecified, default will be ADMIN_MANAGED
    oracle.install.db.rac.configurationType=
    # Value is required only if RAC database type is ADMIN_MANAGED
    # Specify the cluster node names selected during the installation.
    # Leaving it blank will result in install on local server only (Single Instance)
    # Example : oracle.install.db.CLUSTER_NODES=node1,node2
    oracle.install.db.CLUSTER_NODES=
    # This variable is used to enable or disable RAC One Node install.
    #   - true  : Value of RAC One Node service name is used.
    #   - false : Value of RAC One Node service name is not used.
    # If left blank, it will be assumed to be false.
    oracle.install.db.isRACOneInstall=
    # Value is required only if oracle.install.db.isRACOneInstall is true.
    # Specify the name for RAC One Node Service
    oracle.install.db.racOneServiceName=
    # Value is required only if RAC database type is POLICY_MANAGED
    # Specify a name for the new Server pool that will be configured
    # Example : oracle.install.db.rac.serverpoolName=pool1
    oracle.install.db.rac.serverpoolName=
    # Value is required only if RAC database type is POLICY_MANAGED
    # Specify a number as cardinality for the new Server pool that will be configured
    # Example : oracle.install.db.rac.serverpoolCardinality=2
    oracle.install.db.rac.serverpoolCardinality=
    #                        Database Configuration Options                       #
    # Specify the type of database to create.
    # It can be one of the following:
    #   - GENERAL_PURPOSE/TRANSACTION_PROCESSING                      
    #   - DATA_WAREHOUSE                               
    oracle.install.db.config.starterdb.type=GENERAL_PURPOSE
    # Specify the Starter Database Global Database Name.
    oracle.install.db.config.starterdb.globalDBName=cbd
    # Specify the Starter Database SID.
    oracle.install.db.config.starterdb.SID=cdb1
    # Specify whether the database should be configured as a Container database.
    oracle.install.db.ConfigureAsContainerDB=true
    # Specify the  Pluggable Database name for the pluggable database in Container Database.
    oracle.install.db.config.PDBName=pdb1
    # Specify the Starter Database character set.
    #  One of the following
    #  AL32UTF8, WE8ISO8859P15, WE8MSWIN1252, EE8ISO8859P2,
    #  EE8MSWIN1250, NE8ISO8859P10, NEE8ISO8859P4, BLT8MSWIN1257,
    #  BLT8ISO8859P13, CL8ISO8859P5, CL8MSWIN1251, AR8ISO8859P6,
    #  AR8MSWIN1256, EL8ISO8859P7, EL8MSWIN1253, IW8ISO8859P8,
    #  IW8MSWIN1255, JA16EUC, JA16EUCTILDE, JA16SJIS, JA16SJISTILDE,
    #  KO16MSWIN949, ZHS16GBK, TH8TISASCII, ZHT32EUC, ZHT16MSWIN950,
    #  ZHT16HKSCS, WE8ISO8859P9, TR8MSWIN1254, VN8MSWIN1258
    oracle.install.db.config.starterdb.characterSet=AL32UTF8
    # This variable should be set to true if Automatic Memory Management
    # in Database is desired.
    # If Automatic Memory Management is not desired, and memory allocation
    # is to be done manually, then set it to false.
    oracle.install.db.config.starterdb.memoryOption=true
    # Specify the total memory allocation for the database. Value(in MB) should be
    # at least 256 MB, and should not exceed the total physical memory available
    # on the system.
    # Example: oracle.install.db.config.starterdb.memoryLimit=512
    oracle.install.db.config.starterdb.memoryLimit=512
    # This variable controls whether to load Example Schemas onto
    # the starter database or not.
    oracle.install.db.config.starterdb.installExampleSchemas=true
    # Passwords can be supplied for the following four schemas in the             #
    # starter database:                                                           #
    #   SYS                                                                       #
    #   SYSTEM                                                                    #
    #   DBSNMP (used by Enterprise Manager)                                       #
    # Same password can be used for all accounts (not recommended)                #
    # or different passwords for each account can be provided (recommended)       #
    # This variable holds the password that is to be used for all schemas in the
    # starter database.
    oracle.install.db.config.starterdb.password.ALL=CDBadmin12345#
    # Specify the SYS password for the starter database.
    oracle.install.db.config.starterdb.password.SYS=CBDsys12345#
    # Specify the SYSTEM password for the starter database.
    oracle.install.db.config.starterdb.password.SYSTEM=PDBsys12345#
    # Specify the DBSNMP password for the starter database.
    oracle.install.db.config.starterdb.password.DBSNMP=DBsnmp12345#
    # Specify the PDBADMIN password required for creation of Pluggable Database in the Container Database.
    oracle.install.db.config.starterdb.password.PDBADMIN=PDBadmin12345#
    # Specify the management option to use for managing the database.
    # Options are:
    # 1. CLOUD_CONTROL - If you want to manage your database with Enterprise Manager Cloud Control along with Database Express.
    # 2. DEFAULT   -If you want to manage your database using the default Database Express option.
    oracle.install.db.config.starterdb.managementOption=DEFAULT
    # Specify the OMS host to connect to Cloud Control.
    # Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
    oracle.install.db.config.starterdb.omsHost=
    # Specify the OMS port to connect to Cloud Control.
    # Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
    oracle.install.db.config.starterdb.omsPort=
    # Specify the EM Admin user name to use to connect to Cloud Control.
    # Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
    oracle.install.db.config.starterdb.emAdminUser=
    # Specify the EM Admin password to use to connect to Cloud Control.
    # Applicable only when oracle.install.db.config.starterdb.managementOption=CLOUD_CONTROL
    oracle.install.db.config.starterdb.emAdminPassword=
    # SPECIFY RECOVERY OPTIONS                                                    #
    # Recovery options for the database can be mentioned using the entries below  #
    # This variable is to be set to false if database recovery is not required. Else
    # this can be set to true.
    oracle.install.db.config.starterdb.enableRecovery=true
    # Specify the type of storage to use for the database.
    # It can be one of the following:
    #   - FILE_SYSTEM_STORAGE
    #   - ASM_STORAGE
    oracle.install.db.config.starterdb.storageType=FILE_SYSTEM_STORAGE
    # Specify the database file location which is a directory for datafiles, control
    # files, redo logs.        
    # Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE
    oracle.install.db.config.starterdb.fileSystemStorage.dataLocation=/extended1/db/data
    # Specify the recovery location.
    # Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE
    oracle.install.db.config.starterdb.fileSystemStorage.recoveryLocation=/extended1/db/recovery
    # Specify the existing ASM disk groups to be used for storage.
    # Applicable only when oracle.install.db.config.starterdb.storageType=ASM_STORAGE
    oracle.install.db.config.asm.diskGroup=/dev/oracleasm
    # Specify the password for ASMSNMP user of the ASM instance.                
    # Applicable only when oracle.install.db.config.starterdb.storage=ASM_STORAGE
    oracle.install.db.config.asm.ASMSNMPPassword=ASMsnmp122345#
    # Specify the My Oracle Support Account Username.
    #  Example   : [email protected]
    MYORACLESUPPORT_USERNAME=
    # Specify the My Oracle Support Account Username password.
    # Example    : MYORACLESUPPORT_PASSWORD=password
    MYORACLESUPPORT_PASSWORD=
    # Specify whether to enable the user to set the password for
    # My Oracle Support credentials. The value can be either true or false.
    # If left blank it will be assumed to be false.
    # Example    : SECURITY_UPDATES_VIA_MYORACLESUPPORT=true
    SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
    # Specify whether user doesn't want to configure Security Updates.
    # The value for this variable should be true if you don't want to configure
    # Security Updates, false otherwise.
    # The value can be either true or false. If left blank it will be assumed
    # to be false.
    # Example    : DECLINE_SECURITY_UPDATES=false
    DECLINE_SECURITY_UPDATES=flase
    # Specify the Proxy server name. Length should be greater than zero.
    # Example    : PROXY_HOST=proxy.domain.com
    PROXY_HOST=
    # Specify the proxy port number. Should be Numeric and atleast 2 chars.
    # Example    : PROXY_PORT=25
    PROXY_PORT=
    # Specify the proxy user name. Leave PROXY_USER and PROXY_PWD
    # blank if your proxy server requires no authentication.
    # Example    : PROXY_USER=username
    PROXY_USER=
    # Specify the proxy password. Leave PROXY_USER and PROXY_PWD 
    # blank if your proxy server requires no authentication.
    # Example    : PROXY_PWD=password
    PROXY_PWD=
    # Specify the proxy realm.
    # Example    : PROXY_REALM=metalink
    PROXY_REALM=
    # Specify the Oracle Support Hub URL.
    # Example    : COLLECTOR_SUPPORTHUB_URL=https://orasupporthub.company.com:8080/
    COLLECTOR_SUPPORTHUB_URL=
    # Specify the auto-updates option. It can be one of the following:
    #   - MYORACLESUPPORT_DOWNLOAD
    #   - OFFLINE_UPDATES
    #   - SKIP_UPDATES
    oracle.installer.autoupdates.option=SKIP_UPDATES
    # In case MYORACLESUPPORT_DOWNLOAD option is chosen, specify the location where
    # the updates are to be downloaded.
    # In case OFFLINE_UPDATES option is chosen, specify the location where the updates
    # are present.
    oracle.installer.autoupdates.downloadUpdatesLoc=
    # Specify the My Oracle Support Account Username which has the patches download privileges 
    # to be used for software updates.
    #  Example   : [email protected]
    AUTOUPDATES_MYORACLESUPPORT_USERNAME=
    # Specify the My Oracle Support Account Username password which has the patches download privileges 
    # to be used for software updates.
    # Example    : AUTOUPDATES_MYORACLESUPPORT_PASSWORD=password
    AUTOUPDATES_MYORACLESUPPORT_PASSWORD=

    This is the simplest installation you can get, but if you want to do a fast response file based installation, there it is.

  • Crystal Report 2008 doesn't set  page size when export to excel file

    Hi,
    I am using Crystal Report 2008 Developer edition.
    At Crystal report design time setting the below page setup:
    Page Options -
       to A3(297X420 mm)
    Orientation --- Landscape
    and using the following code in .net (c#)
    I am using below format options to export in excel in .net 2005
    ReportDocument oReport = new ReportDocument();
    oReport.FormatEngine.PrintOptions.PaperOrientation = PaperOrientation.Landscape;
    oReport.FormatEngine.PrintOptions.PaperSize = CrystalDecisions.Shared.PaperSize.PaperA3;
    if (aParamlist.ReportFormat == ReportFormatEnum.MicrosoftExcel)
    ExcelFormatOptions excel = new ExcelFormatOptions();
    excel.ExcelUseConstantColumnWidth = false;
    // Use detail section one as a guideline to determine column width
    excel.ExcelAreaGroupNumber = 1;
    //excel.ExcelAreaType = AreaSectionKind.Detail;
    excel.ExcelAreaType = AreaSectionKind.Detail;
    // Prepare exporting options
    ExportOptions export = oReport.ExportOptions;
    export.FormatOptions = excel;
    export.ExportFormatType = ExportFormatType.Excel;
    oReport.Export();
    when export to excel it doesn't set the Paper Size to  A3(297X420 mm).
    Is there any way to set the paper size while export to excel or in other formats also????
    Thanks & Regds,

    Hi,
    thanks for your email.
    This is not happening in development environment.It is setting the paper size anf paper orientation properly.
    this is happening in the production environment where only redist installation is done.
    thanks

  • Oracle 8.1.7.4.1 Enterprise to Oracle 10.2.0.3.0 Standard Edition migration

    Hi,
    I'm in the planning stage of migrating an Oracle 8.1.7.4.1 Enterprise database to an Oracle 10.2.0.3.0 Standard Edition and i have a couple of questions.
    1) Can it be done or do i have to migrate to Oracle 10.2.0.3.0 Enterprise Edition?
    2) If it can be done can i
    a) follow the manual upgrade process to upgrade to 10.2.0.3.0 Standard Edition?
    b) use export to take an 8.1.7.4.1 enterprise export and then import it into a new empty 10.2.0.3.0 database?
    I've read the 10g upgrade guide but i can't see any pointers on this but please feel free to point me to any documentation resources.
    Thanks in anticipation of you help.
    Regards,
    George Johnston
    OCP DBA 9i

    Refer metalink note 421191.1

  • Migration of Windows Small Business Server 2011 Standard Edition to new hardware

    Hi
    I have a Windows SBS 2011 Standard Edition installation, of which, the windows component is very buggy.  Everything on the server is working i.e. AD, Email.  I am unable to shutdown the server gracefully, i am unable to open the system manager.
     Backups also are not running, so i don't have a proper backup that i can use.
    I want to migrate my Windows SBS installation to some standby equipment which i have, then reinstall the old server with Windows SBS 2011 and migrate back from the standby equipment to the original hardware.
    I know this is possible, and i know that Windows SBS 2011 gives a 21 days grace period to complete the migration.
    Is the path i have mentioned above seems to be viable for me to try and get back to my original hardware, with a fresh installation of Windows SBS, keeping AD and Microsoft Exchange intact.
    Regards

    Will not work as you have outlined it.  The installation of a new server installs a new SID and you cannot add SBS to SBS domains.  The only chance you have at this is to install a new non-SBS DC in the domain, export the mail assuming you are
    using Exchange, move the shares to the new DC or some other system, pull out the SBS from the domain, move all the FSMO roles and have a stand alone Server Domain without SBS.  Then, add SBS back to the domain in the documented manner.
    I suggest you contact www.sbsmigration.com for a documented and supported method to accomplish this migration.
    Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

  • Huge size file processing in PI

    Hi Experts,
    1. I have seen blogs which explains processing huge files. for file and sftp
    SFTP Adapter - Handling Large File
    File/FTP Adapter - Large File Transfer (Chunk Mode)
    Here also we have constrain that we can not do any mapping. it has to be EOIO Qos.
    would it be possible, to process  1 GB size file and do mapping? which hardware factor will decide that sytem is capable of processing large size with mapping?
    is it number of CPUs,Applications server(JAVA and ABAP),no of server nodes,java,heap size?
    if my system if able to process 10 MB file with mapping there should be something which is determining the capability.
    this kind of huge size file processing will fit into some scenarios.  for example,Proxy to soap scenario with 1GB size message exchange does not make sense. no idea if there is any web service will handle such huge file.
    2. consider pi is able to process 50 MB size message with mapping. in order to increase the performance what are the options we have in PI
    i have come across these two point many times during design phase of my project. looking for your suggestion
    Thanks.

    Hi Ram,
    You have not mentioned what sort of Integration it is.You just mentioned as FILE.I presume it is FILE To FILE scenario.In this case in PI 711 i am able to process 100MB(more than 1Million records ) file size with mapping(File is in the delta extract in SAP ECC AL11).In the sender file adapter i have chosen recordset per message and processed the messages in bit and pieces.Please note this is not the actual standard chunk mode.The initial run of the sender adapter will load the 100MB file size into the memory and after that messages will be sent to IE based on recordset per message.If it is more than 100MB PI Java starts bouncing because of memory issues.Later we have redesigned the interface from proxy to file asyn and proxy will send the messages to PI in chunks.In a single run it will sent 5000 messages.
    For PI 711 i believe we have the memory limtation of the cluster node.Each cluster node can't be more than 5GB again processing depends on the number of Java app servers and i think this is no more the limitation from PI 730 version and we can use 16GB memory as the cluser node.
    this kind of huge size file processing will fit into some scenarios.  for example,Proxy to soap scenario with 1GB size message exchange does not make sense. no idea if there is any web service will handle such huge file.
    If i understand this i think if it is asyn communication then definitely 1GB data can sent to webservice however messages from Proxy should sent to PI in batches.May be the same idea can work for Sync communication as well however timeouts in receiver channel will be the next issue.Increasing time outs globally is not best practice however if you are on 730 or later version you can increase timeouts specific to your scenario.
    To handle 50 MB file size make sure you have the additional java app servers.I don't remember exactly how many app server we have in my case to handle 100 MB file size.
    Thanks

  • OBI Standard Edition One (10.1.3.2.1) Database Error

    Hi Guys!
    I installed OBI Standard Edition One (10.1.3.2.1). In that BI Admin tool, Presentation services were installed properly. But i have problem in OBI Standard Edition One database it is not installing properly. While installing i didn't get any error message but in start menu i can't able to find any oracle home folder, no oracle listener. The sample reports i opened in dashboard all reports showing TNS error message.
    Can any one tell what is the problem how to solve the problem....

    Ya i'm having but what about OBI Standard Edition database? i want to see the OBISE one inbuilt tables! How to fetch the default schema?

  • Standard Edition Memory Limitations

    What is the upper memory limitation for the SGA size when using Standard Edition 9.x on Windows 2000?
    What about Enterprise?

    According what I know the SGA in one OS is limited by the OS and the parameter SGA_MAX_SIZE. I have never heard that SGA has limitations related to the license.
    SGA_MAX_SIZE
    Parameter type
    Big integer
    Syntax
    SGA_MAX_SIZE = integer [K | M | G]
    Default value
    Initial size of SGA at startup, dependent on the sizes of different pools in the SGA, such as buffer cache, shared pool, large pool, and so on.
    Parameter class
    Static
    Range of values
    0 to operating system-dependent
    SGA_MAX_SIZE specifies the maximum size of SGA for the lifetime of the instance.
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch1190.htm#REFRN10198
    Joel P�rez

Maybe you are looking for