Essbase and Oracle Backups

We are currently implementing Hyperion Planning into our environment. In our existing systems ie SAP we have Oracle archiving turned on in our production systems. With Planning we have ESSBASE and Oracle to be concerned about. Is there a way to archive ESSBASE to be in sync with the Oracle archives? If so how can this be done?If the system for example crashed at 10 AM and our last offline and Essbase backups occurred at 11 PM at night, in oracle we can roll forward using the archives, but in Essbase I'm not sure if that can be done. We can't archive or put the database in read mode during the day since we have live activity going on. Are we stuck to a point where we have to restore from the 11 PM backup? Anyone have this issue?Please send comments to my email [email protected]

I can decribe my scenario in detail.
I got two data source from Oracle relational tables and Essbase. And I need to join them together to do analysis. To make it simple, I will illustrate it by an example.
There is main analysis in Essbase, including fact tables and dimension tables. For example, one of the dimension tables is Time dimension which contains hierarchical data only.
In Oracle table, I got a table named Sales_Date storing description data of Time dimension.
Since description data needs to be used in Time dimension, I use complex join to join Sales_Date to Essbase Time dimension in physical layer and BMM layer.
Sales_Date is dragged from physical to BMM layer, and its columns are dragged to Time dimension tables. Then New Logical Keys are created under Time dimension hierarchy for those columns.
Finally, presentation layer is created by dragging tables from BMM layer.
When I try to select columns from Time Dimension(including columns from Sales_Date) and fact tables, below error msg appears.
nQSError: 42043 An external aggregate is found in an outer query block. (HY000)
Please help.

Similar Messages

  • Query ESSBASE and Oracle in one query

    What is the best way to query in the same time an ESSBASE database and an Oracle Database.I need to retrieve ESSBASE data with information stored in Oracle Database (supplement data).Thanks

    I've used Oracle and MySQL together on several machines; there's no contention or incompatibility that I've ever encountered. They listen on different ports by default (1521 for Oracle, 3306 for MySQL).
    As for PHP, you'll probably want to read an introductory article from the [Oracle PHP Developer Center|http://www.oracle.com/technology/tech/php/index.html]. Nothing you do there should interfere with your MySQL operations, either.
    Have fun!

  • BIEE access to Essbase and Oracle

    I need to access Essbase through BIEE, and lookup the description from Oracle DB using the Essbase id retrieved at particular levels.
    I experienced that even though I select two dimensions out of the five dimensions, all dimensions will be accessed with crossjoin as below:
    With
    set [MATERIALS5] as '[MATERIALS].Generations(5).members'
    set [GEOGRAPHY5] as '[GEOGRAPHY].Generations(5).members'
    set [YEARS2] as '[YEARS].Generations(2).members'
    set [DATE5] as '[DATE].Generations(5).members'
    set [Axis1Set] as 'crossjoin ({[MATERIALS5]},crossjoin ({[GEOGRAPHY5]},crossjoin ({[YEARS2]},{[DATE5]})))'
    select
    {[MEASURES].[AMOUNT]} on columns,
    NON EMPTY {[Axis1Set]} properties ANCESTOR_NAMES, GEN_NUMBER on rows
    from [CUBE01.JP]
    Basically, I only retrieve month only and also the month properties at level 3 of "DATE" dimension. Why is 'DATE5' needed when I need MONTH only (which is 'DATE3')? Is the above an optimal path for the Essbase access?
    My experience is that I see the memory grows up and up and then reaches around 2GB and then BIEE returns an error. Then I also need to restart BIEE so that I can rerun the query.
    Can anyone give me any hints how to tune up the access and address this problem?
    Thanks

    Hi,
    Are there any document that describes how to interpret the following generated statement?
    >>>
    With
    set MATERIALS5 as 'MATERIALS.Generations(5).members'
    set GEOGRAPHY5 as 'GEOGRAPHY.Generations(5).members'
    set YEARS2 as 'YEARS.Generations(2).members'
    set DATE5 as 'DATE.Generations(5).members'
    set Axis1Set as 'crossjoin ({MATERIALS5},crossjoin ({GEOGRAPHY5},crossjoin ({YEARS2},{DATE5})))'
    select
    {MEASURES.AMOUNT} on columns,
    NON EMPTY {Axis1Set} properties ANCESTOR_NAMES, GEN_NUMBER on rows
    from http://CUBE01.JP
    <<<
    Thanks

  • Hyperion Backup of Windows and Oracle DB

    <p>Hi,</p><p> </p><p>I have a question regarding Hyperion System 9 backup of windowsservers and Oracle/Essbase backup.</p><p> </p><p>Do we need to bring down all the services and backup all windowsservers and Oracle/Essbase together.  If we need to restoreonly windows or lets say Oracle.  Will that be out of sync. Do we have be in sync all the time ?</p><p> </p><p>Thanks</p><p> </p><p>Azmat Bhatti</p>

    Hello,<BR>You did not specify which relation Essbase and Oracle have in your environment. I my answer I assume you create Essbase databases from your Oracle environment to analyze this data. You extract with SQL statements and rule files data from Oracle to build up your outlines and load the data. <BR><BR>In this, I would not say you need a synchronous backup, since with a new refresh your structure will be created and the data loaded. Ofcourse I would not recommend more than 24 hours between the backup of Essbase versus Oracle.<BR><BR>I hope this answered your question.<BR><BR>Regards,<BR>Philip Hulsebosch<BR><BR>www.Trexco.nl

  • System copy using oracle backup/restore - sapinst does not restart after re

    I am performing a system copy of a BW3.5 system, using the system copy procedures and Oracle backup/restore. on the target node, I have installed the CI. I have run sapinst to install the database up to the point when it tells me to install the Oracle Server software, then restore the backup, and choose 'OK' in the dialog box. As I did not want to leave this dialog open, I chose 'cancel'. I have now installed Oracle, and restored the database, but when I try restarting sapinst I get the following error, and sapinst quits:
    FKD-00049  XML - Parser error: error: invalid symbol '' in literal 'SAPSYSTEM_DB
    indind_ind_ind_ind_0_SAPSYSTEM_ind_ind_ind_ind_ind_0_SAPComponent_ind_ind_ind_
    ind_ind_0_SAPComponent_Accounts_ind_ind_ind_ind_ind_0_SAPCompon' in line 1, 1
    in file
    ERROR      2007-08-20 15:06:13 [iaxxcsihlp.hpp:208]
               main()
    FCO-00031  An error occurred during the installation of component Problem: error
    in persistency subsystem.. Press the log view button to get extended error info
    rmation or press OK to terminate the installation.
    Has anybody ever experienced this before, or have any clues as to what the problem is? This is a production system, and it is supposed to be available by the end of the week....

    Hi Angie,
    You should always mention OS details while drafting message.
    First, CHeck you must selected same SID as earlier while installation or Oracle and DB.
    Secondly, you can skip this phase in SAPInst, bit technical for you.
    Alternatively,
    Recommendations
    - Set parameters as per SAP Note 356370
    - Change the swap mode from 'intermediate' to 'deferred' as described in
      SAP Note 97179.
    - Add /usr/sbin to the path of the user <sapsid>adm in the file
    .cshrc, .login, .profile in the user's home directory. Enter the
    following command(s) at the end of .cshrc, .login, .profile:
      a) If using a csh, enter:
           set path=(/usr/sbin $path)
      b) If using a sh, enter:
           path=/usr/sbin:$path
           export path
    Br,
    Amit Lal
    Reward suitable pts.

  • OBIEE 11g write back to Essbase and run calc script feature

    Hi,
    I have a requirement to write back into Essbase Cube and run calc script from OBIEE dashboard.
    From what i have search on google, we must deploy additional Java Script into weblogic, but that is before OBIEE 11.1.1.6.
    I have 2 question:
    - Does OBIEE 11.1.1.6 already supported native write-back to Essbase and running calcscript?
    - Anyone has example of the custom java-script for write back and running calcscript?
    And another, if there are requirement like this, is it better to install Essbase Add-in on Microsoft Excel and do the what-if analysis there, then just display the report on OBIEE dashboard? (based on user-friendliness and the complexity on maintenance)
    Thanks in advance.

    Hi,
    Even I am trying to achieve the same thing as you have mentioned but think that it is not possible to achieve easily in obiee 11.1.1.6, though we do have a work around to perform a writeback in Essbase cube using JAPI as mentioned below.
    Also we can call Hyperion reports from OBIEE using Action Links and also pass parameters to the same but dont know if it runs calculation script.
    Below link could be useful for you for write back workaround.
    http://oraclebizint.wordpress.com/2009/05/25/oracle-bi-ee-10-1-3-4-1-writebacks-to-essbase-using-japi-and-custom-html-part-1/
    Let me know in case you have found out anything else related to same.
    Thanks,

  • REDUNDANCY and Level1 backups

    Oracle Version -- 10.2.0.4
    Backup Type -- Differential Incremental Backup
    Current Retention policy -- Recovery window (4 days)
    Sunday
    Monday -------------> Level 0 Backup(3:00am)
    Tuesday
    Wednesday
    Thursday ----------->Level 0 Backup (3:00am)
    Friday
    SaturdayWe have tested our Differential Incremental backup with RECOVERY WINDOW for 2 weeks. Due to space constraints, we don't think we can use RECOVERY WINDOW retention policy. So, we are thinking of going for REDUNDANCY.
    I understand that, after setting REDUNDANCY as the retention policy: Monday's Level0 backup becomes obsolete on thursday when the next level 0 backup is run. We are fine with this. But we are worried about LEVEL 1 backups.
    You cannot set a different separate RETENTION POLICY for level0 and level1 backups.
    On Tuesday ---- We take a Level1 backup
    On Wednesday ---- Will tuesday's Level1 backup become obsolete?Tuesday's level1 backup and the subsequent level1 backups shouldn't become obsolete until the next Level0 backup. Is RMAN binary intelligent enough to recognize this logic/requirement?

    REDUNDANCY applies to the ability to recover the full database.
    Your intermediate L1 backups would not be obsoleted until you do a fresh L0 backup.
    Hemant K Chitale

  • Out of memory using Windows Server 2003 and Oracle 9.2.0.3

    Hi,
    I just installed both Windows Server 2003 and Oracle 9.2.0.3. The server I am using has 4 gigabytes of memory installed, and windows shows that to be the actual physical memory on the server. The paging file is 8 gigabytes for a total of 12 gigabytes of virtual memory.
    Using the Oracle Database Configuration Assistant, I create a new database using default values. After verifying the installation worked OK (database started, queries ran), I attempted to change some of the memory parameters and was able to start the database using about 1.4 gigabytes of total SGA, with the O/S using about .3 gigabytes for a total of 1.7 gigabytes. I then attempted to change the buffer cache + 1 gigabyte for a total of 2 gigabytes. Now the database will not start and I get an out of memory error ora-27102 with an additional O/S memory error of "O/S Error: (OS 8) Not enough storage is available to process this command".
    So, I have two problems:
    1) With 4 gigabytes installed, and the O/S using only about 300 megabytes, why isn't Oracle able to take advantage of the memory on this machine past the 1.7 gigabytes (as reported by Windows task manager).
    2) How do I change the spfile memory parameters so the database will start using spfile? I can start the database pointing to a pfile with lesser memory parameters, but I don't know how to effect change on the spfile, since I cannot start with the spfile.
    Both these technologies (9.2.0.3 and Server 2003) are new to me, so any insight would be appreciated!
    HERE ARE THE SPFILE PARAMETERS THAT WORKED:
    SGA (M)
    Shared Pool=104
    Buffer Cache=960 ***
    Large Pool=0
    Java Pool=64
    Total SGA=1128
    SGA Max Size=1321
    Aggregate PGA Target=1500
    Current PGA Allocated=22868KB
    WINDOWS MEMORY INFO FROM TASK MANAGER SHOW:
    PF Usage=1.66GB
    Physical Memory (K)
    Total=4062704
    Available=3203460
    System Cache=2499096
    Commit Charge (K)
    Total=1748184
    Limit=12288628
    Peak=1925276
    *** When I change this to 2048 the database did not start.
    Thank you.

    CREATE SPFILE
    Purpose
    Use the CREATE SPFILE statement to create a server parameter file from a client-side initialization parameter file. Server parameter files are binary files that exist only on the server and are called from client locations to start up the database.
    Server parameter files let you make persistent changes to individual parameters. When you use a server parameter file, you can specify in an ALTER SYSTEM SET parameter statement that the new parameter value should be persistent. This means that the new value applies not only in the current instance, but also to any instances that are started up subsequently. Traditional client-side parameter files do not let you make persistent changes to parameter values. Because they are located on the server, these files allow for automatic database tuning by Oracle and for backup by Recovery Manager (RMAN).
    To use a server parameter file when starting up the database, you must create it from a traditional text initialization parameter file using the CREATE SPFILE statement.
    All instances in an Real Application Clusters environment must use the same server parameter file. However, when otherwise permitted, individual instances can have different settings of the same parameter within this one file. Instance-specific parameter definitions are specified as SID.parameter = value, where SID is the instance identifier.
    The method of starting up the database with a server parameter file depends on whether you create a default or nondefault server parameter file. Please refer to "Creating a Server Parameter File: Examples" for examples of how to use server parameter files.
    See Also:
    CREATE PFILE for information on creating a regular text parameter file from a binary server parameter file
    Oracle9i Database Administrator's Guide for information on pre-Oracle9i initialization parameter files and Oracle9i server parameter files
    Oracle9i Real Application Clusters Administration for information on using server parameter files in a Real Application Clusters environment
    Prerequisites
    You must have the SYSDBA or the SYSOPER system privilege to execute this statement. You can execute this statement before or after instance startup. However, if you have already started an instance using spfile_name, you cannot specify the same spfile_name in this statement.
    Syntax
    create_spfile::=
    Text description of create_spfile
    Semantics
    spfile_name
    This clause lets you specify a name for the server parameter file you are creating.
    If you do not specify spfile_name, Oracle uses the platform-specific default server parameter filename. If spfile_name already exists on the server, this statement will overwrite it. When using a default server parameter file, you start up the database without referring to the file by name.
    If you do specify spfile_name, you are creating a nondefault server parameter file. In this case, to start up the database, you must first create a single-line traditional parameter file that points to the server parameter file, and then name the single-line file in your STARTUP command.
    See Also:
    "Creating a Server Parameter File: Examples" for information on starting up the database with default and nondefault server parameter files
    Oracle9i Database Administrator's Guide for Windows (or other appropriate operating system specific documentation) for default parameter file names
    pfile_name
    Specify the traditional initialization parameter file from which you want to create a server parameter file.
    If you specify pfile_name, the parameter file must reside on the server. If it does not reside in the default directory for parameter files on your operating system, you must specify the full path.
    If you do not specify pfile_name, Oracle looks in the default directory for parameter files on your operating system for the default parameter filename, and uses that file. If that file does not exist in the expected directory, Oracle returns an error.
    Note:
    In a Real Application Clusters environment, you must first combine all instance parameter files into one file before specifying it in this statement to create a server parameter file. For information on accomplishing this step, see Oracle9i Real Application Clusters Setup and Configuration.
    Examples
    Creating a Server Parameter File: Examples
    The following example creates a default server parameter file from a client initialization parameter file named t_init1.ora:
    CREATE SPFILE
    FROM PFILE = '$ORACLE_HOME/work/t_init1.ora';
    Note:
    Typically you will need to specify the full path and filename for parameter files on your operating system. Please refer to your Oracle operating system documentation for path information.
    When you create a default server parameter file, you subsequently start up the database using that server parameter file by using the SQL*Plus command STARTUP without the PFILE parameter, as follows:
    STARTUP
    The following example creates a nondefault server parameter file s_params.ora from a client initialization file named t_init1.ora:
    CREATE SPFILE = 's_params.ora'
    FROM PFILE = '$ORACLE_HOME/work/t_init1.ora';
    When you create a nondefault server parameter file, you subsequently start up the database by first creating a traditional parameter file containing the following single line:
    spfile = 's_params.ora'
    The name of this parameter file must comply with the naming conventions of your operating system. You then use the single-line parameter file in the STARTUP command. The following example shows how to start up the database, assuming that the single-line parameter file is named new_param.ora:
    STARTUP PFILE=new_param.ora
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_616a.htm#SQLRF01315
    Joel P�rez

  • Oracle backup to ftp

    Hello all
    I have problems with oracle backup through db13 to ftp.
    Job log
    Job started
    Step 001 started (program RSDBAJOB, variant &0000000000028, user ID USER)
    Execute logical command BRBACKUP On host sap1-ast
    Parameters:-u / -jid ALLOG20061117094801 -c force -t online -m all -p initTHD.sap -a -c force -p initTHD.sap -c
    ds
    BR0051I BRBACKUP 7.00 (16)
    BR0282E Directory '/sapbackup' not found
    BR0182E Checking parameter/option 'compress_dir' failed
    BR0056I End of database backup: bdtyppxk.log 2006-11-17 09.48.04
    BR0280I BRBACKUP time stamp: 2006-11-17 09.48.04
    BR0054I BRBACKUP terminated with errors
    External program terminated with exit code 3
    BRBACKUP returned error status E
    Job finished
    this is my initTHD.sap file
    @(#) $Id: //bas/700_REL/src/ccm/rsbr/initNT.sap#5 $ SAP
    SAP backup sample profile. #
    The parameter syntax is the same as for init.ora parameters. #
    Enclose parameter values which consist of more than one symbol in #
    double quotes. #
    After any symbol, parameter definition can be continued on the next #
    line. #
    A parameter value list should be enclosed in parentheses, the list #
    items should be delimited by commas. #
    There can be any number of white spaces (blanks, tabs and new lines) #
    between symbols in parameter definition. #
    backup mode [all | all_data | full | incr | sap_dir | ora_dir
    | all_dir | <tablespace_name> | <file_id> | <file_id1>-<file_id2>
    | <generic_path> | (<object_list>)]
    default: all
    backup_mode = all
    restore mode [all | all_data | full | incr | incr_only | incr_full
    | incr_all | <tablespace_name> | <file_id> | <file_id1>-<file_id2>
    | <generic_path> | (<object_list>) | partial | non_db
    redirection with '=' is not supported here - use option '-m' instead
    default: all
    restore_mode = all
    backup type [offline | offline_force | offline_standby | offline_split
    | offline_mirror | offline_stop | online | online_cons | online_split
    | online_mirror
    default: offline
    backup_type = online_cons
    backup device type
    [tape | tape_auto | tape_box | pipe | pipe_auto | pipe_box | disk
    | disk_copy | disk_standby | stage | stage_copy | stage_standby
    | util_file | util_file_online | rman_util | rman_disk | rman_stage
    | rman_prep]
    default: tape
    backup_dev_type = stage
    backup root directory [<path_name> | (<path_name_list>)]
    default: %SAPDATA_HOME%\sapbackup
    backup_root_dir = /sapbackup
    stage root directory [<path_name> | (<path_name_list>)]
    default: value of the backup_root_dir parameter
    stage_root_dir = /sapbackup
    compression flag [no | yes | hardware | only]
    default: no
    compress = no
    compress command
    first $-character is replaced by the source file name
    second $-character is replaced by the target file name
    <target_file_name> = <source_file_name>.Z
    for compress command the -c option must be set
    recommended setting for brbackup -k only run:
    "%SAPEXE%\mkszip -l 0 -c $ > $"
    no default
    compress_cmd = "C:\usr\sap\THD\SYS\exe\uc\NTI386\mkszip -c $ > $"
    uncompress command
    first $-character is replaced by the source file name
    second $-character is replaced by the target file name
    <source_file_name> = <target_file_name>.Z
    for uncompress command the -c option must be set
    no default
    uncompress_cmd = "C:\usr\sap\THD\SYS\exe\uc\NTI386\uncompress -c $ > $"
    directory for compression [<path_name> | (<path_name_list>)]
    default: value of the backup_root_dir parameter
    compress_dir = /sapbackup
    brarchive function [save | second_copy | double_save | save_delete
    | second_copy_delete | double_save_delete | copy_save
    | copy_delete_save | delete_saved | delete_copied]
    default: save
    archive_function = save
    directory for archive log copies to disk
    default: first value of the backup_root_dir parameter
    archive_copy_dir = /sapbackup
    directory for archive log copies to stage
    default: first value of the stage_root_dir parameter
    archive_stage_dir = /sapbackup
    delete archive logs from duplex destination [only | no | yes | check]
    default: only
    archive_dupl_del = only
    new sapdata home directory for disk_copy | disk_standby
    no default
    new_db_home = X:\oracle\C11
    stage sapdata home directory for stage_copy | stage_standby
    default: value of the new_db_home parameter
    #stage_db_home = /sapbackup
    original sapdata home directory for split mirror disk backup
    no default
    #orig_db_home = C:\oracle\THD
    remote host name
    no default
    remote_host = srv1
    remote user name
    default: current operating system user
    remote_user = "thdadm password"
    tape copy command [cpio | cpio_gnu | dd | dd_gnu | rman | rman_gnu
    rman_dd | rman_dd_gnu]
    default: cpio
    tape_copy_cmd = cpio
    disk copy command [copy | copy_gnu | dd | dd_gnu | rman | rman_gnu]
    default: copy
    disk_copy_cmd = copy
    stage copy command [rcp | scp | ftp]
    default: rcp
    stage_copy_cmd = ftp
    pipe copy command [rsh | ssh]
    default: rsh
    pipe_copy_cmd = rsh
    flags for cpio output command
    default: -ovB
    cpio_flags = -ovB
    flags for cpio input command
    default: -iuvB
    cpio_in_flags = -iuvB
    flags for cpio command for copy of directories to disk
    default: -pdcu
    use flags -pdu for gnu tools
    cpio_disk_flags = -pdcu
    flags for dd output command
    default: "obs=16k"
    caution: option "obs=" not supported for Windows
    recommended setting:
    Unix: "obs=nk bs=nk", example: "obs=64k bs=64k"
    Windows: "bs=nk", example: "bs=64k"
    dd_flags = "bs=64k"
    flags for dd input command
    default: "ibs=16k"
    caution: option "ibs=" not supported for Windows
    recommended setting:
    Unix: "ibs=nk bs=nk", example: "ibs=64k bs=64k"
    Windows: "bs=nk", example: "bs=64k"
    dd_in_flags = "bs=64k"
    number of members in RMAN save sets [ 1 | 2 | 3 | 4 | tsp | all ]
    default: 1
    saveset_members = 1
    additional parameters for RMAN
    rman_channels and rman_filesperset are only used when rman_util,
    rman_disk or rman_stage
    rman_channels defines the number of parallel sbt channel allocations
    rman_filesperset = 0 means:
    one file per save set - for non-incremental backups
    all files in one save set - for incremental backups
    the others have the same meaning as for native RMAN
    rman_channels = 1
    rman_filesperset = 0
    rman_maxpiecesize = 0 # in KB - former name rman_kbytes
    rman_rate = 0 # in KB - former name rman_readrate
    rman_maxopenfiles = 0
    rman_maxsetsize = 0 # in KB - former name rman_setsize
    additional parameters for RMAN version 8.1
    the parameters have the same meaning as for native RMAN
    rman_diskratio = 0 # deprecated in Oracle 10g
    rman_pool = 0
    rman_copies = 0 | 1 | 2 | 3 | 4 # former name rman_duplex
    rman_proxy = no | yes | only
    special parameters for an external backup library, example:
    rman_parms = "BLKSIZE=65536 ENV=(BACKUP_SERVER=HOSTNAME)"
    rman_send = "'<command>'"
    rman_send = ("channel sbt_1 '<command1>' parms='<parameters1>'",
    "channel sbt_2 '<command2>' parms='<parameters2>'")
    remote copy-out command (backup_dev_type = pipe)
    $-character is replaced by current device address
    no default
    copy_out_cmd = "dd ibs=8k obs=64k of=$"
    remote copy-in command (backup_dev_type = pipe)
    $-character is replaced by current device address
    no default
    copy_in_cmd = "dd ibs=64k obs=8k if=$"
    rewind command
    $-character is replaced by current device address
    no default
    operating system dependent, examples:
    HP-UX: "mt -f $ rew"
    TRU64: "mt -f $ rewind"
    AIX: "tctl -f $ rewind"
    Solaris: "mt -f $ rewind"
    Windows: "mt -f $ rewind"
    Linux: "mt -f $ rewind"
    rewind = "mt -f $ rewind"
    rewind and set offline command
    $-character is replaced by current device address
    default: value of the rewind parameter
    operating system dependent, examples:
    HP-UX: "mt -f $ offl"
    TRU64: "mt -f $ offline"
    AIX: "tctl -f $ offline"
    Solaris: "mt -f $ offline"
    Windows: "mt -f $ offline"
    Linux: "mt -f $ offline"
    rewind_offline = "mt -f $ offline"
    tape positioning command
    first $-character is replaced by current device address
    second $-character is replaced by number of files to be skipped
    no default
    operating system dependent, examples:
    HP-UX: "mt -f $ fsf $"
    TRU64: "mt -f $ fsf $"
    AIX: "tctl -f $ fsf $"
    Solaris: "mt -f $ fsf $"
    Windows: "mt -f $ fsf $"
    Linux: "mt -f $ fsf $"
    tape_pos_cmd = "mt -f $ fsf $"
    mount backup volume command in auto loader / juke box
    used if backup_dev_type = tape_box | pipe_box
    no default
    mount_cmd = "<mount_cmd> $ $ $ [$]"
    dismount backup volume command in auto loader / juke box
    used if backup_dev_type = tape_box | pipe_box
    no default
    dismount_cmd = "<dismount_cmd> $ $ [$]"
    split mirror disks command
    used if backup_type = offline_split | online_split | offline_mirror
    | online_mirror
    no default
    split_cmd = "<split_cmd> [$]"
    resynchronize mirror disks command
    used if backup_type = offline_split | online_split | offline_mirror
    | online_mirror
    no default
    resync_cmd = "<resync_cmd> [$]"
    additional options for SPLITINT interface program
    no default
    split_options = "<split_options>"
    resynchronize after backup flag [no | yes]
    default: no
    split_resync = no
    volume size in KB = K, MB = M or GB = G (backup device dependent)
    default: 1200M
    recommended values for tape devices without hardware compression:
    60 m 4 mm DAT DDS-1 tape: 1200M
    90 m 4 mm DAT DDS-1 tape: 1800M
    120 m 4 mm DAT DDS-2 tape: 3800M
    125 m 4 mm DAT DDS-3 tape: 11000M
    112 m 8 mm Video tape: 2000M
    112 m 8 mm high density: 4500M
    DLT 2000 10/20 GB: 10000M
    DLT 2000XT 15/30 GB: 15000M
    DLT 4000 20/40 GB: 20000M
    DLT 7000 35/70 GB: 35000M
    recommended values for tape devices with hardware compression:
    60 m 4 mm DAT DDS-1 tape: 1000M
    90 m 4 mm DAT DDS-1 tape: 1600M
    120 m 4 mm DAT DDS-2 tape: 3600M
    125 m 4 mm DAT DDS-3 tape: 10000M
    112 m 8 mm Video tape: 1800M
    112 m 8 mm high density: 4300M
    DLT 2000 10/20 GB: 9000M
    DLT 2000XT 15/30 GB: 14000M
    DLT 4000 20/40 GB: 18000M
    DLT 7000 35/70 GB: 30000M
    tape_size = 100G
    volume size in KB = K, MB = M or GB = G used by brarchive
    default: value of the tape_size parameter
    tape_size_arch = 100G
    level of parallel execution
    default: 0 - set to number of backup devices
    exec_parallel = 0
    address of backup device without rewind
    [<dev_address> | (<dev_address_list>)]
    no default
    operating system dependent, examples:
    HP-UX: /dev/rmt/0mn
    TRU64: /dev/nrmt0h
    AIX: /dev/rmt0.1
    Solaris: /dev/rmt/0mn
    Windows: /dev/nmt0 | /dev/nst0
    Linux: /dev/nst0
    tape_address = /dev/nmt0
    address of backup device without rewind used by brarchive
    default: value of the tape_address parameter
    operating system dependent
    tape_address_arch = /dev/nmt0
    address of backup device with rewind
    [<dev_address> | (<dev_address_list>)]
    no default
    operating system dependent, examples:
    HP-UX: /dev/rmt/0m
    TRU64: /dev/rmt0h
    AIX: /dev/rmt0
    Solaris: /dev/rmt/0m
    Windows: /dev/mt0 | /dev/st0
    Linux: /dev/st0
    tape_address_rew = /dev/mt0
    address of backup device with rewind used by brarchive
    default: value of the tape_address_rew parameter
    operating system dependent
    tape_address_rew_arch = /dev/mt0
    address of backup device with control for mount/dismount command
    [<dev_address> | (<dev_address_list>)]
    default: value of the tape_address_rew parameter
    operating system dependent
    tape_address_ctl = /dev/...
    address of backup device with control for mount/dismount command
    used by brarchive
    default: value of the tape_address_rew_arch parameter
    operating system dependent
    tape_address_ctl_arch = /dev/...
    volumes for brarchive
    [<volume_name> | (<volume_name_list>) | SCRATCH]
    no default
    volume_archive = (THDA01, THDA02, THDA03, THDA04, THDA05,
    THDA06, THDA07)
    volumes for brbackup
    [<volume_name> | (<volume_name_list>) | SCRATCH]
    no default
    volume_backup = (THDB01, THDB02, THDB03, THDB04, THDB05,
    THDB06, THDB07)
    expiration period for backup volumes in days
    default: 30
    expir_period = 30
    recommended usages of backup volumes
    default: 100
    tape_use_count = 100
    backup utility parameter file
    default: no parameter file
    util_par_file = initTHD.utl
    mount/dismount command parameter file
    default: no parameter file
    mount_par_file = initTHD.mnt
    Oracle instance string to the primary database
    [primary_db = <conn_name> | LOCAL]
    no default
    primary_db = <conn_name>
    description of parallel instances for Oracle RAC
    parallel_instances = <instance_desc> | (<instance_desc_list>)
    <instance_desc_list> -> <instance_desc>[,<instance_desc>...]
    <instance_desc> -> <Oracle_sid>:<Oracle_home>@<conn_name>
    <Oracle_sid> -> Oracle system id for parallel instance
    <Oracle_home> -> Oracle home for parallel instance
    <conn_name> -> Oracle instance string to parallel instance
    Please include the local instance in the parameter definition!
    default: no parallel instances
    example for initRAC001.sap:
    parallel_instances = (RAC001:/oracle/RAC/920_64@RAC001,
    RAC002:/oracle/RAC/920_64@RAC002, RAC003:/oracle/RAC/920_64@RAC003)
    database owner of objects to be checked
    <owner> | (<owner_list>)
    default: all SAP owners
    check_owner = sapr3
    database objects to be excluded from checks
    all_part | non_sap | [<owner>.]<table> | [<owner>.]<index>
    | [<owner>.]<prefix>* | <tablespace> | (<object_list>)
    default: no exclusion, example:
    check_exclude = (SDBAH, SAPR3.SDBAD)
    database owner of SDBAH, SDBAD and XDB tables for cleanup
    <owner> | (<owner_list>)
    default: all SAP owners
    cleanup_owner = sapr3
    retention period in days for brarchive log files
    default: 30
    cleanup_brarchive_log = 30
    retention period in days for brbackup log files
    default: 30
    cleanup_brbackup_log = 30
    retention period in days for brconnect log files
    default: 30
    cleanup_brconnect_log = 30
    retention period in days for brrestore log files
    default: 30
    cleanup_brrestore_log = 30
    retention period in days for brrecover log files
    default: 30
    cleanup_brrecover_log = 30
    retention period in days for brspace log files
    default: 30
    cleanup_brspace_log = 30
    retention period in days for archive log files saved on disk
    default: 30
    cleanup_disk_archive = 30
    retention period in days for database files backed up on disk
    default: 30
    cleanup_disk_backup = 30
    retention period in days for brspace export dumps and scripts
    default: 30
    cleanup_exp_dump = 30
    retention period in days for Oracle trace and audit files
    default: 30
    cleanup_ora_trace = 30
    retention period in days for records in SDBAH and SDBAD tables
    default: 100
    cleanup_db_log = 100
    retention period in days for records in XDB tables
    default: 100
    cleanup_xdb_log = 100
    retention period in days for database check messages
    default: 100
    cleanup_check_msg = 100
    database owner of objects to adapt next extents
    <owner> | (<owner_list>)
    default: all SAP owners
    next_owner = sapr3
    database objects to adapt next extents
    all | all_ind | special | [<owner>.]<table> | [<owner>.]<index>
    | [<owner>.]<prefix>* | <tablespace> | (<object_list>)
    default: all abjects of selected owners, example:
    next_table = (SDBAH, SAPR3.SDBAD)
    database objects to be excluded from adapting next extents
    all_part | [<owner>.]<table> | [<owner>.]<index> | [<owner>.]<prefix>*
    | <tablespace> | (<object_list>)
    default: no exclusion, example:
    next_exclude = (SDBAH, SAPR3.SDBAD)
    database objects to get special next extent size
    all_sel:<size>[/<limit>] | [<owner>.]<table>:<size>[/<limit>]
    | [<owner>.]<index>:<size>[/<limit>]
    | [<owner>.]<prefix>*:<size>[/<limit>] | (<object_size_list>)
    default: according to table category, example:
    next_special = (SDBAH:100K, SAPR3.SDBAD:1M/200)
    maximum next extent size
    default: 2 GB - 5 * <database_block_size>
    next_max_size = 1G
    maximum number of next extents
    default: 0 - unlimited
    next_limit_count = 300
    database owner of objects to update statistics
    <owner> | (<owner_list>)
    default: all SAP owners
    stats_owner = sapr3
    database objects to update statistics
    all | all_ind | all_part | missing | info_cubes | dbstatc_tab
    | dbstatc_mon | dbstatc_mona | [<owner>.]<table> | [<owner>.]<index>
    | [<owner>.]<prefix>* | <tablespace> | (<object_list>) | harmful
    | locked | system_stats | oradict_stats
    default: all abjects of selected owners, example:
    stats_table = (SDBAH, SAPR3.SDBAD)
    database objects to be excluded from updating statistics
    all_part | info_cubes | [<owner>.]<table> | [<owner>.]<index>
    | [<owner>.]<prefix>* | <tablespace> | (<object_list>)
    default: no exclusion, example:
    stats_exclude = (SDBAH, SAPR3.SDBAD)
    method for updating statistics for tables not in DBSTATC
    E | EH | EI | EX | C | CH | CI | CX | A | AH | AI | AX | E= | C= | =H
    | =I | =X | +H | +I
    default: according to internal rules
    stats_method = E
    sample size for updating statistics for tables not in DBSTATC
    P<percentage_of_rows> | R<thousands_of_rows>
    default: according to internal rules
    stats_sample_size = P10
    number of buckets for updating statistics with histograms
    default: 75
    stats_bucket_count = 75
    threshold for collecting statistics after checking
    default: 50%
    stats_change_threshold = 50
    number of parallel threads for updating statistics
    default: 1
    stats_parallel_degree = 1
    processing time limit in minutes for updating statistics
    default: 0 - no limit
    stats_limit_time = 0
    parameters for calling DBMS_STATS supplied package
    all:R|B:<degree> | all_part:R|B:<degree> | info_cubes:R|B:<degree>
    | [<owner>.]<table>:R|B:<degree> | [<owner>.]<prefix>*:R|B:<degree>
    | (<object_list>) | NO
    default: NULL - use ANALYZE statement
    stats_dbms_stats = ([ALL:R:1,][<owner>.]<table>:R|B:<degree>,...)
    definition of info cube tables
    default | rsnspace_tab | [<owner>.]<table> | [<owner>.]<prefix>*
    | (<object_list>) | null
    default: from RSNSPACE control table
    stats_info_cubes = (/BIC/D, /BI0/D, ...)
    recovery type [complete | dbpit | tspit | reset | restore | apply
    | disaster]
    default: complete
    recov_type = complete
    directory for brrecover file copies
    default: $SAPDATA_HOME/sapbackup
    recov_copy_dir = C:\oracle\THD\sapbackup
    time period for searching for backups
    0 - all available backups, >0 - backups from n last days
    default: 30
    recov_interval = 30
    degree of paralelism for applying archive log files
    0 - use Oracle default parallelism, 1 - serial, >1 - parallel
    default: Oracle default
    recov_degree = 0
    number of lines for scrolling in list menus
    0 - no scrolling, >0 - scroll n lines
    default: 20
    scroll_lines = 20
    time period for displaying profiles and logs
    0 - all available logs, >0 - logs from n last days
    default: 30
    show_period = 30
    directory for brspace file copies
    default: $SAPDATA_HOME/sapreorg
    space_copy_dir = C:\oracle\THD\sapreorg
    directory for table export dump files
    default: $SAPDATA_HOME/sapreorg
    exp_dump_dir = C:\oracle\THD\sapreorg
    database tables for reorganization
    [<owner>.]<table> | [<owner>.]<prefix>* | [<owner>.]<prefix>%
    | (<table_list>)
    no default
    reorg_table = (SDBAH, SAPR3.SDBAD)
    database indexes for rebuild
    [<owner>.]<index> | [<owner>.]<prefix>* | [<owner>.]<prefix>%
    | (<index_list>)
    no default
    rebuild_index = (SDBAH0, SAPR3.SDBAD0)
    database tables for export
    [<owner>.]<table> | [<owner>.]<prefix>* | [<owner>.]<prefix>%
    | (<table_list>)
    no default
    exp_table = (SDBAH, SAPR3.SDBAD)
    database tables for import
    [<owner>.]<table> | (<table_list>)
    no default
    imp_table = (SDBAH, SAPR3.SDBAD)
    I can log in to ftp from server
    C:\Documents and Settings\thdadm>ftp srv1
    Connected to srv1.
    220 Microsoft FTP Service
    User (srv1:(none)): thdadm
    331 Password required for thdadm.
    Password:
    230 User thdadm logged in.
    ftp> ls
    200 PORT command successful.
    150 Opening ASCII mode data connection for file list.
    sapbackup
    226 Transfer complete.
    ftp: 11 bytes received in 0,00Seconds 11000,00Kbytes/sec.
    ftp> mkdir sap
    257 "sap" directory created.
    please help
    best regards
    Olzhas Suleimenov

    del

  • Oracle Backup tools

    Hi Experts,
    Plz guide me which is the best third party tool for backup & recover of database in Oracle and where can i get the trail version of this tool.
    Thanx in Advance
    Mani

    Most people use RMAN nowadays, I don't think you need any other third party tools to do Oracle backup. Most storage vendor will try to make their tools to be integrated with RMAN rather than come up a new tool.
    When it comes to backup/recovery of Oracle database nobody can do a better job than Oracle itself.
    http://download-west.oracle.com/docs/cd/B19306_01/backup.102/b14192/intro005.htm#sthref66

  • Differance between microsoft sql 7 server and oracle 8

    can anybody give me the exact technical differances between microsoft 7 server and
    oracle8 server ?

    hi,
    below i listed few differences known to me.
    Oracle is a multiplatform rdbms whereas sqlserver is restricted to NT server workstations.
    Oracle does not include the concept of master db. All db runs independently, with their own data files,mem management, and control.
    Sql server has much larger set of fundamental data types than oracle.
    Oracle uses row-level locking whereas sqlserver uses page level locking.
    Oracle is more mature product. It should be used for high throughput and availability and reliable backup and recovery.
    hope it will give u some idea.
    regards,
    arun.

  • How to do oracle  backup,restore,recovery using php?

    Is there anyone know how to do oracle backup,restore and recovery using php? any tips... is there any ways to do that?

    Are you referring to performing RMAN backup operations via the OSB web tool? RMAN operations are managed, not via the web tool, but through RMAN command line or Oracle Enterprise Manager (EM)
    Donna

  • System Copy/ Oracle Backup/Restore as part of migrating from 32 to 64-bit

    Source system (I386): R3E47 Ext Set 2.00 SAP_BASIS 620 Kernel 640 Windows 2000, Oracle 10.2.0.4, non-unicode
    Target system (x86-64/AMD64): R3E47 Ext Set 2.00 SAP_BASIS 620 Kernel 640 Windows 2000 Oracle 10.2.0.4, non-unicode
    Am using method System Copy/ Oracle Backup/Restore to migrate from 32 to 64 bit (HOM System Copy).
    Actions on source system:
    a) Upgrade from 9.2.0.7 to Oracle 10.2.0.4
    b) Used ora_br_copy.bat to generate CONTROL.SQL and init<sid>.ora
    c) Switched logfiles
    d) Performed offline backup
    Actions on target system:
    a) Installed Oracle 10.2.0.1 and patched it to 10.2.0.4
    b) Used CD 51033746 "6.20/6.40 based products Installation Master (Edition May 2008)" to install the CI
    c) Started installation of the DB instance selecting System Copy/ Oracle Backup/Restore (same <SID> for source and target systems)
    Relevant input parameters used:
    Database schema: SAPR3
    Database character set: US7ASCII
    d) When SAPINST stopped to allow for restoring of datafiles, logs and init<sid.ora>:
    - copied datafiles and logs to the usual place
    - copied CONTROL.SQL (edited to include utilrp.sql and utlrp.sql for the migration from 32 to 64) to the DB-instance intallation . directory.
    - copied generated init<SID>.ora to the <ORACLE_HOME>\database
    e) Resumed SAPINST.
    David Byrne in a previous post suggested: "check your oracle alert file in case there are errors there you may need to update the word size for the 64bit install. Errors like this in the oracle alert file would suggest that.,
    ORA-12012
    ORA-06544: PL/SQL: internal error, arguments: [ORA-06544: PL/SQL: internal error, arguments: 56319], [, ], [, ], [, ], [
    ORA-06553"
    Well, I am getting ORA-06553: PLS-801: internal error [56319] but then my edited CONTROL.SQL (which is mainly a CREATE CONTROLFILE as it would be obtained with a ...BACKUP CONTROLFILE TO TRACE) includes at the end this:
    shutdown immediate
    startup upgrade
    spool utlirp.log
    @?/rdbms/admin/utlirp.sql
    spool off
    Shutdown immediate
    Startup
    Spool utlrp.log
    @?/rdbms/admin/utlrp.sql
    Spool off
    exit
    which is supposed to do just that... (I think)
    Help, anyone?

    > Trying to cheer me up, are you?
    No
    > It is NOT free that reorganization! Quite expensive, actually, paid for in time! But you're right... the database needed a reorg anyway :-\
    True, not "free" - it takes time but the data will be nicely aligned then
    > And why would I have to reconfigure all those 10.2 features? Everything's either in the database or init<sid>.ora, ain't it? And my database is a pretty 10.2.0.4 with all those nice features already activated...
    No - not really auotmatically if you upgraded from 9.2 And "init<SID>.ora" is past, you nowadays use "spfile" If, of course, e. g. Automatic Undo was activated in 9.2 then it's there of course in 10.2 too.
    > One sticky point... I haven't really read the r3load procedure yet and I will before I import, but... I would say I don't have to do anything about the 32->64 bit, right? I mean, it should behave properly while reloading on 64-bit...
    The exported content is about 10 % of the size of the system, it's database and OS independent so yes, you can import it nicely on 32bit. Another tip: make sure you don't just use the default configurations for R3load, it will take a HUGE amount of time. Use the package splitter (builtin-in in sapinst) so you get a much higher parallelism when importing.
    Markus

  • PMON process and ORACLE Instance  - Cannot allocate log. Archival required

    Hello there,
    We are running Oracle RAC (9i) database with two nodes and Oracle Applications 11i.The operatiing system is solaris 5.8.
    1.Recently while bouncing the db, i happen to see many PMON process get started up? is it a normal thing to see those process? what is actually happening?
    oracle 14125 1 1 05:02:36 ? 18:46 ora_p007_CMWPROD1
    oracle 14123 1 1 05:02:36 ? 21:33 ora_p006_CMWPROD1
    oracle 14117 1 3 05:02:34 ? 30:58 ora_p003_CMWPROD1
    oracle 14121 1 1 05:02:35 ? 18:56 ora_p005_CMWPROD1
    oracle 5230 1 0 21:45:54 ? 0:11 ora_qmn0_CMWPROD1
    oracle 5192 1 0 21:45:09 ? 0:07 ora_pmon_CMWPROD1
    oracle 5194 1 0 21:45:09 ? 1:37 ora_diag_CMWPROD1
    oracle 5196 1 0 21:45:09 ? 0:48 ora_lmon_CMWPROD1
    oracle 5198 1 0 21:45:09 ? 2:15 ora_lmd0_CMWPROD1
    oracle 5200 1 0 21:45:12 ? 7:51 ora_lms0_CMWPROD1
    oracle 5202 1 0 21:45:13 ? 7:59 ora_lms1_CMWPROD1
    oracle 5204 1 0 21:45:13 ? 0:06 ora_dbw0_CMWPROD1
    oracle 5206 1 0 21:45:13 ? 0:17 ora_lgwr_CMWPROD1
    oracle 5208 1 0 21:45:13 ? 0:53 ora_ckpt_CMWPROD1
    oracle 5210 1 0 21:45:13 ? 0:11 ora_smon_CMWPROD1
    oracle 5212 1 0 21:45:13 ? 0:00 ora_reco_CMWPROD1
    oracle 5214 1 0 21:45:13 ? 0:06 ora_cjq0_CMWPROD1
    oracle 5218 1 0 21:45:13 ? 0:00 ora_arc0_CMWPROD1
    oracle 5220 1 0 21:45:13 ? 0:05 ora_arc1_CMWPROD1
    oracle 5223 1 0 21:45:17 ? 0:17 ora_lck0_CMWPROD1
    oracle 14113 1 1 05:02:33 ? 5:30 ora_p002_CMWPROD1
    oracle 14109 1 0 05:02:33 ? 5:14 ora_p000_CMWPROD1
    oracle 14119 1 1 05:02:34 ? 21:03 ora_p004_CMWPROD1
    oracle 14111 1 1 05:02:33 ? 6:12 ora_p001_CMWPROD1
    2.We happen to see some notifications like
    "Oracle instance <xxx> - cannot allocate log -Archival required" in the alert log file and could see many log switches in a second in archival destination.
    we have three members of log groups (two in each group) in one node and same on the other. Should we have to increase log_buffer_size or addition of redo log files is required?
    the error messages:
    ORACLE Instance xxxx - Can not allocate log, archival required
    ARCH: Connecting to console port...
    Thread 2 cannot allocate new log, sequence 55487
    All online logs needed archiving
    Current log# 12 seq# 55486 mem# 0: /dev/vx/rdsk/racdg/log12a
    Current log# 12 seq# 55486 mem# 1: /dev/vx/rdsk/racdg/log12b
    Fri Oct 10 21:47:45 2008
    Completed checkpoint up to RBA [0xd8be.2.10], SCN: 0x0000.e6dcbc2a
    Fri Oct 10 21:47:49 2008
    ARC0: Completed archiving log 7 thread 2 sequence 55482
    ARC0: Evaluating archive log 10 thread 2 sequence 55480
    ARC0: Unable to archive log 10 thread 2 sequence 55480
    Log actively being archived by another process
    ARC0: Evaluating archive log 9 thread 2 sequence 55483
    ARC0: Beginning to archive log 9 thread 2 sequence 55483
    Any suggestions to overcome these errors would be helpful.
    Thanks,
    Balu.

    Tux Dueñas wrote:
    Bueno.
    A nosotros nos apasado el error de que no se puede guardar los archive logs por falta de espacio en Disco. Eso pasa cuando algun proceso genera demasiadas ransacciones que necesitan ser escritas en los logs. Por esa razon se genera mucho archive log y se llena el espacio en disco.
    Borra los archivelog mas viejos, y que ya los tengas en un backup y asi no habra problema te recomiendo tener un espacio en disco minimo de 50%I hope this is what you meant,
    >
    We apas the error that you can not save the archive logs for lack of space on disk. That happens when any process that generates too many ransacciones need to be written in the logs. For that reason much archive log is generated and fills the space.
    Removes archivelog older, and those who already have a backup and there will be no problem so I recommend you have a disk space minimum of 50%
    >
    This is an international forum so to spread your message as far as possible, use a more universal language, English for example can be a good choice.
    Cheers
    Aman....

  • Down Time for  Installing APEX 4.2.1 and oracle HTTP server?

    Hi, all:
    I plan to install APEX 4.2.1 and oracle HTTP server on 10.2.0.4 database.
    Is there any down time required during installation?
    I mean during installation, do I need to block users from accessing the database?
    Can they do their normal data entry / inquiry?
    thanks,
    John
    ps. There will be server backup before installation.

    Hi,
    Documentation says
    >
    3.1 Recommended Pre-installation Tasks
    Before installing Oracle Application Express, Oracle recommends that you complete the following steps:
    Review and satisfy all Oracle Application Express installation requirements. See "Oracle Application Express Installation Requirements".
    Shut down with normal or immediate priority the Oracle Database instances where you plan to install Oracle Application Express. On Oracle Real Application Clusters (Oracle RAC) systems, shut down all instances on each node.
    An alternative to shutting down the database is to prevent all users from accessing Oracle Application Express when upgrading your installation from a previous release of Oracle Application Express. Oracle only recommends this option in high availability production environments where planned outages are not available. For all other scenarios, the database should be shut down.
    To disable access to Oracle Application Express when the existing installation is using the Application Express Listener, shut down the appropriate application server where the Application Express listener is deployed.
    To disable user access to Oracle Application Express when the existing installation is using the Oracle HTTP Server with mod_plsql, you should either shut down the Web server or disable the Application Express Database Access Descriptor of the Web server.
    For an existing installation using the embedded PL/SQL gateway, you should disable the Oracle XML DB Protocol Server by setting the HTTP port to 0. This can be accomplished by starting SQL*Plus, connecting as SYS to the database where Oracle Application Express is installed, and running:
    EXEC DBMS_XDB.SETHTTPPORT(0);
    Once you have prevented access from Oracle Application Express users, you should log into SQL*Plus as SYS, connecting to the database where Oracle Application Express is installed, and query V$SESSION to ensure there are no long running sessions which would interfere with the upgrade process.
    Back up the Oracle Database installation.
    Oracle recommends that you create a backup of the current Oracle Database installation before you install Oracle Application Express. You can use Oracle Database Recovery Manager, which is included in the Oracle Database installation, to perform the backup.
    See Also:
    Oracle Database Backup and Recovery User's Guide
    Start the Oracle Database instance that contains the target database.
    After backing up the system, you must start the Oracle instance that contains the target Oracle database. Do not start other processes such as a Web Listener. However, if you are performing a remote installation, make sure the database listener for the remote database has started.
    >
    Regards,
    Jari
    My Blog: http://dbswh.webhop.net/htmldb/f?p=BLOG:HOME:0
    Twitter: http://www.twitter.com/jariolai

Maybe you are looking for